Any phase · Onboarding
Learn the technical landscape
Understand the systems behind the product, their constraints and the technical debt, so you can plan realistically.
About 2-5 daysEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Technical and AI fluency
- PM types
- All
- Product types
- All
- Starting points
- Partway through a buildRunning a live product
- Ways of working
- All
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- Ask an engineer to draw the main systems and how they connect.
- Learn which systems are owned by other teams.
- Ask about the biggest technical risks and debt.
- Learn how releases work and how often.
- Note constraints that will affect your plans.
Intermediate (1 to 4 years)
- Understand architecture and dependencies.
- Review technical debt and risks.
- Learn the release process.
Experienced (5+ years)
- Assess technical strategy and its fit with product strategy.
- Identify platform dependencies.
- Agree technical health priorities with engineering.
Who can do this
Owner: Product manager
Can be delegated to
- Tech Lead or Architect: Explain the architecture and debt
Reviewed by: Tech Lead
Tool examples
- GitHub
- Read the README and architecture notes.
- Miro
- Redraw the architecture and check it with engineers.
Definition of done
- Architecture understood
- Risks and debt known
- Release process understood
Common pitfalls
- Skipping it because you are not technical
- Ignoring other teams' systems
- Promising dates without understanding constraints