The knowledge journey
For engineers, engineering managers 5 min read
A staged path from project context to engineering-ready. Each stage unlocks when the one before is done.
Understand before you operate. The knowledge journey takes a new engineer through what they need to know about their project, in order, before they're trusted to change it.

Stages
The journey runs through ten stages: Project Context, Architecture, Services, Toolchain, Infrastructure, Deployment, Observability, Operations, Safe Contribution and Engineering Ready. A stage stays locked until the stages before it are complete.
Complete a stage
Each stage has nodes. Each one says why it matters and what it's grounded in.
- A content review node: read the linked material, then choose Mark reviewed.
- A knowledge check node: choose Start knowledge check and answer the graded questions.
Views
- Focus shows one node at a time, so you work through the journey step by step.
- Timeline shows every stage, your current stage and your progress.
Readiness is a decision
Readiness is measured across dimensions, such as knowledge, tools, access and operations. Mandatory gates decide it, not an average, so strength in one area can't hide a gap in another.
A manager starts the journey from the engineer's page with Knowledge journey › Generate journey, which needs the Manage people permission.
What's next
- Engineering readiness: Readiness across all your engineers: who's ready, who's ramping, who's blocked, and where journeys stall.