The AFS Engine
The Loop That Turns Fitness Into Practice
Part of the Adaptive Fitness System (AFS) series. This post unpacks Level 1, Building Block 4: the AFS Engine.
I had a car once with a nearly perfect dashboard. Every warning light worked. Every gauge was accurate. The fuel readout was so precise my mechanic said he’d never seen anything like it.
The engine seized at 80,000 kilometers.
Information without a functioning engine is just very good news about a stopped vehicle. And I’ve thought about that car often when watching organizations run excellent diagnostics on themselves (thorough, honest, well-facilitated) and then wonder, six months later, why nothing actually changed.
Knowing your fitness level doesn’t make you fit. Something has to convert the knowing into movement.
That something is Building Block 4.
Where we are
Level 1 of the Adaptive Fitness System is the foundation layer — four building blocks that have to be in place before the capability domains on Level 2 can do their work.
Building Block 1: the Four Questions and the Fitness Dial. A recurring check on where you are across the four fitness dimensions.
Building Block 2: the AFS Compass. An orientation device that maps the four pulls — Value, Learning, Stability, Control — and helps you recognize which tension you’re actually navigating.
Building Block 3: the Validation Lens. The discipline of knowing what you actually know: surfacing assumptions, designing small tests, detecting early signals before they become expensive surprises.
Building Block 4 — today’s post — is the AFS Engine. The loop that takes everything the first three building blocks produce and turns it into adjusted practice.
After this, we move to Level 2. But Level 1 doesn’t work without the Engine. None of it does.
What a loop actually means
The word “loop” gets used a lot in organizational thinking. Feedback loop. Learning loop. Improvement loop. It’s become so common it’s nearly empty.
So let me be precise about what I mean.
A loop, in the AFS sense, has four beats. They are not phases. They don’t have a start date and an end date. They run continuously, at whatever cadence the work demands.
Sense. Something is happening. A signal from the Validation Lens. A shift on the Compass. A Four Questions check that returns a different reading than last month. The organization is receiving information about its current state — whether it wants to or not.
Interpret. What does this signal mean? This is not the same question as “is this signal bad?” It’s a harder question. Context matters here. The same reading on the Fitness Dial can mean very different things in a team at the start of a transition versus a team twelve months in. Interpretation without context is just pattern-matching to prior experience, which is precisely how organizations keep making the same mistakes in new situations.
Decide. Not every signal requires action. That’s important to say clearly, because there’s a version of “agile responsiveness” that degenerates into constant thrashing — reacting to everything, committing to nothing, confusing motion with adaptation. The decision beat asks: given what we’re sensing and what it means, what — if anything — should change? And who decides that?
Act. This is where most loops die. The sensing was honest. The interpretation was careful. The decision was sound. And then the organization encounters its own immune system — the structures, incentives, habits, and power arrangements that keep things as they are. Acting means making a specific, observable adjustment to how work actually gets done. Not a slide. Not a principle. A practice.
Then you sense again. Because acting changes the system, and a changed system produces new signals.
That’s the loop.
Why the Engine is what makes the other three blocks matter
Think of what you’ve built so far at Level 1.
The Four Questions give you a recurring read on your fitness. The Compass tells you which direction you’re being pulled. The Validation Lens keeps your assumptions honest and surfaces early signals.
All three produce something valuable. All three are pointing at information.
The Engine is what you do with it.
Without the Engine, the Four Questions become a ritual — a quarterly ceremony that produces a score everyone discusses and nobody adjusts behavior around. The Compass becomes a map you look at before putting it back in the drawer. The Validation Lens becomes a set of fascinating discoveries that get presented in retrospectives and forgotten by the following sprint.
I’ve seen all three of those failure modes in organizations that had genuinely good diagnostics. The diagnostics weren’t the problem. The absence of a functioning conversion mechanism was.
The Engine doesn’t make the other blocks more accurate. It makes them consequential.
What breaks the loop and where
In my experience, loops break at predictable points.
The most common is the transition from Interpret to Decide. Organizations are reasonably good at sensing — bad news travels eventually, signals accumulate. They’re even reasonably good at interpretation, when given a structured way to do it. Where things collapse is the moment someone has to say: this means we need to change something. Because changing something means someone’s current arrangement gets disrupted. And in most organizations, the people with the clearest view of what needs to change are not the people with the authority to change it.
This is not a morale problem. It’s a structural one. The Engine exposes it.
The second break point is Act. Even when a decision is made, the distance between “we’ve decided to change this” and “the change is visible in how work gets done on Tuesday morning” is enormous. Most change programs live in that distance and call it implementation. The Engine doesn’t cross that distance for you — but it makes the distance visible, which is the first step toward doing something about it.
The Engine as a fitness practice, not a project
Here’s what distinguishes organizations that actually build adaptive capacity from those that periodically attempt to.
The ones that build it stop treating improvement as a project with a start and end date, and start treating it as a practice — something that runs continuously alongside the work, not as a separate workstream above it.
The Engine is designed for that. It doesn’t require a transformation program to run. It runs at team level, at value stream level, at portfolio level — wherever there are signals worth sensing and decisions worth making. Its cadence adapts to context. A team in rapid learning mode might be running the loop weekly. A stable operational unit might run it monthly. What matters is not the frequency — it’s that the loop actually closes. That sensing leads to interpreting, interpreting to deciding, deciding to acting, and acting back to sensing.
When that loop closes consistently, something shifts. The organization stops experiencing change as something that happens to it — a disruption arriving from outside, requiring heroic response — and starts experiencing it as something it does, routinely, as part of how it works.
That’s the move. From reactive to generative. From transformation as event to adaptation as capacity.
Closing Level 1 of the AFS
Four building blocks. Each one necessary. None sufficient on its own.
The Four Questions orient you to your current fitness. The Compass shows you the tensions in play. The Validation Lens keeps your learning honest. The Engine ensures that learning actually changes something.
Together, they form the foundation of the AFS — not a methodology, not a framework to comply with, but a set of disciplines that have to be practiced before the higher-order capability domains can take root.
Which is where we’re going next.
Level 2 of the AFS is where fitness becomes capability — where the foundational disciplines we’ve been building start showing up as organizational competencies that compound over time. We’ll introduce the structure of Level 2 in the next post, and then move through each capability domain in turn.
If you’ve been following the series from the beginning: thank you for staying with it. The foundation work is rarely glamorous. But there’s no shortcut through it.
If you’re joining now: the prior posts are in the archive. The series is designed to be read in order — not because it’s complicated, but because each piece is load-bearing.
A question to close on
Where does your organization’s loop break? Is it at the sensing — signals that never surface? At the interpretation — data that sits without meaning being made of it? At the decision — clarity that never converts to commitment? Or at the act — intentions that dissolve before Tuesday morning?
Most organizations I’ve worked with have a predictable break point. Finding it is more useful than fixing everything at once.
Drop your answer in the comments. I read them all.
Adaptive Ways Publications
Licensed under Creative Commons Attribution 4.0 International (CC BY 4.0)
Share freely with attribution.