Discovery Architecture

The SD track teaches you the 3-Layer Model: Situation questions establish context, Problem questions expose pain, Implication questions attach dollar signs to that pain. At the 101 level, you run that model in a single discovery call. At the enterprise level, you run it across multiple meetings with multiple stakeholders over multiple weeks. That is discovery architecture — the deliberate sequencing of discovery conversations across the buying committee to build a complete picture of the account's pain, priorities, and decision criteria.

Enterprise discovery is not one meeting. It is a campaign. Each conversation has a specific objective, targets a specific stakeholder, and feeds intelligence into the next conversation. The discovery with the technical evaluator informs the questions you ask the economic buyer. The discovery with the end user reveals pain points the champion did not mention. The discovery with the detractor tells you exactly what objections will surface in the final presentation.

1. Phase 1: Champion Discovery Start with your champion. Run the full 3-Layer Model — situation, problem, implication. Your champion gives you the internal language, the political landscape, and the pain points that will resonate with the economic buyer. This is your foundation conversation. Every subsequent discovery builds on what you learn here. Ask the champion: who else needs to be convinced, what has failed before, and what would make this a career win for them personally.
2. Phase 2: Technical Validation Move to the technical evaluator. Use SD discovery questions focused on current architecture, integration requirements, and performance criteria. The technical evaluator will tell you things the champion does not know — infrastructure constraints, security requirements, data migration complexities. Feed these back into your competitive positioning matrix. Where does the technical evaluation create an advantage or a risk against each alternative?
3. Phase 3: Economic Framing The economic buyer conversation is the culmination. By now you know the technical requirements, the champion's priorities, and the competitive landscape. Your SD implication questions should translate everything into financial impact. "Your team spends 340 hours per quarter on manual reconciliation — at loaded cost, that is $127,000 per quarter in labor alone." Dollar signs. Always dollar signs. The economic buyer does not care about features. The economic buyer cares about outcomes measured in currency.