Stakeholder mapping.
Identify who decides, contributes and needs an update.
Map the people
Create a shared outline with an owner, a review date and space for decisions. Use it as the starting point for the next conversation.
Map the people: record the project-specific decision, who owns it and what would cause the team to revisit it.
Set decision rights
Use a short intake form to capture the requester, the outcome and the date. Review new entries together before assigning an owner.
Set decision rights: record the project-specific decision, who owns it and what would cause the team to revisit it.
Agree a communication rhythm
Group the records by status and review what changed. Open a source note to see the detail behind a weekly summary.
Agree a communication rhythm: 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