Set the boundaries
Name the event that starts the process and the outcome that ends it. Identify the people who depend on that outcome. Without clear boundaries, a review can expand indefinitely or solve a small local problem while moving the difficulty elsewhere. Use a familiar example to keep the conversation specific.
Map the current reality
Write down the main steps, decisions, inputs and handovers. Include exceptions and informal workarounds. Keep the first map simple enough to discuss with the team. The purpose is a shared understanding, not a technically perfect diagram that only one specialist can interpret.
Challenge the purpose of each step
Ask what the step contributes, who needs its output and what would happen if it changed. Some controls exist for good reasons; others remain after the original need has disappeared. Consider the risks before removing approvals. Simplification should make responsibilities and safeguards easier to understand.
Define ownership and feedback
Give the revised process an owner and agree how people will raise issues. Use a small set of measures connected to the outcome, such as completion reliability or avoidable rework. Review after the new process has been used in real conditions and adjust the design based on experience.
A useful next step
Choose one question from this article and discuss it with the people closest to the work. Write down the current position, a possible improvement and the evidence you would need to decide. Keep the first action small enough to review.
STOVELO editorial. General management information, not advice tailored to a particular business. No specific outcome is guaranteed.
Explore relevant services