Praise the Fix, Discuss the Miss

Workplace Growth Daily · 2026-09-25

Workplace Growth Daily · LUMARA · 25 September 2026

Illustrative scene: A customer asks why a revised order still carries the old delivery date. The account manager has fixed the order, but the correction never reached dispatch. In the team chat, someone types, “Great save!” Someone else types, “Who missed the update?” Both messages arrive before anyone checks what happened. The order now has three delivery dates and, apparently, a fan club.

The useful conversation is neither a public celebration that hides the miss nor a hunt for someone to blame. It is a private, specific discussion of the handoff, followed by recognition for the work that genuinely helped the customer. This is a research-backed practical briefing, not breaking news: none of the supplied findings on this angle was published in the past seven days. Findings below are sourced; the exercises and scripts are LUMARA’s practical suggestions, not tested outcomes.

What is changing

What the evidence suggests

Recognition belongs in everyday management. In its India workplace report, published 20 August 2026, Gallup says Indian managers clarify expectations, coach performance, recognise contributions and manage trade-offs. It reports that 23% of Indian employees were engaged in 2025. That is an India-specific finding, not a score for your team. For a real team, the practical question is whether people know what good work looks like and hear when they have done it.
Managers need capacity to do that well. The same Gallup report, published 20 August 2026 says engagement among Indian managers fell from 39% in 2024 to 30% in 2025. This does not establish why any particular manager is struggling. It does suggest a useful team check: before adding another feedback routine, ask what existing meeting or report it can replace.
Development is on employers’ minds, but practice needs a task. A CIPD UK employer survey reported on 22 September 2026 found 48% had increased efforts to develop talent in-house over the previous year. This describes surveyed employers, not a guaranteed retention result. For a team, a short rehearsal of a difficult conversation is more concrete than telling someone to “improve communication.”

Build a skill in 10 minutes

Skill: the two-sided feedback check

LUMARA suggests practising feedback that names the contribution and addresses the problem without making either one cancel the other. Use a real, low-stakes work example with identifying details removed. Keep performance discussions with the person concerned private.

Ten-minute exercise: Spend two minutes writing down what you directly observed, separating it from guesses about intent. Spend two minutes identifying the agreed expectation and the effect of the work on a customer or colleague. Spend two minutes naming one specific contribution worth recognising. Then spend three minutes saying the feedback aloud: observation, impact, recognition, concern, and a question that invites the other person’s account. Use the final minute to write an agreed next step—or a question that still needs an answer.

For example: “You corrected the customer’s order quickly; that helped us respond. The revised date did not reach dispatch, so the customer received conflicting information. What happened at that point in the handoff, and what check would make the next update clearer?” The first sentence credits a real action. The second addresses a separate miss. Neither guesses at character or motive.

Visible success criteria: A listener can point to one observable contribution, one observable gap against a stated expectation, an invitation to explain, and a next action with an owner. If the account is disputed, success means recording what needs checking—not pressing for agreement before the facts are clear.

Staff and management: respect in both directions

Respect travels both ways

Managers: Apply the same stated standards to comparable work, while checking whether people had the same information, authority and time. Give recognition for specific actions, including quiet work that prevents errors; do not reserve praise for whoever speaks loudest. Explain expectations before judging a result. Listen without interruption, ask what blocked the work, and keep workload manageable by deciding what will move when a new check is added. A difficult conversation can be direct without becoming an audience event. Bullying, intimidation or retaliation are not feedback; use the appropriate workplace reporting route rather than asking anyone to tolerate them.

Manager—say this privately: “I appreciate how you resolved the customer’s request. I also need to discuss the delivery-date update that did not reach dispatch. Our agreed step was to confirm the change before replying. What did you see, and is that step workable with your current queue? Let’s agree who owns the next confirmation.”

Staff: You can acknowledge an error without accepting an inaccurate account of it. Bring a concrete example, state the effect, ask for the expected standard, and propose a workable alternative. Disagree with a decision by explaining a risk and requesting a review, rather than assigning motives. If a concern involves bullying or safety, document it and use the appropriate reporting channel; a routine coaching chat is not a substitute.

Staff—say this: “I agree the customer needed one confirmed date. I updated the order, but I did not know dispatch needed a separate message. Can we confirm that expectation? With today’s queue, I can take on that check if we move the summary report, or we can assign it elsewhere. Which option should we use?”

Work better as a team

A 15-minute handoff rehearsal

LUMARA’s team exercise turns the illustrative delivery-date problem into a shared standard, not a vote on who was at fault. Use a fictionalised order; do not name the colleague from a live incident. Assign a facilitator to protect time, a customer voice to say what the customer must receive, a handoff mapper to trace the update, and a scribe to capture the decision. Others act as reviewers; the facilitator invites each person once before opening discussion.

Minutes 0–3: Read the fictionalised sequence: a change is confirmed, the order is corrected, dispatch retains the previous date, and the customer receives mixed messages. Each person silently writes one thing that worked and one point requiring clarification.

Minutes 3–7: The mapper draws the path from customer request to dispatch confirmation. The customer voice identifies the exact point where an inconsistent message could leave the team. Reviewers ask factual questions, not “Who usually messes this up?”

Minutes 7–11: Draft one recognition sentence for the useful correction and one respectful question about the missed update. Test both against the two-sided feedback check. If someone raises workload or unclear authority, record it as a condition to resolve, not an excuse to dismiss.

Minutes 11–15: Agree a single handoff rule: who sends the revised date, who confirms receipt, and what happens when confirmation is missing. The scribe posts a one-page shared output containing that rule, a sample customer-safe update and one unresolved question with an owner. Make it available to anyone who could not attend.

Turn teamwork into measurable growth

Seven days, one modest test

LUMARA suggests testing the handoff rule on revised delivery dates for seven days, rather than announcing a permanent fix. The owner is the dispatch lead, working with the account manager. Before the test, count revised-date orders from the previous seven days and note how many prompted a customer query about conflicting dates; record the number reviewed so the comparison is meaningful. If that count is unavailable, start measuring now and do not claim an improvement against an invented baseline.

During the test, use the agreed confirmation step and offer private, specific recognition when someone catches a mismatch before a customer message goes out. Discuss misses using the same evidence standard. At the seven-day review, compare the share of revised-date orders followed by conflicting-date queries with the baseline, and examine examples where the rule did not work. The balancing measure is added time per revised-date order and any work displaced from the queue. Keep, simplify or drop the step based on what the team observes; a better conversation alone does not guarantee a better customer result.