Why Your Team Isn't Thinking Strategically (And What to Do About It)

If your team isn't thinking strategically, odds are you've been protecting them from your thinking.

This is a pattern I see in almost every VP I coach. They want their team to be more strategic, to see the bigger picture, to connect their work to business outcomes. But when I look at how information flows, the leader is making strategic decisions behind closed doors and only sharing the conclusions — not the reasoning.

Strategy doesn't transfer through instructions. It transfers through process visibility. And that distinction changes everything about how you develop strategic thinkers.

The Instruction Trap

Most leaders try to make their teams more strategic by telling them what the strategy is. They share the plan, explain the priorities, and then expect their team to execute with strategic awareness. But this approach has a fundamental flaw: it teaches people what to do without teaching them how to think.

Your team can memorize the strategy deck. They can recite the three priorities for the quarter. But when they face an unexpected situation that isn't covered by the plan, they don't know how to reason their way through it. They come back to you for direction, reinforcing the very dependency you're trying to eliminate.

What Process Visibility Looks Like

Process visibility means letting your team see how you arrive at strategic decisions, not just what you decide. It means thinking out loud about tradeoffs, sharing the data and constraints you're weighing, and explaining why you're prioritizing one path over another.

Here's what this looks like in practice:

When you're deciding between two initiatives, bring your team into the evaluation process. Show them the criteria you're using. Let them see the data you're looking at. Talk through the tradeoffs out loud. Even if you ultimately make the final call, the exposure to your decision-making process is what builds their strategic capacity.

When you receive information from leadership meetings, don't just relay the conclusions. Share the context: what questions were raised, what tensions exist between competing priorities, what the organization is wrestling with. This context is the raw material of strategic thinking.

When you review your team's work, don't just evaluate whether it's good. Ask them about the strategic choices they made. Why did they prioritize this feature over that one? What business outcome were they optimizing for? What did they consider and reject? The questions you ask signal what kind of thinking you value.

Breaking Down Organizational Silos

Process visibility has a powerful secondary effect: it breaks down silos. When your team understands not just their own objectives but the reasoning behind cross-functional decisions, they start thinking beyond their domain. They anticipate how their work affects other teams. They spot misalignments before they become problems.

This is particularly valuable at the VP level, where cross-functional alignment is a core part of the role. If your team can see the broader strategic landscape, they become extensions of your strategic influence rather than executors who only understand their piece.

The Practice

This week, pick one decision you'd normally make alone. Instead of announcing the outcome, walk your team through your thinking process. Share the competing considerations, the data gaps, and the tradeoffs you're weighing. Then ask: given this information, what would you recommend?

You might be surprised by what they come up with. And even when they reach a different conclusion than you would, the exercise of strategic reasoning is exactly the capability you're trying to build. Strategy is a muscle. It develops through use, not instruction.