Once a strategy is approved, leadership needs a shared view of the work: what matters, who is accountable, what is happening and which decisions need attention.
Translate the priority into an organised piece of work
A strategic priority may be too broad to manage as a single action. “Improve the customer experience” could involve research, service design, staff capability and systems. Each part may depend on another decision or activity.
Break the priority into work that can be assigned and reviewed. Define the intended result, the next milestone and any dependencies. Keep the connection to the strategic priority visible so that the action list does not become detached from its purpose.
Make accountability specific
An action can have many contributors, but leadership needs to know who is accountable for coordinating it and reporting its position. A name beside an action is only useful if that person understands the responsibility and has the authority and support required.
Clarify who contributes, who approves key decisions and who resolves constraints. Where ownership crosses functions, agree how the teams will coordinate rather than assuming collaboration will happen.
Distinguish progress from a business outcome
Completing a project milestone demonstrates that work has been done. It does not necessarily show that the desired business result has occurred.
For example, completing a new process design is a delivery milestone. Whether the process improves service reliability requires separate evidence. Both are useful to review, but they answer different questions.
Two useful views
Action review asks: “What has been completed, what comes next and what is blocking the work?” Performance review asks: “What has changed in the business, and does the evidence support the intended result?”
Keep the measures proportionate. A small action may need a clear completion criterion. A significant initiative may need milestone reporting and a defined set of operating or commercial measures.
Use meetings to resolve decisions
A review meeting should have enough information in advance for participants to understand the position. The discussion can then concentrate on constraints, dependencies and decisions.
A useful action update explains progress since the last review, the next step, changes to timing and the help required. A status label alone rarely provides enough context.
Record the decisions made and the responsibility for following them through. If a constraint cannot be resolved at that meeting, agree who will address it and when it returns for review.
Adapt the plan without losing the record
Implementation takes place in a changing business. New evidence can make an action less useful, reveal an overlooked dependency or alter the sequence of work.
Changes should be deliberate. Record the reason, the approving decision and the effect on related work. Preserving this history helps leadership distinguish an agreed adjustment from a missed commitment.
Establish a manageable review rhythm
- Keep an agreed record of priorities and actions.
- Assign an accountable owner and a practical next milestone.
- Identify dependencies and the decisions required to resolve them.
- Review action progress and business performance separately.
- Record changes and agree the next review point.
The system can be simple. Its value depends on whether people keep it current and use it to coordinate work and make decisions. Technology can support visibility, while ownership and management discipline give that information purpose.
Discuss the question in your business.
Explore our implementation and organisational capability or contact us to define a practical scope.
Implementation and organisational capabilityThis perspective provides general planning considerations. The appropriate approach depends on the circumstances and evidence in your business.