Exorcising the Expert: How VPs Become Architects

Todd Curzon

[calm] Welcome to the show. Daniel, I want to start with a sentence that tends to make newly promoted VPs deeply uncomfortable: the very excellence that earned your promotion can become the thing that keeps you small. And I mean that quite literally. The pattern is almost always the same. You were the person who could write the cleanest deck, rescue the slipping launch, answer the impossible question in the room. And then one day the job changes, but your identity... [short pause] doesn't.

Daniel Carter

[curious] That phrase you used there -- “the job changes, but your identity doesn't” -- that's the whole knot, isn't it? Because nobody gets promoted for being vague. They get promoted for being RELIABLE. For being the person who gets in there and fixes it. So when you say that excellence becomes a liability, I can almost hear people bristling. They're thinking, hold on, competence is not the problem.

Todd Curzon

[measured] Quite right. Competence is not the problem. Over-identification with competence is the problem. There's a difference. The competence penalty begins the moment being the best doer starts crowding out the work of strategic leadership. You're still reaching for the keyboard. You're still rewriting the slide. You're still answering the question that someone else should have been allowed to answer badly, learn from, and improve.

Daniel Carter

[skeptical] Let me sharpen that. When you say “reaching for the keyboard,” you don't just mean literally typing faster. You mean the reflex. The body memory of, I see a problem, therefore I enter the problem. And for a director moving into VP, that can look noble from the outside. Helpful. Responsive. But underneath it, there's usually something else: discomfort with distance.

Todd Curzon

Exactly. And distance is not detachment. That's where people get confused. They think strategic leadership means becoming abstract, aloof, somehow less useful. It doesn't. It means your usefulness is no longer measured by how quickly you personally produce the answer. It's measured by whether the organization can produce good answers repeatedly, under pressure, without your constant intervention.

Daniel Carter

[responds quickly] Repeatedly. That word matters. Not once. Not heroically. Repeatedly. Because a lot of high performers build a career on emergency brilliance. They can save the quarter, save the meeting, save the customer. But if you have to save everything, you are not leading a system. You ARE the system.

Todd Curzon

[warmly] Yes -- and that is the trap. You were promoted because you were excellent. Now excellence, in its old form, is the thing holding you back. There is a ghost in the room, if I can put it that way. The ghost of the former expert self. It still whispers: just do it yourself, it will be faster. Just fix the deck, it will be better. Just answer for them, it will be cleaner. And every time you listen, you confirm an identity that no longer fits the role.

Daniel Carter

[softly] And in high-growth tech, that ghost gets rewarded for a while. That's the dangerous bit. Fast company, messy environment, incomplete data -- the old expert can look like the hero for months. Maybe longer. Until people stop bringing you leaders and start bringing you dependencies.

Daniel Carter

[reflective] I've coached a lot of leaders through this exact shift, and the ghost shows up in three habits over and over. They solve, they rescue, and they polish. Solving is obvious -- every issue turns into their issue. Rescuing is subtler -- they jump in when someone struggles before the struggle has taught anything. And polishing is the sneakiest one. They can't let a draft, a plan, a narrative, even a rough answer exist without making it “VP-ready” themselves.

Todd Curzon

[curious] That last one -- polishing -- I think listeners may underestimate how corrosive it is. Because it can look like high standards. It can look almost virtuous.

Daniel Carter

It absolutely can. But if every document gets better only after you touch it, then your team learns the wrong lesson. They don't learn judgment. They learn escalation. They learn that the final layer of thinking lives above them. And once that happens, you haven't built capacity. You've built a dependency loop.

Todd Curzon

[calm] That distinction between capacity and dependency is, I think, one of the cleanest ways to separate director behaviour from VP behaviour. A director is often still quite close to the work. In many cases, appropriately so. They are driving execution, sharpening decisions, keeping pace. A VP, by contrast, must design decision-making itself. The question is no longer, “Can I solve this?” It is, “Have I built the conditions under which this can be solved well, consistently, by the right people?”

Daniel Carter

[questioning tone] So let me try to say that back. Director says, “I improve the work.” VP says, “I improve the machine that produces the work.” Is that too neat?

