4C Macroscope · The Diagnostic

The Four Cs

A diagnostic sequence, not a scorecard. Each C is a question about a different layer of an organization — and the order matters, because a failure at one layer masquerades as a failure at another.

1 · Clarity of Vision

Do you know what game you’re playing? Clarity is not a mission statement or a set of values on a wall. It is a shared, accurate model of the actual game: what terrain you’re on, what winning requires, what the real constraints are, and what you are choosing not to do.

Most dysfunction that looks like poor execution is actually a clarity failure in disguise. When people are working hard in different directions, the problem is rarely effort — it’s that no two people are playing the same game in their heads. Clarity failures are the most expensive because they are the hardest to see: everyone is busy, everyone is competent, and the organization is confidently building the wrong thing.

2 · Capability of Management

Can you translate vision into coordinated action? Capability is the machinery between intent and behavior: decision rights, communication, feedback, the ability to sequence work and move a whole group together. It is the answer to “we know what to do — can we actually get everyone to do it?”

Clear vision with weak capability produces articulate failure: beautiful strategy decks and no coordinated movement. Strong capability with unclear vision produces efficient motion toward the wrong destination. The two must be read together.

3 · Capacity of Operations

Can you actually deliver under stress? Capacity is what remains when the plan meets reality — buffers, slack, redundancy, skilled people, and the ability to absorb shock without breaking. It is measured not on a good day but on the worst day.

Optimization is the enemy of capacity. Systems tuned for peak efficiency in stable conditions become brittle the moment conditions turn hostile. The organization looks lean and healthy right up until the stress arrives — and then discovers it removed the very slack that would have let it bend instead of snap.

4 · Coherence of Execution

Do all your systems point the same direction? Coherence is the hidden variable. Each part of a system can be individually excellent while the whole works against itself, because incentives reward one thing, structure enables another, and the stories people tell point somewhere else entirely.

Coherence is not authoritarian control or forced uniformity. It is system intelligibility — the degree to which the parts understand and reinforce one another rather than quietly cancelling each other out. Incoherence is the failure mode that survives every reorganization, because reorganizations change the boxes without changing the forces between them.

How the Cs interact: why optimizing one can break another

The four are not independent dials. They are coupled, and pushing hard on one frequently degrades another:

  • Clarity ↔ Capacity. A sharper, more ambitious vision raises the bar — and can quietly consume the operational slack that made the organization resilient.
  • Capability ↔ Coherence. Strengthening central management to move faster can override the local feedback that kept the parts aligned with reality.
  • Capacity ↔ Coherence. Efficiency drives (cutting capacity) usually cut it unevenly, leaving some parts starved and others fed — breaking coherence.
  • Clarity ↔ Coherence. A vision that is clear at the top can be incoherent on the ground if it wasn’t translated into the incentives people actually face.

Every intervention on one C is a bet against the others. The Macroscope’s job is to make that trade visible before you make it by accident.

Three ways to run the diagnostic

Trace-back
Start from the visible symptom and ask, for each C in turn: is this the layer that’s actually broken, or is it inheriting the break from the layer above? Keep climbing until the symptom stops explaining itself.
Stress test
Imagine the worst plausible day. Which C gives way first? The one that fails under imagined stress is usually the one silently constraining you on ordinary days.
Cross-scale
Run the same four questions at two adjacent scales (team and org, or org and sector). A failure that appears at both scales is structural; one that appears at only one is local.

What this framework can’t do

The 4Cs diagnose; they do not prescribe. They will tell you which layer is failing and why the layers interact — but not the specific move that fixes it, which always depends on context, power, and history. It is a lens for orientation, not a substitute for judgment, domain expertise, or the messy work of intervention. Read alongside Intervention Design Thinking, which designs the maneuver the diagnosis makes possible.