Suppose an organization decides to focus on three priorities. Leadership builds a budget around them. The board approves the plan.
Then the consequences become specific.
Focusing resources may mean reducing or ending a longstanding program. A board member helped create it. A staff member spent years building it. Some members still value it.
A new priority may require one department to give up resources to another. Innovation may require people to propose ideas that could fail. Moving faster may require leaders to delegate decisions they are accustomed to making themselves.
This is where strategy meets culture.
Strategy Requires People to Act Differently
Strategic planning naturally focuses on what an organization should accomplish. But every consequential priority raises another question:
What will people have to do differently for this to work?
Innovation may require people to propose ideas without knowing whether they will succeed.
Speed may require authority to move closer to the people doing the work.
Accountability may require conversations the organization has historically avoided.
Collaboration may require people to share control over budgets, decisions, or recognition.
Adapting to changing member needs may require questioning programs that helped make the organization successful.
These are not secondary implementation issues. They are requirements of the strategy itself.
How Things Really Work
Every organization has a culture, regardless of what its values statement or employee handbook says.
People learn how decisions actually get made, what can be questioned, how disagreement is received, whether mistakes are survivable, which programs are untouchable, and which constituencies are difficult to disappoint.
Those patterns usually developed for understandable reasons. People punished for mistakes become cautious. A CEO who inherited disorder may centralize decisions. Departments that repeatedly fought for resources learn to protect them. An association accustomed to satisfying every constituency may struggle to stop programs.
A culture suited to yesterday's strategy may not be suited to today's.
The useful question is not whether an organization has a “good culture.” It is whether the way the organization actually operates will support what its strategy now requires.
Announcements Don't Change the Rules
People reasonably give more weight to experience than announcements.
If leadership encourages experimentation but treats every unsuccessful attempt as failure, caution remains the rational response.
If collaboration is praised but departments are rewarded for their individual results, protecting territory still makes sense.
If empowerment is announced but significant decisions continue to move upward for approval, people will continue to wait.
The organization has taught people how to succeed within it. A new strategic plan does not automatically change those lessons.
Leadership Faces Hard Choices
Before committing to a consequential priority, leaders should ask:
- What will people have to do differently?
- What established expectations, incentives, or unwritten rules will make that difficult?
- What will leadership itself have to do differently?
The last question is often the hardest.
Approving “focus” is easier than ending a program with influential supporters.
Endorsing “innovation” is easier than accepting a well-designed experiment that fails.
Calling for “accountability” is easier than addressing poor performance by someone important.
Supporting “empowerment” is easier than accepting a reasonable decision you would have made differently.
If leaders retreat when the consequences become uncomfortable, the organization learns that the old rules still apply.
Culture Makes Strategy Executable
Mission helps an organization decide what matters. Strategy determines where limited resources should go. But allocating resources does not execute a strategy. People do.
Culture shapes whether people can and will behave in the ways the strategy requires.
But changing how an organization operates creates consequences too. Moving faster can increase mistakes. Delegating authority can weaken useful checks. Experimentation can expose the organization to consequences it did not anticipate.
So, another question follows:
What consequences are we prepared to accept, and where must we draw the line?
That is where risk enters the conversation.