Studio field guide
Engineering project management.
Bring technical risk into the project's planning rhythm.
Write a technical brief
Start a page with a short summary, add the relevant context and finish with the decision or next action.
Working note
Open Capture →Write a technical brief: record the project-specific decision, who owns it and what would cause the team to revisit it.
Track dependencies
Choose an example, open its preview and save a copy to your browser notebook. Edit the copy to suit your next project.
Working note
Open Template marketplace →Track dependencies: record the project-specific decision, who owns it and what would cause the team to revisit it.
Schedule review points
Set aside focus time, attach the brief to a meeting and review the week before moving a deadline.
Working note
Open Calendar →Schedule review points: 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 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
- Stakeholder mapping