From Four Questions to a System

Why the Adaptive Fitness System (AFS) exists — and how it hangs together.

I started with four stubborn questions that kept reappearing in every change context:

  • Fit for purpose
  • Fit for context
  • Fit for execution
  • Fit for improvement

Over time, I realized these weren’t just coaching prompts. They function as a decision model: a way to test assumptions before investing, and to diagnose why change stalls once underway.

That insight became the bridge from four questions to what I now call the Adaptive Fitness System (AFS).

AFS is not a framework, a methodology, or a new “agile religion.”
It’s an approach for navigating change when you don’t fully control the terrain — by making fitness visible and friction discussable.

Fitness vs. friction

Most “resistance to change” is better understood as friction:

Friction is what happens when the system makes the desired behaviour expensive, risky, or irrational.

  • misaligned incentives → compliance theatre
  • heavy governance → delays
  • conflicting priorities → politics
  • overload → burnout and blame

AFS shifts the question from “How do we get people to adopt the change?” to:

“What would make this change fit — so it can survive contact with reality?”

AFS as a two-level approach

AFS is intentionally built in two levels:

Level 1 — Core building blocks

These are the mechanics of the decision model:

  1. Four Questions for Fitness — the entry diagnostic
  2. Fitness Dial — a quick baseline reading (using the four questions)
  3. AFS Compass — orientation across perspectives and trade-offs
  4. Validation Lens — turn decisions into testable assumptions (early signals)
  5. AFS Engine — the operating loop: sense → decide → validate → adapt

Each element is simple on its own. The power comes from how they combine.

Level 2 — Capability domains

These describe what the system develops in real organisations:

  • Beyond Agile stance — practice over ideology; outcomes over rituals
  • Adaptive Intelligence — sense–learn–adapt without thrashing
  • Reverse Validation — validate backwards from outcomes (early evidence)
  • Portfolio coherence — sequencing, capacity, WIP limits, stopping rules

In other words: Level 1 is how AFS works.
Level 2 is where it shows up as capability.

The repeating interaction pattern

AFS runs as a loop at multiple altitudes (team, product, portfolio, leadership):

Dial → Compass → Lens → Engine → Portfolio → (back to Dial)

  • Dial makes friction and weak fitness visible
  • Compass forces explicit trade-offs and shared orientation
  • Lens makes assumptions testable early
  • Engine embeds learning under pressure
  • Portfolio turns learning into coherent bets (and stop-work choices)

That’s the system: not more process — a repeatable way to make change decidable, testable, and adaptable.

This page is the short, stable overview. It distills a concept that emerged through earlier reflections.
The original essay can be read on SubStack here: https://adaptiveways.substack.com/p/from-four-questions-to-a-system

(and/or a downloadable PDF when ready).