Should You Build At All?
Not all projects should be built.
In a stressed system, the most critical decision may be whether to start at all.
This walkthrough shows how a development decision
can determine whether risk is created — or avoided entirely.
Step 1 — Situation
A developer considers launching a new residential project.
- Market demand: present but uncertain
- Financing: available but conditional
- Construction: fixed-price contracts expected
- Timeline: exposed to approval and delivery delays
The project appears viable under current assumptions.
Step 2 — Collapse Signal
No failure has occurred — yet.
But early signals emerge:
- rising construction costs
- tighter financing conditions
- extended approval timelines
- builder instability in the market
Failure is not visible.
But structural pressure is already forming.
Step 3 — Governance
The project is shaped by:
- Policy constraints (planning, approvals, housing targets)
- Capital expectations (return thresholds, risk appetite)
- Contract structures (risk passed downstream)
The decision to build
locks these conditions into motion.
Step 4 — Risk Flow
If the project proceeds:
- risk is created at the development level
- transferred to builders through fixed contracts
- pushed further down to subcontractors and suppliers
The system does not remove risk.
It distributes it.
Step 5 — Decision
Surface decision:
→ Launch the project
→ Capture market opportunity
Structural decision:
→ Create downstream risk
→ Initiate risk flow
Alternative:
→ Delay or cancel the project
→ Avoid initiating risk flow
→ Do not step into the risk-bearing position
Closing Statement
Starting a project is not neutral.
It defines where risk will be carried.
In a constrained system,
the most important decision
is not to begin.
Continue
→ Understand the structural model → Structural Framework
→ See how decisions are made → Decision System
→ Compare alternative positions → Builder / Supplier Cases