Practical guide
A feedback framework is easy to learn. The harder part is stating the change clearly enough that the other person knows what to do next.
Want to get better at something specific?
Try Cadence for a course built around your goal, with short lessons, practice, and saved progress. Start free on iPhone or request Android access.
There is a specific way feedback conversations fail, and it is not rudeness. It is that the person giving the feedback wraps the message in so much cushioning that the actual point never arrives. Both people leave feeling the conversation went well. Nothing changes. Three months later the same problem appears in a performance review, and now it is a surprise.
This guide is about the words: what to say, which openings can bury the point, and how to check whether the message was understood before you end the conversation.
The short answer
Feedback changes something when you decide beforehand what you want to be different, start from one specific moment rather than the pattern, say what it cost out loud, and then stop talking so the other person can respond. Agree on one change, not a plan, and check in earlier than feels necessary.
The method
The order matters. Step three explains why the change matters instead of leaving the feedback as a personal preference.
Before you open your mouth, finish this sentence: after this conversation, I want them to start or stop doing X. If you cannot finish it, what you have is a complaint. Vague dissatisfaction delivered kindly is still vague dissatisfaction.
Say what you saw, once, with a time attached. In Tuesday's client call you answered the pricing question before Priya finished asking it. A person can argue with "you are dismissive in meetings" forever. A specific moment is harder to wave away, though expect them to explain it, which is fine and often useful. The pattern conversation comes later, once the specific one is accepted.
This is the step people skip, and skipping it is why nothing changes. Name what the behaviour actually cost, and pick a cost that genuinely stings: the client asked us to re-present the following week, so two people lost a day rebuilding a deck we had already delivered. Without a cost, feedback sounds like a preference, and people are entitled to ignore your preferences.
Ask what their read on it is, then leave enough silence for an answer. Filling that space with more explanation can soften or confuse a point you already made clearly.
End with one concrete different behaviour, and say it back to each other so you both heard the same thing. Not "I will work on my communication", but "in client calls I will let them finish the question before I answer". One change that happens beats five that were agreed to.
Come back within two weeks, and lead with the thing that improved if it improved. Feedback with no follow-up teaches people that your feedback does not matter, because the only evidence they get is silence either way.
What it sounds like
The steps above cover the opening. This is the part people actually dread: what you say once the other person answers back. Priya has shipped work that technically met the ticket but missed what the customer asked for.
I want to talk about the export feature. When it shipped on Thursday it did what the ticket said, but it was not what the customer asked for on the call, so we rebuilt it over the weekend and the launch slipped a week.
The ticket was ambiguous though. I asked in the channel and nobody came back to me.
That is fair, and I should have answered that message. So the ticket was unclear and your question went nowhere. What would have helped you get an answer before you started building?
Honestly I would have built it anyway. I did not want to be blocked for two days waiting.
That is the bit I want to change. Being blocked for two days costs us less than rebuilding for a week. If a ticket is unclear and nobody replies within a day, I would rather you came straight to me, even if it feels like escalating.
Alright. That is easier for me anyway.
Good. So from now on, an unanswered question after a day and you come to me directly. Can you say that back so I know we mean the same thing?
If I ask something and nobody answers by the next day, I come to you instead of guessing.
That is it. I will fix my end too, which is answering the channel.
Three things are doing the work there. The cost is concrete, a week and a weekend, so it is not a vague complaint about quality. The pushback is accepted where it is true, which helps keep the conversation specific, and the manager takes their own share of the blame. The change is then said back in the other person's words, reducing the chance that they leave with different versions of the agreement.
The openings
Some standard openers can make the action harder to identify, even when they feel kind to the person saying them.
The hardest version
A first-time manager may now supervise someone who was previously a peer or friend. The difficulty is not only finding the words. It is naming a new power relationship without turning every conversation into an apology for it.
Name the changed relationship once at the start: this is the part of the job I find strange, because a month ago we would have had this over lunch. Then move to the current issue. Repeating the apology in every feedback conversation can make the working relationship harder to define.
Do not soften the content until the requested change disappears. If a former peer first learns about the concern in a formal review, the delay adds a separate trust problem to the original feedback.
Worth saying explicitly, because people assume the opposite: becoming their manager does not end the friendship. It makes you the person who tells them the truth first, before anyone else does.
If you already left it
Raising things within days is the right rule and it is useless if you have already spent a month saying nothing. Plenty of people reading this are in the second situation, where their own silence now reads as approval.
Do not pretend to have just noticed. Open by owning the delay, because it costs you nothing and removes the unfairness: I should have said this weeks ago and I did not, which is on me. That one sentence stops the whole conversation being about why you waited.
Then pick the most recent instance and leave the rest. One example from last week can be discussed. Four examples going back to March feels like a case being built, and they will defend the list instead of hearing the point.
Expect them to say they wish they had known earlier. They are right. Agree, skip the defensiveness, and move to what changes now.
The other direction
Everything above assumes you have some authority. Giving feedback to your own manager does not work the same way, because the cost of getting it wrong is not symmetrical.
Two things change. First, ask permission, because it gives them a moment to switch from output mode to listening mode: can I give you a reaction to something from the planning meeting? Second, frame it around your own ability to do your job, because that is a request they can act on without hearing a judgement. When priorities changed on Thursday I had already built the deck, so I lost a day. Could we lock scope before I start building?
There is nothing political about that. Their behaviour genuinely did affect your work, and that is the part you can speak to with authority.
Where we fit
Cadence is our app, so weigh this accordingly.
Cadence has a reviewed course on giving feedback, built as short daily lessons you can use between real conversations. The daily shape matters for this particular skill, because feedback is learned between the lessons and not during them. You get one idea, you use it in a real conversation that week, and the next lesson lands on someone who has actually tried something.
You can also describe your own situation and get a course built around it, which is worth doing when the general version does not fit. Feedback to a peer with no authority, feedback to someone more senior than you, and feedback to someone who cries are three genuinely different problems.
Put it into practice
If you want to keep going, Cadence turns what brought you here into a course of short daily lessons with practice and saved progress. Cadence is our app.
Questions
Name one specific moment with a time attached, state what it cost, then stop talking and let them respond. The specificity is what makes it hard to dismiss, and the cost is what makes it worth acting on. Frameworks matter far less than resisting the urge to soften the point until it disappears.
Usually not. Putting criticism between two compliments can make the requested change harder to identify. State the feedback and action plainly. Give genuine praise separately when it deserves its own attention.
Ask permission first, then frame it around your own work. Saying that a late change cost you a day of rebuilt work is a fact about your job that they can act on. Telling them they are disorganised is a judgement, and it will be received as one.
Within days, while both of you remember the specifics. Feedback saved for a performance review is not feedback, because the person had no chance to change anything, and being told about a six-month-old problem for the first time in a formal review feels like an ambush.
Stop advancing and start listening. If they hear a judgement about their character, return to the specific moment, the specific cost, and the change you need. You can acknowledge the reaction without withdrawing a message that still needs to be addressed.
See it in concrete terms
These Cadence courses cover the same ground in daily lessons, with the syllabus visible before you start.
Make feedback specific, useful, and easier for a teammate to act on without burying the point.
Name the real issue, lower the drama, and leave the conversation with an owner, decision, or next step.
Shift from doing the work yourself to setting context, inspecting quality, and helping other people succeed.
Continue in Cadence
Use the article now. If you want to go further, Cadence can turn the problem or curiosity behind it into a structured course. Cadence is our app.