Product backlog.
Keep a useful queue of opportunities and work items.
Collect requests
Use a short intake form to capture the requester, the outcome and the date. Review new entries together before assigning an owner.
Collect requests: record the project-specific decision, who owns it and what would cause the team to revisit it.
Clarify the value
Start with an observation and a concrete example. Collect comments on the same brief before recording the next decision.
Clarify the value: record the project-specific decision, who owns it and what would cause the team to revisit it.
Select the next slice
Follow a short studio tour, try the workflow in your own notebook and return to the help directory for the next step.
Select the next slice: 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 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