Todd Curzon

Not too neat -- though I'd refine one word. The VP doesn't merely improve the machine. The VP designs the environment in which judgment compounds. That includes who decides, what information reaches them, how trade-offs are framed, and what happens when the first answer is incomplete.

Daniel Carter

[chuckles] “Judgment compounds” -- I'm stealing that. Because that's the bit ex-high-performers hate, if I'm honest. Ambiguity. Watching someone else work through a messy decision at 70 percent of your speed and maybe 80 percent of your quality... [sighs] that can feel excruciating.

Todd Curzon

[reflective] It can. And I should admit, I know that feeling rather intimately. Early in my own leadership work, I had a habit of stepping in too early -- especially on communication. A presentation would arrive, and I could already see the stronger narrative, the cleaner structure, the better opening line. And because I could see it, I assumed I should do it. That assumption cost people growth. It also exhausted me.

Daniel Carter

[softly] The “better opening line.” That's so specific, and that's why it stings. Because the temptation isn't abstract. It's tiny. It's one sentence, one slide, one answer in a meeting. And each one feels harmless.

Todd Curzon

Precisely. Leadership drift rarely arrives as a grand failure. It arrives as a thousand elegant little interventions. And over time, the team becomes less decisive, the leader becomes more overloaded, and everybody mistakes proximity for value.

Todd Curzon

[matter-of-fact] So what does the shift actually look like when competence is no longer enough? It looks like leverage. Your output becomes organizational, not personal. Delegation, yes, but not delegation as task dumping. Delegation as the transfer of ownership, context, and decision rights. Strategic framing, too -- meaning you do not merely ask for updates, you shape how the problem is understood. And perhaps most importantly, you create momentum by making the next move clearer for everyone around you.

Daniel Carter

[curious] “Decision rights” is a useful phrase there. Because a lot of leaders think they're delegating when they're really just renting out labor. They hand off the task, but they keep the thinking. They keep the final call, the interpretation, the message to stakeholders. So the team executes, but they never really OWN anything.

Todd Curzon

Quite. And that produces one of the clearest signs of what we might call The Haunting. You over-edit work that is already good enough. You over-answer in meetings before your team can reason aloud. You avoid ambiguity by collapsing it too quickly into your preferred answer. In short, you keep proving that you are the smartest operator in the room while quietly preventing the room from becoming smarter.

Daniel Carter

[skeptical] I want to push on “good enough,” because some listeners hear that and think, ah yes, permission for mediocrity. That's not what you mean.

Todd Curzon

No, not at all. I mean proportion. A VP must ask a different question: what level of polish is required for the decision at hand, and who should own that standard? If you apply your personal gold-standard craftsmanship to every internal artifact, every draft, every reply, you become a bottleneck dressed as a quality bar.

Daniel Carter

[laughs softly] “A bottleneck dressed as a quality bar.” That one's going to annoy people because it's true. And then there's The Transition, which to me is the messy middle. You still feel the urge to jump in, but now you catch yourself. You ask one more question instead of giving one more answer. You let a leader present before you refine. You tolerate the awkward five seconds in a meeting where someone else has to think on their feet.

Todd Curzon

[warmly] Yes. The Transition is not elegant. It is a season of restraint. You are learning that leadership is not doing more. It is creating clarity, systems, and momentum. The person who frames the conversation is perceived as more senior than the person who simply answers the question. And framing, notably, requires space. If you are forever in the weeds, forever polishing, forever rescuing, you never quite rise high enough to see the pattern beneath the incident.

Daniel Carter

[questioning tone] So if someone wants a simple test: after a hard week, ask yourself this -- did I spend most of my time producing answers, or increasing the organization's ability to produce answers? Those are not the same week. Not even close.

Daniel Carter

[calm] This is why I actually like the Ghost Score as a diagnostic, because it gets uncomfortably concrete very fast. Ten questions. Two minutes -- I think it even says one minute thirty in one version -- immediate results. And the promise is simple: how much of your VP role is still being run by the director you used to be?

Todd Curzon

