Picture a supervisor returning from a two-day workshop on delegation.
The program was good. She understood why delegation matters. She learned how to choose the right person, explain the result, provide support, and follow up without micromanaging. Before leaving, she completed an action plan and promised to delegate more often.
Then Monday morning arrived.
An employee approached her desk holding a task folder.
“Ma’am, I’m not sure what to do next.”
The phone was ringing. Two deadlines were already in danger. Her own manager wanted an update. The supervisor knew that taking the work back would not help the employee grow.
She also knew she could finish the task herself in fifteen minutes.
Her hand reached for the folder.
The workshop did not necessarily fail. The supervisor was not lazy, dishonest, or unwilling to change. When the pressure returned, the old move was simply easier to run. It was familiar. It protected speed and certainty. The action plan had described what she wanted to do, but it had not prepared her for the moment when she would have to do it.
That is where most action plans fail.
They do not fail while people are writing them. They fail when Monday morning asks for a move the plan never made clear.
A Plan Can Look Complete and Still Be Unusable
Most action plans contain the familiar parts: goals, tasks, owners, deadlines, resources, and progress measures. These are useful. A plan without them will probably create confusion.
But their presence does not guarantee action.
A team can have a clear goal and still not know what to do first. A task can have a name beside it even though that person lacks the authority to make the necessary decision. A deadline can appear on the calendar while everyone quietly assumes the work will begin later.
The document looks complete because every box has been filled.
The work remains uncertain because the choices underneath the boxes have not been made.
An action plan is not merely a list of things people intend to do. It is a decision about what happens next.
That distinction changes the planning conversation. Instead of asking only, “What activities must we complete?” we ask, “What must someone do when the real moment arrives?”
For the supervisor, “delegate more” was an intention. The real moment came when the employee returned with a problem and the supervisor was under pressure. The action plan needed to help her decide what to say and do then.
She might have used a simple play: ask the employee what they understood, clarify the desired result, agree on one next step, and set a short check-in. That response may take five minutes instead of taking the whole task back.
Now the plan has entered the work.
Big Goals Often Hide the First Move
Organizations often begin action planning with important goals: improve teamwork, build accountability, increase customer satisfaction, reduce errors, accelerate innovation, or strengthen employee engagement.
These goals are worth pursuing, but nobody can perform them on Tuesday morning.
“Improve teamwork” does not tell a manager what to do when two departments blame each other for a delayed handoff. “Build accountability” does not tell a supervisor how to respond when an agreement is missed. “Increase customer satisfaction” does not tell an employee which decision can be made without waiting for approval.
The goal gives direction. The first move creates traction.
This is why large action plans sometimes create the illusion of progress. Teams spend hours breaking a broad objective into smaller tasks. They produce charts, timelines, and status reports. Yet the first move remains vague enough to postpone.
A stronger plan identifies one visible action close to the work.
When the handoff is delayed, who calls whom? When a commitment is missed, what conversation happens and by when? When a customer problem reaches a second team, who owns the next response?
The action should be clear enough that another person could tell whether it happened.
Assigning a Name Does Not Create Ownership
One of the easiest things to do in a planning workshop is place someone’s name beside a task.
“Maria will handle the customer follow-up.”
“James will coordinate with Technology.”
“The supervisor will monitor implementation.”
The plan now has owners. Or so it appears.
But responsibility without authority is not ownership. It is exposure.
Maria may be responsible for the customer response but unable to approve the solution. James may be expected to coordinate with Technology but have no access to the decision-maker. The supervisor may be told to monitor implementation without receiving the information needed to see what is happening.
When the work stalls, the named person looks accountable even though the decision still sits elsewhere.
A useful action plan tests ownership before the meeting ends. Does this person have the information, authority, access, time, and support needed to act? When the answer is no, the plan must name the missing condition and the person who can provide it.
Otherwise, the team has not assigned ownership. It has assigned someone to wait.
“Done” Can Hide an Unfinished Problem
A fictional composite case in Impact-First Leaders shows another weakness in conventional action planning.
A supervisor found a repeat labelling error and escalated the system issue to Technology. Technology accepted the request and placed the correction in a future deployment queue. The ticket was then marked closed.
Administratively, the action was complete.
Operationally, the wrong label remained available. The next shift was still exposed to the same mistake.
The team had moved the ticket. It had not moved the risk.
This is what happens when plans measure activity instead of movement. A meeting is held, so the action turns green. An email is sent, so the item is closed. A report is submitted, so the commitment is complete. Yet the condition that justified the action remains unchanged.
The Meridian team eventually adopted a stricter definition. A case would not be considered resolved simply because it had been forwarded or acknowledged. Someone had to own the next action, and the next comparable output had to be checked. When a permanent repair required more time, the issue remained actively owned rather than being declared closed.
That is what a good action plan must do: define completion in the real world, not only inside the reporting system.
Give the First Move a Clock
Final deadlines matter, but they do not protect the beginning.
A plan may say that the project will be completed in three months. That still allows the first serious action to be postponed for three weeks. By then, ordinary work has reclaimed everyone’s attention, the energy from the planning session has faded, and the reasons behind the decision have become less vivid.
A strong plan places the first move close enough to preserve momentum.
In many leadership and learning situations, forty-eight hours is a useful discipline. It is not a universal rule, but it forces clarity. What can this person actually do within the next two days?
The move may be small. Schedule the conversation. Send the request. Test the script. Ask five users to try the first version. Remove one approval. Review one real case. Agree on the owner of a delayed handoff.
Small does not mean unimportant. The first move changes the plan from something discussed into something already happening.
In Create Shifts, I use a simple design question: What will participants do within forty-eight hours? The action must be real, visible, and possible without waiting for an ideal situation. That first act becomes the bridge between the learning room and the workplace.
What Trainers Must Do Differently
Trainers often leave action planning until the end.
The program runs late. The final activity is shortened. Participants receive a worksheet and are asked to write three actions they will take after the session. They complete it because the facilitator is waiting, not because they have designed a move that can survive Monday.
A stronger close gives action planning enough time to do its real job.
Ask participants to choose one actual situation, not one broad aspiration. Let them name the first move, the likely barrier, the person involved, and the time it will happen. Then help them practise it while they are still in the room.
A participant preparing for a difficult conversation can draft the opening line and rehearse it. A manager planning to delegate can identify the task, the decision boundary, and the first check-in. A team trying to improve follow-through can rewrite one vague commitment with an action, owner, deadline, and proof.
When possible, let the first move begin before the session ends. Send the message. Book the meeting. Put the review on the calendar.
The workshop should not finish with the hope that action will happen later. It should finish with action already in motion.
What HR Must Examine After the Workshop
HR should not treat submitted action plans as proof of application.
The form proves that participants wrote something. It does not prove that their managers created room for it, that the first attempt happened, or that the action helped.
The follow-through system does not have to become heavy. HR can ask for one short proof story: What did you try? Where did you try it? What happened? What will you adjust on the next attempt?
Managers can use the same questions during a brief check-in. The purpose is not to catch people who failed to comply. It is to learn why the planned action survived or disappeared.
Perhaps the participant needed more practice. Perhaps the manager contradicted the new behavior. Perhaps authority was missing. Perhaps the play was too complicated to use under pressure.
That evidence helps HR improve the intervention instead of assuming people simply lacked commitment.
What CEOs Must Ask Before Approving the Plan
Executives often receive plans that look reassuring. Every initiative has an owner, due date, budget, and status colour.
Before approving the plan, ask three questions: What happens first? What must stop or wait so this can happen? What proof will tell us whether to continue, adjust, or stop?
The second question is essential. Every meaningful priority competes for money, time, and attention. When leaders approve a new action without removing or delaying anything else, they create a plan that is complete on paper and impossible in practice.
The third question keeps the organization honest. It prevents teams from reporting that they finished the activity when the underlying problem did not move.
These questions do not weaken accountability. They make accountability credible.
Put the Next Move Into Monday
A practical leadership training program should not finish with a worksheet full of good intentions. It should help leaders choose a real move, practise it, build the conditions around it, and return with proof that something changed in the work.
The supervisor in our opening scene did not need another paragraph explaining the value of delegation. She needed a response she could run when the employee returned with the folder and the pressure made taking the work back feel responsible.
That is the standard for action planning.
The plan should not merely describe a better future. It should prepare someone for the next difficult moment, give that person enough authority and support to act, and define the proof that will guide the move after that.
Most action plans do not fail months later.
They fail on Monday morning, when the old move is ready and the new one is not.
A useful action plan changes that.
About Jef Menguin
Jef Menguin is a leadership development consultant, professional speaker, and founder of Strategic Learning Consultants. He helps CEOs, HR leaders, and L&D teams connect leadership development to business goals and turn strategic priorities into daily leadership behavior.
Explore his work in leadership training, learn about his motivational speaking programs, or connect with him on LinkedIn.