Deliver value iteratively whilst innovating

What this means in practice

Teams make deliberate trade-offs between trying new ideas and delivering proven value. Innovation is expected, but it is directed at outcomes and time-boxed. Delivery remains predictable because teams use established approaches by default, and only introduce new technology when there is a clear justification.

Why this matters

If teams only deliver, they fall behind the market and cannot make informed technology choices. If teams only innovate, they miss deadlines and fail to create value. Balancing both protects pace, quality, and credibility, while still keeping Griffiths Waite at the frontier.

Practices that meet this principle

• Use a clear default: proven approaches first, and new technology only when it is value-justified

• Time-box discovery and spikes, with explicit success criteria and a decision at the end

• Share learnings from investigations so the organisation benefits, not just the immediate team

• Prefer consistency where it reduces complexity and operational risk

• Avoid reinventing the wheel when existing solutions meet the need

Validation

A piece of work meets this principle when:

• Delivery commitments are met with predictable quality

• Any new technology choice has a clear, written rationale tied to a measurable outcome

• Exploration is time-boxed and results in a clear decision: adopt, defer, or stop

• Learnings are captured and shared in a way that other teams can reuse