Pass the Work, Not the Confusion

Workplace Growth Daily · 2026-09-20

20 September 2026 — a research-backed practical briefing, not breaking news.

Illustrative scenario: At 09:07, the customer team sends Operations a cheerful message: “Everything you need is in the folder.” The folder contains 14 files, three called “final” and one called “final_FINAL2”. Operations replies with the traditional workplace distress signal: “Quick question…”

A handoff is not complete when work is sent. It is complete when the receiving team can confidently take the next step. Today’s LUMARA briefing turns that principle into short, practical routines for sharing knowledge and reducing avoidable rework.

What is changing

1. Clear, regular communication matters. Gallup reports that managers account for at least 70% of the variance in team-level engagement scores. It also connects consistent manager communication with higher engagement and identifies clarity of expectations as a basic employee need. The underlying article is dated 8 April 2015; its evidence is primarily US-based, so teams should apply it thoughtfully rather than assume identical results everywhere (Gallup, 8 April 2015).

What it means for a real team: Managers should make the expected handoff explicit: what is being transferred, why it matters, who receives it and how “ready” will be judged. A shared checklist is more useful than telling people to “communicate better”.

2. Useful knowledge may already exist—but sit in the wrong place. CIPD reports that 45% of UK employees feel their skills are under-used in their current roles. Its guidance links good matching of skills and roles with greater job satisfaction and productivity, while mismatches can appear as lower trust, confidence and output, alongside higher stress. These are UK-focused, self-reported findings, not a universal measure (CIPD, 24 June 2026).

What it means for a real team: Before creating another process document, ask who has handled this type of request before. Invite that person to help design the handoff without automatically making them the permanent unpaid troubleshooter.

3. Learning works best when connected to actual work. In a YouGov survey of 1,342 people professionals and business leaders, conducted from 14 January to 3 February 2026, CIPD found that skills development around AI was often reactive or disconnected from deployment. Although the research concerns AI, its broader practical lesson is relevant: capability-building should follow real tasks and workflows rather than sit apart from them (CIPD, 29 April 2026).

What it means for a real team: Share knowledge at the point of handoff. Capture the exception, decision or customer context that the receiving team will actually need—not a generic presentation that everyone forgets by lunch.

Build a skill in 10 minutes

This is the ability to package work so that another team can act without reconstructing your thinking.

Ten-minute exercise

Choose one handoff due today.

Two minutes — outcome: Write one sentence beginning, “The receiving team needs to…”
Two minutes — context: Note the customer or business need and the most important decision already made.
Two minutes — contents: Link the current source files and label the authoritative version.
Two minutes — checks: Add two or three acceptance criteria: complete, accurate, approved or ready for the next action.
Two minutes — confirmation: Ask the receiver to explain their next step and name anything missing.

Visible success criteria

The handoff has one owner, one current source, a deadline, explicit acceptance checks and a named receiver. That receiver can describe the next action without searching through messages or arranging a rescue meeting.

This format is a LUMARA practical suggestion, not a finding from the cited research.

Staff and management: respect in both directions

A rushed handoff often shifts invisible labour onto the receiving team. Fair management means treating people with respect, setting clear and consistent expectations, recognising both visible delivery and behind-the-scenes knowledge sharing, listening before deciding where fault lies, and keeping workloads manageable.

Managers should not reward one team for speed if another team must repair the result. They should also create a safe route for concerns. Bullying, humiliation or retaliation should never be treated as normal pressure.

Manager—say this: “I want a usable handoff, not a fast-looking one. Please tell me what information, time or authority is missing. I’ll apply the same readiness standard to both teams, and I’ll recognise the people who prevent rework as well as those who deliver.”

Staff also have a responsibility to communicate early, use specific examples and propose a workable next step. Constructive disagreement challenges the process or decision—not the person. Where conduct is unsafe or bullying occurs, use the appropriate formal reporting or support channel rather than tolerating it.

Staff member—say this: “I disagree that this is ready to accept. The approval and customer priority are missing, so starting now may create rework. Can we either supply those items by 14:00 or agree that the deadline moves?”

Work better as a team

Use one recurring transfer between two teams. The tangible output is a one-page Handoff Receipt that both sides can reuse.

Roles

Sender: explains what is normally passed across.
Receiver: identifies what is needed to begin safely.
Customer voice: checks whether important customer context survives the transfer.
Scribe/timekeeper: captures the agreement and keeps the pace.

Steps

Minutes 0–3: The sender states the intended outcome and shows a recent example.
Minutes 3–6: The receiver names the three most common gaps or ambiguities—without blaming individuals.
Minutes 6–9: The customer voice asks, “What could be lost here that would affect the customer or final quality?”
Minutes 9–12: Agree five fields: outcome, owner, authoritative source, acceptance checks and unresolved risks.
Minutes 12–15: Test the receipt against the example. The receiver either accepts it or identifies one precise missing item.

Publish the finished receipt beside the workflow, not in a forgotten meeting deck. If a specialist contributes crucial knowledge, record it so the team can reuse it without repeatedly interrupting that person.

Turn teamwork into measurable growth

Aim: Test whether a simple receipt reduces rework and improves delivery quality. It does not guarantee revenue, retention or productivity gains.

Owner: The manager responsible for the workflow, supported by one representative from each participating team.

Baseline: Review the previous five comparable handoffs. Record how many were accepted without clarification or correction, how many clarification messages were required, and the approximate rework time. If five cases are unavailable, record every comparable case available and state the small sample.

Experiment: For seven days, use the Handoff Receipt on every eligible transfer. The receiver marks each one accepted, accepted with question, or returned with missing item. Record the reason without naming and shaming.

Customer/quality link: Track whether downstream errors, missed customer requirements or completion delays occur. Treat any change as a signal to investigate, not proof that the receipt caused it.

Seven-day review: Compare first-time acceptance, clarification count and estimated rework with the baseline. Ask both teams which field helped and which added no value. Keep, revise or stop the test.

Balancing measure: Track preparation time and perceived workload. A form that saves ten minutes downstream but adds half an hour upstream is not yet a good design.