Back to the on-screen lesson ·
Useful feedback names the observed action, its effect and the next practice, soon after the event and about the work rather than the person — for good work as well as mistakes.
Paper packet. Every task here also exists on screen, where it is checked automatically; answers written on paper are not assessed by Nydus. When you are back at a device, enter your answers there.
You will frame feedback as an observed action, its effect and a next practice, keep it about the work rather than the person, order a short feedback conversation that ends with a check back, and give specific praise.
Training ends with someone working alone, with spot checks. Those checks find good work and mistakes, and what the owner says about them decides whether the work gets better.
| Term | What it means |
|---|---|
| Feedback | Information about how work went, given so it can be repeated or changed. |
| Observed action | What was done, as it could be seen. |
| Effect | What the action led to. |
| Next practice | What to keep doing or do differently. |
| Timely | Soon after the event, while it is clear. |
| Check back | A look at the work a few shifts later. |
'You're so careless' tells a cleaner that the owner is annoyed. It does not say what was careless, what it caused, or what to do differently, and it is about the person, which invites defense rather than change.
The same moment as useful feedback: The oven racks were left on the dish rack at the Mill Street apartment (the observed action), so the tenant had to call us back (the effect); next time, check off the racks on the checklist before packing up (the next practice). Each part does a job. The action is specific enough to recognize. The effect explains why it matters, without the owner having to raise their voice. The next practice gives the person something to do.
Give it soon, the same day if possible. A comment six months later at a review is about an event nobody remembers clearly, and the mistake has been repeated in the meantime.
Another way: table
One event, two kinds of feedback.
| About the person | About the work |
|---|---|
| You're so careless | The oven racks were left on the dish rack |
| — | so the tenant had to call us back |
| Do better | Check off the racks on the checklist before packing up |
Another way: steps
Most feedback in small businesses arrives only after mistakes. A team member who hears nothing when they do something well learns what to avoid, not what to repeat, and good habits fade because nobody knew they mattered. Specific praise uses the same three parts: you packed the cups upright in the dividers; all four boxes arrived without a chip; keep packing that way. 'Good job' and 'you're a star' are pleasant and teach nothing.
Notice the action. Write it as a camera would see it: 'the cable was left an inch too long', not 'sloppy work'.
Name the effect. What it caused for the customer, the business or the team: the customer came back, the plates looked messy, every box arrived intact.
Agree the next practice. Ask what would prevent it, or what to keep doing; agree one specific action.
Say it soon and privately. A short word after the rush, away from customers and other staff.
Check back. After a few shifts, look at the same work, and say what you see, especially if it has improved.
Check your feedback. Before giving it, read it back: does every sentence describe something that could be seen or measured? Is there an effect and a next practice? Would it still be fair if the person read it a month later? Over a month, count the share of feedback that names good work; if it is small, look for good work to name.
Describing the action rather than the person is needed because an action can be changed and a character cannot, at least not on a Tuesday afternoon. 'You're careless' leaves the person nothing to do except defend themselves.
Naming the effect is allowed, and helpful, because it gives the reason without a lecture. Once the person knows the tenant had to call back, the checklist step makes sense on its own.
Giving it soon is needed because memory fades and habits set. Feedback the same day is about an event both people remember; feedback months later is about a story.
Checking back is what turns a conversation into a change. Without it, neither person knows whether the next practice was adopted.
Feedback about a mistake belongs in private. Said in front of customers or the rest of the team, even mild feedback becomes embarrassing, and embarrassment makes people defend rather than change. A quick word in the back, after the rush, is enough.
Keep it short: the action, the effect, the next practice, and one question, such as 'does that make sense?' or 'what would help?'. A long lecture buries the one thing to change. Praise can be given in front of others if the person is comfortable with that; specific public praise also shows the rest of the team what good work looks like.
If the same issue keeps recurring despite clear feedback, look at the process before the person. A missing step in the standard work, a checklist without the item, a tool that makes the mistake easy: these are the usual causes, as the root-cause lesson showed. Feedback cannot fix a process; it can only ask a person to work around it.
A good test: would a different person, given the same instructions and tools, be likely to make the same mistake? If yes, fix the instructions and tools, and say so to the person: 'the oven racks weren't on the checklist; I've added them'. Feedback that ends with the owner fixing something is the kind people trust.
Feedback works best when it runs both ways. Ask team members, now and then, what makes their work harder: a step that does not make sense, a tool that is always missing, a customer request the standard work does not cover. Use the same three parts when they answer: what happened, what it caused, what might fix it.
An owner who asks, listens and changes something visibly gets more honest feedback, and hears about problems while they are still small. An owner who only gives feedback hears about problems when a customer complains.
The best feedback often comes from a number the person can see for themselves. A cleaner who can read the week's inspection results, or a mechanic who sees how many of their repairs came back, gets feedback every day without anyone having to give it. The owner's job then is to help read the number: which apartments failed, which repairs returned, and what changed.
A visible measure also makes feedback less personal. 'Your first-time pass rate fell from 96 to 88 percent this month; the three failures were all ovens' is about the work, and both people are looking at the same figure. The next lesson builds on this, making a measure the center of how each role is reviewed.
New staff need more feedback, more often, than anyone else, and they need much of it to be praise. In the first weeks, every check from the training lesson is a chance for specific feedback: what met the standard, what did not, what to practice next. A new starter who hears 'your mirror had no streaks under the light; that's exactly the standard' learns the standard faster than one who hears nothing until a mistake.
Plan a short check-in at the end of each of the first few weeks: two things that went well, one thing to practice, and a question about what would help. It takes ten minutes and does more for keeping a good hire than almost anything else an owner can do in that time.
Some feedback is uncomfortable: about a friend, a family member, a long-serving employee, or a mistake with real consequences. The method does not change, and it helps most here. Stick to the observed action, the effect and the next practice, and the conversation stays about the work instead of the relationship.
Prepare by writing the three parts down first. Choose a private time when neither person is rushed. Start with the facts, listen to their side, and agree the next practice together. Avoiding the conversation is usually the unkindest choice, because the mistake continues and the eventual conversation is harder.
Most feedback needs no paperwork. But when the same issue has been raised more than once, or when it touches safety, keep a short note: the date, the action, the effect, the agreed next practice and the check back. It protects both people, because it shows what was said and what was agreed.
These notes also feed the next lesson, on accountability, where a visible measure replaces memory and impressions in reviewing how a role is going. If a situation ever becomes serious enough to affect someone's job, the notes are the fair record that local employment rules may expect to exist.
The practice manager of a veterinary clinic in Minneapolis noticed that staff heard from her almost only when something went wrong, and that turnover among front-desk staff was high. She counted a month of her own feedback: of about 40 comments, 6 named specific good work, 22 corrected a mistake and 12 were general remarks.
She changed the habit. Each day she looked for one piece of good work to name specifically: 'you called Mrs. Lee back about the lab results within the hour, so she didn't have to chase us; keep doing that.' Corrections used the same pattern, privately and the same day, and each was followed by a check back.
Three months later her count was 24 specific praise, 14 specific corrections and few general remarks. Callback times improved, two process problems surfaced because staff began raising them, and the front desk went a year without anyone leaving, which the manager estimated saved about 4,000 dollars in hiring and training costs.
Research on workplace feedback consistently finds that feedback focused on specific tasks and actions improves performance more than feedback about the person, and that feedback about the person can make performance worse. The three-part pattern in this lesson is one simple way of keeping feedback on the task.
Feedback means criticism. Specific praise is feedback, and spreads good practice.
Judge the person so they take it seriously. Judgments invite defense; descriptions invite change.
Save it for the review. By then the moment is gone and the habit is set.
Once said, it's done. Checking back is what makes it work.
Feedback fixes every repeat mistake. If the process causes it, fix the process.
Note the action.
$\text{re-tested the brakes after adjusting}$
On the blue bike, named so there is no doubt which job is meant.
Note the effect.
$\text{the customer rode off safe}$
Why it matters.
Name the next practice.
$\text{every brake job, every time}$
What to keep doing.
Say it soon.
$\text{the same afternoon}$
While the job is fresh and both remember exactly what happened.
Check back on the work.
$\text{next week's brake jobs}$
And say so, so the change is noticed as well as the slip.
Note the action.
$\text{three plates, sauce on the wrong side}$
Specific enough that the assistant could repeat it word for word.
Note the effect.
$\text{the office's photos looked messy}$
Why it matters.
Agree the next practice.
$\text{check each plate against the picture}$
With the assistant.
Say it privately.
$\text{after the rush, in the back}$
Short, and out of hearing of the customers and the rest of the team.
Check back on the work.
$\text{the first ten plates next day}$
All right.
Praise the change.
$\text{every plate matched; keep checking}$
Specific praise.
Note the action.
$\text{racks left on the dish rack}$
At Mill Street.
Note the effect.
$\text{the tenant called us back}$
A return trip.
Ask about the cause.
$\text{racks not on the checklist}$
A process gap.
Fix the process.
$\text{racks added to the checklist}$
For everyone.
Agree the next practice.
$\text{check off the racks before packing up}$
One action.
Check back on the work.
$\text{the next five move-outs}$
No call-backs.
Praise the result.
$\text{five cleans, no call-backs; keep it up}$
Specific praise.
Note the action.
$\text{cups packed upright in the dividers}$
What was done.
Note the effect.
$\text{every box arrived without a chip}$
What it led to.
Name the next practice.
The owner of Northside Repairs wants to give a team member feedback about today's work. Which is useful feedback?
Complete the worked solution: Dev looked back at the $20$ pieces of feedback he gave his mechanics last month. $7$ named specific good work, $9$ corrected a specific mistake, and the rest were general remarks such as 'good job'. Find the share that was specific praise, the share that was specific correction, and the number of general remarks.
Find the share of specific praise.
$(\text{praise}) \div (\text{all}) \times \text{a hundred} =$ s
Out of every hundred notes.
Find the share of specific correction.
$(\text{correction}) \div (\text{all}) \times \text{a hundred} =$ k
The same measure.
Find the general remarks.
$(\text{all}) - (\text{praise}) - (\text{correction}) =$ g
Feedback that taught nothing.
Say what to change.
$\text{turn general remarks into specific praise}$
So good habits spread.
Maya's feedback to her assistant: 'You packed the café order with the cups upright in the dividers. All $2$ boxes arrived without a chip. Keep packing cups that way for every order.' Match each part.
| Observed action | Effect | Next practice | |
|---|---|---|---|
| You packed the cups upright in the dividers | |||
| All $2$ boxes arrived without a chip | |||
| Keep packing cups that way for every order |
Notes Dev made for feedback to his new mechanic. Mark every sentence about the work.
This task has no paper form; do it on a device.
Monica noticed her helper giving the wrong change twice this morning. Put her feedback conversation in order.
Number the steps in order (write the number in the box):
In the $20$ lunch orders before the owner's feedback about checking plates against the picture, Neighborhood Kitchen's new assistant sent out $7$ plates that did not match. In the $20$ orders after, $1$. By how many percentage points did the mismatch rate fall? Fill in each figure on the sheet.
| Amount | |
|---|---|
| Mistakes per hundred before | |
| Mistakes per hundred after | |
| Fall, per hundred |
A bakery manager in Portland noticed a new baker under-proofing the sourdough, so about $3$ loaves a week came out dense and were sold off at a discount, losing about $28$ dollars a loaf. She decided to wait for the baker's review, $6$ weeks away, to mention it. What did waiting cost, in dollars, if the mistake continued until then?
Answer:
A salon owner saw a junior stylist check a client's patch test before coloring, as the salon requires, on all $4$ appointments this week. What should she say?
Lesson test: one question per skill, one attempt each, no hints. Your answers are checked when you submit.
The owner of Bright Home Cleaning looked back at the $20$ pieces of feedback she gave last month. Only $9$ named specific good work. Complete the sentence.
Only p percent of last month's feedback named specific good work.
You can give feedback someone can act on, whether the work went well or badly. Tell someone why 'you're a star' teaches nothing. Next: accountability through a visible measure.
21. Your turn: Maya's packing, step 3
$\text{pack that way for every order}$
What to keep doing.