How Managers Move from Execution to Strategy

A Practical Guide to Driving Decisions, Influence, and Career Growth

Most program manager and engineering manager careers stall because they stay in execution mode far too long and do not influence strategy or move beyond the bounds of their role. This article focuses on how that can happen, tips on how to start influencing program strategy, pitfalls to avoid and how to be seen performing at the next level for promotion while still delivering.

How I got stuck in my career

Early in my career, I built a reputation for getting things done. If something was stuck, I would step in, unblock it, drive it to completion, and make sure nothing slipped. People trusted me because I delivered. My manager trusted me because I didn’t need much oversight. That worked really well and I got excellent reviews.

There was a point when I started noticing something change. People I respected, had worked with, some with less experience, were moving into bigger roles. They were being included when decisions were made. I was still the person everyone went to when something needed to get done fast, reliably despite constraints. On the surface, that sounds like a good place to be. However, I felt trapped in a golden cage. I was doing great, everyone was happy, but I also felt I was falling behind.

I had spent months operating inside the system. I hadn’t stepped back to question whether we were solving the right problem, or whether the approach itself needed to change. That was a turning point for me. Execution builds credibility. But if you stay there too long, it starts to define you in a very narrow way. You become the person who gets things done, not the person who decides what should get done. No one will tell you when it’s time to make the shift.

Moving out of execution mode doesn’t mean you stop delivering. You expand, by asking different questions and get involved with more than the program itself. You spend more time influencing outcomes you don’t directly control or own. There is less immediate feedback. You do not have that clean feeling of achievement you get from execution.

I had to step back from problems I knew I could fix. I was in conversations that didn’t produce immediate outputs but shaped decisions. Over time, instead of driving one program, I was shaping several. I was better informed on how leadership was thinking and where the business was trending. My business sense, ability to question, and suggest alternate perspectives made my opinions valued. Instead of being pulled into problems, I was being pulled in to prevent them or decide the best strategy to divide and conquer.

Execution is very tangible, thus rewarded early and often. It’s visible, measurable and feels productive. Strategy and influence are behind the scenes, with no direct tangible outcome that can be measured. However, they are what define seniority. My two cents is, early in your career, you are valued for how well you execute within a system. Later in your career, you’re valued for how well you shape the system itself.

You get stalled if you keep doing the thing that made you successful, but do not grow in the role. That was true for me till a conversation with a mentor changed my perspective.

Most program managers don’t get stuck because they’re underperforming but because they are very good at execution. They are reliable, run tight programs, manage stakeholders well, deliver on time and are strong communicators. Over time, that becomes their identity. Eventually, that identity starts to limit them. The shift from execution to strategy should not be a promotion-driven change. It is a behavior change that has to happen before the role changes so that you are seen as performing at the next level.

How to get involved in program strategy

Start by changing the questions you ask. Most program managers stay close to the plan. Timelines, dependencies, risks, status. That’s necessary, but it keeps you operating inside the system. Strategy starts when you step outside the box. You will need to spend time learning, understanding and gaining context so that you come prepared.

Get involved before the program is fully defined. Ask why this program exists in the first place. What metric is it trying to move? What happens if it doesn’t get done? What are the alternatives? Sit in early discussions, even if you’re not explicitly invited. Talk to product, engineering, and business stakeholders before plans are locked. Understand how decisions are being made.

If you’re handed a fully baked plan, don’t just execute it. Pressure test it. Where are the assumptions weak? Are teams aligned on outcomes or just activities? Is there a simpler path to the same result?

Takeaway: Start connecting the dots across programs. Strategy is rarely about one initiative. It’s about trade-offs. If you can clearly, concisely articulate how one program impacts another, you are providing valuable and unique insights.

How to be seen as a leader in program strategy

Program managers tend to wait to be given ownership of strategy. That rarely happens. You are only seen as a strategic leader when your input changes direction or brings new perspectives to the table. That doesn’t mean having the right answer all the time. Here are some ways you can make the shift:

Develop a POV. You have to come to discussions/reviews with a point of view(POV). Don’t just report program status. Share what you think should change, risks that are not being discussed, and pressure-test where the plan is likely to break.

Make trade-offs explicit. Senior leaders care about choices and why decisions were made, not just progress. If you can frame decisions clearly, you provide valuable insight very quickly.

Evolve your communication. Provide less detail (let them ask for more, have it handy) and focus on outcomes, not activity. Always tie everything back to business impact.

Build credibility outside your immediate program. Strategy is cross-functional by nature. If people across teams trust your judgment, your influence will expand. Do this by executing reliably, expanding your role by learning, volunteering to do more for the program and networking.

Takeaway: Stop being the person who always has the latest update and start being the person who explains what the update means.

Tips for Program Managers/ Engineering Managers to influence strategy

Excel in execution, don’t stop. Your credibility still comes from delivery. You are trying to expand your scope while maintaining a baseline of reliability.

Pick one or two programs where you go deeper on strategy. Don’t try to do it everywhere at once.

Write more. Strategy becomes clearer when you force yourself to articulate it. Draft one-pagers, summarize decisions and lay out options with their pros and cons. This is where your thinking gets sharper. This is one of my best learnings at Amazon and their approach is heavily adopted by many tech startups.

Gather diverse perspectives. Ask for feedback specifically on your thinking, not just your delivery. “Was my framing useful?” is a better question than “Did that go well?”

Observe how senior leaders operate. Pay attention to what they focus on, what they ignore, and how they make decisions with incomplete information.

Pitfalls to avoid as a Program Manager / Engineering Manager

The biggest pitfall is confusing opinions with strategy. Having a point of view is good, however, having an informed point of view is what matters. If you don’t understand the context, your input will be ignored quickly and you will become noise.

Do not over-index on visibility. Strategy is not about speaking more in meetings. You need to provide a perspective that changes how people think or add a fresh datapoint.

Don’t undermine execution teams in the process. If you move too far away from the details, you lose credibility. The goal is to stay connected without being consumed by it.

Conclusion

Finally, don’t wait for a title change to start behaving differently. By the time you’re officially in a strategic role, the expectations will have already shifted. You want to demonstrate that you are ready for that next role.