73 negative, positive, and constructive scripts, each shown as the weak line and the rewrite
For about two years I kept a text file on my desktop called wording. It existed because I kept saying the wrong sentence. Someone would miss a date, I had roughly ten seconds before I was expected to respond, and what came out was you need to be more proactive. Accurate, useless, impossible to act on. The file was where I wrote down afterwards what I should have said instead.
Every example on this page is a pair. The first line is the one most of us reach for under pressure. The second is the same feedback rewritten so the person can do something with it. The rewrite is longer, usually by two or three sentences, and that is the whole trick. Vague feedback is short because it skips the part that costs effort, which is naming exactly what you saw.
This page is wording only. The frameworks, the cadence, and how to actually run the conversation are covered in the guide to employee feedback, and nothing here repeats them. What follows assumes you have already decided to say something and you are stuck on how to phrase it. I built FirstHR for small businesses where the founder is also the manager and the HR function, which is exactly the situation where the right sentence has to arrive fast.
TL;DR
Feedback works when it names a time and place, a behavior anyone in the room would agree happened, the effect that behavior had, and one specific request. Positive feedback follows the same shape. The 73 pairs below cover deadlines, communication, quality, initiative, team behavior, remote work, praise, and criticism, each shown as the vague version and the rewrite.
Why the wording is worth the effort
80% of employees who say they received meaningful feedback in the past week are fully engaged, according to Gallup research on feedback speed, and people are 3.6 times more likely to say they are motivated to do outstanding work when their manager gives feedback daily rather than annually. The word doing the work in that finding is meaningful. Frequency alone does not produce the effect if what arrives is a vague sentence that nobody can act on.
How to Use These Scripts
Take the rewritten line, replace the details with your own, and keep four moving parts: when it happened, what was observable, what it caused, and what you want next time. Drop any one of the four and the sentence collapses back into something the person can nod at and forget. That is the only rule that matters, and it is why the scripts are long.
Do not read them aloud. A script read word for word sounds rehearsed and people hear it immediately. Use them to draft the first two sentences before a conversation you know is coming, so you do not open with an accusation, then let the rest of it be a conversation. Most of the value is in the opening, because that is where the tone gets set and where the vague version usually escapes.
The table below is the fastest way to see what is missing from the phrases managers reach for by default. Each of these is something I have said and regretted.
The phrase you reach for
What it is missing
What to say instead
Be more proactive.
No behavior, no example, no request
When the tracker broke you waited for direction. On anything reversible, act and tell me after.
Work on your communication.
Names a category, not an act
Your standup update ran four minutes and the blocker came last. Lead with the blocker.
You need to be a team player.
A judgment about character
Jordan has asked three times and is still doing it wrong. Fifteen minutes on a call would end it.
Your attitude is a problem.
Not observable, so not arguable
You said the marketing numbers were made up, in the all hands, with Chris in the room.
Great job!
Reinforces nothing repeatable
You froze the scope in week three and held it. That is why the date held.
You always do this.
Always invites a counterexample
Three of the last five reports came in a day late.
People have been saying...
Unattributable and unanswerable
Two people asked not to be on projects with you, and both mentioned meetings.
I need you to step up.
No definition of the target
End every analysis with a recommendation you would defend.
One more thing before the examples. Who is speaking changes what the sentence can do, and most feedback advice quietly assumes a manager. The scripts here are split three ways, and the peer and upward versions are not the manager version with softer words. They are built differently.
From a managerYou can name a consequence and make a request that has authority behind it. That also means a careless sentence carries further than you intend.
From a colleagueNo authority, so the line has to stand on the cost to your own work. Peer scripts describe an effect on you and ask, they never instruct.
To a managerThe risk runs the other way. Upward scripts stay narrow, offer a fix, and give the manager an easy way to say yes without losing face.
Negative Feedback Examples
Negative feedback works when the recipient can check it. If they can go back to Tuesday, replay the meeting, and agree that the thing you described happened, you are having a conversation about behavior. If they cannot, you are having a conversation about whether you are being fair, and that conversation never produces change.
The forty examples in this section are grouped by the situations that actually come up in a small company. None of them is a formal step. If a pattern has survived several of these conversations, that is the point at which a written warning or a structured plan becomes the right instrument, and the wording rules change with it.
Missed Deadlines and Slipped Commitments
Deadline feedback goes wrong in one predictable way: the manager talks about the date and the employee hears an accusation about effort. Anchoring on the notification rather than the delay fixes most of it. What you usually need is not faster work, it is earlier warning.
A deadline slipped with no warning
Instead ofYou missed the deadline again.
Say thisThe client summary was due Thursday and it landed Monday afternoon. I found out it was late when the client emailed me asking where it was, so I had no answer for her. Going forward I need a message the moment you know a date is at risk, not after it passes.
A pattern of small slips
Instead ofYou are always behind.
Say thisThree of the last five reports came in a day or two after the date we agreed. Each one is small on its own, but Priya holds her part of the work open while she waits, so the delay roughly doubles by the time it reaches her. I want to look at what is making the estimates slip.
The date was hit but the work was rushed
Instead ofThis felt rushed.
Say thisThe proposal went out on time on Friday and two of the pricing tables still had numbers from the old version. It reads like the last hour was a scramble. I would rather you tell me on Wednesday that Friday is tight and we move it than send a document we have to correct.
No status update on a long project
Instead ofYou need to communicate better on projects.
Say thisThe site migration has been running three weeks and I have had no status update since kickoff. I do not need a report. When there is silence I cannot tell the difference between on track and stuck, and I start assuming the worse one. Three lines every Friday would fix it.
Overcommitting during planning
Instead ofYou take on too much.
Say thisIn planning you took six items after we agreed four was realistic. Two carried over, and the carryover is what pushed the release. When you feel the pull to say yes to everything, say the number out loud to me first and we will decide it together.
A dependency on someone else was missed
Instead ofYou dropped the ball.
Say thisThe vendor contract needed my signature before the first of the month and the request reached me on the second, so the renewal sits at the higher rate for a quarter. Anything that needs another person to act has to reach them with a working day to spare.
Repeated lateness to a recurring meeting
Instead ofBe on time.
Say thisYou have joined the Monday planning call five to ten minutes late four weeks running, and we restart the context each time, so the call runs long for six people. If the 11:00 slot no longer works, say so and I will move it. If it works, I need you on at the start.
Communication and Tone
Tone feedback is the hardest to phrase because tone is an interpretation, not an observation. The way through is to quote the actual message or describe what the room did afterwards. Both of those are facts, and facts are what make the conversation possible.
A blunt message in a shared channel
Instead ofYour tone was unprofessional.
Say thisIn the support channel yesterday you replied to Dana with, that is wrong, read the doc. She stopped posting questions in that channel for the rest of the week. The correction itself was right. The way it landed cost us the questions. Lead with the answer, then the doc link.
Interrupting in meetings
Instead ofYou talk over people.
Say thisIn the product review on Tuesday you cut in three times while Sam was still walking through the data. Two of your points are what changed the decision, so I want them in the room. I want them after he finishes. Write them down and take the floor at the end.
Long unfocused updates
Instead ofYour updates ramble.
Say thisYour update in standup ran about four minutes and the part the team needed, that the integration is blocked on the vendor, came last. People had already stopped listening. Lead with the blocker, then the detail, and hold it to a minute.
An email that reads as dismissive to a customer
Instead ofThat email was not great.
Say thisThe reply you sent on Wednesday said the issue was on their side and closed the thread. It may well be on their side. The customer read it as being brushed off and called me. When we hand an issue back, say what we checked, what we found, and what we will do if it turns out to be ours.
Disagreement raised only after the meeting
Instead ofYou are being passive aggressive.
Say thisYou agreed with the pricing change on Monday and then told two people afterwards it would not work. I would much rather hear the objection while we can still act on it. If something about the meeting stops you saying it there, tell me what it is and I will change how I run it.
Hedging that buries the point
Instead ofBe more confident.
Say thisThe risk memo opened with three paragraphs of caveats before the sentence that mattered, which is that we miss the compliance date without a second reviewer. The caveats made the risk look optional and two people read it that way. Put the conclusion in the first line and keep the caveats underneath.
Messages left unanswered
Instead ofYou are hard to reach.
Say thisTwice this month a customer question sat in your queue for two working days with no reply, and both times the customer followed up with me. You do not have to solve it that day. You do have to say you have it and when you will come back. Four working hours is the standard I want.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Quality feedback should name the error and the control that would have caught it. Telling someone to be more careful asks them to try harder at something they were already trying at. Telling them what check to run gives them a mechanism, and mechanisms survive a busy week in a way that intentions do not.
Repeated errors in customer-facing work
Instead ofThe quality of your work is slipping.
Say thisThe last three quotes that went to customers each had a pricing error, and the one on the fourteenth was out by a factor of ten. The customer caught it before we did. From here, every quote over five thousand dollars gets a second pair of eyes before it leaves, and I would like you to pick who that is.
Technically correct, practically unusable
Instead ofThis is not what I asked for.
Say thisThe report has every number in it and I could not find the answer to the question we opened with, which is whether churn is worse on the annual plan. The data is right. The shape is wrong. Open with the answer, then the table that proves it, then everything else.
Skipping a check because the change looked small
Instead ofYou are careless.
Say thisThursday went out without the staging run and the login page was down eleven minutes. I know the staging run feels like a formality on a one line change. Every outage we have had this year came from a small change. The checklist runs even when the change looks trivial.
Feedback already given has not been applied
Instead ofI have told you this before.
Say thisWe agreed two weeks ago that the weekly summary would include the numbers, not just the narrative, and the last two have gone out without them. I want to understand whether that is a memory problem, a time problem, or you disagreeing with the change, because those have three different fixes.
Documentation quietly skipped
Instead ofYou need to document better.
Say thisWhen you were out last week nobody could run the billing export because the steps live in your head, and Ana lost most of a day rebuilding them. Before you close a recurring task, the runbook entry has to exist. Ten minutes then saves the day we just lost.
Good work on the wrong priority
Instead ofYou are working on the wrong things.
Say thisYou put about two weeks into the reporting rebuild and it is genuinely better. The onboarding bug list did not move in that time, and that is what customers write in about. Nothing about the rebuild was wasted. It was second in line and it went first. Check with me before you switch.
Estimates that are consistently wrong
Instead ofYour estimates are useless.
Say thisThe last four estimates came in at roughly double the time. I plan the quarter off those numbers, so a consistent factor of two means I promise things we cannot deliver. Give me the number you would bet money on rather than the number you hope for, and I will plan around that.
Initiative and Ownership
Be more proactive is the most common piece of feedback in a small company and one of the least useful, because proactive is a description of a result rather than an action. The rewrite always involves naming the specific decision you want the person to make without you.
Waiting to be told
Instead ofBe more proactive.
Say thisWhen the shipment tracker broke on Tuesday you flagged it to me and then waited most of the day for direction. You already knew the workaround. On anything reversible, do the thing and tell me after. I will tell you which decisions are not yours to make, and that list is short.
Escalating what they already know
Instead ofYou escalate too much.
Say thisFour of the six questions you brought me this week were ones you had already answered correctly inside the same message. You are checking, not asking. If you are confident enough to write the answer, send the answer and copy me on it.
Owning the task but not the outcome
Instead ofYou need to take more ownership.
Say thisYou sent the onboarding documents to the new hire on day one, which is exactly what the task said. He still had not signed on day five and nobody chased him. The task is sending. The outcome is signed. Chase it until it is done or hand it to someone who will.
Bad news arriving late
Instead ofWhy did you not tell me?
Say thisYou knew on the second that the supplier had missed the container and I heard about it on the tenth. Eight days is the difference between rebooking and apologizing to customers. Bad news reaches me the same day you learn it, and I will not be annoyed about the news itself.
Doing the minimum in a role that has grown
Instead ofYou need to step up.
Say thisYour work is accurate and it stops exactly at the edge of the ticket. The role has grown past that. What I am looking for is the next question, which is why these tickets keep arriving, and one suggestion a month about what to change. That is the gap between this level and the next.
Not asking for help
Instead ofYou should have asked.
Say thisThe integration took you nine days and Marco had done the same one in two. He was one message away the entire time. I would rather lose ten minutes of his day than nine of yours. My rule of thumb is two hours stuck and then you ask someone.
Behavior in the Team
Behavior feedback carries the highest risk of sounding like a verdict on someone as a person, so it needs the tightest anchoring to a single incident. Describe what one other person did in response, because the effect on a colleague is the part that is hard to argue with. If the behavior has continued through several of these conversations, the situation has moved into managing a persistent problem rather than giving feedback.
Dominating meetings
Instead ofYou need to let others speak.
Say thisIn the last three retros you spoke for a bit over half the time by my count, and two people on the team have not offered an opinion in a month. Make one point and then ask someone who has not spoken what they think. Your points are good. I need theirs as well.
Criticizing a colleague in front of the team
Instead ofThat was out of line.
Say thisWhen you said in the all hands that the marketing numbers were made up, Chris was sitting two seats away and he did not speak again for the rest of the meeting. If the numbers are wrong that is worth pursuing. Take it to him directly first, and bring it to the group as a question.
Complaints that never reach the room
Instead ofStop the drama.
Say thisTwo people have told me about the side chat where the new process gets picked apart. The concerns in it are reasonable and not one of them has reached the meeting where we could act on it. If it is worth saying to three colleagues, it is worth saying to me.
Working around a decision after it was made
Instead ofGet on board.
Say thisYou argued against the new intake form, we discussed it, and we went ahead. Since then you have used the old form four times. Disagreeing during the discussion is exactly what I want from you. Once the call is made I need you running it, and telling me in six weeks whether you were right.
Not helping a newer teammate
Instead ofYou are not a team player.
Say thisJordan has asked you three times how the returns process works and each time he got a link to the folder. He is still doing it wrong. Fifteen minutes on a call would end it. Teaching the process is part of being the person who knows it best.
Credit for shared work
Instead ofYou took credit for that.
Say thisIn the board update the pipeline dashboard was described as your project. Nina built the data layer and it took her most of two weeks, and she was in the room. When work had more than one pair of hands on it, name the hands. It costs you nothing and it is why people help you next time.
Reacting badly to feedback
Instead ofYou are defensive.
Say thisWhen I raised the invoice error on Monday, the first four sentences back were reasons it was not yours, and some of them were true. What I needed first was, let me look. If the feedback is wrong, say so once you have checked and I will drop it. Starting with the defense makes me hesitate to raise the next one.
Remote and Async Situations
Remote feedback fails in a specific way: the manager describes a visibility problem as if it were an effort problem. Nobody is offline because they are lazy, and almost nobody writes a curt message on purpose. Name the gap in the signal rather than the imagined attitude behind it, which is the same adjustment hybrid teams need across most of their management practice.
Silent and camera off in every call
Instead ofTurn your camera on.
Say thisFor the last month you have been camera off and have not spoken in the weekly call unless asked directly. I do not care about the camera. I do care that a third of the team has no idea what you are working on. One update a week, in the call or in the channel, whichever you prefer.
Written messages that read colder than intended
Instead ofYou come across as rude in writing.
Say thisYour message closing the design thread was three words, no, we discussed. In a room that reads as brisk. In writing with no face attached, three people asked me if you were angry. One extra line of reasoning removes all of that and it costs you eight seconds.
Going quiet for hours with no signal
Instead ofYou are never online.
Say thisOn Wednesday there was a five hour gap with no reply while the release was going out and two people were blocked waiting on you. Deep work blocks are fine and I want you to have them. Post the block in the channel with an end time and they will plan around it instead of waiting.
Time zone load falling on one person
Instead ofYou need to be more flexible with hours.
Say thisYou have taken the seven in the morning call every week since the Berlin team joined, which means you start early and finish at the normal time. That is not sustainable and I did not set it up deliberately. From next month we alternate, and on the weeks you take it you start the rest of your day later.
Decisions that live only in a call
Instead ofNobody knows what you are doing.
Say thisThe decisions from your Thursday syncs exist in the call and nowhere else, so anyone who missed it asks you again. That is three or four interruptions a week for you. Five lines in the channel afterwards ends the interruptions and it is the only record we would have if you were out.
Fast for some people, slow for others
Instead ofYou are slow to respond.
Say thisThe pattern I see is a same day reply to me and a two or three day reply to people outside your immediate team. They have started routing requests through me to get a faster answer, which is worse for both of us. Same standard for everyone, one working day.
Positive Feedback Examples
Positive feedback should name the behavior you want repeated, not the outcome you were pleased about. Great job on the launch reinforces nothing, because the person did roughly a hundred things and does not know which one you are pointing at. The test is whether they could repeat the specific action from your sentence alone.
The other failure is timing. Praise saved for a review has almost no reinforcing power, because the behavior is months old and the setting makes it read as scoring rather than noticing. Gallup finds that 67% of employees whose manager focuses on their strengths are engaged, against 31% whose manager focuses on weaknesses, which is a large gap for something that costs a sentence. Structured recognition programs are a separate mechanism and they do not replace this.
Results and Delivery
A launch that actually hit its date
Instead ofGreat job on the launch.
Say thisThe launch went out on the date we set in January, which we did not manage on the previous two. What made the difference was you freezing the scope in week three and holding it when three separate people asked for one more feature. That decision is the thing I want you to repeat.
Someone fixed a cause instead of a symptom
Instead ofNice work this quarter.
Say thisSupport tickets are down about a third since you rewrote the setup guide, and it was not on anyone’s list. You noticed the same question arriving five times a week and fixed the cause instead of answering it faster. That is the most useful thing anyone did this quarter.
A deal that was heading for a no
Instead ofThanks for closing that deal.
Say thisOn the renewal that was going nowhere, you asked to speak to their operations lead rather than only the buyer, and the operations lead is who turned it around. Going one level sideways when the front door is closed is a move I want the rest of the team to learn from you.
Effort Under Pressure
An outage handled well
Instead ofThanks for the extra effort.
Say thisWhen the payment provider went down on Saturday you had the fallback live in about forty minutes and posted a plain English note to customers before anyone asked for one. Most of the value was the note. People forgive outages. They do not forgive silence.
A difficult customer de-escalated
Instead ofYou handled that well.
Say thisThe customer on Tuesday was shouting for the first two minutes. You let it run out, repeated the problem back in her words, and only then offered the credit. She has since renewed. Not matching the temperature in the room is a hard skill and you have it.
Covering for an absent colleague
Instead ofThanks for stepping in.
Say thisWith Ella out for two weeks you picked up the invoicing on top of your own work and nothing slipped on either side. I know what that cost you. I have moved the reporting deadline out a week so you get some of it back, because I would rather do that than pretend it was free.
Collaboration and Helping Others
Teaching instead of doing
Instead ofThanks for being a team player.
Say thisYou spent most of Thursday afternoon walking Ben through the pricing model instead of your own work, and he ran his first quote alone on Friday. That afternoon bought us a second person who can do the thing, which is worth more than the tasks you would have closed.
Making room for a quieter colleague
Instead ofGood work in the meeting.
Say thisIn planning you noticed Rosa had twice tried to get a word in and you stopped and handed it to her. Her point about the pilot customers is what changed the plan. Watching the room while you are in the middle of making your own argument is rare and I noticed it.
Building on someone else’s idea
Instead ofYou are easy to work with.
Say thisTwice this month you took a half finished idea from someone else and made it work rather than replacing it with your own, and the design review last week was the clearest case. People bring you things early because of it, and early is when ideas are cheap to change.
Growth and Change Over Time
Someone who now brings solutions
Instead ofYou have improved a lot.
Say thisSix months ago you would bring me a problem. Now you bring me the problem, two options, and which one you would pick, and I have agreed with your pick every time since April. That is the change I would point at if anyone asked what growth looks like here.
A presentation that got shorter
Instead ofYour presentation was better.
Say thisThe board deck ran fourteen slides instead of forty and you finished inside the time you were given, which has not happened before. Cutting your own material is the hardest edit there is. The questions afterwards were about strategy rather than about slides, which is how you know it worked.
A change that stuck
Instead ofGood job taking the feedback.
Say thisAfter we talked about the standup updates in March, the change showed up the next morning and it has held for four months. Most changes fade inside three weeks. Holding a small habit past the point where anyone is watching is the part almost nobody does.
Constructive Criticism Examples
Constructive criticism is not softened negative feedback. It addresses something that is not going wrong yet: a capable person with a narrow range, a strong contributor who cannot get their thinking read, someone who wants a promotion they are not ready for. The failure is usually the opposite of the negative case, which is that managers go so gentle the message never arrives.
Two rules keep it honest. Be specific about the gap even when the gap is uncomfortable, and attach a concrete next step so the conversation ends with work rather than with a feeling. If you are heading into a formal cycle, the phrasing conventions there are different again and covered in review keywords and phrases.
Craft and Skills
Strong work, narrow range
Instead ofYou need to develop more.
Say thisYour execution is the most reliable on the team and almost all of it sits inside the same three types of work. If the next role you want involves running something end to end, the gap is not skill, it is range. Take the supplier review as the owner rather than a contributor.
Excellent thinking, hard to follow
Instead ofYou need to work on communication.
Say thisThe retention analysis was the best piece of thinking anyone produced last quarter and I had to read it three times. The people who need to act on it will read it once. Get the finding into two sentences at the top and your work starts changing decisions instead of informing them.
Fast, but skips the check
Instead ofSlow down.
Say thisYou are roughly twice as fast as anyone else at a first draft and the rework eats most of the gain. The habit worth building is a ten minute pass before you hand anything over, reading it as the person who receives it. You would still be the fastest and the rework would go to near zero.
Great with detail, misses the frame
Instead ofThink more strategically.
Say thisYou catch things in the numbers nobody else catches. What I have not seen yet is you saying what we should do about it. The next step is to end every analysis with a recommendation you are willing to defend, even when you are only sixty percent sure of it.
Reluctant to lead
Instead ofYou should be more of a leader.
Say thisPeople already come to you for answers, which is most of the job. What is missing is you setting a direction rather than only responding. Run the Monday planning meeting for the next two months, and if it goes the way I expect we talk about a lead role after that.
Role, Direction, and Hard Conversations
Performance is fine, motivation is not
Instead ofYou seem checked out.
Say thisThe work is still good and something has changed in how you are showing up, and I am asking rather than assuming. You used to push back in planning and you have not in about two months. If the role has stopped being interesting, I would rather have that conversation now than after you have decided.
Not ready for the promotion they asked for
Instead ofYou are not ready yet.
Say thisI am not putting you forward this cycle and I want to be specific about why, because vague is worse than no. The gap is getting work done through other people. You already do your own work at the next level. Take the onboarding project with two people on it and we revisit in six months.
Right person, wrong role
Instead ofThis may not be the right fit.
Say thisYou are working harder in this role than almost anyone and getting average results, and I do not think that is about effort. The parts you are fastest at are all analysis and this job is mostly relationship management. Before either of us concludes anything, I want to talk about what an analysis role here would look like.
Behavior is costing them the promotion
Instead ofYou need to work on your soft skills.
Say thisYour results are the strongest case for the promotion, and the reason it is not straightforward is that two people asked not to be on projects with you, both mentioning meetings. That is fixable and it is the only thing in the way. I want to work on it with you rather than leave it unsaid.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Peer feedback has to earn the change rather than request it, because a colleague has no authority to make anything happen. The line that works describes a cost to your own work and then asks. The line that fails borrows a manager tone the relationship does not support, and it is heard as someone appointing themselves supervisor.
These are the seven I would hand to a team rather than keep for myself. They are worth circulating, because in a small company most friction never reaches a manager at all, and a structured process such as 360 degree feedback is a heavy instrument for something a two minute conversation would solve.
A colleague keeps missing a handoff you depend on
Instead ofYou keep holding me up.
Say thisI have been picking up the specs on Thursday afternoon for three weeks and I need most of a day with them, so I end up working Friday evening. If Wednesday is possible I get my part done inside hours. If it is not possible, tell me and I will change my end instead.
A colleague talks over you
Instead ofLet me finish.
Say thisI noticed I got about a sentence in before we moved on in the last two syncs, and I have a piece of this that has not been said yet. Can I take two minutes at the top of the next one.
Their output creates rework for you
Instead ofYour files are a mess.
Say thisWhen the export arrives with the columns in a different order I spend about half an hour remapping it. It is nothing once. It is two hours a month. Could we agree a fixed column order, and I am happy to be the one who writes it down.
Correcting a peer in front of others
Instead ofThat is wrong.
Say thisI think the number on slide four might be the old one, I have a different figure in front of me. Can we check it after this rather than hold everyone up now.
A peer took credit for shared work
Instead ofYou took credit for my work.
Say thisIn the update it came across as your project, and I did the data side, which was most of two weeks. I am not looking for an apology. Next time we present something we both worked on, I would like both names in it.
Praising a peer
Instead ofGood job.
Say thisYour question in the review about who actually uses the feature is what stopped us building the wrong thing. I would not have asked it. Thanks for slowing that one down.
A peer is struggling and it is reaching the team
Instead ofYou need to sort this out.
Say thisThe last few weeks have looked harder than usual on your side and I do not know whether that is the workload or something else. I am not asking you to explain. If there is a piece of it you would like me to take for a fortnight, say the word.
Scripts for Feedback to Your Own Manager
Upward feedback works when it is narrow, tied to work you are responsible for, and arrives with a fix attached. The risk runs the other way here, so a script that works downward almost never works in reverse. One issue per conversation is the right dose, and a regular one on one is the natural place for it.
Priorities are unclear
Instead ofI have too much on.
Say thisThe audit, the migration, and the hiring plan all land in the same two weeks. I can do two of them well or three of them at seventy percent. I would rather you pick which than have me guess and pick wrong.
Feedback arrived months late
Instead ofYou should have told me earlier.
Say thisThe point about the client emails came up in the review and it goes back to March. I would have changed it in March. When something like that shows up, could you tell me that week, even if it is only one line in a message.
Direction keeps changing
Instead ofYou keep moving the goalposts.
Say thisThe reporting spec has changed three times in five weeks and I have rebuilt it each time. I understand why each change happened. What would help is a week where the spec is frozen before I start building. I would rather wait a week than rebuild a fourth time.
Your manager rewrites your work
Instead ofYou are micromanaging me.
Say thisYou rewrote the customer email before it went out and the version that went is better. What I do not know is what was wrong with mine, so I will probably write the same thing again next month. Could you send me the two changes that mattered instead.
Praising your manager
Instead ofThanks for your support.
Say thisYou took the blame in the leadership meeting for the missed date and the call was mine. The team noticed. I wanted you to know it changed how people here talk about working for you.
Openers, Handovers, and Closers
Most feedback conversations are decided in the first sentence and the last one. The opener sets whether the person is preparing a defense while you talk, and the closer decides whether anything happens afterwards. These are the lines I use to move between the parts, independent of what the feedback is about.
Moment
The line
What it does
Opening something difficult
I have one specific thing I want to raise and it will take about five minutes.
Sets the size, which removes the dread of an open ended conversation
Opening when you might be wrong
Here is what I saw, and I may be missing context.
Leaves room for another version without weakening the observation
Naming the behavior
On Tuesday, in the product review, you...
Time and place make it checkable rather than arguable
Naming the effect
What happened next was...
Answers the unspoken question of why this is worth the conversation
Handing over the floor
That is what I saw. What did it look like from where you were sitting?
Turns a verdict into a conversation while you can still be corrected
Making the request
Going forward, what I need is...
The only part of the conversation that changes anything
When they get defensive
Let me finish describing it, then tell me where I have it wrong.
Keeps the observation intact without shutting the person down
Closing praise
That is the thing I want you to do again.
Names the behavior to repeat, which is the entire point of praise
Closing a hard one
What is your read on that?
Surfaces disagreement while there is still time to act on it
Following up a week later
I noticed you did the thing we talked about.
The follow up is what makes the next piece of feedback land
Wording That Backfires
Six words and phrases account for most feedback conversations that turn into arguments. They are not rude and none of them sounds wrong when you say it. Each one quietly moves the conversation off the behavior and onto something the other person can dispute, which is exactly where you do not want it.
Always, neverOne counterexample and the whole conversation becomes a debate about the word rather than the behavior. Use a count: three of the last five.
Attitude, energy, toneNot observable, so it cannot be confirmed or denied. Describe the sentence that was said and where it was said.
People have been sayingUnattributable and unanswerable. Either name the effect you saw yourself or say how many people raised it and what they raised.
A bit, slightly, kind ofSofteners tell the listener the issue is optional. If it is worth the conversation, it is not a bit of anything.
ButEverything before but gets discarded. Split it into two sentences and let the praise stand on its own.
We need to, one shouldThe plural hides who has to do what. Say I need and you, or do not say it.
There is a deeper version of this problem. The Harvard Business Review argument in The Feedback Fallacy (Buckingham and Goodall, March 2019) is that ratings and assessments say as much about the rater as about the person being rated, and that the part of feedback you can actually vouch for is your own reaction. That is why every rewrite on this page describes what happened and what it caused rather than scoring the person. You are a reliable witness to the effect something had on you. You are an unreliable judge of what kind of person they are.
Consistency matters more than eloquence
Feedback is evidence. If two people do the same thing and only one of them hears about it, the wording of the conversation is not what you will be asked about later. Apply the same standard across the team, and keep your notes factual and free of adjectives, because a note written in irritation reads very differently a year later. The EEOC guidance on prohibited employment practices is the reference point for what consistent treatment means in practice.
One last habit that matters more than any sentence here. Go back a week later and say you noticed the change. Almost nobody does it, and it is the single cheapest thing that makes the next piece of feedback land, because it proves the first conversation was about helping rather than about catching someone out.
How FirstHR Fits
Feedback only compounds when it is written down somewhere that survives a busy month, and in most small companies that place does not exist. FirstHR keeps employee profiles, notes, and the record of what was agreed in one system, so the conversation you had in March is still findable when you are writing a review in November. It is built for small businesses without a dedicated HR person, on flat, predictable pricing.
Key Takeaways
Every feedback line that works has four parts: when and where, what was observable, what it caused, and what you want next time.
The rewrite is always longer than the vague version, because the extra sentences are the evidence that makes it actionable.
Positive feedback should name the behavior to repeat rather than the outcome you were pleased about.
Peer scripts describe a cost to your own work and ask; upward scripts stay narrow and arrive with a fix attached.
Cut always, never, attitude, and people have been saying, since each one moves the conversation off the behavior.
Follow up a week later to acknowledge the change, which is what makes the next conversation possible.
Frequently Asked Questions
What is a good example of negative feedback?
One that names a time, a behavior, an effect, and a request. The client summary was due Thursday and it landed Monday afternoon, I found out when the client emailed me, and going forward I need a message the moment a date is at risk. Compare that with you missed the deadline again. The first can be checked and acted on. The second can only be absorbed.
How do you give constructive criticism without demotivating someone?
Describe one situation rather than a pattern you have never mentioned, say what it cost in concrete terms, and finish with a step small enough to take this week. Criticism demotivates when it reads as a judgment about who somebody is instead of what happened. Skip the praise wrapper as well, since most people learn to hear opening praise as a warning.
What are examples of positive feedback for employees?
You froze the scope in week three and held it when three people asked for one more feature, and that is why the date held. Or, support tickets are down about a third since you rewrote the setup guide. The test is whether the person could repeat the specific action from your sentence alone. If not, it is praise rather than reinforcement.
How do you give feedback to a coworker who does not report to you?
Describe the cost to your own work and ask instead of instructing. A colleague has no authority to require a change, so the line has to earn it: I need most of a day with the specs and they arrive Thursday afternoon, so if Wednesday is possible I finish inside hours. Keep it private, and only involve a manager if a direct conversation has failed several times.
Should negative feedback ever be given in writing?
Have the conversation first, then write down what you agreed. A cold written message strips out tone and removes the chance to hear the other side, and it usually reads as a formal step even when you did not intend one. A short factual follow up note after the conversation is different, and it is worth doing whenever the change matters.
What words should you avoid when giving feedback?
Always, never, attitude, energy, and people have been saying. The first two invite a counterexample that derails the conversation. Attitude and energy are interpretations rather than observations, so there is nothing to confirm or change. Unattributed complaints leave the person defending themselves against an audience they cannot see. Softeners such as a bit signal that the issue is optional.
How do you give feedback to your own manager?
Keep it to one issue, tie it to work you are accountable for, and bring a remedy. The reporting spec has changed three times in five weeks and I have rebuilt it each time, so a frozen week before I start building would help. That version raises the cost, offers a fix, and gives the manager a way to agree without conceding anything about their judgment.
How many of these scripts should a manager memorize?
None. Keep the shape rather than the wording, since the shape can be assembled live and a memorized line sounds rehearsed. Scripts are most useful as a way to draft the opening two sentences before a conversation you know is coming, so you do not start with an accusation. After a dozen real conversations the structure becomes automatic.