[measured] It is, in that sense, less a personality quiz than a confrontation. The questions sit around three pressure points. Delegation and strategy: are you building systems, or still being the system? AI readiness: are you using AI to think differently, or merely to type faster? And identity and influence: is your value located in what you do, or in what you have built?

Daniel Carter

[responds quickly] That AI line -- “think differently or just type faster” -- is a perfect tell. Because the ghost loves acceleration. If your old identity is expert operator, then every new tool becomes a way to produce more output yourself. Faster emails, faster summaries, faster decks. Useful, sure. But still very individual-output thinking.

Todd Curzon

Exactly. And the assessment sorts people into three tiers, which I think are quite elegantly named. The first is The Haunting. That is the leader still run by reflex. Still over-functioning. Still over-answering. Still too close to the work to see that proximity has become the problem. The second is The Transition. Here, the shift has begun, but it is incomplete. You are delegating more, framing more, perhaps using systems language -- but under pressure, the old expert returns.

Daniel Carter

[softly] Under pressure. That's where the truth lives. Not on the calm Tuesday. On the ugly Thursday when the launch slips, the board deck is messy, and two teams disagree. That's when you find out whether you're building leaders or becoming the emergency department.

Todd Curzon

[calm] Very well put. And then the third tier is The Architect. That is the leader whose value is increasingly expressed through structures, not personal heroics. Decisions travel well. Ownership is visible. Capacity expands without requiring the leader's fingerprints on every line. The Architect still has expertise, of course, but no longer needs constant proof of it.

Daniel Carter

[skeptical] And this is the provocative bit: a high performer can absolutely be operating at a lower leadership tier without realizing it. You can be admired, busy, responsive, technically brilliant -- and still haunted. In fact, those traits can camouflage it.

Todd Curzon

[short pause] Yes. Which is why the Ghost Score feels useful as a free diagnostic rather than a sermon. It gives language to a very specific experience: the sensation that you have advanced in title, but part of your operating system has not caught up. And once you can see the ghost, you can stop mistaking it for leadership.

Todd Curzon

[reflective] Becoming The Architect, then, is not about becoming less capable. It is about becoming capable in a different register. Your aim is to build systems that outlast your personal effort. Systems of delegation. Systems of decision-making. Systems of clarity. The goal is not that nothing important ever reaches you. The goal is that important things reach you at the right altitude, in the right form, with the right ownership already attached.

Daniel Carter

[warmly] “Right altitude” is good. Because architects still care about the building -- they just don't spend all day holding the bricks. And for newly promoted leaders, that identity shift is the hard part. You're moving from, “I am valuable because I do the hard thing,” to, “I am valuable because hard things get done well around me, even when I'm not in the middle of them.”

Todd Curzon

Quite so. And that can feel, at first, strangely empty. There is less immediate applause. Fewer moments where someone says, “Thank goodness you jumped in.” More invisible work. More patience. More design. But leadership is often like a winter garden -- it can look bare, even a touch unimpressive, while the real structure is being established beneath the surface. What appears to be less activity is often the beginning of healthier growth.

Daniel Carter

[chuckles] That is the most elegant way anyone has ever told a VP to stop rewriting the deck at midnight. But it's true. If every win still depends on your late-night intervention, you don't have scale. You have stamina. And stamina is a terrible operating model for a senior leader.

Todd Curzon

[calm] Nicely put. Which brings us back to identity. The old script says: my value lives in what I do. The newer, more mature script says: my value lives in what I've built. In the judgment I've cultivated. In the clarity I've created. In the momentum I've made possible. That is the movement from expert to architect.

Daniel Carter

[softly] And maybe that's the question to sit with after this episode. Not, “Am I competent?” You almost certainly are. That's how you got here. The sharper question is whether your competence is still serving the role you actually have... or whether it's keeping you loyal to the role you used to have.

Todd Curzon

[warmly] If the answer is uncomfortable, good. That usually means you're near something important. Take the Ghost Score if you want the mirror. Ten questions, two minutes, immediate results. Then see which tier you're really operating from: The Haunting, The Transition, or The Architect.

Daniel Carter

[reflective] And if you find a ghost in there, don't panic. Just don't keep giving it your calendar.

Todd Curzon

[soft laugh] A very good place to end. Thank you for listening.