Think of the last market signal your frontline noticed.
How many days passed between that signal appearing on the frontline and a decision being made at leadership level? In most scaling businesses, the answer is 20–45 days. Which means your strategy is responding to conditions that existed six weeks ago — in a market that moved last week.
Your feedback loop latency — measure it now
Count the days: frontline signal → leadership decision → adjusted direction
That number is your feedback loop latency. If it's above 14 days, your strategy is structurally reactive rather than structurally responsive. The difference compounds: a business with a 7-day loop makes 52 strategic adjustments a year. One with a 45-day loop makes 8. Same market. Very different competitive position.
Agility is not "we move fast" or "we change direction when needed." Agility is a function of your feedback loop — the speed at which information travels from where reality is happening to where decisions are being made, and back down again as adjusted direction. A business whose loop runs on a thirty-day cycle is a slow machine moving confidently in an outdated direction.
Three moves compress the cycle.
Move 1
Replace the monthly review with a weekly strategic pulse
Cancel your monthly strategy review. Replace it this week with four weekly sessions of forty-five minutes each. Same agenda every time, one question only: what did we learn this week that makes our current approach less valid than it was seven days ago?
This is not a status update — it is a friction hunt. Status updates look backward at what happened. A friction hunt looks forward at what is about to stop you. A status update generates a report. A friction hunt generates a decision. A decision made this week on data from this week is categorically more valuable than one made next month on data from last month.
The rule: the first three sessions will feel uncomfortable. By the fourth, the team will surface problems early rather than manage them quietly. That shift alone reclaims weeks of execution time every quarter.
Move 2
Decentralise the correction — guardrails not handcuffs
A feedback loop that travels all the way to the C-suite before a correction is authorised is not a feedback loop. It is a bottleneck wearing a feedback loop's name. The fix is a clearly documented set of guardrails: specific authority for specific scenarios. Not vague empowerment — specific sentences.
Example: "If weekly conversion drops by more than 15% from the previous three-week average, the team has authority to pause the current acquisition campaign and run a two-week diagnostic." That sentence, written down and shared, eliminates three meetings and two weeks of delay every time that situation occurs.
The rule: map your most common correction scenarios. Write the guardrails. The team stops waiting for permission — and you stop being the bottleneck between the signal and the response.
Move 3
The 72-hour debrief — code the learning immediately
Most post-mortems happen six weeks after a project closes. By then, people reconstruct what they think happened from memory, in a climate of defensiveness or pride. The learning is poor quality and arrives too late to influence the next project, which is already underway.
Fix the timing: debrief within 72 hours of completion. Every project, regardless of outcome. One hour, three questions: what did we predict, what actually happened, what does the process look like next time? Then update the relevant playbook before the team moves on.
The rule: the difference between a business that learns and one that repeats is not intelligence — it is timing. Learning captured on Thursday is five times more accurate than learning captured next month.
"A business with a 7-day feedback loop makes 52 strategic adjustments a year. One with a 45-day loop makes 8. Same market. Very different competitive position."
Apply these three moves and a realistic target is to cut your feedback loop latency in half within a quarter. From 45 days to 20. From 20 to 10. Each compression doubles the number of strategic adjustments you make per year — without changing the strategy, the team, or the market.
Go back to your number. Is it acceptable? If not — which of these three moves will you implement this week?
Most businesses don't fail to scale. They leak value faster than they can create it. Information latency is one of the most structurally embedded sources of that leak — and unlike most structural problems, it has a solution you can start implementing this week.
Free diagnostic
Find where your competitive advantage is leaking
The Stop the Leaks assessment identifies exactly where value is leaving your business — and what to do about it first.
No fluff. No sales pitch. Just clarity on where to look first.
#ScaleUp #BusinessGrowth #FounderMindset #Leadership #OperationalExcellence #BusinessStrategy #GrowthStrategy #Entrepreneurship #UnicornStartup #TheUnicornMentor
Stuart Webb works with founders and leadership teams scaling businesses from £3M toward £50M — helping them identify and seal the leaks in strategy, execution, team, and growth that prevent sustainable scale.
Stuart speaks from direct operational experience, not theory. Every session is grounded in real scaling challenges, real structural fixes, and the specific leaks that cost founders most between £3M and £50M.
After a research science career, Stuart founded and exited three companies, held senior corporate roles, and serves as a Non-Executive Director across multiple sectors.
He holds a doctorate from the University of Oxford and is the creator of the PATH 2 SCALE framework — a proprietary methodology for operational scaling used by founders across the UK.
JOIN MY MAILING LIST