For senior leaders in Government Digital and Data, Discovery rarely fails because the research is wrong. It fails because no one makes the decision the research was meant to enable.
Teams leave Discovery with insight. Journey maps, blueprints, problem statements, but insight isn’t direction. Too often, Discovery ends with artefacts and momentum, but without an explicit choice about what happens next.
This choice matters because Alpha is where investment scales, expectations rise, and scrutiny intensifies. Entering that space without clarity isn’t momentum, it’s risk.
The silent failure of discovery
Discoveries rarely fail because the research was wrong. They fail because nothing gets decided.
Teams understand more than they did at the start, but the fundamental uncertainties remain:
• The problem is still too broad
• The direction is still fuzzy
• The risks are still implicit
So teams slide into alpha carrying the same ambiguity they arrived with, perhaps just better documented.
Ambiguity always travels downstream and it becomes more expensive, more visible and much harder to unwind.
The decision point we keep avoiding
The move from Discovery to Alpha is not a phase handover. It is a decision gate - owned by sponsors and delivery leadership - where you choose what you are funding next.
At that gate, the only honest outcomes are:
Stick: we believe the framing is strong enough to test
Twist: what we learned changes the direction, and we pivot
Stop: the problem, as framed, isn’t worth pursuing right now
If you can’t say which one you’re doing, you’re carrying ambiguity into Alpha and paying for it later.
Stick / Twist / Stop: A simple model for honest decisions
The Stick / Twist / Stop model is a lightweight way to force clarity at the end of discovery and prevent the drift into alpha “because we have to do something next”.
|
Stick The evidence supports the current framing, so we fund Alpha to test it through prototypes, data, and real‑world constraints. |
| Twist The evidence changes the story, so we pivot the framing or route and fund Alpha to test the new direction without pretending the old one still holds. |
| Stop The value case or constraints don’t justify further investment right now, so we pause before cost and expectation scale. |
This is a leadership decision: teams provide evidence, but sponsors decide the investment.
A real twist: when reuse looked obvious and Alpha proved it wasn’t
To see how this plays out in practice, here’s an example from a recent funding platform project.
The initial direction seemed sensible:
‘Repurpose the technology used for an existing tool to support a new portal for organisations to submit data and automate internal approval workflows.’
Discovery explored this viability over nine weeks. The problem appeared clear and familiar: manual processes, bulky spreadsheets and a painful experience for users navigating dense guidance and clunky workflows.
Alpha was deliberately framed to test this reuse hypothesis - deepening requirements and prototyping iteratively to shape recommendations for what came next. And then reality surfaced.
Constraints weren’t abstract, they were structural
Alpha reveals major delivery constraints: limited infrastructure to deploy, delayed access to code and documentation, dependency changes (including decommissioned services) and DevOps friction.
Alongside this, the programme had to navigate policy reform uncertainty, engagement challenges, and process variance across user groups- complexity that sat well beyond the tool.
User needs were consistent and they pointed to deeper issues
The team carried out 42 research sessions with 32 users across 6 rounds, using methods like interviews, usability testing and A/B testing, including participants with access needs and varying digital confidence.
What emerged wasn’t “just” form friction. It was systemic:
Users struggled with collaboration in spreadsheet driven processes, evidence naming conventions, and finding answers buried in long, hyperlink heavy guidance.
Internal reviewers experienced clunky system switching, difficult file retrieval through nested folders, and communication gaps across teams and with external organisations.
Reuse wasn’t impossible.
But reuse, as originally imagined, wouldn’t solve the root problem and pain points.
The hypothesis test produced a decision
The team tested around forty functional requirements against the existing tool, which matched half directly and nearly three quarters of partially so appeared a good match.
Importantly however, they identified unmet needs around complex case management and file generation, including 'must haves' that would need focus on development.
This is where Stick / Twist / Stop stops being theory.
The team engaged stakeholders and reached a clear decision: Twist.
They pivoted to a more policy agnostic direction, ran a focused Mini discovery into BAU processes, and deliberately descoped areas that would have inflated risk and complexity at the wrong time.
Instead of forcing the original plan to hold, Alpha created something more valuable:
A clearer understanding of end-to-end service and BAU processes
Evidence backed options for the next phase (including “do nothing”, reuse as- is , fund development, adopt an off-the-shelf workflow tool, or build bespoke)
A pragmatic set of prerequisites for moving forward: process alignment, broader
research, baseline measures, and explicit decision sign off
That’s what a healthy twist looks like: not a wobble, but a disciplined response to evidence.
What decisive discovery really buys you
A twist doesn’t mean discovery “failed”.
It means discovery did its job.
Because the most expensive outcome isn’t changing direction.
It’s failing to and building the wrong thing with confidence.
Decisions, not deliverables, drive public sector change
The public sector doesn’t need more Discoveries that surface insight and artefacts but avoid the decision. It needs Discoveries that end with a clear, accountable choice: Stick, Twist or Stop. And of course, the why.
If you’re sponsoring the work, ask one question at the end of Discovery: “What decision are we funding next, and what evidence makes that the responsible choice?”
Then document the decision, the rationale and the risks you are consciously accepting.
Because in the end, the most strategic thing is not to move fast, but to move deliberately in the right direction.
Discuss how to make your Discovery‑to‑Alpha decision explicit and reduce risk before investment scales. Talk to an expert.