Make Feedback Fair Enough to Use

Workplace Growth Daily · 2026-09-18

18 September 2026 — a research-backed practical briefing, not breaking news. None of the supplied evidence was published in the past seven days.

Illustrative scenario: A project review begins with, “Let’s be completely honest.” Three people suddenly become fascinated by their notebooks; one studies the ceiling as if it contains the strategy. The manager praises a “great team effort”, then tells one employee their attitude is “not quite right”. Nobody knows what to repeat, change or challenge.

Feedback fails when it becomes a verdict on the person rather than useful information about the work. Recognition fails when it is distributed by visibility, confidence or habit instead of contribution. Today’s LUMARA approach is simple: use observable evidence, apply consistent expectations and leave room for a respectful response.

What is changing

1. Managers strongly shape the conditions around engagement. Gallup says managers account for 70% of the variance in team-level engagement, and identifies clear expectations, recognition and coaching among the elements managers can influence (Gallup, 26 March 2026). For a real team, feedback is not administrative decoration. Managers need shared standards, specific recognition and regular conversations—not a dramatic annual ambush.

2. Clarity remains weak for many employees. Gallup reports that its 2025 data found only 47% of employees strongly agreed that they knew what was expected of them at work; it also identifies unclear expectations and limited recognition as contributors to detachment (Gallup, 26 March 2026). The practical implication: before criticising performance, check whether the expected result, deadline, quality level and decision rights were genuinely clear.

3. Manager capacity matters too. Gallup’s study of 2,658 US managers found that managers with high well-being were twice as likely to be engaged at work. Its longitudinal analysis found that well-being influenced later engagement slightly more than engagement influenced later well-being (Gallup, 24 April 2015). This is an association with directional longitudinal evidence, not a promise. For teams, the useful lesson is to avoid expecting overloaded managers to deliver thoughtful feedback through sheer goodwill.

LUMARA’s practical suggestion: treat clarity, recognition and manageable workload as one system. If any part is missing, even well-intended feedback can feel arbitrary.

Build a skill in 10 minutes

This skill keeps difficult feedback focused on observable work rather than personality.

Ten-minute exercise

Choose one real feedback point that you need to deliver.

Minutes 0–2 — Write the evidence. Record what was seen, heard or delivered, including when and where. Remove labels such as “careless”, “negative” or “brilliant”.
Minutes 2–4 — Check the standard. Write the expectation previously communicated. If none was clear, acknowledge that management must clarify it before judging fairly.
Minutes 4–6 — State the impact. Name the effect on a customer, colleague, deadline, quality measure or workload. Avoid guessing motives.
Minutes 6–8 — Ask and listen. Draft one open question: “What was happening from your perspective?”
Minutes 8–10 — Agree the next step. Make it small, specific, supported and time-bound. Include what the manager will do.

Visible success criteria

A neutral observer can identify:

one observable example;
one known expectation;
one work-related impact;
one genuine invitation to respond;
one agreed action, owner and review date.

Apply the same structure to recognition: name the contribution, its impact and what should be repeated. “Excellent work” is pleasant; “Your concise handover let support answer the customer without reopening the case” is useful.

Staff and management: respect in both directions

Managers should treat staff with dignity and apply comparable standards to comparable work. That means setting clear expectations, recognising specific contributions—including less visible work—listening before reaching conclusions, and checking whether workload is manageable. Difficult feedback should be private, timely and based on evidence. If bullying, discrimination, threats or retaliation are alleged, do not frame them as a communication-style problem or ask someone to tolerate them; follow the organisation’s formal safeguarding, grievance or reporting route.

Manager, say this: “I want to discuss Tuesday’s client handover. The agreed checklist required the risk note, but it was missing, so the service team had to contact the client again. What happened from your perspective? Let’s agree a workable safeguard. I will also check whether the deadline and workload made the expectation unrealistic.”

Staff can communicate upwards by describing the event, its work impact and the change requested. Ask questions, keep relevant records and disagree with the proposal rather than attacking the person. If direct discussion feels unsafe or the concern is serious, use an appropriate trusted contact or formal channel.

Staff member, say this: “I see the deadline differently. Completing both checks by Friday would require us to skip the agreed quality review. Can we compare the risks and decide which outcome takes priority? I’m raising this because I want the delivery to be reliable.”

Recognition should also travel upwards and sideways. Thank colleagues for concrete contributions, not for sacrificing their health or repeatedly absorbing unreasonable work.

Work better as a team

Run this 15-minute exercise with four to eight people. The tangible output is a one-page Team Feedback Standard containing three agreed rules and one recognition example.

Roles

Facilitator: protects time and respectful participation.
Reader: presents the case.
Fairness checker: tests evidence and consistency.
Recorder: produces the shared standard.

Steps

Minutes 0–3: The reader shares an illustrative case: “A colleague submitted a report late after receiving two additional urgent requests. The manager plans to say, ‘You need to be more committed.’”
Minutes 3–6: Everyone silently rewrites the comment using Evidence–Impact–Next Step.
Minutes 6–10: Compare versions. The fairness checker asks: Was the expectation clear? Would the same standard apply to everyone? Was workload considered? Is there room for the employee’s account?
Minutes 10–13: Rewrite the feedback together and add specific recognition for something the employee did well.
Minutes 13–15: The recorder captures three rules—for example, “use observable examples”, “check prior clarity and workload” and “agree a review date”—plus the final recognition sentence.

Publish the one-page output where the team prepares one-to-ones and project reviews.

Turn teamwork into measurable growth

Experiment: For seven days, add one evidence-based recognition note and one clear next-step question to each daily shift handover or project check-in. This is a LUMARA suggestion, not a sourced claim that recognition guarantees performance.

Owner: Team leader.
Outcome link: Quality and customer experience.
Baseline: Review the previous seven days and record the number of reopened customer cases or internal corrections caused by unclear handovers. Also record how many handovers contained a named owner and next action.
Test: Recognise one specific helpful behaviour—such as documenting a customer constraint—and ask, “What is the next action, who owns it and by when?” Rotate recognition across contributors rather than rewarding only the most visible speaker.
Seven-day review: Compare reopened cases or corrections and the proportion of handovers with clear ownership against baseline. Ask the team which recognition felt specific and credible. Treat any movement as a signal for further testing, not proof of causation.
Balancing measure: Track handover duration and ask whether the practice added pressure or encouraged unpaid overtime. Stop or simplify it if workload rises materially.