Most digital programmes don't fail at launch. They fail at month nine. They fail quietly, the way a car drifts across a lane when you take your hands off the wheel for a few seconds too long. Not a crash - just a slow, almost imperceptible slide away from where you were supposed to be heading.
I've seen this enough times now that I can almost set my watch by it. A firm invests in a new platform, a website rebuild, a client portal overhaul - whatever the initiative is. The launch goes well. There's energy, attention, maybe even some early wins. And then... nothing structural changes about how the programme gets governed. The monthly operational meetings keep ticking along, the delivery team keeps delivering, but nobody is sitting down every quarter to ask the only question that actually matters: is this investment still doing what we approved it to do?
That's the gap this piece is about. Not the delivery of digital work - that's what your steering committee and your monthly meetings handle. This is about the decision-making rhythm that keeps a digital programme connected to commercial reality after the initial excitement fades.
We have a monthly digital meeting. Do we really need a separate quarterly review on top of that?
Yes. And they're not the same thing.
Your monthly meeting manages operational delivery. Are tasks on track? Is the sprint on schedule? Does the development team need anything unblocked? That's important work, but it's inward-facing. It asks "are we building the thing right?" The quarterly review asks a fundamentally different question: "are we still building the right thing?"
Here's why the cadence matters. Monthly is too frequent to show you anything meaningful. A month's variation in website enquiries or conversion rates is usually noise. You'll spend the entire meeting debating whether a 3% dip means something or whether it's just what happens when there's a bank holiday and half your prospects are in the Cotswolds. You'll take actions based on that noise, and then those actions won't have had time to produce results before the next monthly meeting rolls around. It becomes a hamster wheel of reaction.
Annual is obviously too infrequent. If you're reviewing your digital programme once a year, you're essentially driving with your eyes closed for twelve months and then wondering why you're in a ditch. The course correction required after a year of drift is proportionally enormous - and politically much harder, because people have been working on things for a long time and nobody wants to hear that it was the wrong things.
Quarterly hits a sweet spot. You get enough data to separate signal from noise. You get enough elapsed time for actions taken in the last review to have produced visible results. And - this is the bit that people underestimate - quarterly connects naturally to the rhythms your firm already runs on. Budget cycles, partner performance reviews, strategic planning. The digital review becomes a meaningful input to those processes rather than a parallel exercise that nobody quite knows how to connect to anything else.
I've written about this rhythm in more detail through the lens of our WHNN® framework - the quarterly review described here is essentially what the Now and Next dimensions of WHNN® look like when you put them into practice.
Three people. Seriously, three.
The accountable sponsor. The managing partner, senior operations leader, or whoever owns the commercial outcome that the digital investment was approved to deliver. They're not there to observe or to "stay informed." They're there because they're the person who can make the continue, adjust, or stop decisions the review produces. If this person isn't in the room, you're running a reporting ceremony, not a decision-making meeting.
The delivery lead. Internal or external - whoever is responsible for the programme's day-to-day execution. They bring the performance data and the delivery perspective. They can explain why something happened, not just that it happened.
The measurement lead. The person tracking the commercial outcomes and digital performance metrics. Often the marketing lead or analytics owner. They're the one who can connect what's happening on the website or in the portal to what's happening in the pipeline, the P&L, or the client satisfaction scores.
That's it.
I know this sounds brutal. What about the partners who want visibility? What about the board member who'd like to "just sit in"? What about the junior team member who'd benefit from the exposure?
The board member should receive the review output - there's a separate piece on how to report digital performance to people who don't care about digital, and that's the mechanism for keeping the board informed without clogging the review itself. The junior team member is attending a different meeting. And the partner who wants visibility can read the one-page summary that gets distributed within 24 hours.
Every additional person in the room dilutes the decision-making. I sat in a "quarterly review" last year that had eleven people around the table. Two and a half hours. Zero decisions. Eleven people spent two and a half hours looking at charts and then agreed to "discuss further offline." Which, as we all know, is code for "this will not be discussed again until the next quarterly review."
I'll be honest - I've made this mistake myself. Early on, I thought bigger rooms meant better buy-in. What they actually meant was longer meetings and weaker decisions, because everyone was performing for the audience rather than making calls. I stopped doing it.
The agenda should produce decisions, not discussion for its own sake. Here's what works:
Outcomes vs. targets. The three to five commercial metrics that the programme was approved to deliver, compared to the targets set at the start of the quarter. Not twenty metrics. Not a dashboard with forty-seven graphs. Three to five numbers that connect directly to the business case. Website enquiries. Conversion rate. Client onboarding time. Portal adoption. Whatever your programme was designed to move - those numbers, and an honest assessment of whether the variance is acceptable or requires intervention.
The data doesn't need to be perfect. If your measurement infrastructure is still maturing, work with what you've got and note the confidence level. A review that waits for perfect data never happens. A review that works with directionally reliable data and improves its measurement each quarter is doing exactly what it should.
What's working and why. Two or three things that performed above expectation, with a specific hypothesis about why. This matters because it informs where you put your money next quarter. "The new service pages are converting well" is not useful. "The new service pages are converting at 4.2% vs. the 2.1% baseline, and we think it's because we restructured them around client problems rather than internal practice areas" - that's useful. That tells you something you can apply elsewhere.
What's not working and why. Same analytical rigour, applied to underperformance. And here's something worth flagging, because I've seen this go wrong too many times: this is not a performance review of the delivery team. It is a programme governance decision. The initiative that's underperforming might be underperforming because the market shifted, because the assumption behind it was wrong, or because it hasn't had enough time to produce results yet. The point is to understand why and decide what to do about it - not to assign blame.
What's changed in the external context. Competitive moves. Client feedback patterns. Regulatory changes. Technology developments. A quarterly review that doesn't scan the external environment produces a programme that optimises for last year's assumptions. I remember working with a consulting firm that spent an entire quarter refining their content marketing approach, only to discover at the review that their two biggest competitors had both launched AI-powered client portals in the meantime. The content work wasn't wrong, but it had become the wrong priority. They wouldn't have spotted that without the external scan.
What to prioritise next quarter. Specific initiatives, in priority order, with success criteria defined before the quarter begins. Not after the results come in. Before. This is the bit that separates a managed programme from an approved cost line.
Every quarterly review should produce three categories of decision. Not three hours of discussion. Three categories of decision.
Continue, adjust, or stop for current initiatives. The thing that's working gets confirmed. The thing that's underperforming gets adjusted or stopped. Not tolerated indefinitely because someone important championed it six months ago. This is where the accountable sponsor earns their place in the room.
One new priority for next quarter. The highest-value opportunity that emerged from the data or the external context scan. And here's the discipline that makes this work: a new addition should be matched by either a continuation decision on something existing or a stop decision on something that isn't delivering. Otherwise, the programme just accumulates initiatives until nobody can focus on any of them properly.
A specific escalation, if needed. Any decision beyond the authority of the three people in the room gets escalated with a specific question and a recommended answer. Not a vague "we need to discuss the platform situation with the board." Something specific: "We recommend stopping the content migration workstream and redirecting that budget to the portal improvement. This requires board approval because it changes the approved scope. We recommend approval because [reason]."
Data pack distributed 48 hours in advance. Not the morning of. Not the night before at 11pm. Forty-eight hours, so people actually read it. The meeting is for decisions, not for absorbing information for the first time while squinting at a projector.
Then:
Decisions documented in a one-page summary, distributed within 24 hours. Next quarter's targets set before anyone leaves the room.
The first time you run this, it'll probably feel rushed. Someone will want to relitigate a decision from last quarter. The external scan will uncover something that sends the conversation sideways. That's fine. The discipline of the 90-minute format isn't about being rigid - it's about forcing the preparation to happen before the meeting, so the meeting itself is spent on the thing that only the meeting can do: making decisions together.
I was working with a 200-person management consulting firm a while back - good business, serious clients, genuine digital ambition. They'd invested in a new website and client portal the year before. Both had launched well. But by the time I got involved, the portal adoption rate had flatlined at 34% and nobody could quite explain why, because nobody had been formally reviewing it. The delivery team had moved on to the next project. The sponsor had moved on to the next priority. The programme had just... stopped being managed.
We ran the first quarterly review and found three things in 90 minutes that hadn't surfaced in twelve months of monthly operational meetings: the portal's login flow was broken on mobile for a specific browser version, two of the five most-used features had never been properly communicated to clients, and a competitor had launched a similar tool six months earlier with a noticeably cleaner interface. None of these were catastrophic on their own. Together, they explained the flatline completely.
The firms that run quarterly reviews well - and I've seen this in law firms, IT services businesses, financial services - aren't doing it because they're more disciplined by nature. They're doing it because they've accepted that a digital investment without a governance rhythm isn't really an investment. It's a spend.
That rhythm is what turns an approved cost into a managed asset. If you want the quarterly review agenda - pre-meeting data pack format, 90-minute running order, and decisions documentation template - as a ready-to-use framework, download it here. For the full operational rhythm that the quarterly review sits within, see WHNN®.