Most consultancy frameworks end up as PDFs. Nicely formatted, expensively produced, thoroughly ignored within about six weeks of delivery. You've probably got one in a shared drive somewhere right now - a digital strategy or transformation roadmap that someone paid good money for, presented to the board with genuine enthusiasm, and then quietly let drift into irrelevance as the day job took over.

WHNN is built to avoid that exact fate. But saying "our framework is different" is what every consultancy says, so let me show you what it actually looks like when it's running inside a real firm.

I've written about the rationale behind WHNN elsewhere - there's a companion piece on how to turn digital transformation from project to habit that covers why the quarterly cadence matters, and another on why transformation fails that explains the governance problems WHNN is designed to solve. If you haven't read those, they're worth your time. This piece assumes you've already got the gist and you're now asking the more pointed question: Fine, but what does it actually look like? Who's in the room? What do I get? And what does it cost?

Fair questions. Let me answer them.

A quick recap, then we'll get into it

WHNN stands for "The What and the How, for the Now and the Next." Four dimensions, each doing a specific job. The What defines the problem statement and investment priorities - not a wish list, but a ranked set of initiatives that will genuinely move the needle. The How designs the governance model and delivery sequencing - who's responsible for what, how decisions get made, and what success looks like at each stage. The Now benchmarks where the firm actually is today, honestly, with measurement that surfaces drift before it becomes entrenched. And the Next keeps everything connected to commercial strategy - where the firm needs to be in 3, 6, 12, or 18 months, so improvement doesn't become self-perpetuating busywork.

If you want to understand your firm's current position before committing to anything, our digital maturity assessment is a natural starting point - it'll show you which of the four dimensions offers the highest resilience payoff from improvement. But for now, let me walk you through what happens when a firm actually adopts WHNN as an operating rhythm.

The engagement: a 140-person accountancy firm

Where they were when we started. The firm is a regional accountancy practice - around 140 people across three offices, a healthy mix of compliance and advisory work, and a practice management platform that had been in place for the best part of nine years. Bolted to it: a client portal nobody liked, a CRM that had been "rolled out" two years earlier and quietly abandoned, and a website the partners were mildly embarrassed by. The trigger wasn't dramatic. They lost two decent mid-market clients in the same quarter, and both exit conversations mentioned the same thing - dealing with the firm felt harder than it should. The managing partner's specific frustration, when we first spoke, was that every previous attempt to fix this had turned into a technology project that consumed budget and attention without changing how clients actually experienced the firm.

The What phase - establishing what matters. The original wish list had thirty-one items on it (I counted). A new website, a portal replacement, resurrecting the CRM, "doing something with AI", automating onboarding - all reasonable, none ranked. We scored everything against weighted criteria agreed up front: client impact, margin impact, dependency risk and delivery effort. Twelve initiatives survived as a ranked list, and three made the first quarter. The website rebuild - the thing everyone assumed would top the list - was deprioritised, because the evidence pointed at client onboarding and document exchange as the places where value was actually leaking. And the AI ambitions were parked entirely until the data underneath them could be trusted. The output was deliberately modest: a one-page problem statement and a scored matrix, not a sixty-slide strategy. Three weeks, end to end.

The How phase - designing the governance. Delivery was sequenced across quarters rather than run as one big programme, with the operations director accountable for delivery overall and a named partner sponsoring each initiative - so nothing could quietly become "IT's problem". The decision protocol was simple: anything that moved scope, cost or timeline by more than ten per cent went to a monthly steering group; everything else got decided in the room by the people doing the work. That one rule did more to prevent drift than any amount of reporting, because decisions stopped queueing behind a committee.

The Now phase - accurate measurement. We agreed a small set of measures and resisted the urge to build a dashboard empire: portal adoption among active clients, time to onboard a new client, hours spent each month chasing documents manually, and unplanned platform incidents. The measurement earned its keep in week four, when it surfaced that the onboarding work was quietly stalling - it turned out to depend on a data cleanup nobody had scoped. Because the drift was visible early, it became a re-plan rather than a crisis, and the priority order was adjusted at the next quarterly session instead of being discovered in a post-mortem.

The Next phase - keeping it connected to commercial strategy. The firm's growth plan was weighted towards advisory work, so the 3, 6 and 12-month horizons were framed around that: what does the client experience need to look like for advisory clients specifically, and what has to be true underneath it? That framing killed at least one tempting project - a systems integration piece that was technically interesting but did nothing for the advisory goal - and it kept the quarterly commitments pointed at the same destination rather than drifting into improvement for its own sake.

The outcomes. After four quarters: new-client onboarding down from eleven working days to four. Portal adoption up from roughly a quarter of active clients to just over seventy per cent. Around thirty-five hours a month of manual document-chasing removed, and no unplanned platform outages in the final two quarters. The outcome the managing partner mentions first, though, isn't a number - it's that partners stopped apologising for the firm's technology in new business conversations. That's what closing the gap between promise and delivery actually feels like.

What the first session looks like

This is the bit that trips people up. You read about WHNN, you find the logic compelling, and then you think: Right, but what am I actually signing up for? Is this a two-day workshop with sticky notes and breakout groups? Do I need to bring my entire leadership team?

