The Four Questions
Vertex 1 · Differentiation
Can you say what this is in one sentence to someone who doesn't already agree?
Not what it does — what it is. The test: would someone outside it recognize the same thing you're describing?
Vertex 2 · Connection
Who specifically is affected, and how do you know — from actual exchange, not assumption?
Not who you think might benefit. Who has actually told you. Last week. In words you can remember.
Vertex 3 · Boundaries
What is this NOT? What's the smallest version that still works?
The limits, stated as information. Not what you fear it might become — what you've actually decided not to include.
Vertex 4 · Architecture
If you disappeared, what would remain?
Not whether someone would step in. What persists. The infrastructure, the records, the practices that work without you holding them up.
What your answers reveal
Re-read your four answers. The one you struggled most with — vague, qualified, "it's complicated," or simply left thin — is the development edge. Not because you're failing; because that's where the work next wants to happen. Below: what each vertex names, and what a thin answer signals.
Differentiation
Knowing what you are.
If clear: The system has a distinct identity. You can hold position under pressure without the identity dissolving into context or hardening into defense.
If thin: The system coordinates but doesn't know what it is. Agreement is everywhere because there's no position from which to disagree. This often feels harmonious. It's the failure mode hardest to detect from inside.
Connection
Genuine contact with what's outside.
If clear: The system updates based on what's actually arriving, not on a model of what should be there. Both you and the people involved are changed by the exchange.
If thin: The system is structured but isolated. Perfect processes, zero genuine exchange. It produces work nobody needs because it's stopped checking whether the world moved.
Boundaries
Legible limits that serve form.
If clear: The limits are visible as information rather than apology. Constraints generate the form. The "no" lands as data, not as rejection.
If thin: The system flows without holding. Generous to the point of dissolution. Everything circulates, nothing accumulates. The most seductive failure mode because it looks like virtue.
Architecture
Building beyond yourself.
If clear: Capacity has become infrastructure. The work persists in your absence. Documentation, designed environments, practices that function without ongoing personal effort.
If thin: The system is coherent but ephemeral. Beautiful in the moment, gone when the moment passes. Brilliant practice whose knowledge dies with the practitioner.
The weakest answer is your development edge. Not a problem to fix — a place the work wants to go next.
Run this again in a month on the same system. Notice what changes when you've held the edge in attention. The diagnostic is the practice, not the verdict.