You’ve done 10 interviews. You have 50 pages of notes. Now what? Most consultants write rambling reports no one reads. Here’s the formula for a diagnostic report that’s clear, actionable, and sets you up perfectly for the next phase.
The Report No One Will Read
You’ve finished discovery.
Ten interviews. Hours of conversations. Fifty pages of notes. Insights everywhere.
Now you need to write the diagnostic report.
So you sit down at your computer and start typing.
“Executive Summary: Following comprehensive stakeholder interviews and extensive document review, we have identified several key areas of concern that require immediate attention…”
You write for three days. Twelve pages. Detailed findings. Thorough analysis. Every insight you gathered.
You send it to the client.
Subject: Diagnostic Report – Please Review
They respond: “Thanks! I’ll take a look.”
Translation: This is going in a folder labeled “To Read Someday” and will never be opened again.
Here’s the brutal truth:
Nobody reads long reports. Not your client. Not their team. Nobody.
They skim the first page. Maybe.
If you’re lucky, they jump to “Recommendations” at the end and just read that.
Which means you wasted three days writing something that won’t get read, understood, or acted upon.
I’ve made this mistake. Multiple times.
Then I learned: The best diagnostic report isn’t the most thorough. It’s the most readable.
Today, I’m showing you the formula.
Why Most Diagnostic Reports Fail
Let me show you what goes wrong:
Mistake #1: Too Long
You think more pages = more value.
Wrong.
More pages = less likely to be read.
A 12-page report takes 45 minutes to read. They don’t have 45 minutes.
A 3-page report takes 10 minutes. They’ll actually read it.
Keep it short. Force yourself to be concise.
Mistake #2: Buried Findings
Your report structure:
- Page 1: Background and methodology
- Page 2: Overview of interviews conducted
- Page 3-8: Detailed findings
- Page 9-10: Analysis
- Page 11-12: Recommendations
The actual insights don’t appear until page 3.
They never get there.
Lead with findings. Background goes at the end.
Mistake #3: No Clear Action Items
You describe problems beautifully. You explain root causes thoroughly.
But you don’t tell them what to do about it.
So they read your report and think: “Okay… now what?”
Every finding needs a recommended action.
Mistake #4: Death by Bullet Points
Your report is 47 bullet points of findings.
All equal weight. No prioritization. No hierarchy.
They read the first 10 and their eyes glaze over.
Three to five major findings. That’s it. Everything else is supporting detail.
The Diagnostic Report Formula That Works
Here’s the structure that gets read, understood, and acted upon:
SECTION 1: Executive Summary (1 Page Max)
This is the ONLY section guaranteed to be read. Make it count.
Subsection A: The Situation (2-3 sentences)
“Over the past two weeks, I conducted interviews with 10 stakeholders across [departments/roles] and reviewed [key documents]. The goal was to diagnose why [problem they hired you to solve] is happening and identify the root causes.”
Keep it factual. Don’t editorialize yet.
Subsection B: What I Found (3-5 bullets)
State your major findings clearly. One sentence each.
“Here’s what I learned:
- The primary issue isn’t [what they thought it was], it’s [what it actually is].
- This is costing approximately [$XXX,XXX] annually in [lost revenue/wasted costs/opportunity cost].
- Root cause: [The fundamental problem beneath the symptoms].
- Quick wins are available in [area 1] and [area 2].
- If unaddressed, this will get worse as [the company scales/market changes/etc.].”
Notice:
- You’ve reframed their understanding (it’s not what they thought)
- You’ve quantified the cost (business case for action)
- You’ve identified root cause (not just symptoms)
- You’ve flagged quick wins (early momentum)
- You’ve created urgency (it will get worse)
Subsection C: What’s Next (2-3 sentences)
“Based on these findings, I recommend a three-phase approach: [Phase 1 focus], [Phase 2 focus], [Phase 3 focus]. The attached report provides details on each finding and recommended actions. I’ll walk through this in our [meeting date] discussion.”
Set expectations. Tell them what to do with this report.
Why this works:
If they read NOTHING else, they have:
- The core problem
- The cost
- The recommendation
That’s enough to move forward.
SECTION 2: Key Findings (1-2 Pages)
Now you elaborate. But still keep it tight.
For each major finding (3-5 max), use this structure:
FINDING #1: [Clear Statement of Problem]
Example: “Teams don’t have a clear prioritization framework, leading to scope creep and project delays.”
The Evidence:
- 8 out of 10 interviewees mentioned “changing priorities” as a top frustration
- Review of last 12 projects showed 9 experienced scope changes mid-project
- Average delay: 4-6 weeks per project
The Impact:
- 12 projects delayed per year
- Average cost per delay: $60,000 (lost market timing + rework)
- Annual cost: ~$720,000
Root Cause:
Leadership hasn’t established criteria for what gets prioritized vs. what gets deferred. Everything is treated as equally important, so teams try to do everything and succeed at nothing.
What’s Been Tried:
A change request process was implemented in 2023 but failed because leadership bypassed it whenever they wanted. It wasn’t mandatory—just a suggestion.
Recommended Action:
Establish a formal prioritization framework with leadership buy-in and enforcement. This includes:
- Clear criteria for prioritizing initiatives (customer impact, revenue potential, strategic alignment)
- Mandatory review process for any mid-project scope changes
- Quarterly priority setting with leadership team
Expected outcome: 50% reduction in project delays, $360K annual savings
That’s the template for each finding.
Notice what you included:
- Clear problem statement (no ambiguity)
- Evidence (not just your opinion)
- Quantified impact (dollar cost)
- Root cause (why this is happening)
- What’s been tried (shows you did your homework)
- Specific recommendation (actionable)
- Expected outcome (ROI)
Repeat this for your 3-5 major findings.
SECTION 3: Quick Wins (1/2 Page)
These are small fixes that can be implemented immediately while you work on bigger solutions.
Example:
QUICK WIN #1: Clarify Project Ownership
Problem: 6 out of 10 interviewees couldn’t name who owns which cross-departmental projects.
Fix: Create a simple one-page “Project Ownership” document listing all active projects and their owners. Distribute to all teams.
Time to implement: 1 week
Impact: Immediate reduction in “who’s responsible for this?” confusion
QUICK WIN #2: Weekly Standup for Department Heads
Problem: Departments operate in silos with minimal coordination.
Fix: Institute a 30-minute weekly standup for all department heads to share updates and flag dependencies.
Time to implement: 1 week
Impact: Earlier identification of conflicts and bottlenecks
Why quick wins matter:
✓ They build momentum and trust
✓ They show immediate value from your work
✓ They make the bigger recommendations easier to accept
Include 2-4 quick wins. No more.
SECTION 4: Next Steps (1/4 Page)
Tell them exactly what happens next.
Example:
NEXT STEPS:
- Review this report before our [date] meeting
- Come to the meeting prepared to discuss: • Which findings resonate most • Any findings that surprise you or you disagree with • Which quick wins to implement first
- In the meeting, I’ll present a proposed solution design addressing the top 3 findings
- Assuming alignment, we’ll move into Phase 2: Solution Design & Planning
Timeline: • [Date]: Findings presentation meeting • Date range: Solution design phase • Date range: Implementation phase
Why this works:
✓ Clear expectations
✓ Specific actions for them to take
✓ Visible path forward
✓ No ambiguity about what comes next
SECTION 5: Appendix (Optional – As Needed)
This is where extra detail goes IF they want it.
Include:
- Full list of interviewees
- Interview methodology
- Complete data/metrics
- Supporting documents
- Detailed process maps (if relevant)
Most people won’t read this. That’s fine.
It’s there if they need to go deeper or share with stakeholders.
The Complete Template (Copy This)
Here’s the exact structure you can follow:
[YOUR NAME] – DIAGNOSTIC REPORT
[Client Company] – [Project Name]
[Date]
EXECUTIVE SUMMARY
The Situation:
Over the past [timeframe], I conducted interviews with [X] stakeholders and reviewed [documents]. The goal was to diagnose why [problem] is happening and identify root causes.
What I Found:
- The primary issue isn’t [what they thought], it’s [what it actually is]
- This is costing approximately [$XXX,XXX] annually
- Root cause: [The fundamental problem]
- Quick wins are available in [areas]
- If unaddressed, this will [consequence]
What’s Next:
Based on these findings, I recommend a [X]-phase approach: [brief overview]. Details below. I’ll walk through this in our [date] meeting.
KEY FINDINGS
FINDING #1: [Problem Statement]
Evidence:
- [Data point]
- [Data point]
- [Data point]
Impact:
- [Quantified cost/consequence]
Root Cause: [Why this is happening]
What’s Been Tried: [Previous attempts and why they failed]
Recommended Action: [Specific steps to fix this]
Expected Outcome: [ROI/improvement metrics]
[Repeat for Findings #2-5]
QUICK WINS
QUICK WIN #1: [Name]
Problem: [Brief description]
Fix: [Specific action]
Time to implement: [Timeline]
Impact: [Expected benefit]
[Repeat for Quick Wins #2-4]
NEXT STEPS
- Review this report before our [date] meeting
- Come prepared to discuss [topics]
- In the meeting, I’ll present [what you’ll cover]
- Assuming alignment, we’ll move into [next phase]
Timeline:
- [Date]: Findings presentation
- Date range: Solution design
APPENDIX (Optional)
[Additional detail as needed]
Total length: 4-5 pages (not including appendix)
How to Present the Report
Don’t just email it and hope they read it.
Schedule a presentation meeting (60 minutes):
The Presentation Flow:
Opening (5 minutes):
“Thanks for making time. Over the past two weeks, I’ve talked to 10 people and reviewed your processes. Today I’m going to walk you through what I found, the cost of these issues, and what I recommend we do about it. I’ve sent you the report, but I’ll cover the highlights here.”
Findings (30 minutes):
Walk through each finding. One at a time.
For each:
- State the problem clearly
- Show the evidence (quote from interviews, data)
- Quantify the cost
- Explain root cause
- Get their reaction (“Does this resonate? Are you surprised by this?”)
Let them talk. This is a dialogue, not a lecture.
Quick Wins (10 minutes):
“Before we talk about the bigger solution, here are some quick wins we can implement in the next 1-2 weeks…”
Get their buy-in on which ones to prioritize.
Next Steps (10 minutes):
“Based on what we’ve discussed, here’s what I recommend for Phase 2…”
Outline your proposed approach.
Get agreement to move forward.
Q&A (5 minutes):
“Questions? Concerns? Anything you disagree with?”
Why presenting matters:
✓ You control the narrative (they don’t misinterpret written findings)
✓ You gauge their reaction in real-time
✓ You build alignment before moving to solutions
✓ You demonstrate expertise through explanation
The report is a reference document. The presentation is where the real work happens.
Common Diagnostic Report Mistakes (And How to Avoid Them)
Mistake #1: Making It About You
Bad: “I interviewed 10 people and spent 20 hours analyzing…”
Good: “Here’s what I learned about your business…”
Nobody cares how hard you worked. They care what you found.
Mistake #2: Overwhelming Them
Bad: “I identified 47 issues that need to be addressed…”
Good: “Three major issues are driving most of your problems…”
Focus. Prioritize. Simplify.
Mistake #3: No Clear Recommendations
Bad: “Communication is a problem. Multiple interviewees mentioned this.”
Good: “Communication breaks down because there’s no clear escalation process. Recommendation: Implement a 3-tier escalation framework. Expected impact: 40% reduction in miscommunication delays.”
Every problem needs a solution.
Mistake #4: Hiding Behind Jargon
Bad: “Leveraging synergistic cross-functional alignment paradigms…”
Good: “Getting departments to actually talk to each other…”
Speak like a human. Clarity beats sophistication.
The Metrics That Matter
Your diagnostic report should answer:
✅ What’s broken? (Clear problem statement)
✅ How much is it costing? (Quantified impact)
✅ Why is it broken? (Root cause, not just symptom)
✅ What should we do? (Specific recommendations)
✅ What will that accomplish? (Expected outcomes/ROI)
If your report answers all five, you nailed it.
What Success Looks Like
After you present your diagnostic report, the client should:
✓ Understand the problems clearly (no confusion)
✓ Agree with your findings (validation from their team)
✓ See the cost of inaction (urgency to move forward)
✓ Trust your recommendations (confidence in your expertise)
✓ Be ready to move to Phase 2 (solutions design)
If they’re saying “This is exactly what we needed” or “This makes so much sense” or “When can we start Phase 2?”—you crushed it.
Your Diagnostic Report Checklist
Before writing:
- Organize all interview notes
- Identify patterns (3-5 major findings)
- Quantify impact for each finding
- Identify root causes (not just symptoms)
- List quick wins (2-4 items)
- Draft recommendations for each finding
While writing:
- Keep Executive Summary to 1 page max
- Limit to 3-5 major findings (not 20)
- Include evidence for each finding
- Quantify cost/impact with numbers
- Provide specific recommendations
- Include expected outcomes/ROI
- Add 2-4 quick wins
- Make next steps crystal clear
- Keep total report to 4-5 pages
Before sending:
- Read it out loud (does it flow?)
- Remove jargon (could a non-expert understand it?)
- Check that every finding has a recommendation
- Verify all numbers/data points
- Schedule presentation meeting
- Send report 24 hours before meeting
Talk Tomorrow
Tomorrow, we’re talking about how to transition from discovery to solution design—presenting your approach and getting buy-in for the work ahead.
Hit reply and tell me: Have you ever written a report that got ignored? What happened? Did it get read? Did they act on it?
I want to know if this is where you’re losing momentum.
And if you know a consultant who’s drowning in interview notes and doesn’t know how to turn them into a report, forward this to them. Structure is everything.
— Bob
P.S. That quantification piece—putting dollar amounts on every finding—is what transforms your report from “interesting insights” to “we need to act on this now.” Always. Quantify. Everything.
