The hierarchy of competence
Every team I’ve worked on has had one person like that: hand them something, and it’s off your plate for good, done, no follow-up needed. That’s got nothing to do with being pleasant. I’ve known plenty of pleasant people who couldn’t handle a real deadline.
I spent a long time trying to name the difference, because “they’re just good” explains nothing. No review form has a box for “the thing didn’t come back to me,” so the skill doesn’t show up on paper. Watch the same person for a week, though, and the team already knows exactly who has it, before any review happens.
So here’s an attempt at codifying it: nine stages, in order, where the order isn’t decorative. Each stage is only reachable from the one below it, and skipping a rung doesn’t create a shortcut, it creates a specific, recognizable kind of failure. One test runs through all nine: each stage removes a job from your manager. That’s the part visible from the outside, and it’s what turns something unmeasurable into something you can point to.
Execution
You do the work to the expected standard. That’s the whole bar for this stage, and nothing above it counts if this one fails. Your manager still checks this work, and it isn’t distrust. Finished-and-correct isn’t automatic yet, so someone still has to look.
Careers stall here too, but less often than people assume, because failing at execution is loud. Miss a deadline and it shows immediately. Get a number wrong and review catches it. This is the one stage where the system itself surfaces the problem for you. Everything past this point goes quiet, which is exactly why it’s dangerous.
Efficiency
Same work, but faster, and for less. Efficiency has to sit on top of execution, not replace it, since you can’t spot the fat in a process you haven’t already run the slow way once. Skip that step and you cut blind. Whatever you skipped understanding is exactly what goes first.
Getting efficient pays out twice: it buys you room to help someone else instead of just moving your own work along, and it compounds, since more cycles in the same week beats one slow, careful pass.
This is also where most careers actually flatten, not at execution. You hit the bar, find a method that clears it, and run that exact method for years. Output stays capped and no review ever catches it, because on paper you’re still doing fine.
Collaboration
Speed alone doesn’t make you easier to work with. I’ve unblocked a teammate before they asked, sent someone downstream the thing they’d need on Thursday before they even knew to ask for it. The harder version is spotting the friction I personally create for the group and fixing it myself, which only works if I first admit I might be the friction the group is quietly routing around.
You can’t do any of this if you’re still buried in your own backlog. The slack you have for other people is whatever’s left once your own work stops eating the whole day.
Visibility
The test here is different. Does your manager know what you’re doing without having to ask? A status update only holds up if real coordination sits underneath it, and skip that coordination and the update turns into guesswork with better formatting. I’ve read plenty of those. Confident, specific, wrong, because the person writing it hadn’t talked to the three people who’d have told them the deadline moved.
Get this right and it removes a category of interruption for your manager entirely. They stop having to go looking for status, because it arrives before the question does.
Anticipation
Reporting looks backward at what already happened. This stage points that same attention forward, at what’s about to happen instead. The skill underneath both is identical: paying close attention to where things actually stand. Do that closely enough and you find out about a problem from a hunch four days before it breaks, not from a message the day it does.
You can see it in what you bring your manager. A question turns into a risk you’ve already named, an option you’ve already weighed, and a recommendation attached to both.
Ownership
Catching a problem early and treating it as yours are two different acts. The second one only becomes possible once you’ve mastered the first, because you can’t commit to fixing something you haven’t learned to notice in time. Skip that step and ownership curdles into heroics: rescuing a situation you could have quietly prevented two weeks earlier, then collecting more credit for the rescue than the prevention ever would have earned.
Do this consistently and an entire area drops off your manager’s list of things to worry about, because you’ve adopted the outcome as yours whether or not it technically sits in your job description.
Foresight
Mapping what happens several cycles after a decision ships is a thought exercise, until you own the outcome. Ownership turns it into self-interest, because you’re the one who has to live with what happens next. If it works, what does it trigger, and is anything downstream ready for that? If it fails, what’s the fallback, and how fast do you catch it?
Most people who are otherwise strong at this stage fake half of it. They describe the upside branch in real detail and go quiet on the downside branch, since planning for failure can feel like predicting it. The actual test is whether you lay out the failure path in as much detail as the success one, unprompted.
Prioritization
Once you own several things, each mapped several cycles out, the hard part stops being what to do. It becomes what to do first. Foresight is what makes that question answerable at all, since ranking by real impact means knowing where each option ends up, not just what it looks like today. Without that view, you default to ranking by whichever thing is loudest, which just dresses up the loudest option as a decision.
This is judgment under real constraint, not the abstract kind. You weigh things you already own against each other, put your limited hours against the one that matters most, and watch the rest slip a little while you do it.
Direction
The final shift is deciding what’s worth deciding on at all. Setting goals for other people means you’re no longer executing against whatever demands the most attention. You’re the one ranking what deserves it. No one hands you the goals at this stage, so you write them yourself, and living with that decision is most of what the stage actually feels like.
What the ladder is actually measuring
Read the nine stages again as a list of things your manager no longer has to do: check the work, hunt for the fat in it, coordinate it, track it, worry about future risk, own the outcome, map what happens downstream, decide what matters most, and set the goals in the first place. By the top there’s exactly one job left between the two of you, and it’s agreeing on where you’re both headed.
Two things worth saying before you try to place yourself on this list. No one operates at a single stage across everything they touch, and most people sit several rungs higher on work they chose than on work that landed on them, which is itself worth noticing. None of it maps cleanly onto job titles, either. Companies hand out levels for tenure, for scarcity in the market, for retention, and, sometimes, for competence, and only one of those four is what this list actually measures.
An honest read doesn’t come from asking which of the nine stages you’re capable of. It comes from asking which ones your manager has actually stopped doing because of you. I flatter myself on the first question constantly. The second one won’t let me, which is the whole reason I keep asking it.
