Giving and receiving feedback at work: a simple guide
A simple guide to giving and receiving feedback at work: use the Situation-Behavior-Impact structure, try a coaching conversation for bigger topics, receive criticism calmly, and build a light weekly and monthly feedback rhythm.

Almost everyone in a small business has held back feedback they knew was needed. The late reports, the abrupt tone with clients, the great idea that deserved a thank you: it all goes unsaid because the moment never feels right. Then it comes out months later in a review, a heated meeting or a resignation letter.
Feedback is a skill, not a personality trait, and it works in both directions. This guide gives you a simple structure for giving feedback so it is specific and fair, a method for receiving it without getting defensive, and a rhythm that makes the whole thing routine instead of dramatic. It is written for owners, managers and team members in small businesses.
Why regular, small feedback beats rare, big feedback
Feedback that arrives once a year is too late to change anything and too big to absorb. Small, frequent comments are easier to give and easier to hear. A leadership resource summarising feedback models for managers recommends making feedback routine, with brief check-ins at the end of weekly meetings and a running record so progress is visible over time. It also advises giving feedback soon after the event, because memories fade, and that applies to praise as well as criticism.
The goal is growth, not judgment
Say so out loud. People hear criticism differently when they know you are on their side. A good opening line is "I am telling you this because I want you to succeed here." That sentence costs nothing and changes how the next minute lands.
Give feedback with the SBI structure
The most widely taught simple model is Situation, Behavior, Impact, developed at the Center for Creative Leadership. Wipfli's guide to the SBI model lays out three steps.
The three steps
- Situation. Tie the comment to a specific moment: "In yesterday's project kickoff..."
- Behavior. Describe what you saw or heard, using only observable facts: "...the meeting started five minutes late and ended without decisions."
- Impact. Explain the effect on you, the team or the work: "...so two people left unsure who owns the next step."
The key discipline is separating what you observed from what you assume. "You do not care about deadlines" is a judgment. "The report was due Tuesday and arrived Thursday" is a fact. Judgments start arguments; facts start conversations.
Pause and listen
After the three steps, stop talking. Wipfli's guidance suggests pausing, resisting the urge to over-explain and letting the person respond or share their view. Good follow-up questions are "How did that look from your side?" and "What would you do differently next time?"
Timing and privacy
Wipfli recommends sharing feedback within about a week while details are still fresh. Give corrective feedback in private and positive feedback in public when the person is comfortable with it. If someone is overwhelmed, let them postpone the conversation; this matters even more on video calls, where emotional cues are harder to read.
Examples
| Instead of | Try | |---|---| | "You are careless with invoices." | "Three invoices this week had the wrong client address. Two came back, and we lost a day each. How can we catch these before they go out?" | | "Great job!" | "The way you walked the client through the three options on Monday made the decision easy. They approved the same day." | | "You need to communicate better." | "On Friday the delivery date changed and I heard about it from the customer. I would like a heads-up in the team channel as soon as a date moves." |
Use a coaching conversation for bigger topics
SBI suits simple, recent, clear-cut feedback. For broader or more sensitive topics, the same leadership resource describes the Pendleton method, a coaching-style conversation in five loose steps:
- Ask the person what they think went well.
- Affirm their strengths and add your own specific praise.
- Ask what they would do differently next time.
- Offer your own practical suggestions.
- Agree on an action plan together.
This works well because the person speaks first. Many people are harder on themselves than you would be, and hearing their own analysis makes your suggestions feel like a shared plan, not a verdict. The same source adds a few useful rules: keep praise genuine, do not soften criticism into something vague, and address one topic at a time so the person is not overwhelmed.
Receive feedback without getting defensive
Hearing criticism is uncomfortable for everyone. A few habits make it easier. Northwestern University's HR office offers tips for receiving feedback that include letting the speaker finish, asking for more detail and summarising what you heard in your own words.
A six-step routine for the receiver
- Breathe and listen. Do not interrupt or explain yet.
- Take notes. Writing the key words keeps you calm and shows you take it seriously.
- Ask for an example. "Can you tell me about one time you noticed this?"
- Repeat it back. "So what you are saying is..." and check you have it right.
- Say thank you. You do not have to agree to appreciate that someone took the risk of telling you.
- Follow up. Take time to think, then return with questions or a plan.
The University of Colorado's feedback guide adds that you should look for something useful even when it is delivered badly, ask for specific examples and own your part in the outcome. You can separate the message from the messenger: a clumsy comment may still contain a true point.
Asking for feedback
Do not wait to be given it. Ask specific questions such as "What is one thing I could do to make our handoffs smoother?" Specific questions get specific answers. Wipfli also notes you can ask for feedback using the same structure: name the situation, describe the behavior you want input on and ask how it affected others.
Build a simple feedback rhythm
| When | What | Who | |---|---|---| | After a task or client meeting | One specific comment, positive or developmental | Peer or manager | | Weekly | Five-minute check-in: what is working, what is stuck | Manager and each team member | | Monthly | A slightly longer one-to-one on goals and growth | Manager and team member | | Quarterly or yearly | A formal review that summarises, never surprises | Manager |
The rule for formal reviews is simple: nothing in the review should come as a surprise, because it has already been discussed during the year. For a repeatable review process, see fair performance reviews for small business and team accountability without micromanaging.
This article is general management guidance, not legal or HR advice. For disciplinary action, termination or anything involving protected characteristics, check local employment law or speak to an HR professional.
Common mistakes
- The feedback sandwich overload. Burying a real concern between two compliments makes people miss it. Be kind and clear instead.
- Saving it up. A list of ten issues in one meeting overwhelms. Give it as it happens.
- Labels instead of facts. Words like "lazy" or "negative" trigger defence. Describe actions.
- Public criticism. Humiliation destroys the trust you are trying to build.
- No follow-up. Feedback without an agreed next step fades. Write it down and check back.
- Only negative feedback. If you only speak up when something is wrong, people learn to dread you. Notice what goes right.
- Arguing with the receiver. If you are debating details, you have moved from feedback to a fight. Pause and return to facts.
Where WorkBOS fits
Feedback is more useful when it connects to real work. In WorkBOS, managers can run performance appraisals and keep goals, tasks and workload visible in one place, so a one-to-one can start from what the person actually did rather than from memory. Surveys can collect team input, and chat lets a quick thank-you go to the right person straight away. Start with the free plan for up to five users, compare options on the pricing page or learn the appraisal flow in the docs. The conversation itself, of course, still has to happen between people.
Frequently asked questions
Q: What is the SBI feedback model? A: Situation, Behavior, Impact. You name the specific moment, describe only what you observed and explain the effect it had, then pause to listen. It keeps feedback factual and less personal.
Q: How soon should I give feedback after something happens? A: Soon, ideally within about a week while the details are fresh, and sooner for positive comments. Check the person is ready to talk; if they are overwhelmed, agree on a better time.
Q: How do I give feedback to someone who gets defensive? A: Stick to observable facts, say why you are raising it, and ask for their view before offering yours. If emotions run high, pause and reschedule rather than pushing on.
Q: How should I react to feedback I disagree with? A: Listen fully, ask for an example, repeat what you heard and say thank you. You can take time to think and then respond. Often there is something useful even in comments you do not fully agree with.
Q: How often should managers give feedback in a small team? A: Little and often: a quick comment after relevant moments, a short weekly check-in and a longer monthly one-to-one. Annual reviews should summarise, not surprise.
Sources are linked in the text above: Wipfli, Leading Edge, Northwestern University, University of Colorado.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →