Project management.
Bring the brief, milestones and weekly review into a single working plan.
Write a project charter
Group the records by status and review what changed. Open a source note to see the detail behind a weekly summary.
Write a project charter: record the project-specific decision, who owns it and what would cause the team to revisit it.
Assign a milestone
List the outcome, the owner and the next checkpoint. Keep the supporting brief one click away as the work moves forward.
Assign a milestone: record the project-specific decision, who owns it and what would cause the team to revisit it.
Review the work
Start a page with a short summary, add the relevant context and finish with the decision or next action.
Review the work: record the project-specific decision, who owns it and what would cause the team to revisit it.
Close the loop
Set aside focus time, attach the brief to a meeting and review the week before moving a deadline.
Close the loop: record the project-specific decision, who owns it and what would cause the team to revisit it.
More in this collection.
- Iterative planning
- AI product roadmap
- Bug management
- Cross-functional projects
- Engineering project management
- Engineering roadmap
- Engineering workflow
- Project charter
- Technical specifications
- Issue tracking
- Lean product management
- Multiple projects
- Product backlog
- Product launch plan
- Product dashboard
- Product management workflow
- Product specifications
- Project documentation
- Project risks
- Project framework
- Project planning guide
- Project milestones
- Project roadmap
- Project tracking
- Scope statement
- Delivery approaches
- Software delivery strategy
- Sprint planning
- Stakeholder mapping