Series: Systems Shape Success
I have seen organizations invest significant time developing an improvement plan.
The data are analyzed. Needs are identified. Goals are established. Strategies are selected. Action steps are written. Timelines are developed. The plan is reviewed, revised, and eventually approved.
Then implementation begins.
And that is often where a different set of problems emerges.
People may agree with the plan but have different understandings of what they are supposed to do. A strategy may require collaboration, but no time has been protected for people to work together. A new expectation may depend on data or resources people cannot easily access. Someone may be responsible for monitoring the work without having a clear process for doing it.
They may mean that the organization did not build a sufficiently strong bridge between planning and implementation.
None of those problems necessarily mean the plan was weak.
A plan identifies what an organization intends to do.
Implementation requires the organization to create the conditions that allow people to actually do it.
The work changes when the plan moves into practice
Planning can create the impression that many implementation questions have already been answered.
We identified the strategy.
We assigned the action step.
We established the timeline.
We named the evidence.
So we are ready.
But once people begin doing the work, the plan meets the organization’s reality.
Schedules matter.
Communication matters.
Access matters.
Existing responsibilities matter.
Leadership attention matters.
People’s knowledge and skills matter.
The routines already operating within the organization matter.
And the way all those pieces interact can either support implementation or make a reasonable strategy much harder to carry out.
This is why I do not think implementation begins with simply telling people to execute the plan.
There is another question leaders have to ask:
What has to be true within our organization for people to carry this out successfully?
Beneath the surface
When implementation begins to struggle, it is easy to return to the plan and ask whether the action was completed.
I think leaders need to look deeper.
People needed data but lacked access to the platform.
Coaching was expected, but time for coaching had not been protected.
A team was responsible for an action, but ownership within the team was unclear.
A process depended on collaboration between people who were rarely in the same meetings.
Professional learning occurred, but there was no structure for continued practice, feedback, or follow-up.
That distinction matters.
These can easily appear to be individual performance problems.
Sometimes they are.
But before reaching that conclusion, I want to understand whether the system surrounding the work made successful implementation possible.
Leadership insight
An action step is not the same as an implementation structure.
Writing an action into a plan identifies an expectation.
It does not automatically create the time, routines, communication, access, knowledge, support, ownership, or monitoring necessary to carry it out.
That work still has to be designed.
For me, this is where implementation becomes a leadership responsibility rather than simply an expectation placed on the people closest to the work.
Leaders have to translate strategy into operating conditions.
From Plan to Practice
A timeline existed, but the people responsible for the work had different understandings of when something was expected.
I have encountered implementation barriers that had very little to do with whether people believed in the work.
When I think about that translation, I look for several connected conditions:
Clarity
Do people understand the strategy, the intended outcome, and what implementation should look like?
↓
Ownership
Is it clear who is responsible for what, including who leads, supports, monitors, and follows up?
↓
Readiness
Do people have the knowledge, skills, access, resources, and time required to begin?
↓
Structures & Routines
Where does the work live in the organization? What meetings, schedules, protocols, processes, or routines will support it?
↓
Support
What coaching, professional learning, feedback, modeling, collaboration, or problem-solving will people need as they implement?
↓
Monitoring & Adjustment
How will leaders know whether implementation is occurring as intended, where barriers are developing, and what needs to change?
These conditions do not operate as a simple checklist that leaders complete once.
Implementation changes what leaders know.
Monitoring may reveal a capacity gap. A capacity gap may require additional support. Support may uncover unclear expectations. A change in staffing or scheduling may require redesigning a routine.
The system must be able to learn and adjust as the work progresses.
Questions I would ask before calling something an implementation problem
When a strategy is not moving as expected, I would want to know:
- Do the people responsible for the work understand what successful implementation looks like?
- Is ownership clear, or are responsibilities assumed?
- Do people have access to the information, tools, and resources the work requires?
- Has time actually been created for the work?
- Are existing schedules and routines supporting the strategy or competing with it?
- Did professional learning prepare people to begin, and is there continued support after the initial learning?
- Are the people responsible for supporting implementation included in the conversations and decisions that affect their work?
- Is there a consistent process for monitoring implementation?
- Does monitoring examine what is happening, or only whether an action was marked complete?
- When a barrier is identified, is there a way to adjust the support, structure, timeline, or approach?
Those questions help separate two very different situations:
The strategy itself may need to change.
Or:
The organization may need to strengthen the conditions surrounding the strategy.
Leaders need to know which problem they are solving.
Completion can hide implementation problems
This is also why I am cautious about using completion as the primary measure of implementation.
A meeting occurred.
A training was delivered.
A resource was distributed.
A schedule was created.
A walkthrough was conducted.
A box can be checked beside each of those activities.
But completion tells us that something happened. It does not necessarily tell us what happened because of it.
Did the training increase people’s ability to implement the practice?
Is the schedule actually being used?
Did the resource clarify the work?
Did the meeting result in clear decisions, ownership, and next steps?
Did the walkthrough evidence lead to feedback, support, or adjustment?
Monitoring implementation requires leaders to move beyond Did we do it?
The more useful question is:
Is what we did helping the intended practice take hold?
The connection to strong people and weak systems
In the first article in this series, I asked whether the system is supporting the person or whether the person is compensating for the system.
That question remains important here.
A strong person can sometimes overcome unclear ownership, missing routines, limited resources, poor communication, or insufficient support.
That can make implementation look healthier than it is.
But an improvement strategy should not depend on extraordinary individual effort to survive.
A stronger test is whether the system makes successful implementation increasingly possible for the people responsible for doing the work.
That is how a practice begins to move from individual effort toward organizational capacity.
Implications for leaders
Do not treat approval as the end of planning.
Once a plan moves into practice, leaders will learn things they could not fully anticipate during development.
Translate every major strategy into operating conditions.
Determine what people, time, access, routines, communication, resources, and support the strategy actually requires.
Clarify ownership beyond a name on a plan.
People should understand who leads the work, who participates, who supports it, who monitors it, and who responds when barriers emerge.
Build support into implementation.
Do not assume initial communication or professional learning is sufficient. Complex work usually requires opportunities to practice, receive feedback, solve problems, and refine implementation.
Monitor the work beneath the outcome.
Outcome data matter, but leaders also need evidence about what is actually being implemented and under what conditions.
Use barriers as information.
When implementation struggles, determine what the barrier is telling you about the system before assuming the solution is greater pressure on the people doing the work.
A simple implementation check
Take one major strategy from your current improvement plan.
Then temporarily put the plan aside.
Ask the people responsible for implementing that strategy:
What exactly are you expected to do?
Then ask:
What do you need in order to do it well?
And finally:
What happens when something gets in the way?
Compare their answers with what leaders believe has been established.
The gaps between those answers may tell you more about implementation readiness than another review of the written plan.
Closing thought
Strong planning matters.
Organizations need clear goals, thoughtful strategies, meaningful actions, timelines, and evidence.
But a plan cannot create implementation conditions simply because those conditions are implied within it.
People still need clarity.
Ownership still has to be established.
Capacity still has to be developed.
Structures and routines still have to support the work.
Implementation still has to be monitored.
And leaders still have to respond when the reality of the work does not match what was anticipated during planning.
That is why I do not judge an improvement effort only by the quality of its plan.
I also look at what happens after the plan leaves the page.
Because ultimately, improvement is not produced by what an organization intended to implement.
It is shaped by what the organization has built the capacity and systems to actually carry out.
Continue Exploring
Explore Related Resources
The ideas in this Insight connect directly to your work around systems, implementation, capacity, monitoring, and continuous improvement. Your existing materials define systems and implementation as moving from plans to practice through structures, roles, routines, readiness, support, communication, and implementation monitoring.
Systems & Implementation
Explore resources related to structures, routines, readiness, roles, support, communication, monitoring, and sustainable implementation.
Monitoring, Evaluation & Continuous Improvement
Explore resources related to implementation monitoring, evidence review, evaluation, adjustment, sustainability, and continuous learning.
Featured Work
Explore selected examples of your frameworks, tools, and resources that connect planning, implementation, monitoring, and improvement.
Suggested WordPress settings
Category: Systems Shape Success
Tags: Systems Thinking, Implementation, Educational Leadership, Continuous Improvement, Organizational Capacity, Monitoring
Excerpt: A strong improvement plan identifies what an organization intends to do. Strong implementation requires more than that: the clarity, ownership, capacity, structures, support, and monitoring that enable people to move the plan into consistent practice.
Leave a Reply