Kristyn Rankin · October 2026
Organizations invest considerable time and resources in understanding problems and developing strategies to address them. They commission assessments, evaluate alternatives, engage advisors, and reach agreement on a direction. The recommendations make sense, leadership is supportive, and everyone leaves the meeting with a reasonable understanding of what comes next.
And yet, six months later, relatively little may have changed.
We often attribute this to competing priorities, resistance to change, or poor execution. Those may be contributing factors, but I wonder whether we sometimes underestimate how much there is to learn about an organization before we can effectively change it.
Consider a company preparing for a new environmental regulation. Its legal and regulatory teams may have thoroughly evaluated the requirements and developed a credible compliance strategy. But implementation depends on information held by engineering, purchasing decisions made by procurement, data maintained across multiple systems, and operational processes that have evolved independently over many years.
Each function may understand its responsibilities without necessarily understanding how its work affects the others. And the person accountable for compliance may have limited authority over many of the activities needed to achieve it.
I've encountered similar situations in operational transformation work. A process may look perfectly reasonable on paper, but conversations with the people doing the work reveal informal handoffs, workarounds, spreadsheets, and exceptions that have become part of the daily routine.
It's easy to look at these arrangements and see inefficiency or unnecessary complexity. But I've learned to be curious about why they exist. A spreadsheet may be compensating for information that isn't available in a shared system. An additional review may have been introduced after an expensive mistake. An informal conversation between departments may be the only thing preventing a recurring problem.
These practices aren't necessarily the best way to accomplish the work, but they often tell us something important about the organization that the formal process doesn't.
And the people who developed them frequently understand both the limitations of the existing system and what would be lost if their workarounds simply disappeared.
That practical knowledge can be remarkably valuable when considering how to redesign an operation. Yet organizations don't always bring those perspectives into the conversation until implementation is underway.
I think this is where some of the distance between strategy and execution begins. We make decisions based on how we understand an organization to function, without always appreciating the informal relationships, accumulated experience, and everyday adaptations that allow it to operate.
This becomes particularly important when a proposed change crosses organizational boundaries. A strategy may require several functions to change how they work together, even though each has its own priorities, resources, and measures of success. Agreement at the leadership level doesn't necessarily resolve those practical differences.
None of this means we need to understand every detail before making a decision. But I do think there's value in involving the people who understand how the work actually happens earlier in the process, while there is still an opportunity to influence the approach.
I wonder how many implementation challenges could be avoided if we spent a little more time understanding the organization we're trying to change, rather than assuming we already know how it works.
© 2026 Rankin Strategies LLC. All rights reserved. | Privacy
Perspective III