CASE STUDY
CASE STUDY
Helping organizations move from initiative overload to coordinated execution.
Disclosure: The following case study is based on actual client engagements. Certain details, timelines, and organizational characteristics have been generalized or combined to protect client confidentiality while preserving the business challenge, approach, and lessons learned.
Organizations rarely struggle because they lack good ideas.
More often, they struggle because they have too many.
One wealth management organization was preparing to launch more than eighty initiatives over the course of a single year. Each represented a worthwhile investment. Each had a dedicated owner, a business case, a pilot plan, communications, and field support.
Viewed individually, they made sense.
Viewed collectively, they created an entirely different challenge.
Financial Advisors and their teams were being asked to absorb a constant stream of technology enhancements, new processes, pilot programs, communications, training requests, and feedback surveys. Field leaders responsible for supporting adoption understood only the initiatives within their own area of responsibility. No one had visibility into the cumulative experience facing the advisors they served.
Reports of pilot collisions became increasingly common. Communications overlapped. Feedback requests competed for attention. Good initiatives struggled to gain traction—not because they lacked value, but because the organization had exceeded its capacity to absorb change.
The problem wasn’t simply that there were too many initiatives.
The problem was that no one could see the airspace.
One executive conversation led to a simple metaphor that quickly resonated throughout the organization.
“Right now we have no way of knowing whether we’ve got two 747s on a collision course—or even what’s in the air. It could be 747s, Cessnas, helicopters, or hot air balloons for all we know.”
Every initiative owner was acting responsibly based on the information available to them.
The challenge was that each team was planning its own flight path independently.
Without a common operating picture, leaders had no practical way to identify collisions before they occurred, understand the cumulative impact on Financial Advisors, or determine whether another initiative should launch now, later, or alongside another effort.
The organization didn’t need fewer ideas.
It needed greater visibility.
The first step was not prioritization.
It was understanding.
We began by creating the organization’s first comprehensive inventory of initiatives, capturing timelines, pilot locations, rollout plans, ownership, field support requirements, and—perhaps most importantly—clear definitions of success.
That last element proved surprisingly important.
Many initiatives had never established even lightweight success criteria. Without a shared understanding of what success looked like, meaningful prioritization and continuous improvement became difficult.
The inventory evolved into a common planning environment known simply as Engage.
More than a project repository, Engage became the organization’s shared operating picture.
Regular planning sessions brought initiative owners together to coordinate timelines, identify potential conflicts, and discuss opportunities for collaboration. Separate forums with field engagement teams ensured that those closest to Financial Advisors had visibility into the full landscape of change rather than isolated pieces of it.
Rather than creating another approval process, the goal was to create better decisions.
Over time, leaders began consulting the team not because they needed permission, but because they valued the perspective that came from seeing the entire airspace.
Over the following two years, the organization’s approach to change fundamentally evolved.
Reports of frustration from Financial Advisors and field leadership declined as initiatives became better coordinated and communications more intentional.
Senior leadership gained visibility into organizational performance through common metrics and initiative-specific success measures reported within a consistent framework.
Perhaps the most meaningful change, however, was cultural.
The number of small, disconnected initiatives began to decline.
In their place emerged larger, more integrated efforts involving multiple business units working together toward shared outcomes.
The organization had not reduced its ambition.
It had increased its capacity to execute.
Organizations often believe they have a prioritization problem.
More often, they have a visibility problem.
When every initiative is planned independently, every project appears important. Leaders have little ability to understand cumulative impact, identify collisions, or recognize opportunities to combine related efforts into something more meaningful.
Air traffic controllers don’t create flight plans.
They create shared situational awareness.
That visibility allows hundreds of independent decisions to become a coordinated system.
The same is true inside organizations.
Exceptional execution doesn’t begin with saying “no” to more initiatives.
It begins by creating a common operating picture that allows leaders to see the organization as their employees experience it.
Only then can they create the capacity for meaningful change.