Scaffolding, Not Bureaucracy

How to design an operating rhythm that distributes judgement instead of centralising it.

My first real experience of operating rhythm came in the Air Force.

In military aviation, structure is everywhere. Checklists, briefings, debriefings, standard operating procedures, safety systems, radio discipline, command structures, mission planning cycles. Some of that structure is visible. The more powerful part is the mental rhythm underneath it. You observe the environment, orient yourself using training and context, make a decision, act, and then do it again as the environment changes.

The OODA loop is not an abstract framework when you are flying. It is the work. You are trained to make high-quality decisions with incomplete information, under pressure, and with people depending on the outcome. The repetition is not there to make you robotic. It is there to make the basics automatic so that your mind is free when something goes wrong.

That was one of my earliest lessons in structure. Good structure does not remove judgement. It gives judgement somewhere to stand.

The best mission commanders I worked with were not the ones who blindly followed process. They were the ones who understood the structure well enough to move through it with agility. They knew when to follow the checklist exactly, when to escalate, when to listen, when to decide, and when to act. The structure was scaffolding, not the building.

I have been refining that idea in business ever since.

Good structure does not remove judgement. It gives judgement somewhere to stand.

## When the leader becomes the system

One of the clearest signals that an operating rhythm is not working is when the leader becomes the system.

If a CEO, founder, executive, or operator feels the organisation constantly pulling them into every decision, every escalation, every customer issue, every product trade-off, and every internal conflict, my instinct is not to assume the team lacks talent. My instinct is to inspect the cadence.

Is the strategy clear enough? Are decision rights explicit? Is information moving from the people closest to the work to the people who can remove blockers? Do managers understand the intent well enough to act without waiting for permission? Is the culture rewarding ownership, or is it quietly training people to wait for senior cover before taking a risk?

A strong operating rhythm distributes judgement. It gives managers the structure, context, and confidence to solve problems on their own. Pair that with a culture that encourages ownership, rewards success, and treats intelligent failed attempts as learning rather than embarrassment, and you create a team that is willing to take on hard projects knowing the outcome is uncertain. That is where speed starts to compound.

Structure without culture becomes bureaucracy. Culture without structure becomes energy without direction. The magic is in the combination.

A good operating cadence does not centralise decision-making. It distributes judgement.

## Strategy moves down. Capability moves up.

I think about operating rhythm in two directions.

The first direction is top down. Leaders need to define the strategy, purpose, mission, yearly goals, and quarterly priorities clearly enough that they cascade through the organisation. In a well-run company, an individual contributor should be able to say, "Today I am working on X. X contributes to our quarterly goal of Y. Y contributes to our yearly goal of Z. And Z is part of the company's mission."

That sounds simple. It is not. Most organisations are full of people doing work that is locally rational but strategically disconnected. They are busy. They are trying. They may even be succeeding inside their function. But if the work does not connect to a clear operating logic, the organisation loses leverage.

The second direction is bottom up. It is not enough for leaders to cascade strategy and hope execution appears. The people closest to the work need workcycles, routines, metrics, communication channels, and escalation pathways that let them execute, learn, and feed insight back into the system. A strategy that does not connect to operating reality is just a statement of intent.

The operating rhythm joins those two directions together. Top down, it gives the organisation direction. Bottom up, it gives the organisation learning.

Strategy tells the organisation where to go. Operating rhythm teaches it how to get there.

## Scaffolding, not bureaucracy

The word I keep coming back to is scaffolding.

Scaffolding holds a building up as it grows. It does not define the final shape of the building. It gives the builders somewhere to stand, stops people falling off the side, and moves as the building gets higher. You do not build scaffolding one hundred storeys high when you are laying foundations. But if the building is already fifty storeys high and the scaffolding is still at level ten, people are going to get hurt.

Companies are the same.

The aim is not to deploy military structure end to end. It is not to fill everyone's calendar with meetings that make the organisation feel mature. The aim is to deploy the minimum viable scaffolding needed for the organisation to function, learn, and grow at its current stage. Too little structure and the business bends under pressure. Too much structure and the company stops adapting. The art is knowing how much scaffolding the organisation needs now, and how quickly that scaffolding must evolve as the company scales.

Whether I am looking at a regulated technology startup, an industrial robotics programme, an AI compliance company, an FMCG supply chain, or a consulting engagement, I am always looking for the heartbeat. What is the cadence? Where does information enter the system? Where are decisions made? How does customer reality become product? How does product become delivery? How does delivery become growth?

If those questions are not answered deliberately, they get answered randomly. Random does not scale.

Operating rhythm is scaffolding. It supports the company while it grows, but it should not define the shape of the building.

## What this looked like at Swoop

At Swoop, the cadence eventually settled around a Wednesday-to-Wednesday product and sprint cycle. That became the company heartbeat.

Monday morning was deliberately protected from heavy executive meetings. People needed to re-enter the week, clear immediate issues, check in with customers, absorb what had happened over the weekend, and prepare properly for planning. Daily standups still happened, but the deeper planning work began later.