No. The first session is deliberately small and deliberately focused. Typically it's the managing partner or whoever's sponsoring the initiative, the operations lead, and maybe one or two other senior people with direct visibility of the firm's digital situation. Four people in the room, sometimes five. Never more than that. Too many people and you get performance rather than honesty - everyone starts presenting their position rather than actually thinking.

The session runs for about two and a half hours. I facilitate it personally, and the structure follows the four WHNN dimensions - but at a diagnostic level, not a planning level. We're not trying to build a strategy in one sitting.

The questions I ask are pretty simple, actually. What's working in your current digital setup, and what isn't? Where are the bottlenecks that keep coming up? What have you already tried that didn't land? What does the board actually care about when it comes to digital, and what are they just nodding along to? What would "good" look like for you in twelve months?

The conversation tends to be more revealing than people expect. I sat with a managing partner last year who told me - about forty minutes in - that he'd been avoiding a conversation with his technology lead for six months because he knew the platform was failing but didn't want to trigger another big project. That kind of admission doesn't come out in a large workshop. It comes out when you've got a small group, a structured conversation, and permission to be candid.

By the end of the session, participants leave with three things: a clear problem statement (often quite different from the one they walked in with), a set of prioritised questions to answer during the full What phase, and an agreed timeline for what happens next. Not a strategy. Not a roadmap. Just clarity on where to point the telescope.

If you want to understand how WHNN's prioritisation framework works before committing to a first session, download the prioritisation template (form below) - it's the same starting point we use in the What phase. It won't replace the conversation, but it'll give you a feel for how the thinking is structured.

The quarterly rhythm - this is the bit that matters most

Here's where WHNN diverges from every other strategy framework I've encountered. And honestly, it's the thing I'm most proud of in how we've designed it.

Most consultancy engagements follow a predictable arc: discovery, strategy, roadmap, handover. The consultants leave. The roadmap sits in a drawer. Six months later, the firm has drifted back to reactive mode and the investment feels wasted. I've watched this happen dozens of times - sometimes to firms we were subsequently brought in to help recover. It's maddening.

WHNN doesn't have a handover moment. Instead, it runs on a quarterly cycle. Every three months, the same senior group reconvenes for approximately two hours. The session has a fixed structure, and it goes like this.

First, we review. What was committed to last quarter? What was actually delivered? Where are the gaps, and why? This isn't a blame exercise - it's a calibration exercise. Sometimes things slip because priorities genuinely shifted. Sometimes they slip because nobody was accountable. The difference matters, and the quarterly rhythm makes it visible.

Then we surface what's drifting. What's stalling? What new information has emerged that changes the picture? I remember one quarterly session where a firm's head of operations mentioned - almost in passing - that their CRM vendor had announced an end-of-life date for the version they were running. That single comment restructured the next two quarters of work. Without the rhythm, it would have surfaced as a crisis six months later instead of a planned response.

Then we commit. Based on what we now know, what are the priorities for the next quarter? What are we committing to deliver, who's responsible, and how will we know it's done?

The output from each quarterly session is a short written document - usually two to three pages - that becomes the firm's digital operating record. Over time, these documents build into something genuinely valuable: a longitudinal record of decisions, trade-offs, and progress that means no one has to rely on memory or tribal knowledge to understand why things are the way they are.

The quarterly rhythm is what turns WHNN from a framework into an operating habit. Improvement stops being a project with a start and end date. It becomes an expectation - something the leadership team does as naturally as reviewing financials.

I've written about this dynamic separately in the piece on turning transformation from project to habit in quarterly rhythm, but seeing it in practice is different from understanding it in theory. The firms that have been running WHNN for more than a year tell me the same thing: the quarterly session is now the meeting they'd least want to lose.

Investment and timeline

This sounds like another consultancy framework. What does it actually cost, and is it worth the investment?

I'd rather be specific than evasive here, because vagueness at this stage just creates another reason to delay.

The first session is a fixed fee that's credited in full against the What phase if you decide to continue. It typically takes place within two weeks of the initial conversation.

The What phase - the full diagnostic and prioritisation work that follows the first session - runs over three to four weeks and costs between £12,000 and £18,000 depending on the complexity of the firm's digital situation.

The ongoing quarterly rhythm runs as a fixed fee of £4,500 per quarter. That covers facilitation of the session, the written operating record, and access to me between sessions when a priority question can't wait three months. It doesn't cover delivery work itself - that's scoped separately, and only when the priorities justify it.

What you should expect after four quarters: a prioritised and partially delivered digital roadmap, a functioning governance model, measurable progress against defined outcomes, and a leadership team that has a shared language for making digital investment decisions. Not everything fixed - but everything visible, ranked and moving.

The gap this closes

If you've read this far, you probably already understand the framework. The question you're actually asking is whether it would work for your firm, with your constraints, and your history of digital initiatives that didn't quite land.

I can't answer that without a conversation. But the firms where WHNN works best tend to share a few characteristics: they've been meaning to sort their digital situation out for a while, they've probably had at least one initiative that didn't deliver what was promised, and they've got a leadership team that's willing to commit two hours a quarter to actually governing the thing properly.

If that sounds familiar, there are two sensible next steps. If you want to establish a baseline of where your firm currently stands before diving into the full framework, our digital maturity assessment is designed exactly for that.

And when you're ready to explore whether WHNN is the right operating rhythm for your firm, book an introductory session. It's 90 minutes, no charge, and ends with a clear view of whether and how WHNN would apply to your situation.