The Glorified Manager Trap

Aparajita Sihag
Mar 16
10 min read

Why senior hires end up doing the job they just left – and how to make sure it doesn't happen to you

You spend years building a career. You move up, earn the scars, develop judgment that only comes from being in the room when things go wrong. Then you get the call. VP. Director. Head of. The title that signals you've arrived at the level where you stop doing and start leading.

Six months in, you're running spreadsheets. You're in every execution meeting. Your calendar looks suspiciously like it did three years ago – dense with operational tasks, light on the white space that strategy actually requires. You tell yourself it's temporary. It isn't.

This is the Glorified Manager Trap – and it is one of the most common, least-discussed career failures at the senior level. Not a dramatic implosion. Just a slow, quiet collapse of the role from what it was supposed to be into something far smaller.

The title says VP. The work says Manager. And both the company and the hire conspire to pretend otherwise.

This piece is for anyone stepping into – or considering – a VP, Director, or senior leadership role. It will tell you exactly what the trap is, why it happens, how to diagnose it before you accept an offer, and what AI is now doing to make the whole problem significantly worse.

What the Trap Actually Is

Let's be precise. This is not about a manager doing some execution work – that's normal and healthy. This is about a structural collapse: a senior hire who was brought in to operate at a strategic level finding themselves permanently stuck at the operational level beneath it.

Organizational theory distinguishes three modes of senior leadership work: managing down (directing those beneath you), managing sideways (working across peers to make decisions), and managing up (giving your C-suite what they need to enable you). A VP or Director who is only managing down has been, functionally, demoted – regardless of what their business card says.

The real job of a VP or Director is not to run the function. It is to build and architect the function, make the people inside it effective, influence the organization around it, and ensure its direction is tied to the company's future, not just its present. When you're primarily running the function yourself – producing, delivering, executing – you are doing the job of the person who should report to you.

How It Unfolds

The arc is remarkably consistent across industries and company sizes:

Months 1–2: You arrive and find things are under-built. You roll up your sleeves to 'understand the business' and 'establish credibility.' Reasonable.
Months 3–6: The operational work doesn't stop. There's always a fire. You're good at execution so you keep getting pulled in. Nobody recalibrates.
Months 6–12: You haven't built the strategy, hired the team, or created the cross-functional presence the role needed. You've been too busy executing.
Month 12–18: The C-suite wonders if you were the right hire. You wonder why you can't seem to get traction. Both of you are looking at the same problem from opposite sides of the glass.

Why It Happens – The Five Root Causes

The company was not actually ready for a strategic hire
The most common version. The organization is in operational chaos and hires a VP to fix it. The mandate is, implicitly, operational: clean this up, stabilize this function, stop the bleeding. There is no space for strategy because the house is on fire. The hire spends their entire tenure managing the emergency – and never gets to build what they were actually hired to build.
The tell: the job was created reactively, not proactively. The vacancy exists because something broke, not because the company is scaling into new territory.
The C-suite never actually cedes strategic ground
This is the most insidious version. The CEO or founding team says they want a strategic partner. What they actually want is a highly capable executor who won't challenge their decisions. The senior hire is given a seat at the table but not a voice at it. All real decisions continue to be made above them. The function's strategy is, in practice, still dictated from above.
This is not always malicious. Founders in particular find it genuinely difficult to let go of functional control, especially in areas where they have strong opinions. But the result is the same: the VP spends their time translating decisions that were already made, not shaping ones that haven't been.
Title inflation as a recruitment tool
Cash-constrained companies – especially startups – offer elevated titles to close senior candidates who would otherwise be out of their compensation range. Someone who is a Senior Manager by experience gets offered a Director title. Someone who is a Director gets offered a VP. The title is a signing bonus in disguise.
The problem: once you are in the role, the title is decorative. The level of authority, budget, and strategic involvement doesn't change to match it. You are doing Director work with a VP title, creating misalignment with your peers and a performance gap against expectations that were never realistic.
No organizational architecture to support the role
Many companies, especially those scaling quickly, have no clear definition of what each level of leadership actually owns. What is the scope of a VP versus a Director? What decisions can each make without approval? What budget do they control? What does 'strategic' mean concretely at this company?
Without this architecture, everyone defaults to what is visible and urgent: operational work. The senior hire has a title but no clearly defined territory, and without territory, there is nothing to defend or develop.
The psychological pull of execution
This one is uncomfortable because it implicates the hire, not just the organization. Strategic work is slow, ambiguous, and politically complex. The feedback loop is long. You do the work in Q1 and maybe see the result in Q4. Execution is the opposite: immediate, measurable, gratifying. You close the task, the task disappears, you feel productive.
Many people who've been excellent operators their entire careers find the ambiguity of genuine strategy deeply uncomfortable. So they fill the ambiguity with execution. The organization, which is always happy to have more execution happening, lets them. And the role collapses downward into familiar territory.

