A digital investment can launch successfully and drift afterwards. The delivery team moves to the next release, the sponsor returns to other priorities and operational meetings continue without revisiting the business outcome.
A periodic digital review closes that governance gap. Its purpose is different from delivery management. Operational meetings ask whether agreed work is progressing. The review asks whether the investment remains worthwhile, whether evidence supports the current priorities and which leadership decision is now required.
Quarterly is a useful default for many firms because it can connect with commercial planning and gives some changes time to produce evidence. It is not a natural law. High-risk programmes may need more frequent investment decisions; low-volume services may require a longer measurement window. Choose the cadence based on decision need, risk and the time required for a meaningful signal.
Separate three rhythms
Trying to make one meeting serve every purpose produces status-heavy governance.
Delivery rhythm
Teams manage tasks, dependencies, quality, risks and near-term decisions at the frequency the work requires. This may be daily, weekly or linked to delivery stages.
Investment review
Accountable leaders compare outcomes, cost, risk and context, then continue, change, pause or stop work. Quarterly often suits this layer.
Board or partnership oversight
The governing body receives material performance, risk and investment decisions at its established cadence. It should not need to attend every programme review to exercise oversight.
The source article’s distinction remains useful: delivery asks whether the team is building the thing well; investment governance also asks whether it remains the right thing to build.
Put decision authority in the room
Three roles form a sensible core.
The accountable sponsor
This person owns the business outcome and has authority to make or escalate investment decisions. Attendance for information alone is insufficient. If the sponsor sends a delegate, the delegate’s authority should be clear.
The delivery lead
The delivery lead explains what has been completed, what has been learned, where constraints sit and how proposed changes affect scope, cost, time and risk. They may be internal or external.
The evidence lead
This person owns the measures connecting product and service behaviour to the business case. Depending on the programme, the role may sit in analytics, marketing, operations, finance, client experience or product.
Additional specialists should attend for decisions that require them. Legal, compliance, security, accessibility, finance, service or client representatives may be essential. The aim is the smallest group capable of an informed and authorised decision, not an arbitrary limit of three people.
People who need visibility can receive the decision record. People whose work or clients are affected need an appropriate route to contribute before the decision. A small room should not become a device for excluding necessary evidence.
Our article on reporting digital performance to people who do not care about digital covers the wider communication layer.
Prepare an evidence pack that invites challenge
Circulate a concise pack early enough for participants to read and verify it. Include sources, definitions and confidence. The meeting should not be the first time anyone sees a material problem.
The pack can follow five questions.
1. What outcomes changed?
Show the few measures tied directly to the approved problem and expected value. Include baselines, current result, trend, segment and the date of the evidence. Add control and harm measures where relevant.
Avoid a dashboard full of available metrics. Enquiries, completion, service time, adoption, error, satisfaction and revenue all mean different things. Select the measures whose movement can change a decision.
Targets should have a basis. When evidence is immature, report a range, direction or learning question rather than inventing precision. State measurement changes that make periods difficult to compare.
2. What appears to be working, and why?
Separate observation from explanation.
Qualified enquiries increased after the service-page release. The largest change occurred on two pages rewritten around buyer problems. Acquisition mix was broadly stable, although sales follow-up also changed.
This is more useful than declaring the content rewrite a success. It identifies a hypothesis that can be tested elsewhere without claiming sole causation.
3. What is underperforming, and what has been learned?
Treat underperformance as programme evidence, not an automatic assessment of the delivery team. The need may have changed, adoption work may be missing, a dependency may have failed or the original assumption may have been wrong.
Show actions already taken and their effect. Repeatedly reporting the same weak result without a new diagnosis or decision is itself a governance signal.
4. What changed around the programme?
Include client research, regulation, competitor services, supplier changes, technology, costs, organisational capacity and other investments. Focus on changes that can affect the business case or risk.
Competitive activity is a prompt for investigation rather than an instruction to copy. A rival launching an AI portal does not automatically make a content programme the wrong priority.
5. Which choices belong to the next period?
Present a constrained set of options with outcomes, evidence, cost, risk, dependencies and the next irreversible commitment. Show what must stop or move if a new priority begins.
Do not wait until after the quarter to define how a new initiative will be judged. Agree the learning and outcome measures when approving it.
Produce decisions, not a general sense of alignment
Every material initiative should leave the review with one of several states:
- continue under the current plan;
- continue with a defined adjustment;
- gather specified evidence before the next commitment;
- pause because a dependency or risk is unresolved;
- stop and preserve the learning; or
- escalate a specific recommendation to the authority required.
Stopping is not automatically failure. Continuing is not automatically confidence. Record the rationale and conditions that would change the decision.
A new priority should have capacity. Match additions with completed, deferred or stopped work, or explicitly increase the budget and resources. Otherwise the review becomes an initiative-accumulation ritual.
Escalations need a question, recommendation, evidence and decision date. “Discuss the platform with the board” moves the ambiguity upward. “Approve moving the remaining migration budget to the client-access workstream because these three conditions changed” gives the board something it can decide.
Keep the meeting proportionate
The source recommended 90 minutes, a pack 48 hours in advance and a one-page record within 24 hours. Those are useful operating constraints, not quality guarantees.
Set time according to the number and consequence of decisions. Insist on preparation. Use the meeting for disagreement, judgement and commitment rather than reading slides aloud.
A practical running order is:
- confirm decisions and actions from the previous review;
- examine outcome and harm evidence;
- test explanations for over- and underperformance;
- identify material context changes;
- decide initiative states and next priorities; and
- confirm owners, dates, measures and escalations.
Record what was decided, why, who owns the action and what evidence will return. Preserve dissent or uncertainty where it materially affects risk. Distribute the record promptly and feed it into delivery, budget and board governance.
Review the review
After two or three cycles, ask whether the rhythm is improving decisions. Useful signs include fewer ageing escalations, clearer outcome ownership, earlier stopping of low-value work and evidence influencing priority.
If every initiative continues and every new idea is added, the meeting lacks scarcity or authority. If discussion focuses entirely on traffic-light status and budget variance, it has collapsed back into operational reporting. If important specialists repeatedly need to be consulted afterwards, change the attendance or preparation.
Distinction uses WHNN®, What and How, for the Now and the Next, as its quarterly planning framework. The review described here corresponds particularly to the Now and Next dimensions. What WHNN looks like in practice explains the broader rhythm. It is our commercial framework, not the only way to govern digital investment.
The downloadable quarterly digital review framework includes a pre-meeting evidence pack, running order and decision-record template. Adapt the cadence, participants and duration to the programme. Keep the central test unchanged: did this review use evidence to make a decision that ordinary delivery reporting could not make?
