Give feedback to your manager
Prepares feedback to a manager or senior colleague with what to say, framing around shared goals, when and where to raise it, and how to respond if they get defensive.
Feedback up the hierarchy is riskier than feedback down, because the other person controls your work, your reviews and sometimes your job. It goes best when it is framed around a goal the manager already cares about (the team hitting its deadline, a client relationship, their own reputation), is specific about one behaviour and its effect, comes with a suggestion rather than a complaint, is raised privately at a calm moment, and is offered as information rather than judgement ("Something that would help me do this better…"). Asking permission first ("Can I share an observation about the planning meetings?") gives the manager control and lowers defensiveness. Some issues are not feedback matters: harassment, discrimination, safety and ethics breaches belong with HR, a skip-level manager or a formal channel.
Help me give this feedback.
Only if [RELATIONSHIP] is given:
- Check whether this is a feedback conversation. If the issue involves harassment, discrimination, safety, retaliation or a legal or ethical breach, say that a formal channel (HR, a skip-level manager, an ethics line, a union) is the better route, explain why briefly, and give only what helps with that route. If the issue is too vague to name a behaviour, ask up to two questions and stop.
- Narrow it to one behaviour and its effect. If there are several issues, pick the one with the most impact and the best chance of change, and say why the others can wait.
- Find the shared goal: what the manager cares about that this behaviour is getting in the way of.
- Write the core message in situation, behaviour, impact form, plus a specific suggestion or request, under about 80 words, without judgements of character or assumed motives.
- Recommend when and where: private, not right after a tense moment, ideally in a regular one-to-one, or by asking for 15 minutes. Advise against raising it in writing first unless the relationship is mostly remote, and if so, give a short message asking to talk.
- Write the conversation: a permission-asking opener, the core message, an open question inviting their view, and a closing that agrees a next step.
- Prepare for defensiveness: the four most likely reactions for this relationship (justifying, minimising, counter-criticism, pulling rank, going quiet), with a calm reply to each that acknowledges, does not argue, and returns to the shared goal.
- Say how to follow up and how to recognise change when it happens.
- Account for the power difference honestly: name the realistic risks and how to reduce them, without catastrophising or telling me not to speak up.
- Use only facts from the issue; do not add examples. Mark where a concrete example would help as
[example: …]. - No flattery sandwiches, sarcasm, ultimatums or threats to go over their head.
- Keep every line short enough to say naturally in a meeting.
Is this the right move
One or two sentences: feedback conversation or formal channel, and why.
The message
Shared goal, then the SBI message and the request.
When and where
Timing, setting and medium.
What to say
Opener, core message, question, close, as lines I can say.
If they get defensive
Table: If they… | You can say…
After
Follow-up and how to notice change.
Risks
Realistic risks and how to reduce them.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Interpersonal communication
- level
- Beginner
- made for
- Anyone, personal use, Software engineer, Product manager, People manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install give-upward-feedback --target claude-codenpx skills add hermes-hq/hodios-dist --skill give-upward-feedback -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Interpersonal communicationGive feedback with SBI
Turns a reaction into specific, kind feedback using situation, behaviour and impact, adds a clear request and an invitation to respond, and strips out judgements and assumed motives.
give-feedback-sbiPrepare for a difficult conversation
Prepares a difficult conversation with realistic goals, an opening line, the other person's likely view, phrases to use and responses to pushback, and points to help instead when safety is at risk.
prepare-difficult-conversationWrite an escalation email
Writes an escalation to a manager, vendor or another team that states the issue, its impact, what was already tried and the specific decision or help needed by a date, without blame.
write-escalation-emailCommunication coach
Communication coach who helps people say hard things clearly and kindly, rehearses real conversations with them, and teaches listening as much as speaking, at work and at home.
communication-coachApologise effectively
Writes a sincere apology that names the specific impact, owns it without excuses or conditional wording, offers repair and says what will change, fitted to the relationship and channel.
apologize-effectivelyMediate a disagreement
Mediates a disagreement neutrally by restating each position fairly, finding the interests underneath, separating factual from value differences and proposing options both sides can accept.
mediate-disagreement