A strategy framework earns its keep after the workshop. If it produces an attractive document but does not change what leaders fund, stop or review, the document is the work product and the strategy has already started to fade.

WHNN® is Distinction's way of connecting digital ambition to a recurring management process. The name stands for the What and the How, for the Now and the Next. Those four views are deliberately interdependent. A list of projects without a current baseline is guesswork. A target state without delivery ownership is aspiration. A governance process without a commercial direction can become efficient administration of the wrong work.

This article explains the operating model rather than presenting an unverified client success story. The original version included precise results from an anonymised accountancy-firm engagement. Those figures may be suitable for publication once the client, measurement definitions and permission to use them have been confirmed. The framework does not need those claims to be useful.

Now: establish the position you can defend

Now is an evidence-based account of the current position. It should cover the relevant client journeys, business processes, platforms, data, delivery capability and governance. It also distinguishes facts from interpretations and makes important gaps visible.

The purpose is not to manufacture a maturity score. It is to answer questions such as:

  • Where does the client or employee experience create avoidable effort?
  • Which systems are constraining a commercial priority?
  • What work is already under way, and what does it depend on?
  • Which measures are reliable enough to guide a decision?
  • Where are leaders relying on assumptions because useful evidence is absent?

A good Now view can be uncomfortable. The initiative everybody expects to lead may turn out to be less urgent than a broken onboarding process or unreliable data. It can also protect useful work from a fashionable replacement by showing that the real problem sits elsewhere.

The output is a concise baseline with evidence, confidence levels and unresolved questions. It should be possible for somebody outside the original workshop to see how each important conclusion was reached.

Next: describe a commercially relevant destination

Next defines what needs to be different over an appropriate horizon. It begins with the firm's strategy rather than a catalogue of digital possibilities.

If a professional-services firm wants to grow a particular advisory practice, for example, the relevant question is not “What technology should we buy?” It is “What must clients and colleagues be able to do reliably for that growth plan to work?” The answers may involve clearer propositions, faster conflict checks, better knowledge access, different ownership or a platform change. Technology is one part of the operating system.

Time horizons should suit the decision. A three-month view can establish immediate commitments. Six- and twelve-month views can describe capabilities and outcomes. Longer horizons are useful where regulation, contracts, data remediation or platform replacement impose real lead times. False precision several years out is less useful than an explicit direction and the conditions that would cause it to change.

Next also creates a filter. A technically interesting integration or AI experiment may be a poor priority if it does little for the chosen commercial result. Saying no to plausible work is one of the framework's most valuable functions.

What: turn the gap into a small set of choices

What identifies the initiatives that could move the organisation from Now towards Next. It is a ranked portfolio, not a wish list.

The criteria should be agreed before individual projects are scored. Typical considerations include client value, commercial contribution, risk reduction, delivery effort, dependency, reversibility and the cost of delay. Weighting them forces leaders to expose differences in judgement. It also prevents a numerical score from disguising an argument that has never taken place.

Scoring supports a decision; it does not make one. A low-effort improvement may start first because it removes a dependency. A high-value programme may wait because the data, ownership or procurement route is not ready. The rationale is recorded alongside the ranking so that a later leadership team can understand the trade-off.

The first-quarter list should be deliberately short. If everything is a priority, the organisation has preserved the original problem in a tidier format.

A simple prioritisation template can help teams structure the discussion. It should be adapted to the firm's context and supported by evidence, rather than treated as a universal formula.

How: make delivery governable

How defines who owns the result, how decisions are made, what the sequence is and how progress will be assessed. This is where many credible strategies become optional.

Each active initiative needs an accountable owner with authority to resolve normal delivery questions. It may also need an executive sponsor, but sponsorship should not leave the operational owner waiting for every decision. Escalation thresholds can be set for material changes to cost, timing, scope, risk or expected value.

Dependencies are managed across the portfolio. If a new client journey depends on data cleanup, identity controls and a content decision, those are part of the plan. Hiding them behind the headline launch date makes slippage look unexpected when it was built in from the start.

Measures should be few enough to use. They might cover time to complete a client task, adoption by the intended group, manual effort, failure demand, incidents or a commercial outcome. Every measure needs a definition, owner, source and baseline. A dashboard containing numbers nobody trusts adds ceremony rather than control.

How also says what happens when evidence changes. Replanning is not automatically a failure. Continuing with a commitment after its assumptions have collapsed often is.

The first working session

The first session is diagnostic, not a compressed strategy project. It usually brings together the executive sponsor, the person responsible for operations or delivery, and the few leaders with direct knowledge of the problem. The right attendance depends on the decision; a fixed limit would be artificial, but a large representative workshop can encourage position-taking and make candour harder.

Useful questions include:

  • What commercial decision or result are we trying to support?
  • What has already been attempted, and what did it teach us?
  • Where do client experience and internal effort appear to diverge?
  • Which constraints are genuinely fixed?
  • What evidence would change our current view?
  • What would need to be true in twelve months for leaders to regard the work as worthwhile?

The session should end with a bounded problem statement, priority questions, evidence requests and ownership of the next step. It should not pretend to produce a roadmap before the current position has been examined.

The quarterly rhythm

The recurring review is what turns WHNN from a framework into an operating habit. Quarterly is a useful default for many firms because it gives initiatives time to move while preventing an annual plan from becoming untouchable. Faster-moving or higher-risk work may need more frequent operational governance; the quarterly session does not replace it.

A review has three jobs.

First, compare commitments with what happened. This is a search for causes and changed assumptions, not a ritual in which every delay is excused or blamed.

Second, surface drift and new information. A vendor may announce an end-of-life date. A regulation may alter the risk. A user test may disprove the proposed journey. An acquisition may change the priority. Bringing that evidence into one portfolio view prevents a local issue becoming a late strategic surprise.

Third, make the next commitments. Leaders decide what will continue, change, stop or start; name owners; record dependencies; and state how completion will be judged.

The operating record can be short. A few pages capturing evidence, decisions, owners, measures and rationale are more useful than a presentation that is rewritten each quarter. Over time, this record explains why the portfolio looks as it does and reduces dependence on institutional memory.

What the engagement should specify

The scope and commercial terms of a WHNN engagement can change. Current fees, session lengths and service inclusions should therefore be confirmed directly rather than copied from an undated article.

A useful proposal will distinguish the initial diagnostic, any deeper baseline and prioritisation work, recurring facilitation, and delivery services. It will identify what the client owns, which decisions Distinction can support, what evidence is required and which outputs the client retains. It should also make clear that adopting the framework does not oblige the firm to commission delivery from Distinction.

The relevant investment test is not whether a framework sounds distinctive. It is whether the process improves the quality and speed of consequential decisions, keeps work connected to commercial strategy and detects drift early enough to act.

For more on the recurring model, read how to turn digital transformation from project to habit and why transformation fails. The digital maturity assessment is also a useful baseline if that asset remains active and its current scoring method has been reviewed.

If your firm has a collection of plausible initiatives but no shared way to rank and govern them, talk to us about the decision you need WHNN to support. The useful first conversation is about that decision, not a predetermined programme.