The hierarchy of competence

Some people are just easy to work with. Hand them something and you can forget about it. That’s the whole feeling, and it has nothing to do with being pleasant. I’ve known very pleasant people I wouldn’t trust with a real deadline.

For years I tried to name what the good ones do differently. “They’re just good” isn’t an answer, it’s a way of not answering. No review form has a box for “the thing didn’t come back to me,” so this particular skill stays off the page entirely. Watch the same person for a week, though, and you already know exactly who has it.

Here’s my attempt at naming the whole thing: nine stages, in order. The order isn’t optional. Skip a rung and you don’t get a shortcut, you get 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 outside, and it’s what turns something invisible into something you can point to.

Execution

You do the work to the expected standard. That’s the bar. Nothing above it counts if this one fails.

Your manager still checks this work. Not out of distrust. Finished and correct isn’t automatic yet, so someone still has to look. Careers do stall here, but less than people think, because failing at execution is loud. Miss a deadline and it shows up right away. Get a number wrong and review catches it. This is the one stage where the system tells you something’s wrong on its own. Every stage above this one is quiet. That’s what makes them dangerous.

Efficiency

Same work, but faster and cheaper. Here’s the catch: you can’t spot the fat in a process you haven’t run the slow way at least once, so efficiency has to sit on top of execution, not swap in for it. Skip that step and you cut blind, and whatever you skipped understanding is the first thing that goes.

Getting efficient pays out twice. It buys you room to help someone else instead of just moving your own work forward. And it compounds, because more cycles in a 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 same method for years. Output stays capped, and no review catches it, because on paper you’re still doing fine.

Collaboration

Being fast doesn’t make you easy to work with. I’ve sent a teammate the file before they asked for it. I’ve flagged a blocker on someone else’s task a day before it would have cost them a day. Those are the easy version. The hard version is noticing the friction you create for other people and fixing it yourself, which means admitting the friction might be you.

None of this works if you’re still buried in your own backlog. Whatever room you have to help other people is just what’s left over once your own work stops swallowing the whole day.

Visibility

Now the test changes. Does your manager know what you’re doing without asking? A status update is only as good as the coordination behind it. Skip that coordination and the update becomes guesswork wearing a nice format. I’ve read plenty of those. Confident, specific, and wrong, because the person writing it hadn’t talked to the three people who would have told them the deadline moved.

Get this right and your manager stops chasing status altogether, because it lands on their desk before they even think to ask for it.

Anticipation

Reporting looks at what already happened. This stage points the same attention forward, at what’s about to happen instead. The skill underneath both is the same one: paying close attention to where things actually stand. Do that closely enough, and you catch a problem from a hunch, days before it would otherwise show up as a message.

It shows up in what you walk in with. Instead of a question, there’s a risk you already named, an option you already weighed, and a recommendation sitting right on top.

Ownership

Catching a problem early and treating it as yours are two different skills. The second one is only possible once you’ve mastered the first, because you can’t commit to fixing something you haven’t learned to spot in time. Skip that step, and ownership turns into heroics: rescuing a situation you could have quietly prevented two weeks earlier, then getting more credit for the rescue than the quiet prevention would ever have earned you.

An entire area drops off your manager’s list of worries once you do this consistently, because you’ve made the outcome yours whether or not it 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 strong everywhere else fake half of this stage. They describe the upside in real detail and go quiet on the downside, because planning for failure can feel like predicting it. The real test is laying out the failure path in as much detail as the success one, unprompted.

Prioritization

Once you own several things, 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, because ranking by real impact means knowing where each option ends up, not what it looks like today. Without that view, you rank by whatever is loudest, which just dresses up noise as a decision.

This is judgment under real constraint, not the kind you read about. You weigh things you already own against each other, spend your limited hours on the one that matters most, and watch the rest slip a little while you do it.

Direction

The last shift is deciding what’s even worth deciding on. Setting goals for other people means you’ve stopped executing against whatever screams the loudest, you’re the one deciding what deserves attention now. No one hands you the goals at this stage, you write them yourself, and living with that choice is most of what the stage 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, set the goals in the first place. By the top, there’s exactly one job left between the two of you: agreeing on where you’re both headed.

Two things worth saying before you try to place yourself on this. No one sits at a single stage across everything they touch. Most people operate several rungs higher on work they chose than on work that landed on them, and that gap alone is worth noticing. None of this maps cleanly onto titles, either. Companies hand out levels for tenure, for scarcity in the market, for retention, and, sometimes, for competence. 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. Ask me the first question and I’ll flatter myself all day. Ask me the second, and I can’t, which is exactly why it’s the better question.