Concept
Waterfall
Waterfall is used in a software engineering sense. Waterfall refers to a phase-sequenced development model where requirements, design, implementation, testing, and release are treated as largely distinct stages with formal handoffs and review gates.
Recognition signals
- milestone completion stays green while integration risk accumulates under separate team reviews
- analysts, designers, developers, testers, and operators hand work sequentially without shared consequence
- contracts and budgets solidify before the full system meets realistic load or usage
- late-stage discovery turns small technical fixes into multi-team coordination events
- phase completion rewarded more strongly than exposure to operational reality
Questions to ask
- Where in this plan does consequence first return with enough context to redesign cheaply?
- Which handoffs separate decision-makers from the runtime effects of early choices?
- Does status reporting track conformance to plan or learning from reality?
Counterbalances
- insert early integration probes before commitments spread across layers
- keep one cross-phase owner accountable for end-to-end consequence return
- use phase gates to force learning, not only to prove documentation completeness
Trajectory
Early signals
- requirements and design phases complete with excellent artifacts but little runtime contact
- teams optimize local phase deliverables on independent calendars
Intensification
- integration month compresses delayed feedback into organization-wide shock
- fixing issues requires renegotiating contracts, vendors, and approvals embedded across phases
Failure modes
- systems appear highly coordinated while learning remains weak until late catastrophe
- responsibility spreads so widely after late failures that no boundary owns redesign
Restoration paths
- shorten feedback paths between phases without abandoning large-program visibility needs
- treat late integration findings as structural signals, not one-time bad luck
Manifestations
software
- enterprise program reports healthy milestones until interfaces conflict under realistic load
organizations
- government procurement tracks phase completion while operational harm arrives years later
leadership
- program managers rewarded for on-time phase gates before systems prove they work together
politics
- defense software standards emphasize specification-heavy review over timely consequence return