The Perception Gap: Who Sees What

One of the most damaging aspects of this trap is that both parties see the same failure through completely different lenses – and both interpretations have some truth to them.

The organization says...	The hire says...
They're not strategic enough	I'm never given the space to be strategic
They can't let go of the details	No one else is doing this work
They're not building the team	I don't have headcount approval
They don't have executive presence	I'm not invited to rooms where it matters
They're not a culture fit	The culture doesn't support this kind of role

Both sides are often partially right. The hire is retreating into execution. The organization is also failing to create the conditions for strategic work. But in most post-mortems, only one party gets the blame – and it's almost always the hire.

The AI Accelerant

Everything described above is now being amplified by a force that did not exist at scale even three years ago. AI is not just changing what junior employees do – it is restructuring the conditions under which senior hires operate, and almost entirely in ways that make the Glorified Manager Trap worse.

The team-building floor just dropped

The classic path out of the trap is to hire aggressively: build the team, delegate the execution, create the space for strategy. AI is now being used to justify not doing this. Companies increasingly argue that with AI handling research, first-draft analysis, data synthesis, and routine coordination, fewer human layers are needed. The VP is hired to lead a function – but the function never gets properly resourced because 'AI can handle it.'

The result: the VP is the operator of AI tools rather than the leader of a function. The title remains senior. The cognitive work is execution-level. The trap closes with a new and more technologically sophisticated door.

The redefinition of 'strategic work'

There is a growing trend – still nascent but accelerating – of redefining what counts as leadership work in the AI era. Prompt design. AI workflow governance. Output quality review. Model selection. These are presented as strategic and senior. They are not. They are a new layer of sophisticated execution, and organizations are using them to keep VPs visibly busy while never giving them the genuine strategic mandate they were hired for.

If your 'strategic' role consists primarily of decisions about which AI tools the team uses and how outputs get reviewed, you are an operations manager for AI infrastructure. That is a real and important role. It is not what you signed up for.

The compression of the leadership stack

As AI reduces the need for certain junior execution roles, the distance between senior leaders and ground-level work shrinks. There are fewer layers between the VP and the actual work. This sounds efficient. What it actually does is pull the VP back into direct contact with execution they were supposed to be above. The structural buffer – the team of people who stood between senior thinking and operational output – is thinning.

AI is not just automating junior jobs. It is restructuring the conditions under which senior leaders can lead.

For anyone evaluating a VP or Director role today, the AI question is not just 'what will I be doing?' but 'what will this company use AI as a justification for not giving me?' Headcount. Resources. The team. The structure. All of it is now at risk of being replaced with a subscription and a system prompt.

How to Spot It Before You Join

This is where most people are insufficiently rigorous. The interview process is designed to sell you on the role. Your job is to conduct a structured audit of whether the role is real. Here is how to do it.

Questions on Decision-Making Authority

The single most reliable signal of a real senior role is whether it carries real authority – not symbolic authority. Push hard on these:

✓ Ask directly: What budget does this role own independently, without C-suite approval?

✓ Ask directly: What was the last strategic decision this function made, and who actually made it?

