Plan
プラン
A plan is an organized commitment about actions, owners, resources, timing, dependencies, and contingencies for reaching an outcome. It turns direction into coordinated execution; it is more than a goal or calendar.
What it means
A plan describes how people intend to move from a known starting point toward a defined result. A decision-ready plan states the outcome, current conditions, actions, accountable owners, resources, sequence, milestones, dependencies, evidence of progress, and what to do if assumptions fail. Plans vary by scope: strategic plans guide an organization, operating plans coordinate recurring work, project plans govern a bounded delivery, and contingency plans prepare an alternative course. A goal says where to arrive; a schedule says when events occur; neither is a complete plan without the execution logic around it.
How to calculate it
There is no universal formula for a plan. Use a completeness check instead: Outcome + Actions + Owners + Resources + Timing + Dependencies + Evidence + Contingency. Quantitative estimates such as cost, capacity, duration, and probability should show units and assumptions, but adding those numbers does not by itself make the plan feasible.
What counts / what does not
Separate a decision-ready plan from a goal, forecast, calendar, or unprioritized task list. Include | a measurable outcome, baseline, actions, owners, authority, resources, milestones, dependencies, risks, evidence, and review or contingency triggers. Exclude | an aspiration without actions, a calendar without responsibilities, a forecast presented as a commitment, and a backlog with no priority or capacity decision. Scope explicitly | identify the organization, project, period, decision rights, constraints, and interfaces covered so readers know where the plan stops.
| Item | Treatment |
|---|---|
| Include | a measurable outcome, baseline, actions, owners, authority, resources, milestones, dependencies, risks, evidence, and review or contingency triggers. |
| Exclude | an aspiration without actions, a calendar without responsibilities, a forecast presented as a commitment, and a backlog with no priority or capacity decision. |
| Scope explicitly | identify the organization, project, period, decision rights, constraints, and interfaces covered so readers know where the plan stops. |
What moves the number
Start from the present state and the outcome before listing activities. Sequence work around dependencies and the constraint most likely to delay the result. Assign one accountable owner per commitment and distinguish that role from contributors or approvers. Review evidence at milestones; replan when a named assumption fails, not merely because the original document is old.
- Start from the present state and the outcome before listing activities.
- Sequence work around dependencies and the constraint most likely to delay the result.
- Assign one accountable owner per commitment and distinguish that role from contributors or approvers.
- Review evidence at milestones; replan when a named assumption fails, not merely because the original document is old.
When it helps
Teams can coordinate handoffs because actions, owners, dependencies, and decision dates are visible in one operating view. Leaders can test whether resources match commitments before approving scope, reducing plans that depend on hidden overtime or unfunded work. Reviews can compare actual evidence with the planned path and choose correction, contingency, or cancellation instead of reporting activity alone.
- Teams can coordinate handoffs because actions, owners, dependencies, and decision dates are visible in one operating view.
- Leaders can test whether resources match commitments before approving scope, reducing plans that depend on hidden overtime or unfunded work.
- Reviews can compare actual evidence with the planned path and choose correction, contingency, or cancellation instead of reporting activity alone.
How to use it
- A goal belongs inside a plan, but the goal alone does not specify the route, ownership, or resources.
- A schedule is one component of a plan and should not substitute for scope, dependencies, or success evidence.
- A useful plan records assumptions and contingencies so that change is governed rather than treated as failure.
- More detail is not always better; include the detail needed for the next decisions and the risk of the work.
- Planning is iterative: execution produces information that should refine later actions while preserving the agreed outcome or documenting its change.
Decision cautions
Treat the plan as a testable decision record: make uncertainty, dependencies, and change triggers visible. False precision in dates and costs can conceal weak assumptions; record ranges or confidence when evidence is limited. A plan with more commitments than capacity is a wish list, even when every task has an owner. Frequent undocumented changes destroy accountability; preserve the reason, approver, and effect of material replanning.
- False precision in dates and costs can conceal weak assumptions; record ranges or confidence when evidence is limited.
- A plan with more commitments than capacity is a wish list, even when every task has an owner.
- Frequent undocumented changes destroy accountability; preserve the reason, approver, and effect of material replanning.
Example
A product team must reduce onboarding abandonment from its measured baseline within one quarter. The plan names the product lead as accountable, assigns research, design, engineering, analytics, and support work, reserves capacity, and sequences user interviews before interface changes. Milestones include an instrumented baseline, prototype test, limited release, and decision review. The team tracks completion and customer behavior, not just shipping. If interviews show the main barrier is contract approval rather than the interface, a contingency shifts effort to procurement guidance and pauses the redesign. The goal remains the outcome, the release calendar remains the schedule, and the full set of choices forms the plan.
Compare with
Plan | integrates outcome, actions, ownership, resources, timing, dependencies, evidence, and contingencies. Goal | states the result to reach, such as a quality level or customer outcome, without defining the route. Schedule | places activities and milestones on a timeline but may omit why, who decides, and what happens when conditions change. Strategy | determines the governing choices and trade-offs; a plan translates those choices into coordinated execution. Tactic | is a specific action within the plan and can often be replaced without changing the strategy.
| Metric | Difference |
|---|---|
| Plan | integrates outcome, actions, ownership, resources, timing, dependencies, evidence, and contingencies. |
| Goal | states the result to reach, such as a quality level or customer outcome, without defining the route. |
| Schedule | places activities and milestones on a timeline but may omit why, who decides, and what happens when conditions change. |
| Strategy | determines the governing choices and trade-offs; a plan translates those choices into coordinated execution. |
| Tactic | is a specific action within the plan and can often be replaced without changing the strategy. |
Common mistakes
- A detailed Gantt chart is not automatically a plan; it may still omit decisions, resources, assumptions, and alternatives.
- Changing a plan is not inherently poor discipline. Uncontrolled change is the problem; evidence-based replanning is part of management.
- A plan does not guarantee the outcome. It makes commitments and uncertainty visible enough to coordinate learning and corrective action.
Frequently asked questions
What is the minimum viable plan?
At minimum, state the outcome, starting point, next actions, accountable owners, resources, timing, dependencies, evidence, and a response to the main failure condition.
How is a plan different from a forecast?
A forecast estimates what may happen under assumptions. A plan records intended actions and commitments; it can use a forecast without pretending the estimate is controlled.
When should a plan be revised?
Revise when evidence invalidates an assumption, capacity or scope changes materially, or a contingency trigger occurs. Record who approved the change and its consequences.
Can one plan contain several goals?
Yes, if priorities and trade-offs are explicit and the goals share a coherent scope. Otherwise separate plans may provide clearer ownership.