Some discovery phases are sales exercises with a research vocabulary.
A supplier charges for workshops, confirms what the client already knows and recommends the platform it was positioned to sell. Scepticism is earned when the investigation has only one possible conclusion.
Good discovery is a bounded effort to reduce consequential uncertainty before a larger commitment. It should be valuable if the client appoints another supplier, changes direction or stops.
Discovery begins with a decision
“Understand the organisation” is too broad. Name the decision the work must support:
- Should this platform be retained, improved or replaced?
- Which client journey is causing commercial loss?
- What content and integration complexity will shape migration?
- Which service pattern should a portal support?
- Is the apparent technology problem mainly process or ownership?
Define scope, evidence, stakeholders, exclusions and the point at which the client will decide. Proportion discovery to investment and risk. A contained site change may need a short investigation; a regulated platform and data migration will require deeper research and assurance.
Four useful outputs
A tested problem statement
State who is affected, what happens, the consequence and evidence. Distinguish symptom from cause and record important disagreement.
An evidence base
Show interviews, analytics, journey observation, system and content samples, operational data, constraints and data-quality limits. Protect confidential information and collect only what the question requires.
Options with trade-offs
Set out credible routes, including improve, defer or stop where appropriate. Compare outcome, cost range, risk, dependency, internal capacity and uncertainty. Explain the recommendation.
A usable next brief
The client should be able to brief a board, procurement or delivery team without paying the discovery supplier to translate its own report. Include requirements and measures at the depth supported by evidence.
A long deck is not proof of depth. A concise recommendation without traceable evidence is equally weak.
Requirements are one part, rather than the starting assumption
Requirements gathering assumes the team understands the problem and needs to specify a response. Discovery can challenge that premise.
The source describes an accountancy website rebuild allegedly running 70% over budget and requiring £180,000 of rethinking because an enquiry-to-onboarding handoff emerged late. It also says about two-thirds of Distinction briefs describe a symptom. Those figures and the client case need engagement records and permission.
The mechanism is worth preserving: a team optimised to build “a new website” may struggle to pivot when the actual constraint crosses website, CRM and onboarding operations.
Discovery cannot eliminate surprise. It improves which assumptions are explicit and which risks are tested before commitment.
The client is part of the research system
Relevant people need availability and authority. Existing documentation, previous failures, budget constraints and internal disagreement can change the recommendation.
Clients should not disclose information beyond scope or ignore security and confidentiality. Access needs an approved, least-privilege route.
The client also needs willingness to be surprised. A discovery commissioned solely to validate a chosen platform should be described accurately as due diligence or implementation planning. Otherwise the supplier is rewarded for telling stakeholders what they already decided.
Supplier independence matters. Ask how commercial interests are disclosed, whether recommendations include routes the supplier cannot deliver and whether the output is portable.
Test the quality without demanding surprise theatre
The source offers three tests and says every worthwhile discovery should surprise the client. Insight is valuable, but manufactured surprise is not a quality standard.
Ask instead:
- Is the problem clearer and supported by evidence?
- Which important assumption changed, held or remains uncertain?
- Are options and trade-offs visible?
- Can an independent capable team use the output?
- Did the work change a decision, confidence or scope?
- Are limits and dissent recorded?
A discovery may confirm the original diagnosis after testing it. That can still be worth the investment when the evidence reduces a material risk.
Recognise the sales exercise
Warning signs include:
- The recommended product appears in the scope before the problem is tested
- Every interview question leads towards one supplier capability
- Client evidence is summarised without access to the basis
- No option includes retaining the current estate or using another partner
- The report ends in a proposal and cannot stand alone
- Price, risk and internal effort remain vague
- Findings sound equally applicable to every client
Commercial follow-on is legitimate. The problem is concealing it inside supposedly independent diagnosis.
Price the avoided uncertainty carefully
The source says mid-delivery correction is always more expensive and uses £30,000, £50,000 and £500,000 examples. Avoid universal arithmetic.
Discovery itself can be excessive, repeat known work or delay urgent action. Compare its cost with the uncertainty, reversibility and consequence of getting the next decision wrong.
Some action can begin while research continues, particularly a safe repair or access issue. Other decisions should wait for content, data, user or regulatory evidence.
A discovery brief a buyer can inspect
Before appointment, require:
- Decision and intended users
- Questions and assumptions
- Evidence and access
- Methods and sample
- Stakeholders and client demand
- Deliverables and ownership
- Options and independence
- Timetable, fee and exclusions
- Data handling and assurance
- Decision meeting and acceptance
Also ask how disagreements will appear in the final output. A leadership team may hold two credible explanations for the same evidence, and a forced consensus can remove information the eventual decision-maker needs. The discovery lead should state which interpretation it favours, the basis for that judgement and what later evidence would overturn it.
Acceptance should assess the agreed questions and usability of the evidence, rather than whether the recommendation matches a sponsor's expectation. If an important question could not be answered, record the constraint, its effect on confidence and the smallest next step that could resolve it. That is more credible than filling the gap with a benchmark or an assertive conclusion.
Discovery is not valuable because it happens before delivery. It is valuable when it tests a consequential belief, leaves evidence the client owns and makes the next commitment more informed. If it merely produces permission for the supplier's original answer, the sceptics were right.
If you want to understand what a properly structured discovery brief looks like - what it asks, what it produces, and what standard it should be held to - download a sample discovery brief template here. It's designed to be vendor-neutral, so you can use it to evaluate any discovery proposal, not just ours. Frankly, if it helps you get better discovery work from someone else, that's fine by me. The industry needs to raise its game on this.
And if you're trying to decide whether a discovery phase makes sense for your specific situation, a 30-minute conversation will give you a direct answer without any commitment on either side. Sometimes the honest answer is "you probably don't need one." I'd rather tell you that upfront than charge you for something that won't change the outcome.
