In Part 3, we saw how top-down boardroom strategies fail when executives hand down rigid mandates without understanding operational reality.

Usually, the next move is holding a two-day leadership retreat. Everyone gets energized, breaks into sessions, and heads back to the office excited to share the mission. But then reality sets in: How do we actually deliver this?

Turning direction into action takes analysis, coordination, and learning. Some improvements can happen quickly; others need sustained work across teams.

To build a strategy that works, you have to start by accepting what the How is NOT: It is not a laundry list of projects.

Start with outcomes

Several years ago, I worked with a digital transformation leader who banned the word “project” across our company.

I was sceptical at first—after all, some work is a project, right? But once I understood her vision, it transformed how I approached execution:

Start with the business problem before deciding how to organize the work.

When you start with a “list of projects,” teams focus on delivery outputs—finishing tasks on time and on budget—rather than business outcomes. Instead of launching a dozen disconnected initiatives, strategic execution should centre on programs aligned to a problem worth solving.

  • A project has a defined start, end, and scope. Delivery measures ask: “Did we launch the tool on time?”
  • A program brings related work together around business outcomes. The more important question is: “Did we actually fix the underlying issue?”

Think of the program as defining what we want to achieve and why it matters. Projects can be part of how we get there—but they are not the only way to organize the work.

Give projects a clear purpose

There is still a place for formal projects, especially for large, complex changes. One of my favourite planning tools is the charter: it creates clarity about purpose, scope, and outcomes. Within a broader program, however, a team can often break work into small increments of value without turning every improvement into a separate formal project.

Viewing each North Star goal as a program of problems to solve gives leaders a way to hear the challenges, prioritize what matters, and bring people along on the journey. Teams can deliver, learn, and adjust as their understanding grows.

Make strategy an ongoing conversation

And here’s the useful shift: planning, delivery, and prioritization become an ongoing rhythm. You still need to revisit your strategic direction, but you may no longer need to rely on occasional strategic planning sessions to restart the conversation. Strategy becomes part of how the organization works every day.

For a deeper dive into using business analysis to break down problems before launching work, explore my article on the work breakdown pyramid. Or contact me for a deeper conversation about what this could look like in your organization.

Start by choosing a problem your teams can investigate together, defining the outcome, and agreeing how you will measure progress.

The next article puts this into practice: turning a problem statement into a measurable program, with clear ownership and a rhythm for learning.