Quarterly review is already six months late

The two-hour feedback loop – How fast small decisions get tested

There is a specific texture to how decisions get made in startups and some small companies that isn't common anywhere else.

A pricing change gets tested on Thursday afternoon. The website hero gets rewritten over coffee and pushed live before lunch. A conversation with one customer on Tuesday morning reshapes the pitch deck by Tuesday evening. A disagreement about who the product is really for gets answered by asking five people on a call, not by commissioning a segmentation study.

None of this is ceremony. It's just how small teams work when the runway won't wait. Every decision is met with a small, quick test — and the result of the test becomes the next decision.

The gap between I think this is true and I know whether this is true is measured in days, sometimes hours.

Now picture the same kinds of decisions being made inside a large organisation.

A pricing change is discussed in a pricing committee. The committee requests a market analysis. The analysis takes six weeks. It goes to a review board. The review board requests a cost-impact model. The model takes four weeks. It goes to the executive team. The executive team commissions a stakeholder consultation. The consultation takes another two months.

Nine months after someone first raised "I think our pricing is wrong," a decision is finally made. By which time the market has moved, the original insight has been forgotten, and the pricing change that was obvious in month one is now being framed as a bold strategic move in month nine.

The difference between the two is not talent. It is not resources. It is not strategy. It is the length of the feedback loop — applied not just to one kind of decision, but to every decision, everywhere in the business.

Why quarterly is already six months late

There is a tendency, inside large organisations, to treat feedback as a formal process. Quarterly reviews. Annual assessments. Board papers. Performance conversations. These have their place — but they are not feedback in the sense that matters.

Real feedback is the signal that reaches the person making a decision, in time to change what they do next. When feedback arrives at a quarterly review, the decisions that needed it were made months ago. The team has already committed budget, hired people, shipped product, built plans around assumptions. The feedback doesn't inform the decision. It autopsies it.

And the thing most people miss: by the time the quarterly review surfaces a problem, the problem didn't start last month. It started in the first week of the quarter and compounded from there. Small signals that went unnoticed in week one became noticeable in week four, became obvious in week eight, became expensive in week twelve. The quarterly review shows the final state. The opportunity to intervene was distributed across the previous eleven weeks.

By the time you see it in the quarterly pack, you're looking at compounded delay. You're already six months behind the moment where the cheap intervention would have worked.

This is the structural argument. It's not that quarterly reviews are bad. It's that they are the wrong place to learn something you should already have known.

Where feedback actually lives in the Idea to Value flow

In the Idea to Value system, feedback is not a separate activity that happens at the end, or even every quarter. It's woven through every stage of the flow — or should be.

From idea to investment: is this actually worth doing? Feedback is the customer conversation, the small test, the quick review that says we're building something nobody needs before the investment happens.

From investment to activity: are we set up to do this well? Feedback is the team check-in, the resource review, the early signal that something is missing or mismatched.

From activity to creative action: is the work actually producing what we hoped? Feedback is the sprint review, the draft critique, the in-progress check that catches drift before it becomes direction.

From creative action to ship: is this ready, or are we shipping because the deadline says so? Feedback is the pre-launch test, the cold read, the honest assessment of whether the thing is ready to meet the world.

From ship to value: did it actually produce what we meant it to? Feedback is the usage data, the customer response, the market signal, the internal metric that tells you whether the work closed the loop or left a gap. The value being realised.

At every one of these transitions, feedback either exists or doesn't. When it exists, the flow self-corrects. When it doesn't, errors propagate forward to the next stage, where they compound with the errors that stage adds, and so on until something expensive happens, or has shipped that nobody wants and nobody can quite explain how.

The shorter the loop between action and signal at each stage, the less compounds forward. This is why startups outpace much better-resourced competitors. They aren't cleverer. Their feedback loops are just shorter, at every stage, systematically.

The four measures are the starting point

The four measures — delivery, finances, people, products — exist because they carry distinct kinds of feedback, at different cadences, from different parts of the system. Most organisations struggle with feedback not because they don't measure, but because they conflate or delay their measures.

Delivery measures tell you whether work is moving at the pace you planned and outcomes are being created as expected. Progress against these should surface weekly, at least. A team that only learns about its delivery rate at quarter-end has already shipped or failed to ship three months of work before anyone examined it.

Financial measures tell you whether the investment is producing return – and how much it's costing you. These often come more slowly because of internal politics, lack of connection between finances and activity, and out to value. External transactions lag — a customer bought something last month, the invoice settles this month, the revenue books next month. Internal data is not easy to dig through. But within that constraint, the faster you see the numbers, the faster you can respond to the trend.

People measures tell you whether the team is carrying the work well. These are the ones most organisations treat as quarterly or annual, or don't measure at all — engagement surveys, reviews, assessments. And they are often the measures where delay is most damaging. By the time a quarterly pulse engagement survey flags that a team is struggling, the good people may already have quietly started looking elsewhere.

