Use this first: A clear brief prevents scope drift, decision confusion, and mismatched expectations. If the brief is fuzzy, the project will be too.
| Project Name | Project Owner | Deadline | Budget |
| | | |
| Goal / Outcome | Success looks like... |
|
| Scope IN | What is included? |
|
| Scope OUT | What is explicitly not included? |
|
| Stakeholders | Success Metrics | Key Decisions | Risks |
| | | |
Project Assumptions
| Assumption | How We Will Validate It |
| |
| |
| |
Communication Rhythm
- Weekly status update:
- Decision owner:
- Escalation path:
- Reporting cadence:
wingmanprotocol.com | Free tools + printables
Tip: Mark milestones with initials, symbols, or shading. Dependencies should be visible early so blocked tasks do not surprise the team.
| Task | Owner | Status | Dependencies | Wk 1 | Wk 2 | Wk 3 | Wk 4 | Wk 5 | Wk 6 | Wk 7 | Wk 8 |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
Status Key
- Not Started
- In Progress
- Blocked
- Complete
Milestone Row
| Milestone | Target Week | Owner |
| | |
| | |
| | |
wingmanprotocol.com | Free tools + printables
Meeting 1
| Date | Meeting Purpose | Facilitator | Attendees |
| | | |
| Decisions Made | Action Item | Owner | Due Date | Parking Lot |
| | | | |
| | | | |
Meeting 2
| Date | Meeting Purpose | Facilitator | Attendees |
| | | |
| Decisions Made | Action Item | Owner | Due Date | Parking Lot |
| | | | |
| | | | |
wingmanprotocol.com | Free tools + printables
Run this after delivery: Separate facts from feelings. Celebrate what worked, capture what failed, and name the process changes that will make the next project smoother.
What Went Well
What Didn't Go Well
What to Try Next Time
Process Improvements
Team Recognition
| Name | Contribution to Recognize |
| |
| |
| |
Key Metrics
| On Time? | On Budget? | Goal Achieved? | Stakeholder Satisfaction |
| | | |
wingmanprotocol.com | Free tools + printables