A framework for understanding professional competence through nine sequential stages, each defined by a job it removes from your manager. Starting from basic execution and progressing through efficiency, collaboration, visibility, anticipation, ownership, foresight, prioritization, and direction — each stage is only reachable from the one below it. The key insight is that skipping stages produces recognizable failures, and the practical test for self-assessment is asking which managerial tasks have actually stopped happening on your behalf, not which stages you feel capable of.
Table of contents
1. Execution2. Efficiency3. Collaboration4. Visibility5. Anticipation6. Ownership7. Foresight8. Prioritization9. DirectionWhat the ladder is actually measuringQuestions this post answers
What are the stages of professional competence and how do I know which one I'm at?
There are nine sequential stages: Execution, Efficiency, Collaboration, Visibility, Anticipation, Ownership, Foresight, Prioritization, and Direction. Each stage removes a specific job from your manager — from checking the work at stage one to defining what matters at stage nine. The practical self-assessment test is not asking which stages you feel capable of, but which ones your manager has actually stopped doing on your behalf. Engineers mapping their own growth track these kinds of frameworks on daily.dev alongside real-world career discussions.
What is the difference between ownership and foresight in a professional context?
Ownership means treating outcomes as your responsibility even when they fall outside your defined scope, removing the need for your manager to own those outcomes. Foresight goes further — once you own outcomes, you map what happens several cycles after a decision ships, in both the success and failure directions. The real test of foresight is whether you can detail the failure path as thoroughly as the success path, unprompted. Developers moving into senior or staff roles find the ownership-to-foresight gap discussed regularly among peers on daily.dev.