You hired a VP who’s brilliant on paper. Six months in, they’re playing it safe. Second-guessing every decision. Asking for permission instead of forgiveness. Your pipeline’s flat, and you’re watching them shrink.
Sound familiar?
Here’s the question that keeps you up at night: Do you step in? Replace them? Let it fail and hope they figure it out?
Every week of hesitation costs you. Pipeline stalls. Team morale drops. Momentum bleeds out. And your VP? They’re spiraling deeper into risk-aversion because they feel your doubt.
I watched this exact leadership moment play out during the Lions-Cowboys playoff game. Dan Campbell, the Lions’ head coach, took the playcard from John Morton, the offensive coordinator. Not to replace him. Not to embarrass him. To model what success looks like when you’re calling plays under pressure.
Then he handed it back.
Let me show you why this matters for every founder managing leaders who’ve lost their edge.
The Moment: When Your Leader Stops Leading
Context for the non-football folks: Morton’s been calling plays for the Lions offense. He’s competent. He knows the system. But something shifted.
He started playing not to lose instead of playing to win.
Risk-averse play-calling. Conservative decisions. The kind of choices that come from someone trying to prove they’re not the wrong guy instead of owning their role like they are the right one.
Campbell saw it. And he made a move that most leaders get wrong.
He didn’t sideline Morton. Didn’t call him out publicly. Didn’t bring in someone else’s playbook. He took Morton’s playcard—the same plays, the same system—and showed him how to call them with confidence.
The offense clicked immediately. Aggressive decisions. Using the whole roster. Plays that made it easier for the offensive line to win their individual battles. The same raw materials Morton had. Different execution mindset.
Then, critically, Campbell gave the playcard back to Morton. In the postgame press conference, both Campbell and the players publicly supported Morton and his value to the team.
This wasn’t a demotion. It was a masterclass in leadership intervention.
Here’s what Campbell was actually teaching—and what every founder needs to understand about leading through someone else’s doubt.
Move 1: Model Success, Don’t Replace the Leader
Most leaders get this wrong. They see someone struggling and they either replace them or let them fail. Campbell did neither.
He stepped in front to model success. Then he stepped back.
The difference matters. When you replace someone, you solve the immediate problem but you don’t build leadership capacity. When you let them fail without intervention, you waste time and damage confidence. When you model success using their system, you show them what’s possible within their framework.
Here’s what this looks like in practice.
The typical founder mistake: You see your CMO playing scared with budget allocation. They’re spreading thin across ten channels instead of concentrating force on the two that work. So you either take over the budget decisions (micromanagement) or bring in a consultant who recommends a completely different approach (undermining).
The Campbell move: You sit in their next planning session. You use their budget spreadsheet. You make the hard calls they’ve been avoiding. “We’re pulling 60% from these seven underperforming channels and doubling down on LinkedIn and webinars. Here’s why. Here’s the data. Let’s run it for 60 days.”
You’re not replacing their system. You’re showing them how to use their own tools with conviction.
I’ve been on both sides of this. Early in my agency career, I had a client—a mortgage lender CEO—who watched me hedge on a major campaign recommendation. I was pitching three “safe” options instead of the one bold play I knew would work. He stopped me mid-presentation.
“Bill, which one do you actually believe in?”
I pointed to the aggressive content play. The one that required real budget and real commitment.
“Good,” he said. “Sell me on that one. Stop giving me options that protect you if it fails.”
He didn’t replace me. He modeled what confidence looked like. That conversation changed how I approached every client recommendation after that.
The Framework: When to Step In vs. Step Back
Before you take someone’s playcard, answer these questions:
Question 1: Are they struggling with capability or confidence?
- If it’s capability, you need training or replacement
- If it’s confidence, you need modeling and support
- Morton had the capability. Campbell restored the confidence.
Question 2: Is their system fundamentally sound?
- If yes, model success within their framework
- If no, you have a bigger problem than confidence
- Campbell used Morton’s playbook because it was solid
Question 3: Can you step back after stepping in?
- If you can’t commit to giving it back, don’t take it
- Taking control permanently destroys leadership development
- Campbell took it temporarily with clear intention to return it
Question 4: Will your team see this as support or undermining?
- Public support matters more than private intervention
- Campbell’s postgame comments reinforced Morton’s authority
- How you frame the intervention determines whether it builds or destroys trust
Research from the Center for Creative Leadership shows that leaders who model desired behaviors while maintaining their team’s autonomy drive 40% higher performance outcomes than leaders who either micromanage or delegate without support.
The difference is in the execution. You’re not taking over. You’re demonstrating what success looks like in real-time, then immediately returning control.
Move 2: Use Their Playbook, Not Yours
Here’s what Campbell didn’t do: bring in a completely new offensive system. Install his own plays. Scrap Morton’s approach.
He used Morton’s playbook. The same plays. The same system. The same raw materials.
The difference was in the play-calling philosophy. More aggression. Higher risk tolerance. Optimization for making each position group’s job easier rather than trying to minimize mistakes.
This is where most founders fail when they step in.
You see your VP of Sales struggling with pipeline conversion, so you bring in your old playbook from when you ran sales. Different qualification criteria. Different stages. Different tools. You just undermined everything they built.
The better move: Use their system. Show them how to run it with confidence.
I learned this the hard way running my agency. We had a project manager who was brilliant at organization but terrible at prioritization. Every client request got equal weight. We were drowning in low-value work.
My first instinct? Introduce my priority matrix from my Air Force days. Urgent/important quadrants. The whole nine yards.
But that would’ve meant she had to learn a new system while already feeling behind. So instead, I sat with her for a week and used her project management system. Same tool. Same categories. But I showed her how to ruthlessly rank work by client revenue impact and strategic value.
“Everything on this list still matters,” I told her. “But we’re doing these five things this week and these twenty things next month. Watch what happens when we’re not trying to do everything at once.”
Within two weeks, she was running the system better than I ever did. Because it was her system. I just showed her how to use it like an owner, not like someone trying to please everyone.
The Playbook Assessment Framework
Before you step in to use someone’s playbook, evaluate whether it’s worth preserving:
Green Light Indicators (Use Their System):
- The framework is logically sound
- The problem is execution, not design
- The team already understands the system
- Changing systems would cost more time than it saves
- The leader has ownership of the current approach
Red Light Indicators (Time for New System):
- Fundamental design flaws in the approach
- The system doesn’t match current market reality
- Multiple stakeholders are confused by the framework
- Previous attempts to fix execution have failed repeatedly
- The leader themselves admit the system is broken
Morton’s playbook wasn’t the problem. His confidence in calling the plays was the problem. Campbell knew the difference.
Most founders don’t. They see any struggle as a system failure rather than an execution challenge. They bring in new frameworks when what their team actually needs is someone to show them how to run the current system with conviction.
The tactical question: Can you win with better execution of the current system? If yes, model it. If no, then you’ve got bigger problems than confidence.
Move 3: Give It Back With Purpose—And Public Support
Here’s where Campbell’s move becomes brilliant.
He didn’t keep the playcard. He used it for specific situations, modeled the approach, then gave it back to Morton. And critically, in the postgame press conference, both Campbell and the players publicly supported Morton’s value to the team.
The handoff moment matters more than the takeover moment.
Most leaders either never give control back (micromanagement), or they give it back without any reinforcement (leaving the person still doubting themselves). Campbell did neither.
He gave it back with clear signal: You’ve got this. I trust you. The team trusts you. Now go call plays like you own it.
I see founders miss this constantly. They step in to “help” during a critical moment, then forget to explicitly step back. So their VP is stuck in limbo—unclear whether they still have authority or whether the founder’s just hovering.
Let me tell you about a consulting engagement where I had to coach a founder through this exact moment.
His VP of Marketing had launched a campaign that flopped. Not catastrophically, but clearly below expectations. The founder’s instinct was to take over the next launch. “I’ll run point on this one, you support.”
“Don’t do that,” I told him. “You’ll destroy her credibility with the team and she’ll never take another risk.”
Instead, we did this: He sat in her planning session for the next campaign. He asked hard questions. He challenged assumptions. He pushed for bolder decisions. Then he said, in front of her team: “This is your campaign. You own it. I trust your judgment. I’m here if you need me, but this is yours to run.”
She knocked it out of the park. Because he showed her what conviction looked like, then gave her the authority to execute with that same conviction.
The Handoff Conversation Framework
When you’re ready to give control back, here’s the conversation structure that works:
Step 1: Name What You Saw
“I stepped in because I saw you second-guessing decisions that you have the expertise to make. You know this system better than anyone.”
Step 2: Acknowledge What You Modeled
“What I was showing you isn’t a new system. It’s higher risk tolerance with the same playbook you built. That’s the only difference.”
Step 3: Give It Back Explicitly
“This is yours again. I’m not going to second-guess your calls. Run it like you own it.”
Step 4: Provide Public Support
This can’t be a private conversation only. Your team needs to see you reinforce their leader’s authority. In meetings, in emails, in public forums—make it clear you trust this person to execute.
Step 5: Establish Clear Re-engagement Rules
“The only time I step back in is if you ask me to, or if we’re off track on [specific metrics] for [specific timeframe]. Otherwise, this is your show.”
Research from Harvard Business Review shows that the “set-up-to-fail syndrome” happens when managers withdraw support after delegating without providing clear success criteria and explicit authority. The handoff has to be unambiguous.
Campbell did this perfectly. He took the playcard, used it, gave it back, and then publicly reinforced Morton’s role in front of the entire organization. No ambiguity. No lingering doubt about who’s in charge.
Warning: When NOT to Give It Back
Sometimes you evaluate the situation and realize this person can’t run the playbook—even with modeling and support.
Don’t give it back if:
- Multiple interventions haven’t changed the pattern
- They’re unable to execute even after clear modeling
- The role requirements have outgrown their capabilities
- They’re not bought into the approach after seeing it work
- The timeline doesn’t allow for more development
That’s a different conversation. That’s not about confidence—it’s about fit.
But if you can give it back, do it explicitly and publicly. The whole organization is watching how you handle this moment.
What This Looks Like Monday Morning
Let’s make this tactical. You’re reading this because someone on your team is playing scared and you’re trying to figure out what to do.
If you’re the Morton in your organization (the leader who’s lost confidence):
Ask yourself these questions:
- Am I making decisions like an owner, or like someone trying to not get fired?
- What’s the bold move I keep avoiding because I’m worried about being wrong?
- If this were my company, what would I do differently this week?
Then do this:
- Make one aggressive decision this week that you’ve been hedging on
- Tell your team why you’re making that call (own the reasoning)
- Accept that some bets won’t work—and that’s part of leadership
- Ask your boss explicitly: “Do you trust me to run this, or do you want to be more involved?”
If you’re the Campbell in your organization (the leader watching someone play scared):
Do this diagnostic:
- Is this a capability issue or a confidence issue?
- Is their system sound but their execution tentative?
- Can I model success without permanently taking over?
- Am I prepared to give control back publicly?
Then take action:
- Schedule time to sit with them and run their system together
- Make the bold calls they’re avoiding—using their framework
- Name explicitly what you’re modeling and why
- Give control back with public reinforcement
- Set clear metrics for when you’d re-engage
The Critical Distinction:
This isn’t about being a “hands-on” leader vs. a “hands-off” leader. It’s about knowing when to step in front to model, then stepping back to empower.
Most founders are either always in front (micromanagement) or always in back (absentee leadership). Campbell showed you can move fluidly between the two based on what your team needs in the moment.
That’s the skill that separates good leaders from great ones.
The Bigger Point: Great Leaders Create More Leaders
Here’s what matters most about the Campbell moment: he didn’t solve the problem permanently. He gave Morton the confidence and the pattern to solve it himself.
Next time Morton faces a high-pressure situation, he’s got a model. He’s seen what conviction looks like. He’s experienced what happens when you call plays like you own them instead of plays that minimize criticism.
That’s leadership multiplication. Campbell didn’t just win one game. He made Morton a better play-caller for every game going forward.
This is what founders miss when they either replace struggling leaders or let them fail without intervention. You’re not just solving today’s problem. You’re building capacity for the next hundred problems.
I learned this from a colonel in the Air Force who let me completely botch a briefing to a general. I was a young officer, nervous as hell, and I hedged every recommendation. Made everything sound optional. Presented three paths instead of one clear course of action.
The general dismissed me politely. Painful moment.
My colonel pulled me aside after. “You know what you should’ve said. Say it now.”
I gave him the brief I should’ve given—clear, direct, single recommendation with reasoning.
“Good,” he said. “That’s what you’re giving them next time. And Bill—they’re not going to eat you alive for having a point of view. They’ll respect you for it.”
He didn’t do the brief for me. He didn’t replace me. He showed me what confidence looked like, then made sure I had another shot to execute with that confidence.
That’s the move Campbell made with Morton. That’s the move you need to make with your leaders who’ve lost their edge.
Model it. Hand it back. Support them publicly. Watch them rise.
Leading a team that’s playing scared? Let’s map out exactly when to step in and when to step back. Schedule a discovery call and I’ll show you the intervention framework that restores confidence without creating dependence.
Or get frameworks like this delivered weekly in My Executive Brief—the newsletter for fintech founders who need tactical leadership insights, not just theory.
Stay focused. Stay productive. Keep building.
— Bill Rice
