Example architecture

A development decision, downstream

This is an example architecture, not a client engagement. The operation is composite and the names are generic.

Context

A design-build organization where development, design, preconstruction, construction and operations each own a phase and hand over to the next.

Operational constraint

The decision is made once, early, with the least information. Everything downstream inherits it, and the people who inherit it often cannot see why it was made.

Programme change approved in developmentDecides: Development director
The decision is made once, early, with the least information. Everything downstream inherits it, and the people who inherit it often cannot see why it was made.
DevelopmentState it is left in:Decision made and recorded as an outcome, not as a rationaleDecides:Development directorSystem of record:Board paperFinds out:Immediately
DesignState it is left in:Re-solving a constraint whose reasoning was not carried overDecides:Design leadSystem of record:ModelFinds out:Next design cycle
PreconstructionState it is left in:Estimating against an assumption nobody restatedDecides:PreconstructionSystem of record:EstimateFinds out:At pricing
ConstructionState it is left in:Discovers the constraint as a field conditionDecides:Project managerSystem of record:RFI logFinds out:On site
Turnover and operationsState it is left in:Inherits a building whose decisions are undocumentedDecides:OperationsSystem of record:O&M handoverFinds out:At handover

A dashed marker means the handoff has no defined owner and depends on a person carrying the context.

The decision is made once, early, with the least information. Everything downstream inherits it, and the people who inherit it often cannot see why it was made.

How to read it

  • The decision propagated. The reasoning did not, and the reasoning is what downstream functions actually needed.
  • An RFI at construction is often a decision being re-made, not a question being asked.
  • Carrying rationale forward is an architecture problem: it needs an owner, a place to live and a trigger that makes people read it.
  • Turnover is where undocumented decisions become someone else's operating cost for thirty years.
Example architecture: a development decision through design-build | BoRo Studio