The hierarchy of competence

Some people are easy to work with. Not pleasant, not agreeable, easy. You hand them something and it stops being your problem, and the relief you feel has very little to do with whether you enjoy their company.

I’ve spent a long time trying to name what those people actually do differently, because when someone asks why a peer is moving faster than they are, “they’re just really good” is a useless answer, and it’s the answer most people get. The traits involved are hard to measure, which is why they rarely survive contact with a performance rubric. They’re also very easy to observe, which is why everyone in the room already knows who has them.

So here’s an attempt at codifying it. Nine stages, in order, and the order isn’t decorative. Each stage is only reachable from the one below it, and skipping a rung doesn’t produce a shortcut, it produces a specific and recognizable failure. There’s also one test running through all nine: each stage removes a job from your manager. That’s the part you can actually see from the outside, and it’s what makes an unmeasurable thing measurable.

1. Execution

You do the work to the expected standard. This is the floor, and nothing above it counts if this one fails. Your manager still checks the work here, not out of distrust, but because completion and quality aren’t yet guaranteed without someone looking.

Careers do stall at this stage, but fewer than people assume, because failing here is loud. It gets caught in a review, it gets named in a performance cycle, and everyone involved knows what’s wrong. Every stage above this one is quiet, which is what makes them dangerous.

2. Efficiency

Now you do the work well. But are you getting faster at it, and are you finding lower-effort, lower-cost routes to the same outcome? Efficiency has to come after execution, because you can’t identify the fat in a process you haven’t already done the standard way. You need a baseline before you can optimize against it, and people who try to optimize before they have one usually just cut the parts they didn’t understand.

Efficient work pays out twice. It buys you the bandwidth to collaborate instead of just transact, and it compounds directly into output, through more cycles of iteration and more net work per person in the same amount of time.

This is where most people actually plateau, not at stage one. They meet expectations, then repeat the same method for years, capped on output with no visible reason, because they’re still technically performing. Nobody flags it. There’s nothing to flag.

3. Collaboration

Now you’re doing the work fast and well. But are you making it easier for the people around you to do theirs? Collaboration requires efficiency first, because someone still buried in the slow version of the work has no slack to invest in anyone else’s. The room to help is a byproduct of not needing all of your own time for yourself.

It shows up as unblocking a teammate before they’ve asked, sending someone downstream the thing they were going to need on Thursday, and noticing the friction you personally create for the group and removing it. That last one is much rarer than the first two, because it requires entertaining the possibility that you are the friction.

4. Visibility

Now you’re working well and working well with others. But does anyone know what you’re doing without asking? Visibility requires collaboration first, because accurate reporting depends on already coordinating with the people the work touches. A report with no collaboration behind it is just noise wearing an update’s clothes, and I’ve read plenty of those, confident summaries written by someone who hadn’t spoken to any of the three people who could have told them the date had already moved.

Done right, your manager stops chasing status, because the work reports itself, clearly, to the right people, without being asked.

5. Anticipation

Reporting the work well means you’re looking, closely and often, at where things stand. So when something is about to go sideways, does that same close look catch it before it lands, or only after? Anticipation requires visibility first, because the habit of reporting status accurately is the habit of tracking status closely, and you can’t notice a problem in work you aren’t already watching.

Reporting looks at what happened. Anticipation takes that same attention and points it at what’s about to happen. In practice it’s the shift from bringing your manager a question to bringing them a risk, an option, and a recommendation.

6. Ownership

Now you catch problems early. But do you treat them as yours to fix when nobody has assigned them to you? Ownership requires anticipation first, because you can’t commit to owning a problem you haven’t already learned to spot early. Without anticipation, ownership is just reactive heroics: someone visibly rescuing a situation they could have quietly prevented two weeks earlier, and collecting more credit for the rescue than the prevention would ever have earned.

Done well, your manager stops worrying about an entire area, because you treat the outcome as your responsibility whether or not it sits inside your defined scope.

7. Foresight

Now you own outcomes beyond what’s assigned to you. But have you mapped what happens several cycles after this one ships, in either direction? Foresight requires ownership first. Mapping future cycles for something you have no stake in is a thought exercise, but once you own the outcome, you map it out of self-interest, because you’re the one who has to live with whatever happens next. If it works, what does it trigger, and is the team ready for that. If it fails, what’s the fallback, and how fast can you catch it.

This is the stage most high performers fake. They describe the win branch with real confidence and then go quiet on the loss branch, because planning for failure feels like admitting it’s likely. The actual test is whether you can lay out the failure path in as much detail as the success path, unprompted.

8. Prioritization

Now you own several things, and you’ve mapped where each one leads several cycles out. But with all of them competing for the same hours, do you know which one deserves them first? Prioritization requires foresight first, because ranking effort by real business impact only works once you can see where each option ends up, not what it looks like today. Without that forward view you’re ranking by urgency and volume, which is how the loudest thing in the room keeps winning.

This stage is judgment under constraint. You’re weighing things you’re already responsible for against each other, and putting your limited time against the one that matters most, knowing the others will visibly suffer for it.

9. Direction

Now you can see several cycles past your own decisions, and you know how to sequence your time against what matters most. But can you decide what’s worth deciding at all, for yourself and for other people? Direction requires prioritization first, because setting goals for others means you can already rank what deserves attention, rather than executing against whatever’s loudest. At this stage nobody is handing you the goals. You set them.

What the ladder is actually measuring

Read the nine stages again as a list of things your manager no longer has to do.

By stage nine, there’s one item left in that column, which is agreeing on where you’re both pointed.

Two things worth naming before anyone tries to place themselves on this. Nobody sits at a single stage across everything they do. Most people operate several rungs higher on the work they chose than on the work they inherited, and the gap between those two numbers usually predicts what happens next better than either number does alone. And none of this maps cleanly onto titles. Levels get handed out for tenure, for scarcity, for retention, and occasionally for competence, and only one of those four is what this list measures.

So if you want to find yourself on it, don’t ask which of the nine stages you’re capable of. Ask which ones your manager has actually stopped doing on your behalf. You can answer the first question flatteringly, and you can’t answer the second one that way, which is the only reason it’s worth asking.