Workplace Growth Daily · 2026-09-28
Workplace Growth Daily | LUMARA | 28 September 2026
Illustrative scene: At 10:12, a customer request arrives marked “urgent”. At 10:14, another arrives with three exclamation marks. By lunch, the team’s task list looks like a small airport departures board, except nothing has actually taken off. One colleague knows the deadline is unrealistic but hesitates to say so. The manager, seeing no objection, assumes the plan is fine.
Today’s move is modest: when work arrives, make room for it openly. That means asking whose task it displaces, when the customer needs an answer and what the team can deliver well within its available time. This is a research-backed practical briefing, not breaking news: none of the supplied research was published in the last seven days. The exercises below are LUMARA’s suggestions, not tested outcomes promised by the sources.
What is changing
What the research says—and what a team can do with it
- In its 21 July 2026 report, Gallup reported that 31% of US employees were engaged in the first half of 2026, unchanged from
- The share strongly agreeing that they knew what was expected of them rose to 49%, while Gallup noted slight declines in feeling that opinions count and in connection to organisational purpose. For a real team, a clearer task list is not enough: ask whether people can challenge the list and see what happens next. These are US survey findings, not a measurement of LUMARA.
- In a 22 September 2026 UK employer survey release, the CIPD reported that 48% of surveyed employers had increased efforts to develop talent in-house over the previous year; 44% reported greater difficulty retaining talent. This does not show that training solves retention. It does make a practical question worth asking: when someone takes on development work, which existing duty will be reduced, shared or paused?
- The CIPD’s 24 June 2026 skills-matching guide says mismatches can show up as trust issues, stress and lower confidence, alongside lower job satisfaction and productivity. Its publicly available page reports that 45% of UK employees feel their skills are under-used. The useful team question is not simply “Who can do more?” but “Who is suited to this task, wants a fair chance to try it and has room to do it?”
Build a skill in 10 minutes
Skill: Capacity-aware prioritisation
Practise it in 10 minutes using one incoming request. For two minutes, write its customer impact and genuine deadline—not just the urgency label. For three minutes, identify the work already committed, the available owner and what would have to move. Spend three minutes offering two feasible options: for example, a smaller response sooner or a fuller response later. Use the final two minutes to write the decision, its owner and when affected colleagues will hear it.
Visible success criteria: a colleague can point to the agreed next step, the task being deferred or narrowed, the person authorised to decide and the customer-facing commitment. If no work moves and no capacity has appeared, the request is not yet a workable plan. The aim is not to become better at squeezing extra tasks into the evening. It is to make the trade-off legible before anyone pays for it privately.
Staff and management: respect in both directions
Trust needs a reply, not just an invitation to speak. Managers should give everyone the same clear expectations for priority, deadlines and quality. Ask about manageable workload without making people justify every minute; listen without interruption; recognise specific contributions without rewarding habitual overwork. Explain decisions, including why a concern cannot be resolved immediately, and revisit them. Never treat bullying as a difference of opinion to be endured: address it through appropriate workplace channels.
Manager—say this: “You’ve flagged that the new request clashes with the customer checks already due. Thank you for raising it. What would you pause or narrow? I’ll decide with you before we promise a time, and I’ll explain the decision to everyone affected.”
Staff can help management act by naming the constraint, the consequence and an alternative. Disagree about the plan rather than a person’s motives; ask for a decision if two priorities conflict. If raising an issue directly feels unsafe, use an appropriate alternative reporting route rather than staying silent.
Colleague—say this: “I see why this customer request matters. I disagree with adding it to today’s queue unchanged: I’m already due to finish two checks, and rushing either could affect quality. Could we move one deadline or agree on a smaller first response?”
A respectful challenge should not be a test of bravery. Managers can make it routine by asking, “What have we missed?” and then showing what changed—or why it did not. Staff should not have to disclose personal circumstances to establish that the agreed workload exceeds the available time.
Work better as a team
15-minute team exercise: The capacity card
Use one real incoming request, with customer details removed if needed. The facilitator keeps time and invites each person to speak; a request owner explains the need and deadline; a capacity checker names existing commitments; a recorder captures the decision. Rotate these roles next time so the same person is not always expected to challenge the plan.
Minutes 0–3: The request owner states what the customer needs and what is still uncertain. The facilitator asks the group not to treat “urgent” as a complete specification.
Minutes 3–7: Each person silently notes one potential conflict or overlooked dependency. The capacity checker then reads the current commitments aloud. Invite objections before the most senior person proposes a solution; the facilitator ensures quieter colleagues have a way to contribute, including in writing.
Minutes 7–12: Compare two choices: defer or narrow an existing task, or offer a smaller first response to the new request. Name the quality check that must remain. The manager or designated decision-maker chooses, states the reason and checks whether the choice creates hidden extra hours for anyone.
Minutes 12–15: The recorder produces a shared capacity card: request, agreed scope, customer response time, owner, displaced or narrowed task, quality check, unresolved concern and review point. Share it where the team normally tracks work. A card that says “everything stays on schedule” despite a known conflict goes back for revision.
Turn teamwork into measurable growth
A seven-day test, not a growth promise. The customer-service lead owns a low-cost trial: use the capacity card for one category of incoming customer requests during the next seven days, rather than changing every workflow at once. Before starting, record the previous seven days’ baseline for that category: how many replies missed the agreed time and how many needed correction or reopening. Use the same definitions during the trial; if volume changes, note that too.
At the seven-day review, compare the counts, read a small selection of affected customer messages and ask the team whether decisions became easier to explain. The balancing measure is workload: record extra hours worked and whether essential checks were skipped. If response timeliness improves only because people work longer or quality falls, do not call the test a success. If the pattern is mixed, adjust one part of the card and test again. This experiment may improve understanding; it cannot guarantee retention, productivity or revenue.
Try it today
Try it today
- Pick one incoming request with a genuine priority conflict.
- Ask the people doing the work what it would displace.
- Agree a scope and response time that leave room for quality checks.
- Record the decision, owner and unresolved concern where everyone affected can see them.
- Thank the person who surfaced the conflict; follow up on what happened.
Discussion question: When we call something urgent, whose existing commitment becomes negotiable—and who gets to say so?
