fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 27439–27446

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:00:13 UTC

A.15.2:2 - Problem (what breaks without WorkPlan)

  1. “Workflow = schedule” conflation. Flowcharts or code are used as calendars; resource clashes and SLA misses follow.
  2. Plan and occurrence blur. Gantt bars or Kanban tickets are reported as if the work already happened; audits and costing degrade.
  3. Specification and time leakage. People and calendars creep into MethodDescriptions; reuse and staffing agility collapse.
  4. No variance model. Without planned baselines, planned-versus-actual deviations in time, cost, and quality cannot be explained or improved.
  5. Structure entanglement. BoM and org charts get baked into “process” views; plans become brittle and unmaintainable.