Most people put off holding someone accountable for one reason. They do not want to be the bad guy. So they wait, hint, sigh loudly near the coffee pot, and hope the problem fixes itself. It rarely does.
Here is the short answer. You can hold someone accountable without embarrassing them if you do four things. Talk in private. Start with facts, not labels. Ask before you decide what happened. End with a clear next step and a date to check in. The rest of this page gives you the words to say, a ten-minute meeting plan, and what to do the following week.
Why accountability feels so hard
If you dread these talks, you are not weak. You are kind, and you are worried about hurting someone. That is a good instinct. It just needs a better plan.
Many leaders think they have only two choices. Say nothing and keep the peace, or speak up and risk a fight. Al Switzler of Crucial Learning calls this kind of either-or trap a "Sucker's Choice." There is a third option: speak up, and do it with respect.
And it matters. When Google studied what made its teams work, one of the five things that mattered most was dependability. On dependable teams, members "reliably complete quality work on time." Dependability does not happen by accident. It happens when somebody notices a missed promise and talks about it in a way that keeps the person's dignity.
Rule one: correct in private
Kim Scott, author of Radical Candor, puts it simply: praise in public, criticize in private. She calls it "a rule of thumb, not a law." Her reason is plain. When people are corrected in front of others, they get defensive. Then they are busy protecting their pride, not fixing the problem.
So do not raise it in the team meeting. Do not raise it in the group chat. Do not raise it in the doorway with three people walking by. Ask for a few minutes alone, at a calm time, not right after a mistake when everyone is upset.
One more thing. If the person does great work, you may want to thank them in front of the team. Scott notes that some people dislike any public attention, so ask what works for them.
Rule two: name the gap, not the person
The Center for Creative Leadership teaches a feedback tool called Situation-Behavior-Impact, or SBI. It has three parts:
- Situation. When and where it happened. Be specific. CCL warns against vague words like "last week."
- Behavior. What the person did that you saw or heard. Keep to the facts.
- Impact. What happened because of it.
Crucial Learning teaches a close cousin of this idea. Describe what you agreed on, then what you saw, and how the two were different. In Switzler's words, "start with facts, not emotions or conclusions."
Here is the difference in practice:
| Embarrassing | Respectful |
|---|---|
| "You're always late with this." | "We agreed the schedule would go out Thursday at noon. It went out Friday afternoon." |
| "You clearly don't care about this team." | "Two people came in on their day off because they did not have the schedule." |
| "What's wrong with you?" | "Help me understand what happened." |
The left column puts a label on a person. The right column puts a fact on the table. Facts can be fixed. Labels just get argued with.
Rule three: ask before you decide
CCL adds a fourth step to SBI. After you share the impact, ask about intent. One question they suggest is: "What were you hoping to accomplish with that?"
Then stop talking. Really listen. You may learn that the person did not know the deadline moved. Or they were waiting on someone else. Or they are dealing with something at home. Or, yes, they just forgot.
Crucial Learning frames this as finding the cause. Was it a skill problem, or a motivation problem? A person who does not know how to do the task needs help. A person who knows how but does not see why it matters needs a different talk. You cannot tell which one it is until you ask.
Rule four: end with a real next step
A talk that ends with "Okay, just do better" is not accountability. It is a wish.
End by agreeing on three things, out loud:
- What will happen next.
- Who will do it.
- When you will check in.
Crucial Learning's Justin Hale puts the last part as two questions: "When will they take that action? When will you follow up with them?" Write the answers down. Let the other person say them back in their own words.
The ten-minute private talk
Use this plan when one person missed something they agreed to do.
Purpose. Address a missed commitment, find the cause, and agree on a next step, while keeping the person's dignity.
Time. About ten minutes.
Group size. Two people: you and the person. Nobody else.
Materials. A quiet place, a note with the facts (date, what was agreed, what happened), and something to write the next step on.
Setup. Ask ahead: "Do you have ten minutes today? I want to talk about the Thursday schedule." Naming the topic is kinder than "We need to talk," which makes anyone's stomach drop.
Instructions.
- Open with respect (one minute). "Thanks for making time. I want to talk about something small before it turns into something big."
- Name the gap (one minute). "We agreed the schedule would go out Thursday at noon. It went out Friday afternoon. Two people came in on their day off."
- Ask and listen (four minutes). "Help me understand what happened." Then listen. Do not fill the silence.
- Agree on the fix (three minutes). "What would make Thursday at noon work next week?" Let them suggest the plan first. Add only what is missing.
- Close with the who, what, and when (one minute). "So you will send the draft to me Wednesday by 3:00, and I will check in with you Thursday morning. Does that sound fair?"
Discussion questions to ask the person.
- What got in the way?
- What do you need from me to make the next deadline?
- Is the deadline itself the problem? Should we change it?
- How do you want me to check in, so it feels like help and not like watching over your shoulder?
A way in for everyone. Some people freeze in face-to-face talks or need time to think. Offer a choice: "Want to talk now, or would you rather think it over and we meet tomorrow?" You can also send the facts in a short, kind note first, then meet. A person who does not speak English as a first language, or who has a hearing difference, may do better with the plan written down as well as spoken.
The following week. Check in exactly when you said you would. If it went well, say so, specifically: "The schedule was out Wednesday. That made Thursday easy for everyone. Thank you." If it did not go well, have the same talk again, a little more firmly, and look harder at the cause. If the same gap keeps happening, it may now be a pattern, and a pattern is its own conversation.
An illustration
This is an illustration, not a real person.
Dana leads a small maintenance crew. Marco, her best mechanic, has missed turning in his work orders three Fridays in a row. Dana is tempted to say something at the Monday huddle, with a little joke about "some people" and their paperwork. Instead, she asks Marco for ten minutes after lunch.
She says, "We agreed work orders get turned in each Friday. The last three Fridays they came in Monday. That meant the parts order went out late." Then she asks, "Help me understand what is going on."
Marco tells her the new tablet form logs him out before he can save it. He was ashamed to admit he could not get it to work. They agree that Marco will fill out paper forms this Friday, and Dana will get the tablet fixed by Wednesday. She checks in Friday afternoon. The forms are in.
Nobody was embarrassed. The real problem got fixed. And Marco is far more likely to come to Dana next time before a small problem grows.
Common mistakes
- Waiting too long. Small and soon beats big and late. By the fifth missed deadline, you are not upset about the deadline anymore. You are upset about all five.
- The "compliment sandwich." People learn to hear the bread and brace for the filling. Be kind and be clear. You do not need to hide the point.
- Talking to everyone about one person. A team-wide email about "a few people" embarrasses the guilty and confuses the innocent.
- Skipping your own part. Ask yourself first: was the expectation clear? Did I give a real deadline, or did I say "whenever you get a chance"?
- Forgetting to follow up. If you never check in, the person learns the agreement did not really matter.
Where this fits
Accountability is easier on a team where people already feel safe speaking up. If your team has gone quiet, start with How to Build Trust on a Team That Has Stopped Speaking Up. If you are new to leading, the First-Time Leader's Guide to Leading a Team shows how to set clear expectations from day one, which makes these talks much rarer. And the best place to practice keeping promises is with yourself, which is the heart of Lead Yourself First.
Sources
- Center for Creative Leadership, Use Situation-Behavior-Impact (SBI) To Understand Intent. The SBI steps, the intent step, and the quoted question. SBI is a trademark of the Center for Creative Leadership.
- Al Switzler, Crucial Learning, How to Hold Employees Accountable Without Micromanaging. The "Sucker's Choice," describing the gap, starting with facts, and agreeing on check-ins.
- Justin Hale, Crucial Learning, From Good to Great: Using the Crucial Accountability Model. Motivation and ability questions and the quoted follow-up questions.
- Kim Scott, Radical Candor, Why Praising in Public and Criticizing in Private Is Key. Praise in public, criticize in private, and why.
- Google re:Work, Guide: Understand team effectiveness. Dependability as one of five team dynamics.
The ten-minute meeting plan, the comparison table, the illustration, and the follow-up week are our additions.
Want your leaders to practice this together?
Our Lunch and Learn sessions bring a working session like this one to your team, over lunch, at your place. You bring the people. We bring the leadership.
Ask About a Lunch and Learn