✓ Ask directly: Has this function ever pushed back on a C-suite direction and won? What happened?

✓ Ask directly: What decisions require escalation versus being made at this level?

Vague answers to these questions – lots of 'we're collaborative' or 'we work together on these things' – are a strong signal that decision-making authority is concentrated above you and the role is primarily executional.

Questions on the C-Suite's Real Intent

✓ Why are you hiring externally rather than promoting internally?

✓ What would success look like in 12 months that couldn't be achieved without this hire?

✓ Who does this role work most closely with at the C-suite level, and how often?

✓ What does this role need to be able to do that the function currently cannot?

Pay close attention to whether the answers are structural (we need someone to build this capability) or operational (we need someone to run this better). 'Run this better' is a management mandate. 'Build this capability' is a leadership mandate. They are not the same role.

Questions About Role History

✓ What happened to the last person in this role?

✓ If this is a new role, why is it being created now?

✓ What does the career path look like for someone who excels here?

'We outgrew them' from a company that has not meaningfully scaled in the past 18 months is a red flag. 'They left for a great opportunity' without being able to name it is a red flag. And a new role with no prior incumbent often signals that the company has not thought clearly about what the role actually is yet – meaning you'll be discovering that in real-time, on your own time.

The Peer-Level Test

⚠ Are the other VPs and Directors in the company doing strategy or execution? Talk to them on LinkedIn before you accept.

⚠ Does the company have a visible, articulated career ladder? If not, titles are impressionistic.

⚠ How lean is the team you'd be inheriting? A 'VP of Product' with a team of two is almost certainly doing PM work themselves.

⚠ Where does this role sit in the org chart? Who are you actually adjacent to?

The best signal is almost never in what the hiring manager tells you. It is in the texture of the company: how its people describe their work, what problems they spend their time on, whether strategic thinking is visible anywhere in the organization's output. If the culture worships execution and treats strategy as a luxury, your role will reflect that culture, regardless of the title.

If You Are Already in the Trap

Some of you are not evaluating a new role. You are already in one, six months in, wondering what happened. A few direct observations:

– Name it clearly. To yourself first. The trap cannot be addressed if it is not identified. 'I am doing Manager-level work in a VP role' is a diagnosable condition. It has causes. It can be addressed. But not if you're explaining it away.

– Have the explicit conversation with your manager. Not 'I feel underutilized' – that's too soft. 'I was hired to do X. I am currently doing Y. I need us to create the conditions for X. Here is specifically what that requires.' If the conversation is deflected twice, you have your answer.

– Stop filling the vacuum. The single most powerful thing you can do to create space for strategic work is to stop doing the execution work that no one assigned you but that you picked up because it needed doing. Let some things be undone. The discomfort that follows is information.

– Set a timeline. Give it 90 days from the explicit conversation. Either the conditions change materially, or you update your LinkedIn and treat the role as an expensive lesson in due diligence.

The Title Is Not the Role

The Glorified Manager Trap is not a failure of individual ambition or capability. It is a structural failure – of organizations that use senior titles as retention tools, of hiring processes that prioritize closing the candidate over defining the role, and of cultures that are far more comfortable with visible execution than invisible strategy.

But it is also, in part, a failure of due diligence. The questions that would expose this trap before joining are available to every candidate who is willing to ask them directly and listen carefully to the answers. Most people don't ask because they want the role and don't want to risk the offer. That calculation is wrong. A VP title doing Manager work is not a career milestone. It's a career detour that will cost you two years and compound the positioning problem for every role that follows.

The job market for senior talent is not getting more forgiving. AI is structurally reducing the team sizes that justify leadership roles. Companies are getting more comfortable keeping headcount lean and using senior titles as a form of cheap equity. The conditions for this trap are multiplying, not shrinking.

Go in with your eyes open. Ask the hard questions before you sign. The role should be able to withstand scrutiny. If it can't, that's your answer.

The best senior leaders are not those who accepted the highest titles. They are those who chose roles where the work matched the mandate – and had the discipline to walk away when it didn't.