Untested assumptions can make a digital project expensive because money and effort may be committed to a solution before the underlying problem, user needs and delivery constraints are clear. The result is not necessarily failure, but it can mean changing scope late, funding work that users do not adopt, or discovering that a proposed service is not viable or cost-effective.

The cost is often in committing too early

A request for a website, app, platform or automated workflow can sound like a settled brief when it is actually a proposed answer. If the problem has been defined around the answer rather than the need, the project can optimise the wrong thing. Later changes then affect more than design or development: they can alter operations, content, support, marketing, data handling and internal ownership.

This is why early uncertainty is not automatically waste. The more material commercial risk is treating untested beliefs as decisions. Government service guidance similarly advises understanding the problem, users, wider context and constraints before committing to build a service.

Which assumptions create avoidable cost?

  • That a proposed feature addresses a real and sufficiently important user problem.
  • That people will use the service in the way the organisation expects, rather than relying on existing channels or workarounds.
  • That the digital experience can operate effectively alongside existing teams, processes and offline touchpoints.
  • That accessibility and inclusion needs have been considered early enough to influence the direction of the service.
  • That legacy systems, contracts, legislation or internal dependencies will not prevent the intended outcome.
  • That the available budget, people and ongoing commitment are sufficient for a service that is useful, not merely launched.

Late discoveries have wider consequences

A technical constraint discovered after a direction is approved may force a less useful experience or a broader redesign. An operational constraint may create manual work that erodes the expected efficiency benefit. A weak understanding of the wider customer journey can leave users repeating information or abandoning the process between channels. These are commercial risks, not simply delivery inconveniences.

The exact financial effect varies by project, so it would be misleading to claim a standard cost increase. However, the pattern is clear: the later a fundamental assumption is challenged, the more existing decisions, commitments and dependencies may need to change.

A decision to stop can protect investment

Not every investigation should lead to a build. The supplied guidance notes that stopping can be the right outcome where research shows there is no viable service or no cost-effective case to continue. For a commercial organisation, that can mean redirecting investment towards a simpler change, a different channel, an operational improvement or a better-defined opportunity.

This is not an argument for indefinite research. It is an argument for reaching a decision with evidence proportionate to the risk. A small, reversible change needs a different level of confidence from a customer-facing platform, a service dependent on legacy technology or a product that changes how teams work.

What leaders should want before major delivery commitment

  • The organisation can describe the user or business problem independently of a preferred solution.
  • The scope reflects the wider journey and the teams or channels that influence it.
  • The most consequential uncertainties have been examined rather than deferred without ownership.
  • Material constraints and dependencies are understood well enough to judge viability.
  • There is a credible case that the proposed outcome can meet needs and justify the investment.
  • Success can be assessed through relevant measures, rather than launch activity alone.

Product validation is a strategic investment

The aim is not to eliminate uncertainty; that is rarely possible. It is to reduce uncertainty where being wrong would be costly, and to make a deliberate stop-or-go decision before a project gains momentum. For buyers, the desired outcome is a clearer problem, a more defensible scope, an understanding of constraints and a realistic basis for investment.

OUROPT can help organisations turn early uncertainty into clearer product strategy, UX and prototyping decisions before significant delivery investment is committed.

Explore our services →

Sources and references

  1. How the alpha phase workswww.gov.uk
  2. How the discovery phase workswww.gov.uk