The Missing Decision in the Handoff

Workplace Growth Daily · 2026-09-27

Workplace Growth Daily for LUMARA · 27 September 2026

Illustrative scene: A customer request reaches the next team with a file named “final-final”. The file is there; the decision about what the customer actually approved is not. Someone asks in chat, three people search their messages, and the work pauses. The filename, at least, remains confident.

Today’s focus is not a longer handoff document. It is a small habit: make the decision behind the work easy for the next person to find and question. This is a research-backed practical briefing, not breaking news. The findings below concern engagement and expectations; the handoff methods are LUMARA’s suggestions to test, not outcomes the research guarantees.

What is changing

Trends: what the evidence can—and cannot—tell us

In an article published 21 September 2026, Gallup reported that global employee engagement fell to 20% in 2025 and that managers account for 70% of the variance in team engagement. That makes a manager’s role in setting expectations worth examining. For a cross-team task, a practical question is whether both teams can name the same next decision and owner. The figures do not measure handoff rework. Gallup, 21 September 2026.
The same 21 September 2026 article reported that, in May 2026 U.S. engagement research, 29% of employees strongly agreed they had received recognition or praise for good work in the previous seven days. A team can recognise the colleague who records a useful decision or flags a gap early—not only the person who closes the task. This is a suggested practice, not a tested finding about handoffs. Gallup, 21 September 2026.
In research published 21 July 2026, Gallup found that 49% of U.S. employees strongly agreed they knew what was expected of them at work in the first half of 2026, up from 47% in

That is about general expectations, not cross-team transfers. Still, it gives teams a useful prompt: ask the receiving colleague to say what “ready” means before a request moves on. Gallup, 21 July 2026.

Build a skill in 10 minutes

Skill: decision-back briefing

Decision-back briefing means asking the receiving person to restate the decision they will act on, rather than merely confirming that they received the file. It takes a little courage to say “I don’t know what this means”; make that question welcome.

Ten-minute exercise: Choose one real task that will change hands today. For two minutes, the sender writes three plain-language lines: Decision made, Evidence or customer instruction behind it, and Still open. Include a link to the working record if there is one, but do not paste sensitive customer details into a new public space. For three minutes, the receiver reads the lines and explains what they would do next, without the sender filling gaps. Spend three minutes correcting any mismatch together. Use the final two minutes to name who will answer the remaining question and where the answer will be recorded.

Visible success criteria: The receiver can identify the approved next step and its owner; any unresolved point is labelled as unresolved; and both people can locate the same decision record. If they cannot, the exercise succeeded at finding a gap before it travelled further. Do not call that a failure of the receiver.

Staff and management: respect in both directions

Relationships: make it safe to ask before work moves

Managers should set the same clear acceptance standard for everyone sending or receiving work. Ask where the handoff is confusing, listen without interrupting, and recognise people who prevent an avoidable mistake. Check capacity before adding a new documentation step: a tidy record is not fair if someone must build it after hours. Give credit across teams, including to the person who notices an ambiguity rather than quietly repairing it.

Manager, say this: “Thank you for stopping to check. I may have assumed the approval was obvious. What is missing from the record, and what should we pause while we clarify it?” Then agree who will obtain the answer and when, rather than leaving the employee with an indefinite chase.

Staff can tell management what they understand, what they cannot verify, and what the delay may affect. Disagree about the process with evidence and a proposed next step; do not make it a judgement about another team’s competence. If a concern involves bullying or intimidation, raise it through the appropriate reporting route—nobody is expected to tolerate it.

Staff, say this: “I can take the next step once we confirm which option the customer approved. The current note points to both. Could we ask the owner to update the decision record before I proceed? If this is urgent, which other task should wait?”

Work better as a team

Teamwork: the 15-minute missing-decision map

Bring one anonymised, illustrative or real handoff that both teams recognise. The sender knows what was passed along; the receiver describes what they needed; a facilitator watches the clock and keeps the discussion about the process, not blame. If the real work contains confidential information, use a stripped-down version.

Minutes 0–3: On a shared page, write the customer need, the next team’s task and the point where work stalled. The receiver marks the exact question they had to ask. Do not jump straight to a solution.

Minutes 3–7: The sender identifies where the decision originally lived: a record, a message or a conversation. Together, distinguish a decision already made from one that is still pending. If nobody can verify it, write “unconfirmed”; do not reconstruct it from memory and present it as fact.

Minutes 7–12: Draft a compact handoff note with four fields: decision and evidence, open question, next action and owner, where to find updates. The receiver reads it back and flags anything they would still need to ask. Keep only fields that help the next action; this is knowledge sharing, not an archive-building contest.

Minutes 12–15: Agree where this note will live and who will update it when a decision changes. The shared output is one tested note plus one named owner for its upkeep. If the teams cannot agree on a decision, the output is a clearly labelled open question and an escalation owner—not a guessed answer.

Turn teamwork into measurable growth

Growth: a seven-day quality check

LUMARA’s suggested low-cost experiment is to try the four-field note on one recurring type of cross-team customer request for seven days. The owner is the manager of the receiving team, working with a sender-side colleague; they should use an existing shared workspace rather than introduce a new tool by default.

Before starting, record a baseline from recent comparable requests: the number handed over and the number reopened because a decision or instruction had to be clarified. Note how you identified a reopening, so the teams count it consistently. During the trial, record the same counts and one brief reason for each reopening. This connects the behaviour to quality: whether the next team can act on the customer’s confirmed instruction without having to revisit it.

At the seven-day review, ask whether the note was findable, whether clarification-related reopenings changed, and whether other causes explain the pattern. A week’s small sample cannot establish causation. Use workload as a balancing measure: ask senders and receivers how much extra time the note took and whether it delayed other work. Keep, simplify or stop the practice based on both sets of observations; do not claim a productivity or customer benefit that has not been measured.