--- slug: one-plan-method type: pattern summary: "Keep strategy design, participant validation, Critical Chain planning, execution measures, and audit in one revisable organizational plan." created: 2026-11-02 updated: 2026-11-02 related: strategy-tactics-tree: relation: extends note: "The S&T Tree supplies the strategy-and-tactic logic; the One Plan Method carries that logic through validation, implementation planning, execution, and audit." st-trees-organizations: relation: refines note: "Organizational S&T deployment assigns validation and ownership by management level; the One Plan Method adds an explicit recurring execution-and-learning cycle." critical-chain: relation: uses note: "The planning stage translates accepted tactics into a protected project network rather than a list of disconnected initiatives." continuous-improvement-auditing: relation: uses note: "The audit stage compares expected and actual results, separating tactic compliance from achievement of the intended performance effect." five-focusing-steps: relation: implements note: "The method applies constraint-focused learning to the organizational plan by revising assumptions and actions when evidence contradicts them." --- # One Plan Method > **Pattern:** A named solution to a recurring problem. *Keep strategy design, participant validation, Critical Chain planning, execution measures, and audit in one revisable organizational plan.* *Also known as: One-Plan Method; One Plan.* ## Context An [S&T Tree](strategy-tactics-tree.md) connects an organizational objective to the strategies, tactics, and assumptions required to achieve it. That logic can still fracture during implementation. One group validates the strategy, another turns tactics into projects, a project office manages dates, and an audit group reviews results after the fact. Each artifact may be competent while the causal thread between them disappears. Alan Barnard's One Plan Method treats that thread as the management object. TOCICO's current presentation describes five stages: Design, Validate, Plan, Execute, and Audit. The method keeps the S&T logic visible while people test its assumptions, commit to actions, schedule the work, measure what happened, and revise the plan. This is current practitioner material rather than settled Dictionary doctrine. It extends organizational S&T practice; it doesn't replace the S&T Tree or redefine its strategy-and-tactic nodes. ## Problem Large changes commonly split into separate management systems. Strategy documents explain intent. Workshops collect agreement. Project plans track tasks and dates. Dashboards show activity. Reviews compare results with targets. The division looks orderly, but it makes a failed result hard to diagnose. Suppose a tactic ran on time and the expected performance didn't appear. The project plan can confirm completion, but it can't show whether the original assumption was false. The strategy document can explain the assumption, but it may not contain the implementation evidence. The dashboard can show movement, but it may not distinguish a tactic that wasn't carried out from one that was carried out and didn't work. The organization then argues from incompatible records. One group says the project succeeded because the work finished. Another says the strategy failed because the target was missed. A third asks for another initiative. Without one connected plan, evidence doesn't reliably correct the logic that produced the action. ## Forces - **A strategy has to remain testable.** If its assumptions vanish when project planning begins, execution can confirm only task completion. - **Agreement has several meanings.** People may agree that the goal matters while rejecting the causal logic, the tactic, the resource commitment, or their own role. - **Plans compete for the same constraint.** A list of approved initiatives isn't executable until resource contention, sequence, and release are resolved. - **Activity and effect are different measures.** Running the tactic as designed doesn't prove it caused the expected result. - **Learning can destabilize ownership.** New evidence may require changing a tactic that a team has already budgeted, staffed, and defended. - **One plan can become one enormous document.** Integration helps only while each role can see the logic and decisions it owns. ## Solution Manage the change through five connected stages, preserving the links between each stage rather than producing five independent artifacts. **Design.** State one organizational goal and express the route to it as strategy-and-tactic logic. Write the assumptions that make each tactic plausible. The design is not a portfolio of desirable projects; it is a causal claim about what the system must change and why. **Validate.** Ask the people who own the affected work to challenge the goal, the need for change, the proposed direction, the risks, and the implementation conditions. Validation is not a request for ceremonial support. A reservation that defeats an assumption changes the design before resources are committed. **Plan.** Translate accepted tactics into an executable project network. Use [Critical Chain](critical-chain.md) where shared resources and uncertain durations determine the sequence. The planning stage should retain the link from each project deliverable back to the tactic and strategy it serves, so priorities don't collapse into whoever argues most loudly for a date. **Execute.** Track two different signals. Compliance measures show whether the tactic ran as intended. Performance measures show whether the expected system result occurred. A tactic can be compliant and ineffective, or effective despite imperfect compliance. Keeping the measures separate prevents task completion from masquerading as strategic success. **Audit.** Compare actual results with the assumptions and expected effects recorded at design time. Continue what works, correct incomplete execution, revise false assumptions, or stop a tactic whose expected effect didn't appear. The audit closes the loop by changing the same plan that authorized the work. Barnard's public account also describes five recurring change questions, a one-goal cascade, and a six-step focusing cycle. Those formulations reinforce the method's emphasis on focus and learning, but the accessible sources don't establish a one-to-one mapping between that cycle and TOCICO's five stages. Keep the formulations distinct unless a fuller primary treatment reconciles them. > **⚠️ Do Not Merge Compliance With Performance:** A completed tactic is evidence about execution, not proof of causation. If the tactic ran and the expected result didn't appear, the plan has learned something about its assumptions. Calling the project successful and moving on discards that evidence. ## How It Plays Out An organization uses an S&T Tree to make reliable rapid response its market strategy. The design says shorter, more reliable lead times will create a decisive competitive edge. Its tactics include changing order release, protecting the system constraint, and aligning sales promises with demonstrated operating performance. During validation, operations accepts the direction but rejects an assumption about available setup capacity. The tree changes before launch. The planning stage then turns the accepted tactics into a Critical Chain network, with the setup-capacity work preceding the market promise. Sales cannot pull the launch forward merely because its own material is ready. Execution measures show that the new release rule ran on nearly every order. The performance measure shows that lead-time reliability improved, but quoted lead time did not. Audit reveals that the sales quoting rule still uses the old risk allowance. The method doesn't call the initiative complete because operations complied. It returns the quoting assumption and its tactic to the plan, assigns the corrective work, and keeps the original goal visible. The same structure works when results disappoint. If every tactic ran and reliability didn't improve, the audit points back to the causal design. The constraint may have moved, a parallel assumption may have been false, or an omitted condition may have dominated the result. The next move is a corrected plan, not a larger batch of disconnected projects. ## Consequences **Benefits.** The method gives strategy, execution, and review a shared chain of evidence. People can trace a project to the tactic it implements, the assumption that justifies the tactic, and the performance effect it is supposed to produce. Resource priorities inherit their order from the strategy rather than from local urgency. Audits can distinguish incomplete execution from faulty logic. When evidence forces a change, the correction updates the plan instead of becoming an exception stored in meeting notes. **Liabilities.** Maintaining the connections takes discipline. A weak S&T design creates false precision downstream, while a badly built project network can make sound strategy impossible to execute. Validation can become slow if every participant is asked to approve every level. The plan can also become unreadable when it absorbs task-level detail that belongs in project systems. Finally, a single plan makes contradictions visible. Leaders who prefer separate artifacts because each can appear successful on its own may resist the method more than the operating teams do. ## Sources - TOCICO Learning Center, ["Introduction to the Theory of Constraints: Strategy & Tactics — From ONE Goal to Everyone's ONE Thing"](https://learningcenter.tocico.org/courses/Introduction-to-the-Theory-of-Constraints-Strategy-and-Tactics) (current page retrieved 2026-11-01). Institutional presentation of the One Plan Method's Design, Validate, Plan, Execute, and Audit stages; its change questions; performance and compliance measures; Critical Chain planning; and audit feedback loop. - Alan Barnard, ["Why Change Initiatives Fail and How to Pick the Right Tech"](https://www.linkedin.com/posts/dralanbarnard_why-do-most-change-initiatives-fail-and-activity-7471635639394799616-qBcR) (2026; retrieved 2026-11-01). Author-originated summary of the method's five questions, one-goal cascade, and six-step focusing cycle. The post also promotes a podcast and software, so it establishes Barnard's formulation rather than independent validation. - Lisa A. Ferguson, "Applications of Strategy and Tactics Trees in Organizations," in Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 34. The organizational S&T foundation: validation by management level, responsibility-authority alignment, and the distinction between transformation and organizational trees. - Alan Barnard, "Continuous Improvement and Auditing," in Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 15. The prior TOC treatment of change questions, implementation evidence, performance auditing, and correction when a change does not produce its expected system effect. --- - [Previous: Learning from Surprising Events](learning-surprising-events.md)