Multiple projects.
Maintain a portfolio view while keeping each team's work manageable.
Choose a common status model
Map one source of information to a workspace record, then document who maintains it and how a teammate can use it.
Choose a common status model: record the project-specific decision, who owns it and what would cause the team to revisit it.
Review shared dependencies
Start with an observation and a concrete example. Collect comments on the same brief before recording the next decision.
Review shared dependencies: record the project-specific decision, who owns it and what would cause the team to revisit it.
Resolve competing priorities
Follow a short studio tour, try the workflow in your own notebook and return to the help directory for the next step.
Resolve competing priorities: 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
- 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