Discovery Call Analysis Framework
Creating a Continuous Feedback Loop Between PM and Client
Core Philosophy
"Diagnose before prescribing" - Every interaction should deepen our understanding of the client's real needs, not just their stated wants. This SOP creates a systematic feedback loop ensuring nothing gets lost between sales and delivery.
The Discovery Analysis Framework
Phase 1: Immediate Post-Call Analysis (Within 2 Hours)
Sales Team Completes Discovery Debrief Form
Section A: What They Said They Want
- Stated features/requirements
- Explicit timeline
- Declared budget
- Mentioned competitors
Section B: What They Actually Need (Reading Between Lines)
- Real business problem
- Unspoken fears/concerns
- Hidden stakeholders
- Success metrics they didn't mention
Section C: Strategic Opportunities We See
- Features they don't know they need
- Market advantages we could provide
- Risks they haven't considered
- Growth accelerators
Section D: Concerns & Watch-outs
- Potential scope creep areas
- Unrealistic expectations
- Technical debt or dependencies
- Organizational readiness
The 2-Hour Rule
Send internal debrief to PM team within 2 hours while memory is fresh. Include:
- Call recording link
- Completed framework above
- Recommended approach (which of the 3 tiers fits best)
- Any "gut feelings" about the client
Phase 2: Pre-Proposal PM Review (Within 24 Hours)
PM Reviews and Adds Technical Lens
Technical Feasibility Check
- Stated requirements achievable in timeline?
- Any technical red flags not caught in sales?
- Integration complexity assessment
- Scalability considerations
Resource Planning Preview
- Ideal team composition
- Potential bottlenecks
- Skills gaps to address
- Timeline reality check
PM Feedback to Sales
- "This will actually take X weeks, not Y"
- "They'll also need Z to make this work"
- "Watch out for [specific technical risk]"
- "Consider adding [strategic technical element]"
Phase 3: Client Feedback Loops During Project
Week 1: Alignment Check
PM leads a "Discovery Validation" call with client
Script Opening:
"Now that we're diving deep into your project, I want to validate some assumptions from our initial conversations and make sure we're building exactly what will drive your success."
Key Questions:
- "Has anything changed since our initial conversation?"
- "Now that you've had time to think, what concerns you most?"
- "What would make you say 'wow' when we deliver?"
- "What haven't we asked about that we should know?"
Bi-Weekly: Strategic Check-ins
Format: 30-minute calls led by PM with structured agenda:
- Progress Update (5 min)
- What we've completed
- What we learned
- What's next
- Discovery Insights (10 min)
"As we've been building, we discovered [insight]. This made us think you might also benefit from [suggestion]."
- Priority Validation (10 min)
"Given what we now know, should we adjust our priorities?"
- Success Metrics Check (5 min)
"You mentioned [original success metric]. Is this still how you'll measure success?"
The Hidden Agenda Questions
Weave these into natural conversation:
- "Who else has gotten involved since we started?"
- "How is [stakeholder] feeling about progress?"
- "What's your biggest worry right now?"
- "If you could change one thing about our approach, what would it be?"
Phase 4: Post-Mortem Analysis
End of Each Sprint/Milestone
PM Documents:
- What we discovered vs. what sales understood
- Scope creep attempts and how handled
- Stakeholder dynamics evolution
- Budget pressure points
- Success metric changes
Sales Reviews PM Notes and Updates:
- Qualification criteria refinements
- New discovery questions needed
- Proposal framework adjustments
- Pricing model insights
The Feedback Loop Tools
1. Discovery-to-Delivery Handoff Template
markdown## Client: [Name]
## Project: [Name]
## Sales Lead: [Name] | PM: [Name]
### What We Sold
- [Bullet points of proposal commitments]
### What They Really Want
- [Deeper needs discovered]
### Watch-Out Areas
- [Potential problems]
### Suggested Approach Modifications
- [PM recommendations]
### Key Relationships
- Champion: [Name/Role]
- Skeptic: [Name/Role]
- Hidden Influencer: [Name/Role]
2. Weekly Evolution Tracker
| Week | Original Understanding | New Discovery | Impact | Action |
|---|---|---|---|---|
| 1 | Wanted simple marketplace | Needs complex matching algo | +20% scope | Discuss in next check-in |
| 2 | 3 user types | Actually 5 with sub-roles | +1 week | Approved by client |
3. Client Insight Repository
Build a searchable database of:
- "They said X but meant Y" examples
- Common discovery gaps by industry
- Technical surprises by platform
- Stakeholder dynamics patterns
Scripts for Difficult Conversations
When Scope Has Crept Beyond Recognition
"I want to revisit our original conversation. You came to us wanting [original need], and we're now building [current scope]. This evolution is natural, but it impacts timeline and investment. Let's align on whether we adjust the vision or the budget."
When New Stakeholders Appear
"I notice [new person] has joined our conversations. Help me understand their role and what success looks like from their perspective. I want to ensure we're building something that works for everyone."
When Success Metrics Change
"In our discovery, you mentioned [original metric] was crucial. You're now focusing on [new metric]. Both are valid, but they lead to different product decisions. Which should be our North Star?"
Continuous Improvement Process
Monthly Discovery Accuracy Review
Calculate:
- Discovery Accuracy Rate = (Delivered Scope / Original Understanding) x 100
- Target: 85%+ accuracy
If Below Target, Examine:
- Which questions weren't asked?
- What assumptions were made?
- Where did scope evolve most?
- What patterns emerge?
Quarterly Calibration Session
Sales + PM Team Meeting Agenda:
- Review top 3 scope evolution examples
- Identify missing discovery questions
- Update qualification criteria
- Refine handoff process
- Practice new questioning techniques
The PM's Discovery Mindset
You Are Not Just Building, You're Still Discovering
Every sprint reveals new information. Your job is to:
- Listen for what's not being said
- Watch for stakeholder dynamics shifts
- Question new requirements against original goals
- Document everything for future learning
- Communicate insights back to sales continuously
Remember Blair Enns:
"The answer to every problem is contained in the problem itself. Keep asking questions until the solution becomes obvious."
KPIs for This Framework
- Scope Creep Percentage: Target <15%
- Client Surprise Events: Target <1 per project
- Mid-Project Pivots: Target <10%
This framework ensures that discovery isn't a one-time event but a continuous process that makes every project more successful than the last.