Same Work, Same Standard, Shared Credit

Workplace Growth Daily · 2026-10-02

LUMARA Workplace Growth Daily — 2 October 2026

Illustrative scene: At the weekly service meeting, Leo gets applause for a polished customer presentation. Mina, who checked every figure and spotted an incorrect price, gets asked why her spreadsheet arrived late. The spreadsheet, sadly, has no acceptance speech prepared.

Both contributions deserve an accurate account. The late delivery also deserves a conversation—but not a personality verdict, and not before anyone asks what changed during the work.

Today's angle: check whether the same standard applies to comparable work, then make the whole contribution visible.

This is a research-backed practical briefing, not breaking news: none of the supplied research articles was published within the last seven days. The findings below are sourced; the exercises and scripts are LUMARA's practical suggestions.

What is changing

Recognition is far from universal. Gallup's article published 21 September 2026, reporting May 2026 US research, says 29% of employees strongly agreed they had received recognition or praise for good work in the previous seven days. Gallup. Team implication: review whose useful work receives attention, including preparation and checking—not only presentations.
Clear expectations remain uneven. In the first half of 2026, 49% of US employees strongly agreed they knew what was expected at work, up from 47%, according to Gallup's article published 21 July 2026. Gallup. Team implication: before criticising a result, establish whether the standard, deadline and competing priorities were explicit.
Internal development is receiving more attention. CIPD's release published 22 September 2026 reports that 48% of surveyed UK employers increased efforts to develop talent in-house over the previous year. CIPD. Team implication: make feedback usable for learning, with a supported practice opportunity rather than simply a rating.

These findings describe different populations and measures. They do not establish that today's exercise will improve retention or productivity.

Build a skill in 10 minutes

Before delivering feedback, ask: Would I describe this work the same way if someone else had done it? Compare similar responsibilities and circumstances, not people with different roles.

A 10-minute exercise

Minutes 0–2: Choose one forthcoming feedback conversation. Write the agreed expectation and one observable event. Replace labels such as “careless” with what happened.

Minutes 2–4: Record relevant context: changed instructions, available time, dependencies and support. Mark anything you still need to ask about.

Minutes 4–6: Test your wording against a comparable colleague. Would “confident” become “pushy”? Would one person's missed deadline be excused while another's becomes a character flaw?

Minutes 6–8: Draft two separate sentences: one recognising a specific contribution, another addressing the gap. Do not make praise a decorative wrapper around criticism.

Minutes 8–10: Read the wording to a partner, who identifies assumptions and asks one clarifying question.

Visible success criteria: your draft contains an agreed standard, an observable event, a genuine question and a feasible next step. It names a useful contribution without personality labels or comparisons that shame someone.

Staff and management: respect in both directions

Managers: discuss sensitive performance concerns privately. Explain expectations before evaluating them, recognise specific work and ask how each person prefers to receive recognition. Listen without preparing your rebuttal. Check whether the workload was manageable and whether your own instructions contributed to the problem.

Equal standards do not require identical support. Explain role-relevant expectations while allowing appropriate adjustments. If you got the facts wrong, correct the record—including public credit when appropriate.

Manager—say this: “Your price check caught an error before the presentation; thank you. We also agreed the sheet would be ready on Tuesday, and it arrived Wednesday. What changed? Let's agree the next deadline and what needs to move so it is achievable.”

Staff: raise concerns using specific examples, explain the impact and request a clear decision. You can disagree with an interpretation without attacking the manager. Ask for the standard in writing if it remains unclear.

Staff—say this: “I agree the sheet was late. The extra price review was added on Tuesday, and I flagged the timing risk. I disagree that this shows a lack of commitment. Can we clarify which task takes priority next time, and acknowledge the checking work?”

Respectful disagreement is not permission for bullying, humiliation or retaliation. If these occur, document the incidents and use an appropriate reporting route, such as HR, a trusted senior manager or a staff representative.

Work better as a team

Use fictional cases, not disguised complaints about identifiable colleagues.

Roles: a facilitator keeps discussion on standards; a recorder captures decisions; a timekeeper protects the limit. Everyone reviews.

Minutes 0–3: The facilitator shares two anonymous fictional cases: each worker completes accurate work one day late after an additional checking task. One delivers the presentation; the other prepares the underlying information.
Minutes 3–6: Individually write what deserves recognition, what needs discussion and what context is missing.
Minutes 6–10: Compare responses. Identify differences based on visibility rather than responsibility. Ask whether the deadline expectation applies equally.
Minutes 10–13: Agree recognition wording and one respectful opening question for each case.
Minutes 13–15: The recorder produces a shared feedback reference card with four headings: expectation, evidence, contribution and context to ask about.

Keep the card available for future conversations. Its purpose is consistent reasoning, not identical scripts or a public ranking of colleagues.

Turn teamwork into measurable growth

Low-cost experiment: for seven days, use the reference card during existing reviews of customer quotations. Recognise useful checking work and discuss errors against the same agreed accuracy standard.

Owner: the quotation team lead. Use the existing tracker; do not buy a tool or add a meeting.

Baseline: record the previous seven days' proportion of quotations returned for correction, plus the number reviewed. Keep the quotation type comparable.

Balancing measures: record review time and ask staff whether the approach added work or made it harder to raise concerns. Recognition must not reward unpaid extra hours.

Seven-day review—9 October: compare correction proportions, review time and staff observations. Check for changes in case difficulty before interpreting the result. Continue, adjust or stop. A small before-and-after test cannot prove causation, but it can help the team decide what to examine next.