You're operating as a senior individual contributor inside a leader's title.
I've been thinking about this pattern for years, and it has a specific shape. There are seven behaviors that mark it. Most newly-promoted senior leaders show five of the seven in the first year. The discomfort of recognizing them is the first step out of them.
Here's what they look like.
You're still doing work that should be delegated
You're writing the brief yourself instead of having someone on your team draft it. You're building the model in Excel. You're editing the deck the night before the board meeting. You're handling the customer escalation directly because you know how to handle it.
The reason isn't capacity. Your team is capable. The reason is reflex. You see the work, your hands start moving toward the keyboard, and the next thing you know it's eleven at night and you've spent three hours doing something a senior analyst on your team should have done in five.
Here's what's actually happening. Every hour you spend doing that work is an hour your team doesn't get to develop the muscle. They watch you do it and they think, that's how it's supposed to be done. So when you're not there, they don't try, because they've never been forced to. You're not just doing their work. You're disabling their growth.
You're being the technical expert instead of the leader of leaders
You walk into a meeting with three of your VPs. The CEO asks a question about the platform rollout. Before any of your VPs can speak, you answer it. You answer it accurately. You answer it well.
But you just signaled to the CEO that you don't trust your VPs to handle the question. And you signaled to your VPs that you'll always be in front of them in the room. So next time, why would they prepare to answer? You'll handle it.
In the new role, the meeting isn't about your knowledge. The meeting is about the system you've built. The CEO should be hearing from your team, learning what your team can do, calibrating to your team's capability. You're in the room to shape, direct, and set context, not to demonstrate.
Your calendar is dominated by execution, not strategy
Pull up last week's calendar. Count the meetings that were tactical: status updates, escalation calls, project reviews, customer escalations, problem-solving sessions on specific issues.
Now count the meetings that were strategic: annual planning, capability building, organizational design, board prep, market positioning, leadership development.
If the tactical column outnumbers the strategic column by more than three to one, you're operating at the wrong decision altitude. The role pays you for the second column. You're spending your time in the first.
This pattern is the hardest to see because tactical meetings always feel urgent. Strategic meetings always feel postponable. So they get postponed for a year, by which point you've never actually done the job.
Your first instinct in a crisis is to solve, not to direct
A customer is escalating. Production is down. A senior person has resigned suddenly. Something's broken. Watch what you do in the first ten minutes.
If your first move is to roll up your sleeves and start fixing the problem, you're operating as a senior IC.
The Leader's first move in a crisis is different. Who do I assign this to. What authority do they need. What's the cadence we'll run. When do I check in. What's my role in the resolution, which is typically context-setting, decision-making, and unblocking, rather than execution.
The Leader does not solve the crisis. The Leader makes sure the crisis gets solved by the right people, in the right way, at the right speed.
Most newly-promoted leaders fail this in the first six months. They keep diving in. The team learns that the boss handles crises. The boss becomes the bottleneck. And the leader's day becomes one crisis after another, because every problem now routes to them.
You feel productive only when handling tactical work
This one's harder to spot because it's a feeling, not a behavior. But notice it next time it happens. You spend a day in strategic meetings, alignment with peers, planning for next quarter, talking with your boss about the operating model. End of day. You feel restless. You feel like you didn't accomplish anything.
Then you spend two hours that evening answering emails and editing a document. Now you feel productive.
That feeling is the addiction.
Real productivity at your altitude rarely produces an end-of-day feeling of accomplishment. The work doesn't ship. The wins are slow. The needle is moving but you can't see it move on a given Tuesday. If you only feel productive when you've shipped something, you'll spend the rest of your tenure chasing that feeling and avoiding the actual job.
You're avoiding the meta-work
The meta-work is the work about the work. It's the stuff that doesn't feel like work because it doesn't produce a visible artifact. Thinking time. Reflection time. Calendar redesign. Forum redesign. Team development planning. One-on-one preparation. Mentoring conversations. Reading. Writing.
Most newly-promoted leaders avoid all of it. Because it doesn't feel productive. Because nobody's asking for it. Because the inbox doesn't reward it.
But the meta-work is the highest-leverage time at your altitude. Five hours of meta-work in a week is worth more than fifty hours of tactical work, by a factor I can't quantify but I can promise. If you can't point to specific hours last week that were meta-work hours, you're not doing the job. You're doing the old job inside the new title.
You're confusing being needed with being effective
This is the deepest one. The hardest to admit.
You like being the person they come to when something matters. You like being the call that gets made when there's a problem. You like the validation of being the one who fixes things. That feeling, of being needed, has been the marker of your career success for fifteen or twenty years.
In the new role, being needed is the failure mode.
The most effective senior leader in the building is the one who is least needed for any specific operational decision. Their team handles things. Their systems handle things. Their forums handle things. The leader provides direction, decides on the major calls, and otherwise creates the conditions where their presence is not required for the org to function.
If you're being needed all day, your system is broken. The job isn't to be needed. The job is to build something that operates without needing you.
Count them
Go back through honestly. For each pattern, ask: is this me, in my role, right now?
If you count zero or one, you're operating cleanly. Make sure you're being honest with yourself.
If you count two or three, you're in the transition. The old reflexes are still firing in specific areas. You're closer to the target than most.
If you count four or five, you're caught in the Promotion Paradox. The path through is available, but it requires deliberate work.
If you count six or seven, you are operating as a senior individual contributor inside a senior leader's title. That's not a criticism. It's the most common pattern. It's also the pattern that has to change before the role's expectations get met.
Write down today's date and the number. Revisit it in 90 days. The work of moving the number down is the work of making the identity shift the role requires.