Primitives
Primitives are the foundational conditions that allow people to connect, coordinate, repair, and preserve agency inside a system. Communication, Clarity, Consistency, Commitment, Claiming, and Consent.
The Cubed Method™
A missed deadline may reflect a problem elsewhere in the business. The Cube helps us examine the People, Processes, and Products involved before deciding what to change.
Why a Cube?
A missed deadline might begin in a Process nobody can reliably follow. People may be the ones filling the gaps, even though they didn’t create the problem. Or the Product may be promising something the system was never built to support. Looking across all three changes the diagnosis: the first symptom we notice isn’t automatically the source of the problem.
Select a Dimension, Facet, or Vector to examine the business from that perspective. Each definition includes a question to help you apply it.
Drag to turn it. It spins on its own until you do.
Dimensions
The three Dimensions are People, Processes, and Products. Examining them together helps us locate the cause of a problem, including when it differs from where the effects are felt.
The six Facets describe different kinds of action. We use them to consider which response is appropriate to the situation.
Four forces moving through the Cube show what kind of pressure the system is under and what must be balanced. None is a score to maximize in isolation.
Select one to see its definition and a question you can use.
People
People are where the system becomes lived experience. They bring judgment, skill, memory, care, and capacity, and they’re usually where strain becomes visible first.
Ask: What work has someone taken on because the formal process does not account for it?
Processes
Processes describe how work is organized and coordinated. They determine what people can rely on and what they have to arrange for themselves.
Ask: Where is the process making people remember, chase, translate, wait, or compensate?
Products
What the system makes or delivers: services, experiences, artifacts, promises, and outcomes where the work becomes visible.
Ask: What promise is the rest of the system straining to keep?
Evaluate
The turn toward understanding what is actually happening before the system commits to a change.
Ask: What would be irresponsible to change before we understand it better?
Cultivate
The turn toward strengthening capability so the system can meet future demands without requiring more compensating effort.
Ask: What capability needs strengthening before demand increases?
Accelerate
The turn toward tested movement: increasing pace or load where the system is strong enough to learn under real conditions.
Ask: What is already strong enough to move faster under real load?
Anticipate
The turn toward what is approaching, so preparation happens before reaction becomes the only option.
Ask: What needs to be ready before the system is forced to react?
Illuminate
The turn toward visibility: surfacing hidden labor, cost, risk, assumptions, and dependencies so the system can read itself.
Ask: What hidden cost, labor, risk, or dependency needs to become visible?
Cooperate
The turn toward coordinated action across boundaries, so one part does not succeed by pushing its cost into another.
Ask: What has to move together for one part to stop pushing cost into another?
Stability
The force that keeps a dependable structure while things move. Too little becomes wobble; too much becomes rigidity.
Ask: What must remain dependable while this changes?
Security
The force that protects what is essential without making useful movement impossible. Protection that becomes control is a distortion, not safety.
Ask: What must be protected, and what control is no longer buying safety?
Scalability
The force that lets load increase without distorting the system or multiplying cost faster than value.
Ask: What becomes more expensive every time this grows?
Sustainability
The force that lets the system continue without consuming the people, trust, resources, and meaning that make continuation possible.
Ask: What are we spending now that the system will eventually need back?
The Cube is simple enough to use because it doesn’t try to show everything at once. Primitives define the conditions that let people connect, coordinate, repair, and preserve agency. Constants define what must remain true across the system. Operators are strategies for directing change and responding to pressure.
The deeper architecture is closer to a tesseract than a cube: the visible model is useful, but it can’t show every relationship at once.
Primitives are the foundational conditions that allow people to connect, coordinate, repair, and preserve agency inside a system. Communication, Clarity, Consistency, Commitment, Claiming, and Consent.
Constants are the invariant conditions that must remain true across the Cube while the system changes. Autonomy, Accessibility, Authenticity, Accountability, Adaptability, and Alignment.
Operators are strategic functions applied through the Cube to guide purposeful action under pressure. Persistent Intentionality, Opportunity Premonition, Sovereign Obsolescence, Strategic Erosion, Generative Relinquishment, and Curated Refinement.
What a reading looks like
The team waits because decision context and authority are concentrated in one place. The reading looks at what needs to be visible before responsibility can move.
The reading
People feel the strain first, but the repair begins in Processes. Signal is weak because the decision context is hard to see. Shift is weak because routine decisions still return to the same person. Scalability is under pressure, so Cultivate fits better than Accelerate.
One first move: make decision criteria and current context visible enough for a project to move without routing every judgment through the same person.
Test that change on one project and watch where the decision path still stalls.

A single recurring problem gives us enough evidence to trace the pattern and name one first move worth making. That is where a Clarity Brief starts.