Product specifications.
Give a team the context it needs to decide what to build.
Describe the user problem
Group the records by status and review what changed. Open a source note to see the detail behind a weekly summary.
Describe the user problem: record the project-specific decision, who owns it and what would cause the team to revisit it.
Set acceptance criteria
Keep the original observation beside the decision it informed. Search a project name to retrieve the supporting notes.
Set acceptance criteria: record the project-specific decision, who owns it and what would cause the team to revisit it.
List unresolved decisions
Write the steps once, then use the studio checklist to review each item in order and mark it complete.
List unresolved decisions: 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
- 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