Monday afternoon was preparation for executive planning. Twenty-four hours before the executive meeting, each function updated its section of the notes. Early on, that might have been as simple as the good, the bad, and what needed attention next. As the company scaled, it became more structured. What was working. Where risks were emerging. What was not working. What decisions were needed. What had changed since the last cycle.

That happened across the key verticals of the business. People and culture. Manufacturing. Operations. Hardware development. Software development. Flight operations. Regulation. Finance. Commercial. Product. Everyone arrived prepared.

The first five minutes of the meeting were silent reading. Every leader absorbed the full context, not just their own function. That mattered because the value was usually in the connections between functions. A safety insight from flight operations might land on a product decision. A regulatory shift might reshape the commercial pipeline. A manufacturing constraint might rewrite a roadmap commitment.

The executive meeting was not a performance. It was a decision forum.

On Tuesday, executive planning flowed into final product decisions. Product sat at the centre because product changes had consequences everywhere else. If a new release was going out, operations needed to know what customers had to be told, support needed to know how to handle tickets, documentation needed to be updated, and commercial needed to know what could and could not be promised. Hardware and software teams then took those inputs into sprint planning.

Wednesday was sprint launch. Thursday carried the commercial and safety rhythm, because commercial needed to stay close to product and capacity, and safety needed its own protected cadence in an aviation business. Friday carried finance, closing the loop between operating plan, capital use, forecast, runway, and resourcing. Then the cycle repeated.

That might sound like a lot, but the fixed executive cadence was actually quite lean. A short daily standup. Executive planning. Sprint planning. Commercial. Safety. Finance. Plenty of other things happened ad hoc. The fixed rhythm was the minimum viable scaffolding we needed to let the organisation function and flourish.

One week was planning and deployment. The next was monitoring and evaluation. In OODA language, we acted, observed, oriented, decided, and acted again.

Same loop. Different theatre.

## Different category, same principle

When I joined Vissibl as interim COO and strategic advisor, the category was very different. The company was building an AI-powered compliance platform for physical industries. Different customer, different product, different sector, different cadence than aviation logistics.

But the leadership problem felt familiar. The early challenge was to turn customer pain, product energy, delivery requirements, and commercial momentum into one coherent operating loop.

Compliance is inherently messy. Evidence sits across systems. Policies live in documents. Supplier information is scattered. Audit readiness is often episodic rather than continuous. Customers know they have pain, but the product needs to translate that pain into a workflow they trust enough to use. Internally, the company needed the same discipline as Swoop did. Product, delivery, customer, and commercial learning had to become one operating rhythm.

So we built it. We clarified decision rights. We installed a weekly operating cadence. We built a metrics stack and created a single view across product, delivery, and growth. That cadence helped onboard first customers, turn deployments into referenceable outcomes, refine the roadmap, and start the go-to-market engine.

Different category. Same principle. Create the cadence. Create the clarity. Let the organisation learn faster.

## How I would structure it now

If I were advising an early-stage CEO, a scale-up executive, or an operator in a complex organisation today, I would start by asking one question. What is the heartbeat of the business?

For a product-centric company, I like a Wednesday-to-Wednesday product cycle because it gives the week shape. The exact days matter less than the principle. The company needs a rhythm that matches how value is created. It needs a small number of fixed forums that create clarity without filling the calendar. It needs written context before meetings so the meeting itself is for decisions, not information transfer. It needs clear decision makers, visible metrics, bottom-up feedback channels, and a way for daily work to connect to quarterly goals and company mission.

The objective is not to create a beautiful operating model slide. The objective is to create an organisation that can learn.

Monday is re-entry, customer signal, firefighting, and preparation. Tuesday is executive alignment and product decision-making. Wednesday is sprint launch or deployment. Thursday is commercial, customer, safety, compliance, or operating cadence depending on the business. Friday is finance, resourcing, and runway discipline. The second week is monitoring, evaluation, and preparation to repeat the loop.

The structure can be adapted to any context. The logic should not change. Observe the work. Orient around the signal. Decide with clarity. Act with ownership. Repeat until the organisation becomes faster, not just busier.

## Build it deliberately

Operating rhythm is one of the most underappreciated tools available to leaders. It is not corporate theatre, bureaucracy, or a calendar full of meetings. Done properly, it is the scaffolding that lets an organisation learn at speed without falling over.

The military taught me that repetition creates freedom under pressure. Pollen and Deloitte taught me that cadence can unlock the capability of teams across messy, real-world organisations. Swoop taught me that field learning can become product advantage when the whole company is structured to absorb it. Vissibl reminded me that even in software, especially compliance-grade software, traction only becomes momentum when product, delivery, and go-to-market learn together.

So my advice to founders, executives, and operators is simple. Do not just hire smart people and hope the learning happens. Structure the learning. Build the rhythm. Decide how information moves. Decide who owns decisions. Decide how customer signal becomes product, how product becomes delivery, how delivery becomes growth, and how the team knows whether today's work is connected to the mission.

Build the scaffolding early. Then let the organisation learn faster than the world changes around it.

This is one of a pair of essays on operating rhythm. The companion piece, [Speed of Learning Is Competitive Infrastructure](/writing/speed-of-learning-is-competitive-infrastructure), makes the case for why this matters: how learning loops compound, what happens when they break, and why AI makes cadence more important, not less.