The problem can sit between the teams.
A business improvement project can have a sensible goal, capable people, and executive attention, yet still struggle to move forward. One place to investigate is the connection between departments. Each team may complete its own tasks while the overall process remains slow.
Consider a hypothetical example. Sales sends a request. Operations waits for missing information. Finance needs a different approval. Technology is asked to automate a process whose rules are still unclear. Everyone has performed an activity, but responsibility for the next decision is uncertain. The useful diagnostic question is where that uncertainty begins.
Start with one real journey.
Choose a specific request, order, issue, or decision and trace it from beginning to end. Ask what happens at each step, who owns it, what information is required, and where the work waits. Keep the scope narrow enough that the people involved can examine actual examples.
Compare the process people describe with the work that occurs. A diagram can look complete while an everyday exception forces someone to chase an approval by email. That exception may reveal more than the formal workflow. Record the difference before deciding that another system or another meeting is the answer.
Agree what completion means.
A handoff is stronger when both teams agree on what must be supplied and what the receiving team is accepting. “Sent” is not always the same as “ready to work.” Define the required information, the point at which ownership transfers, and what happens when something is missing.
Keep those rules clear enough that the people using them can apply them. In the hypothetical sales-to-operations example, the relevant decision might be whether a request contains enough information to assign an owner. That is a more useful starting point than a broad instruction to improve communication.
Give exceptions an owner.
Most processes have unusual cases. The goal is to handle them deliberately. Identify who can make a decision, when the issue should be escalated, and how the outcome returns to the normal workflow. An exception without a decision owner can leave both teams waiting for someone else to act.
If the same exception recurs, it may be evidence that the process needs to change. Record the pattern instead of treating every incident as unrelated. The review should distinguish a genuinely unusual case from a routine situation that the existing process does not accommodate.
Measure the whole process.
A team can improve its own task time while work accumulates elsewhere. Choose measures that show the end-to-end effect of the change. Depending on the process, those may include elapsed time, repeated requests for information, rework, overdue actions, or progression to the next stage.
Establish a baseline before claiming improvement. Keep the measurement definition consistent so the comparison is meaningful. If the pilot changes which requests are counted, explain that difference. A smaller backlog alone does not establish an improvement if work has simply moved outside the visible queue.
Pilot before expanding.
A small, well-defined pilot gives the organization a chance to learn. Choose one team, location, or request type. Set a review date and agree what would justify expanding, adjusting, or stopping the change. The purpose is to test the proposed improvement against actual operating conditions.
Review both the process and the conditions around it. Do people understand the responsibilities? Can the systems support the workflow? Are managers reviewing the right exceptions? Is the information reliable enough to make a decision? Record the uncertainty alongside the promising signals.
Turn the findings into a decision roadmap.
A useful roadmap connects the issue to an action, an accountable owner, dependencies, and a measure of progress. It should explain why the action comes next and what must be learned before the following step. A shorter plan with explicit decisions can be easier to execute than a long list of disconnected initiatives.
At the next leadership review, choose one handoff that repeatedly needs intervention. Ask the teams to bring a real example and agree the decision that must become clearer. That creates a concrete starting point for assessment, a bounded pilot, and a review that can lead to action.
Kaizen Ignite helps leadership teams investigate these connections, prioritize practical improvements, and support implementation. An assessment conversation brings your operating context into the discussion and helps establish the right scope for further work.