Technical Discovery and Customer Communication
Run useful customer conversations, design decisive evaluations, and communicate tradeoffs across technical and executive audiences.
Opening discovery and following the evidence
Structure a focused discovery call
Stakeholders, champions, and constraints
Map technical and business decision owners
Success criteria and a PoC that ends in a decision
Translate aspirations into measurable criteria
Technical objections, uncertainty, and difficult conversations
Classify objections by underlying concern
Whiteboards and executive communication
Draw readable request and failure paths
Run a simulated discovery meeting
A fictional SaaS CTO says: We need better performance and security before enterprise expansion. The operations lead worries about migration risk and the finance lead wants predictable cost.
Work through the problem
- Open with an agenda and confirm the desired decision.
- Ask about affected journeys, architecture, evidence, and constraints.
- Map stakeholders and surface conflicting priorities.
- Summarize the problem and propose a bounded PoC with success criteria.
- Give a two-minute technical recap and a 45-second executive recap.
Deliverables
- Discovery notes separating facts and hypotheses
- Stakeholder map
- PoC charter with measurable criteria
Self-review rubric
- Questions follow customer answers
- Symptoms are not treated as causes
- Criteria include usability and rollback
- Recap names owners and next evidence
Compare with the worked approach
A strong meeting establishes which user journeys are slow, where abuse occurs, what baseline exists, and who can approve changes. It does not immediately prescribe a platform migration. The PoC might cover one public endpoint and one protected administrative application, with explicit performance, access, operational, and cost observations. Close by asking whether the summary accurately captures the customer priorities.