Unlock Your Charisma · Hard Conversations
Give Tough Feedback Fast
Behaviour not character, specific example, impact, next step, short close.
Tough feedback fails when it attacks character, stays vague, or cushions until the point vanishes. Six concepts give a fast frame for Indian workplaces: behaviour, one specific example, impact, next step, a short close, and private first.
- Unlock Your Charisma
- Medium level
- 6 concepts
1Target behaviour, not character
Character labels — 'you are careless', 'you are unprofessional', 'you never take ownership' — invite defence, because the person has to protect their identity before they can hear the ask. Behavioural lines name what happened in observable terms: a missed checklist item, a late send, a skipped handoff. Character labels invite defence; behaviours invite change.
In a Bengaluru product team, 'you are careless with releases' lands as an attack. 'The release checklist was not run before Tuesday's deploy, and the hotfix went out without the smoke tests' names the same problem without forcing the other person to defend who they are.
The swap is mechanical: if the sentence still works after you remove the person's character and leave only the action and the date, you are in behaviour territory. If it only works as a label of who they are, rewrite it before you speak.
No diagram — the test is a rewrite. Strike the person's character from the sentence and keep the action and the date: 'you are careless' fails the edit; 'the release checklist was not run before Tuesday's deploy' survives it. If the sentence only works as a label of who they are, rewrite before you speak.
| Character attack | Behaviour rewrite |
|---|---|
| You are careless | The release checklist was skipped before Tuesday's deploy |
| You are unprofessional | The client deck went out with last week's figures still in slide three |
| You never take ownership | The blocker was not flagged in standup for three days |
A teammate in Hyderabad shipped a client deck with outdated numbers. Which line targets behaviour, not character?
- You are so careless with client work.
- You never check anything before you send it.
- Slide three still had last week's figures when the deck went to the client yesterday.
- This is exactly why nobody trusts your work.
It names a dated, observable action. The other three label character or motive, which invites defence before any next step can land.
2One specific recent example beats a vague pattern
Vague pattern claims — 'you always do this', 'this keeps happening' — feel true to the speaker and unfair to the listener, because the listener cannot reply to a fog. One recent, dated example gives both people the same object to talk about.
Prefer the last concrete instance over a career-long summary. 'In Thursday's vendor call, the pricing sheet was shared after the client had already asked twice' is discussable. 'You always leave clients hanging' is a trial.
If you truly need the pattern, earn it after the example: name the instance first, then say 'and this is the third time this month' only if you can point to the other two. Starting with the pattern invites argument about whether the pattern exists.
No diagram — the rule is about evidence selection: one recent, dated instance both people can point to. 'In Thursday's vendor call, the pricing sheet was shared after the client asked twice' is discussable; 'you always leave clients hanging' is a trial. Earn the pattern only after the instance, and only if you can point to the others.
| Vague claim | Specific example |
|---|---|
| You always miss deadlines | The QA build was still pending at 6 pm on Friday when the release window closed |
| You never update the team | In yesterday's standup the blocker was not mentioned, and Priya only learned of it in Slack at 4 |
| This keeps happening with clients | On Tuesday the follow-up mail went out twelve hours after the client asked for confirmation |
You need to raise a recurring delay with a peer in a Pune delivery team. What should you lead with?
- You always miss handoffs — this is a pattern.
- In Friday's handoff the build notes were still empty when QA started at 10.
- Everyone has noticed this about you.
- I do not want to get into specifics; we both know the issue.
A dated instance gives both people the same object. Leading with 'always', crowd opinion, or refusing specifics turns the talk into a defence of identity.
3Name the impact on work or people
Behaviour without impact sounds like preference: 'I do not like how you wrote that mail.' Impact answers why the behaviour matters — a delayed client, a blocked teammate, a rework loop, a trust hit with a stakeholder.
Keep impact factual and local. 'Because the sheet was late, the client pushed the sign-off to next week and Ananya's sprint plan slipped' is usable. 'Because of you the whole company looks bad' is theatre and usually false.
In a Mumbai agency review, skipping impact is how feedback gets heard as nitpicking. Naming the client delay or the unpaid invoice connects the behaviour to a shared cost, which is what makes the next step feel fair rather than personal.
Figure. Impact is what makes feedback more than preference, and it is factual and local: the late sheet cost a client sign-off, which cost a teammate's sprint plan. That chain is checkable, which is what makes the next step feel fair rather than personal. 'Because of you the whole company looks bad' skips the chain for theatre — grand, unfalsifiable, and usually false.
| Behaviour alone | With impact named |
|---|---|
| The sheet was late | The sheet was late, so the client pushed sign-off and the sprint plan slipped |
| You skipped the handoff note | Without the handoff note, QA blocked for half a day waiting on expected cases |
| You disagreed in the client call | The open disagreement in the call left the client unsure which scope we had agreed |
A missed handoff note blocked QA for half a day. Which feedback line includes usable impact?
- I just do not like how you work.
- You are unreliable on handoffs.
- The handoff note was missing, so QA blocked for half a day waiting on expected cases.
- This is the kind of thing that ruins careers.
It ties a concrete behaviour to a concrete work cost. Preference, character labels, and career theatre do not give the other person a reason that belongs to the shared work.
4End with the next step you want
Feedback without a next step is a complaint. The next step is the change you are actually asking for — a checklist before send, a Slack update the same day, a dry-run with you before the client call.
Make the ask small enough to do this week. 'Be more careful' is not a next step. 'Run the three-item release checklist and paste the tick marks in the release thread before you deploy' is.
In a Chennai support pod, the useful close is often a joint next step: 'Can we agree that severity-1 tickets get a same-hour update in the channel?' That invites a yes, not a defence of the past.
Figure. Feedback without a next step is a complaint. 'Run the three-item release checklist and paste the tick marks in the release thread before you deploy' is a change this week. 'Be more careful' is a mood. The close can be a joint ask: severity-1 tickets get a same-hour channel update.
Four-part feedback frame
- BehaviourName the observable action without a character label.
- ExampleOne recent, dated instance both of you can point to.
- ImpactThe work or people cost that makes the behaviour matter.
- Next stepA specific change you want this week — not 'be better'.
You have named a missed checklist and a client delay. Which close is a real next step?
- Just be more careful next time.
- I hope this does not happen again.
- Before the next deploy, run the three-item checklist and paste the ticks in the release thread.
- You need to change your attitude around quality.
It asks for a concrete, doable action. Hopes, attitude talk, and 'be careful' leave no behaviour to agree on.
5Keep the close short — do not cushion until the point disappears
Indian workplaces often cushion hard news with praise sandwiches and long preambles. A little warmth helps; a fog of compliments before and after the point teaches the listener that the middle was optional.
A short close sounds like: state the four parts, ask if the next step is workable, stop. Do not add 'but overall you are amazing and maybe I am overthinking' — that line is how people leave unsure whether anything was asked.
Anger is a separate problem. If you cannot yet name the behaviour calmly, wait. A delayed clear message beats an immediate soft message that undoes itself in the last sentence.
Figure. In the fogged close the point is a sliver between cushions, and the final 'maybe I am overthinking' un-asks it entirely — the listener leaves unsure whether anything was requested. The short close spends the same time stating the four parts and checking the next step is workable, then stops. A little warmth helps; a fog teaches the listener the middle was optional.
| Move | Does | Avoid |
|---|---|---|
| Warm open (optional, one line) | Signals respect without hiding the point | A two-minute praise tour before any ask |
| Core feedback | Behaviour, example, impact, next step | Burying the ask between compliments |
| Close | Check the next step is workable, then stop | Undoing the ask with 'maybe it is fine actually' |
You have delivered clear feedback and a next step. What should you do next?
- Add three more compliments so they do not feel bad
- Ask whether the next step is workable this week, then stop
- Say you might have overreacted and they can ignore it
- Repeat the character concern one more time for emphasis
Confirming the next step and stopping keeps the ask intact. Extra cushioning, undoing, or returning to character fog the point you just made.
6Private first for developmental feedback
Developmental critique belongs in a private channel — a 1:1, a quiet huddle room, a direct message that asks for a call — because public critique adds shame and an audience, and audiences turn feedback into performance.
Public is for process facts and for praise: 'Reminder that releases need the checklist' can be a channel note; 'Sana's checklist catch saved yesterday's deploy' can be public. 'Sana, you skipped the checklist again' in the team channel is almost never the right room.
In a Delhi corporate team with seniors on the thread, private-first also protects the person's standing while still allowing escalation later with facts if the private ask fails. Start private; escalate documented — do not start documented in front of ten people.
Figure. Critique goes to a private channel first — a 1:1, a huddle room, a message asking for a call — because an audience turns feedback into performance and adds shame to the content. The team channel is for process facts and praise. Escalating later, documented, stays open if the private ask fails; starting documented in front of ten people does not.
| Content | Room | Why |
|---|---|---|
| Developmental critique of one person | Private 1:1 or huddle | Shame and audience block change |
| Process reminder with no single target | Team channel is fine | It is about the system, not a person |
| Specific praise for a catch or save | Public is useful | Praise scales; critique does not |
A junior in your Noida team skipped the release checklist. Where should the first developmental conversation happen?
- In the team Slack channel tagging them
- In the all-hands as a learning moment
- In a private 1:1 or huddle, with behaviour and next step
- In a group email to the whole delivery org
Developmental critique starts private so the person can hear the ask without performing for an audience. Public rooms are for process and praise, not first-line personal critique.
Notes
- Tough feedback stays useful when it targets behaviour, not character.
- One specific recent example beats a vague pattern claim.
- Name the impact on work or people, then the next step you want.
- Keep the close short — do not cushion until the point disappears.
- Private first for developmental feedback; public only for praise or process.
Formulas
- Behaviour + example + impact + next step
- Private for critique
- Short close
Exam traps & shortcuts
- Write the feedback in four bullets before you speak.
- If you feel anger, wait until you can name the behaviour calmly.
Reference tables
Each row is a load-bearing move, its job, and the failure mode it replaces.
| Move | Job | Replaces |
|---|---|---|
| Behaviour not character | Name the observable action | You are careless / unprofessional |
| One specific example | Give a dated instance | You always / this keeps happening |
| Impact | Link to work or people cost | I just do not like it |
| Next step | Ask for a doable change this week | Be more careful |
| Short close | Confirm the ask, then stop | Praise sandwich that undoes the point |
| Private first | Protect dignity while being clear | Public call-outs of one person |
Recap
Six lines that keep tough feedback usable.
- Behaviour, not character
- Swap 'you are careless' for the missed checklist on a dated day.
- One recent example
- Lead with a discussable instance; earn the pattern only after the example.
- Name the impact
- Tie the behaviour to a shared work or people cost, not to preference.
- Ask for a next step
- A concrete change this week — not 'be better' or 'be careful'.
- Short close
- Confirm the ask is workable, then stop; do not undo it with fog.
- Private first
- Developmental critique starts 1:1; public is for process and praise.
Practise Give Tough Feedback Fast
Reading is free and needs no account. Practice, mocks and progress live in the app.
- A 5-question practice set that ends the chapter
- 6 quick checks with worked explanations
- Timed mocks scored with the real marking scheme
- Readiness tracked per topic, kept on your device