Building Strategy With Leaders, Not For Them
Most strategies I've seen die in one of two places. Some never leave the slide: a vision statement, supporting pillars, and a launch email, and then everyone goes back to work as usual. Others are complete on paper but belong to one person. The leaders who have to deliver them weren't in the room when the hard choices were made, so they can recite the strategy but can't defend it.
As a Chief of Staff, my job isn't to write the strategy for the leadership team. It's to build a process that lets them write it together, test it against every part of the organization, and walk out able to explain it the same way. Here's how I do that.
How I build strategy with a leadership team
1. Start with the why. Before we talk about what we'll build, we agree on the problem. If the leadership team can't agree on the problem, they won't agree on anything after it.
2. Make the future concrete. A vision statement alone is too abstract to argue with. So alongside the vision, mission, and pillars, I write a short narrative of what the future feels like, moment by moment. Leaders and employees react to a story in a way they never react to a pillar, and that reaction is where the real alignment happens.
3. Test it against the whole organization. A strategy that only describes the technology or the process is half a strategy. I use McKinsey's 7S framework (Strategy, Structure, Systems, Shared Values, Style, Staff, and Skills) to make the team look at every part of the organization. For each one we write the honest current state, the future state, and the strategic objectives that close the gap. This is where blind spots surface: the culture norm that will quietly undo the new model, or the career path that doesn't exist yet.
4. Turn objectives into OKRs and work streams. Every objective gets a key result, an owner, the work streams that will deliver it, and a rough horizon: Now, Near, or Future. That's the step that turns a strategy document into a plan people can run.
5. Translate it for every role. People don't ask "what's the strategy?" They ask "what does this mean for me?" So the strategy answers that directly by role: what changes, what stays core, what expands, and how they'll be measured.
6. Build the machinery to carry it. Before launch, the strategy needs governance, a communication plan by audience, and a risk plan. Who approves the roadmap, who tracks progress, who cascades the message, and what we'll do when the first wave of resistance shows up. Without this, even a well-built strategy stalls by the second quarter.
In practice: an agentic support strategy at UiPath
For fiscal year 2027, our Global Product Support leadership team set out to redesign how support works: a model where AI agents handle routine product issues at scale, and people focus on complex problems, customer relationships, and the outcomes customers bought the product for. It touches how teams are organized, how people are measured, what skills they need, and what leaders spend their time on.
We started with the customer. The strategy opens with a problem statement and a short story of a customer's automation failing at a critical moment, and what the experience feels like when the new model works: an intelligent agent that already understands their environment, investigates, explains what it's doing, and hands off to an engineer without friction when the issue is complex.
Then we worked through all seven areas of the 7S framework. Some of the most important objectives weren't about technology at all. Under Style, leadership had to shift from monitoring activity to owning outcomes and coaching people through change. Under Shared Values, the norm of rewarding case volume had to give way to rewarding customer and business value. Under Staff and Skills, we had to define new roles and career paths before asking anyone to work differently.
We were deliberate about the human side. The strategy includes plain-language pages on what the change means for engineers and for managers: less repetitive case work, more system-level problem solving, and clearer paths to grow. It also says, directly, that change will be sequenced by readiness and value, not by the org chart.
Finally, we built the machinery. A transformation council approves the roadmap and removes blockers. As Chief of Staff, I run the PMO that tracks the OKRs and reports progress to executives. Change champions in each department carry the message and bring feedback back. And a communication plan spells out what each audience needs to hear, through which channel, and how often.
What makes a strategy stick
The last page of our strategy wasn't a summary of initiatives. It was a table of what leaders must reinforce in each of the seven areas: talk about outcomes, not activity; coach, don't police; make learning part of the job. That page matters more than the rest, because a strategy lives or dies in what leaders say and reward.
That's the pattern I come back to. Build the strategy with the leaders who will carry it. Test it against the whole organization, not just the part that's easiest to change. Translate it into what it means for each person. And put the structure in place to keep it alive long after the launch meeting. It pairs naturally with how I lead change: Aligned Change is how the strategy reaches everyone else.