Constraint Profile
The condition preventing adoption movement right now
Mode: WoZ
Constraint: —
Updated: —
This is not a problem list.
A constraint is the single condition that must change before adoption can move. This profile names that bottleneck so you can shift the system condition — not persuade harder.
A constraint is the single condition that must change before adoption can move. This profile names that bottleneck so you can shift the system condition — not persuade harder.
Current Constraint Snapshot
Dominant Constraint
—
Where it shows up
—
Gate / stage / handoff (e.g., Authority gate, Procurement review, Clinical validation)
Who feels it most
—
Risk holder / authority / ops owner (not “persona”)
What the system is protecting
—
Reputation · workload · clinical exposure · budget · precedent
Constraint Types (What the system can’t yet make safe)
These are structural conditions — not founder flaws.
Authority
Decision power is not reachable, not engaged, or not protected.
Risk
Downside is undefined, unacceptable, or lands on the wrong person.
Operational Readiness
Workflow, resourcing, or implementation sequencing makes adoption unsustainable.
Legitimacy
The system does not yet recognize the problem owner or the problem as “real here.”
Incentives
The benefits accrue to one role while cost/risk accrues to another.
Timing
The system cannot act now due to cycles, windows, or competing priorities.
Evidence Signals
What in the founder’s experience indicates this is the bottleneck?
- —
- —
- —
What Changes Conditions
Calm, concrete moves that reduce tension at the bottleneck.
- —
- —
- —
Next Condition to Test
Replace “more explanation” with a condition test:
What would need to be true for this system to say yes safely?
Adoption does not fail because founders lack effort.
It stalls because the system cannot yet say yes safely.
It stalls because the system cannot yet say yes safely.