Make It Safe to Say: “This Is Too Much”

Workplace Growth Daily · 2026-09-21

21 September 2026 — a research-backed practical briefing, not breaking news. None of today’s supplied sources was published within the past seven days.

Illustrative scenario: At 9:07, a manager announces that a request is “only a small extra.” Three cameras freeze—not because of the internet, but because everyone knows the small extra has brought several small friends.

Sustainable workload is not simply a question of personal stamina. It depends on whether priorities are clear, people can influence how work is done and raising a concern leads to a fair decision rather than a damaged reputation.

Today’s LUMARA suggestion is straightforward: make capacity discussable. Managers should ask what must move when work is added; employees should describe risks early and offer options. Trust grows through repeated, observable responses—not cheerful slogans beside an overflowing task board.

What is changing

Clarity improved, but voice weakened. In the first half of 2026, 49% of surveyed US employees strongly agreed that they knew what was expected at work, up two percentage points. However, Gallup also recorded slight declines in employees feeling that their opinions counted and that they were connected to organisational purpose. Overall engagement was 31% (Gallup, 21 July 2026). For a real team: a clear task list is necessary but insufficient. Ask whether people can challenge the list before overload or quality problems appear.
Active manager support is associated with stronger engagement. In organisations adopting AI, employees who strongly agreed that their manager actively supported its use had a 48% engagement rate, compared with 30% among employees reporting lower agreement. Gallup cautions that access to a tool alone does not establish productivity gains (Gallup, 21 July 2026). For a real team: whenever a process changes—technological or otherwise—managers should clarify boundaries, listen to concerns and adjust workloads rather than merely add expectations.
Unused capability can coexist with overload. CIPD reports that 45% of UK employees feel their skills are under-used in their current roles; its guide links skills mismatch with lower confidence, job satisfaction and productivity, as well as higher stress (CIPD, 24 June 2026). A separate practice resource identifies change fatigue, overlapping change and demands on people teams as 2026 challenges (CIPD, 7 May 2026). For a real team: do not assume that a busy person is using their best skills. Review both volume and fit.

Build a skill in 10 minutes

This is the ability to question additional work using evidence, trade-offs and options—not silence, panic or personal accusation.

A 10-minute exercise

Choose one live request.

Minutes 0–2: Write its intended outcome and deadline in one sentence.
Minutes 2–4: Estimate the time and attention it requires. Note one dependency.
Minutes 4–6: Identify what will be delayed, reduced or stopped if the request enters the current plan.
Minutes 6–8: Create two options: change scope, change timing, reassign work or pause another task.
Minutes 8–10: Practise a 30-second challenge: “We can deliver X by Friday if Y moves to Tuesday. If both dates must stay, we need Z support. Which trade-off should we make?”

Visible success criteria

You finish with:

one defined outcome;
one realistic capacity estimate;
at least one explicit trade-off;
two workable options;
a named decision-maker and decision time.

Success is not getting your preferred answer. It is making the decision and its consequences visible.

Staff and management: respect in both directions

Managers should apply consistent standards, explain expectations and priorities, recognise useful effort and judgement, and listen without punishing candour. They should check whether workloads are manageable—not wait for exhaustion to become obvious. If someone raises bullying, harassment or another safety concern, treat it seriously and use the appropriate formal route; nobody should be told to tolerate it for the team’s sake.

Manager—say this: “I can see three urgent items against two available days. Tell me where the pressure is greatest and what risk I may be missing. We will decide together what moves, then I will communicate that decision.”

Recognition should also be specific: “You raised the capacity risk early and gave us options. That protected the quality of the customer response.” This rewards responsible voice, not silent overextension.

Staff also have a responsibility to communicate early, distinguish facts from assumptions and disagree with the proposal rather than attack the person. State the workload, likely consequence and possible choices. Record the agreed priority afterwards. If normal discussion feels unsafe or fails repeatedly, use a trusted manager, HR, employee representative or formal reporting channel.

Employee—say this: “I disagree with adding this without changing the plan. My current commitments total about 18 hours before Thursday, and this needs another six. We could move the report, narrow this request or add support. Which option best protects the customer deadline?”

Work better as a team

Purpose: expose hidden overload and produce one agreed, sustainable plan.

Roles: a facilitator keeps the discussion neutral; a timekeeper protects the 15 minutes; a scribe updates the shared board; every team member contributes capacity information. The manager is the decision owner but speaks last during the risk round.

Steps

Minutes 0–3 — List: The scribe places every significant seven-day commitment on a shared board.
Minutes 3–6 — Mark: Each owner labels their item green (comfortable), amber (at risk) or red (not credible without a change). No defence is required yet.
Minutes 6–9 — Hear: Each person names one constraint or concern. No interruptions and no immediate problem-solving.
Minutes 9–12 — Trade: The group proposes work to stop, shrink, move or reassign. Check skill fit as well as spare hours.
Minutes 12–15 — Commit: The manager confirms priorities, owners and deadlines. The scribe records unresolved risks and when they will be decided.

Tangible shared output: a seven-day Capacity and Voice Map containing colour-coded commitments, agreed trade-offs, named owners and a short decision log. Send it to affected stakeholders so that removed work does not quietly return through another channel.

Turn teamwork into measurable growth

LUMARA’s practical suggestion: test whether an explicit workload trade-off improves reliability on one recurring customer-facing process, such as replying to support enquiries or checking orders.

Owner: the team manager.

Baseline: record last week’s number of items completed by the agreed deadline and the number returned for correction. Also capture the team’s average daily workload rating on a simple 1–5 scale.

Experiment: for seven days, discuss every new urgent request using the capacity-based challenge. The owner must document what is stopped, moved, reduced or resourced. Team members may flag amber or red capacity without having to present a complete solution.

Seven-day review: compare on-time completion and correction counts with the baseline. Ask: Did earlier voice reveal risks? Did customers receive a more reliable response? Which trade-offs helped, and which merely transferred pressure?

Balancing measure: compare average workload ratings and any extra hours worked. Do not call the test successful if service improves only because people work longer or skip necessary breaks. One week can indicate whether the behaviour merits further testing; it cannot prove lasting retention, productivity or revenue effects.