DailyWF / Projects
Project Plan
Turn a charter into phases, tasks, owners, dependencies, and checkpoints.
Project use
Use this after charter approval to turn intent into sequenced, owned work.
- Break the work into phases, deliverables, owners, dependencies, and checkpoints.
- Define acceptance criteria and validation before execution begins.
- Sequence work around risk, lead time, and irreversible decisions.
- Create communication and review cadence appropriate to project size.
- Update the plan when reality changes; do not preserve a false forecast.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Treating the initial plan as truth after assumptions change.
Use notes
| Best trigger | Use before a project decision becomes expensive to reverse. |
|---|---|
| Evidence | Keep enough context to explain the decision later without reconstructing conversations. |
| Review point | Review when scope, stakeholder expectation, timing, risk, or ownership changes. |
Related pages
- Project CharterDefine purpose, scope, owner, constraints, and success criteria.
- Milestone ReviewCheck whether a project should continue, adjust, pause, or close.
- Pilot PlanTest a solution with limited scope before broad rollout.
- Project CloseoutClose work formally and preserve ownership of remaining obligations.
- Project IntakeCapture a proposed project before committing time or budget.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.