Aligned Change: How I Lead Organizational Change

Most change efforts I've seen don't fail at launch. They fail weeks before it, in a leadership meeting where everyone nodded at a plan they didn't fully agree with. Then the email goes out, managers explain it three different ways, and employees do the sensible thing: they wait to see if it sticks.

I've rolled out strategies, annual OKRs, new team structures, and new ways of working across merged and global organizations. The approach I use every time comes down to one idea: leaders have to be aligned before the organization is asked to move. I call it Aligned Change.

The model: align, then engage

Aligned Change blends two models I trust. Patrick Lencioni's Organizational Health Model keeps the focus on the leadership team: are we cohesive, are we clear, are we saying the same thing, and are we reinforcing it? The ExperienceChange model gives the work its steps, so change moves from an idea to something people actually do. Neither is enough on its own. Lencioni tells you what a healthy team needs but not how to sequence a rollout. ExperienceChange gives you the sequence but assumes the leaders are already on the same page. They usually aren't.

Aligned Change model: align key stakeholders, then engage the organization

Phase 1: Align the leaders. Before anything goes to the wider organization, the leadership team does three things. They understand the opportunity: why this change, why now, and what happens if we don't. They enlist the right people: a change champion with the credibility to push through resistance, a small core team to do the work, and an honest map of who is a champion, who is a helper, who is a bystander, and who will resist. Then they envisage the future together: a shared vision and a plan concrete enough that every leader can explain it the same way. This is where Lencioni's first two disciplines live. The team has to trust each other enough to disagree in the room, commit to one answer, and get clear on what it is.

Phase 2: Engage the organization. Only then do we take it to everyone else. We motivate by explaining the why, not just the what. We communicate the same message through every channel, more times than feels necessary, because people need to hear something several times, from different people, before they believe it. We help people act with hands-on learning, peer support, and room for questions. And we consolidate by handing ownership to the people doing the work, so the change outlasts the project. Throughout, leaders reinforce it in their own decisions and meetings.

It's an open framework on purpose. I adapt the steps to the size and type of change, but I never skip the first phase.

In practice: bringing a merged team together at T-Mobile

After a merger brought three companies together, our training organization had twice as many program managers as before and a much bigger scope. We moved from one central program management team to program managers dedicated to each instructional design team. Half of them were new to this line of business. The other half knew the old processes, but not the new ones. Everyone did similar work in different ways, with different tools, and nobody was sure where they fit.

Align. Before we asked a single program manager to change anything, we built the team that would lead it. The Senior Manager of Training served as change champion, backed by a steering committee that kept the work tied to company priorities. As Senior Manager, I led the core change team. We started with ourselves: working through Lencioni's five behaviors of a cohesive team until we were putting the organization ahead of our own departments. Then we used his six critical questions to get clear on purpose, roles, and what success meant. We didn't do that in a vacuum. Surveys and one-on-one interviews with the program managers told us what the new structure needed to fix.

Engage. We kicked off with an all-program-manager meeting where leaders shared the mission, vision, and goals, so the why came first. From there, the onboarding experience mixed hands-on learning with brown bag sessions, where guest speakers from partner teams explained how their work connected. Every program manager joined a cross-functional Partnership Pod, an instant network of peers to ask questions and review work with. We opened a dedicated channel for ongoing communication, and over time the program managers took it over and ran it themselves.

Consolidate. To close, we launched a Community of Practice led by the program managers. Ownership moved from the change team to the people doing the work. We also saw something we hadn't planned for: the program managers were building leadership skills along the way, which led us to add continuing education paths for them.

In practice: the annual strategy and OKR rollout at UiPath

Today I use the same model every year to launch our strategy and OKRs across a global support organization.

Align. It starts with the annual strategy meeting, which I produce for our SVP and senior leadership team. The goal isn't a polished deck. It's a leadership team that has argued through the priorities, committed to them, and can explain them the same way. Out of that meeting come three things: the strategy, the OKRs that measure it, and the communication plan that carries it. The alignment came together when we wrote our mission and vision statements, as a team, in one room. I started that work and kept us focused, and I made it collaborative and, honestly, fun. We walked out with a set of statements every leader had shaped and agreed to, which made them much easier to stand behind in front of their teams.

Engage. The strategy reaches employees through a defined path: email, Slack, our SharePoint Comms Hub, team meetings, and All Hands. Every people leader gets a Manager Communication Pack, so the message a new engineer hears from their manager matches what the SVP said. That's over-communication by design. When we rolled out the OKRs, leaders used their packs to take them to their teams, and every team had its own OKRs in place within a month.

Reinforce. The rollout doesn't end at launch. Monthly status reports and quarterly business reviews tie back to the same OKRs, so leaders keep coming back to the strategy in the rooms where decisions get made.

Making it fit the change

The model flexes with the size of the change. A new reporting structure might need weeks in the align phase and a light touch on engagement. An annual OKR rollout runs through both phases on a set calendar. A new tool or process might move quickly through alignment and spend most of its time in act and consolidate.

What doesn't change is the order. When leaders skip alignment to move faster, they usually spend that time and more cleaning up mixed messages later. When they take the time to align first, the rest of the organization can feel it: one message, from people who believe it.