Note Capture & Normalization
Purpose
This step preserves truth.
The goal is to:
- Capture exactly what was said
- Avoid premature summarization
- Create a clean bridge from raw conversations to structured analysis
High-level summaries are not enough. Direct quotes matter.
Raw Capture
What Must Be Captured
| Artifact | Requirement |
|---|---|
| Full audio | Entire interview |
| Verbatim transcript | Word-for-word, unedited |
| Speaker attribution | Who said what |
| Timestamping | Optional but helpful |
Do not rely on memory or post-hoc notes.
Recommended Tooling
| Tool | Why |
|---|---|
| Granola | Records off local audio driver; no third bot |
| Native platform recording | Acceptable fallback |
| External note-taker bots | Avoid if possible |
Granola is preferred because it is invisible to the meeting and produces clean transcripts.
Recording Hygiene
Always:
- Inform participants the meeting is being recorded
- State purpose clearly: internal analysis and synthesis
- Confirm comfort before proceeding
This builds trust and avoids downstream issues.
Why Raw Transcripts Matter
| Reason | Impact |
|---|---|
| Exact language | Reveals real pain |
| Direct quotes | High credibility in exec readouts |
| Avoids bias | Prevents over-interpretation |
| Cross-validation | Confirms themes across interviews |
Executive decks land harder when they include:
"We spend more time validating data than using it."
That power is lost in summaries.
Post-Interview Processing
Within 24 hours of the interview:
| Step | Action |
|---|---|
| Store transcript | Central shared location |
| Label file | Function + name + date |
| Flag quotes | Highlight strong language |
| Add context | Note tone and emphasis |
Do not wait until synthesis week.
Normalization Framework
Every interview is normalized into the same structure.
Normalized Note Template
| Section | What Goes Here |
|---|---|
| Role & scope | Accountability and decisions |
| Core workflows | Repeated or manual work |
| Pain points | Friction, failures, delays |
| Systems & data | Tools, SoR vs SoT |
| Reporting and latency | Freshness, mismatches |
| Constraints | Security, policy, risk |
| Desired outcomes | What "better" means |
| Notable quotes | Verbatim excerpts |
This structure mirrors the interview framework.
Quotes Handling
Guidelines:
- Use exact wording
- Preserve context
- Avoid paraphrasing
- Attribute by role, not name in deliverables
Example:
"We don't trust the number until we've checked it three times." (Finance)
AI Assistance
AI may be used to:
- Segment transcripts by topic
- Suggest candidate quotes
- Flag repeated phrases
AI may not:
- Replace raw transcripts
- Rewrite quotes
- Decide what matters
Output of This Step
| Output | Used For |
|---|---|
| Raw transcripts | Evidence |
| Normalized notes | Analysis |
| Quote bank | Executive deck |
| Observation list | Opportunity framing |
If normalization feels tedious, it's working. This is where rigor is established.
Next step is Opportunity Identification, where normalized notes become scorable inputs.