Product/Service measures tell you whether the thing you've built is doing what it's meant to do – or will do what it's supposed to do. In digital products, these are immediate — usage, conversion, retention, satisfaction. In other contexts they're slower but still available, if you look for them. Customer feedback, support tickets, complaints, referrals, ability to sell what is being built. These are the closest thing you have to the market telling you whether your work is valued.

Four distinct streams of feedback, each at its own cadence. The healthiest organisations see all four regularly (before, during and after the creation process), keep them separate from each other - but visible side by side, and resist the temptation to blend them into a single "performance" number that hides more than it reveals. Watermelon reporting happens when these measures get conflated and smoothed into a single green dashboard while the underlying signals are red.

Feedback isn't only measures

Not all feedback is data. Much of the most useful feedback in any organisation travels through conversation — a colleague noticing a behaviour that's starting to fray, a leader hearing a tone in a meeting that tells them something isn't quite right, a quiet check-in that reveals someone is carrying too much.

This is where the Physics layer meets the Wiring layer. Feedback requires communication to travel. If the wiring is good — if people can speak honestly, disagree productively, surface concerns without fear — then the system has access to human signals that metrics will never catch. If the wiring is broken, the data-only feedback loops will miss exactly the things that matter most.

And this is where cultural discipline becomes structural. A team that expects feedback, offers it generously, and receives it as information rather than as judgement builds something closer to a learning culture. A team that treats feedback as criticism — or worse, as political risk — closes down the very channel that would let it correct itself.

The reframe that matters: feedback is not blame. It is not judgement. It is information. Neutral until interpreted. Useful when met with curiosity. The same observation, delivered in an organisation with healthy wiring, produces a productive conversation; delivered in one with broken wiring, produces defensiveness and silence. The observation itself is identical. The climate around it determines whether the feedback gets used or buried.

Most organisations that say they have a feedback problem actually have a wiring problem. The signals are there. They just can't move.

What shortening the loop actually looks like

If quarterly is too late, and the signals are already distributed across the previous twelve weeks, what does it look like to intervene earlier?

It doesn't require replacing the quarterly review. It requires building smaller feedback events into the way work already happens, so that quarterly becomes a summary of what you already know rather than a revelation of what you didn't.

Some practical patterns worth naming:

Weekly retrospectives on delivery or build. Not a formal meeting — just fifteen minutes of honest conversation at the end of each working week or sprint. What shipped? What stalled? What's the signal telling us about where to focus next week? A team that does this doesn't get surprised by the quarterly review, because the quarterly review is just twelve weeks of retrospectives compressed.

Sprint reviews that include actual customers. Many organisations run sprint or demo reviews as internal show-and-tells. The missing step is putting the work in front of someone outside the team — a customer, a stakeholder, a fresh pair of eyes, someone neutral — and watching what they do with it. The signal from an outsider's reaction is worth more than an hour of internal debate.

Quarterly reviews based on what was actually committed. If the quarterly review is a recitation of activity, it surfaces nothing. If it's a comparison of what the team committed to at the start of the quarter against what actually happened — and an honest conversation about why — it becomes useful feedback on the planning and building process itself. A quarterly that doesn't do this is just a meeting held because the calendar said so.

Real-time signals from the systems of record. Every organisation has systems — ticketing, product analytics, customer support, sales pipeline — that produce signals in near real-time. Most of those signals sit in dashboards – but do people read them, or understand what the numbers show? The move is to make a few of them visible constantly, in ways that the team can actually use. Not all of them. The two or three that most directly indicate whether the work is producing value.

Conversations held deliberately, not reactively. The best leaders I've worked with make a point of having short, informal conversations with the team across the week — not to check on them, but to create the ambient space for signals to surface. Most organisational feedback travels through these conversations first. The formal structures catch up later. Or don't.

None of these patterns are expensive. None of them require new tooling. They require the discipline of creating feedback moments before the calendar demands them, and the cultural climate to use what they produce.

The compounding argument, one more time

The reason shorter loops matter more than longer ones isn't just that they give you information sooner. It's that they prevent problems from compounding.

A problem in week one, uncaught, shapes the work of week two. The decisions made in week two assume week one was correct, and build on it. By week four, four weeks of decisions depend on an assumption that was wrong in the first place. By week eight, eight weeks. By the quarterly review, twelve weeks of compounded dependency on a problem you could have caught on day three.

The cost of the error isn't the problem. The cost is everything that was built on top of it while it went unnoticed.

Short feedback loops aren't a management preference. They're a structural requirement for any organisation that wants to catch problems, mistakes and delays while they're cheap. The longer the loop, the more the work is built on the problem, and the more expensive the unwinding becomes.

And — this is the quiet truth — the organisations that learn this usually learn it the hard way. They discover at the quarterly review that what they thought they were building in week three wasn't what the customer wanted, and by week twelve they've shipped it anyway, and now they have to go back and rebuild it. The cost of the rebuild is many multiples of what a week-three conversation would have cost.

A compass rarely shouts. It simply points. And those who check it often arrive where they intended.