Military feedback is one of the clearest systems going. It is immediate, specific and plainly
spoken, it comes from someone responsible for your development, and it is documented on a known
schedule against a published standard. You always know where you stand, and that certainty is
genuinely valuable.
Civilian feedback works on a different model. It arrives from every direction — your manager, your
peers, the people who report to you, sometimes a colleague in another department. It tends to be
delivered gently, often some time after the event. The standard is frequently unwritten and varies
by team.
And here is the piece that matters most: in most civilian workplaces, feedback is something you
go and collect rather than something delivered to you on a cycle. People are reluctant to offer
criticism unasked, so the person who asks well hears things that everyone else has to wait a year
for.
That makes this one of the highest-return skills in your first two years. The people who actively
gather feedback improve visibly faster than the people who wait for it, and managers notice. Give
this page a careful read — it pays for itself quickly.
Every direction, including upward and peer-to-peer
Timing
Immediate, on the spot
Often delayed to a scheduled review
Directness
Very high
Hedged, softened, sometimes coded
Documentation
Formal and frequent
Annual or semi-annual, sometimes sparse
Who initiates
Your superior
Increasingly, you
Emotional framing
Minimal
Substantial — people worry about how it lands
Unsolicited criticism
Normal
Often considered rude between peers
The practical consequence is worth planning around. Without asking, you can work for a year before
anyone mentions something small and fixable about how you operate — and by then it may have shaped
a review or a promotion decision.
The whole problem dissolves the moment you start asking. A single good question every few weeks
keeps you current on how your work is landing, and gives you the chance to adjust while the
adjustment is still easy.
Receiving feedback well is a skill, and it is often hardest for the people who are best at their
jobs — which describes most people reading this.
There is a good reason for that. When you have spent years operating at a high standard and being
right most of the time, your mind reaches for the context that explains the situation. That
instinct serves you well in an operational setting, where correcting a misunderstanding quickly
matters.
In a feedback conversation, the more useful move is to collect the information first and evaluate
it afterwards. The pattern below makes that easy, and it takes about three conversations to become
natural.
Listen all the way to the end. Do not begin formulating the response. Most people delivering
feedback are nervous and will trail off if interrupted — and the most important part is usually
last.
Say thank you, and mean it. Someone just took a social risk on your behalf. Whatever else
happens, that deserves acknowledgment.
Ask for a specific example. Not defensively — genuinely. “Can you give me an example of when
that happened? I want to make sure I’m picturing the same thing you are.” Vague feedback you
cannot act on is worse than none.
Ask what it looked like from their side. “What was the impact?” This is the question that
turns criticism into something usable.
Hold your context for later, even when it is good. You will often have a perfectly sound
explanation, and there will be a moment for it. Offering it immediately tends to read as
pushing back, which quietly teaches the other person that feedback to you is expensive — and
they stop bringing it. Gather now, respond in a day or two.
Take 24 hours before deciding what you think. Your first reaction is almost never your best
judgment about whether the feedback is right.
Come back. “I’ve been thinking about what you said. Here’s what I’m going to do differently.”
This is rare and it lands enormously well.
Very few people ask for feedback deliberately, which is exactly why doing it well sets you apart.
The key is the shape of the question. “How am I doing?” is genuinely hard to answer — it is broad,
it puts the other person on the spot, and the kind response is to say something encouraging. You
will get “great, keep it up” almost every time, and they are not being evasive; you have asked a
question with no easy handle.
Narrow questions give people something to hold on to, and they will answer them honestly.
Ask narrow questions instead:
“What’s one thing I could do differently that would make the biggest difference?”
“If you were going to give me one piece of critical feedback, what would it be?”
“What do you think I’m underestimating about this role?”
“Where do you think I’m spending time that isn’t paying off?”
“How did that presentation land? Specifically the middle section — I wasn’t sure about it.”
“What would someone need to see from me to be confident I’m ready for the next level?”
Then let the silence sit. People need a few seconds to decide whether you want the real answer
or the polite one, and the pause is them choosing. Wait it out. If you fill the gap with “…but
obviously it’s going fine,” you have answered for them and the moment is gone.
Ask at the right moment. Right after a project ends, right after a presentation, right after a
difficult meeting. Specific and recent beats general and abstract every time.
Ask people who are not your manager. Peers see things your manager does not. So do the people
who report to you, if any. So does the person from another team who has to work with you.
In the military, correcting a peer is ordinary and expected — everyone is responsible for the
standard, and letting something slide is the unusual choice.
Civilian workplaces place more weight on the delivery, because colleagues have no shared standard
to point to and no formal responsibility for each other’s development. Peer feedback still happens
constantly among people who trust each other, and it is genuinely valued. It simply needs a little
more setup, and the setup takes about four seconds.
“Can I give you some feedback on the client call?”
That one short question does a surprising amount of work. It lets them choose the moment, it signals
that nothing is being sprung on them, and it turns the exchange into something they opted into. Ask
it and almost everyone says yes.
The most widely used structure, and it works because it is factual rather than characterological.
Situation — when and where, specifically.
Behavior — what you observed, described neutrally, without motive.
Impact — what happened as a result.
“In the design review this morning [situation], you cut across Maya twice while she was
explaining the constraint [behavior]. She stopped contributing after that, and I think we lost
something we needed [impact].”
Compare that with “you were rude to Maya.” The first describes something both of you watched
happen, so there is nothing to dispute and plenty to discuss. The second is a conclusion about the
kind of person they are, which invites them to defend their character instead of considering their
behaviour.
Staying on the observable facts keeps the conversation useful — and it is close to how a good
after-action review works, which you already know how to run.
Praise publicly, and give corrections privately. Almost without exception, and people remember
both.
Stay on behaviour. “You interrupted three times in that meeting” gives someone something to
work with. “You’re dismissive” asks them to accept a description of their character.
Weight it heavily toward the positive, and make the positive specific. “That was great” feels
good for a second and teaches nothing. “The way you reframed the problem at the start gave everyone
a way into it” tells them precisely what worked, which means they can do it again on purpose.
Specific praise is one of the most useful things you can hand a colleague, and it costs you
nothing.
Your manager gets far less feedback than you do, from almost nobody, and most of them genuinely
want it. Offered well, upward feedback is one of the fastest ways to become someone a manager
trusts.
Ask permission, and lower the stakes:
“Would it be useful if I told you how that landed with the team?”
Be specific and non-personal:
“When the reorg was announced in the all-hands without a heads-up, a few people on the team spent
the next week assuming the worst. If something like that comes up again, even a one-line warning
beforehand would help a lot.”
Bring a suggestion alongside the observation. “Here’s what I noticed, and here’s what would
help” is easy to act on and lands as partnership rather than complaint.
Pick your moments. Early on you have a limited budget for this, so spend it on the things that
genuinely affect the work rather than on preferences. As your credibility grows, so does the
latitude.
Where a manager turns out to be less open to this, that is useful information about your situation.
Note it, adjust how you operate, and factor it into your longer-term plans.
The formal version. Usually annual or twice a year, and usually more consequential than it appears,
because it feeds into pay and promotion decisions made in a room you are not in.
How it actually works at most companies:
You write a self-assessment.
Your manager writes an assessment, often gathering peer input.
Managers meet to calibrate — comparing people across teams, sometimes against a distribution.
Ratings drive raises, bonuses, and promotion decisions.
You get the conversation, after all of the above has already happened.
The single most useful habit is a running log of your accomplishments, started on day one.
One line a week, with a number attached wherever you have one. It takes two minutes every Friday.
Twelve months later you walk into your review with a documented year while most people are working
from memory, and the conversation goes very differently. See
making your work visible for a template.
Before the review: ask your manager what would constitute a strong year, months ahead of time,
not the week before. Then work on that.
In the review: if a rating surprises you, put your energy into the forward-looking questions.
Ask what specifically would have moved it, and ask for the written criteria for the next level.
By the time you are in the room the rating has usually been through calibration and is settled, so
the productive conversation is about the next cycle. Asking “what would a strong year look like from
here?” turns a disappointing hour into a clear plan, and managers respond well to it.
After: ask for the two or three things to focus on, in writing, and check in on them quarterly.
In the military, meeting the standard is the baseline expectation and does not call for comment;
recognition is reserved for performance above it, and that restraint makes it mean something when
it comes.
Civilian workplaces run on more frequent, more explicit acknowledgment, and in that setting its
absence tends to get read as dissatisfaction rather than as normal.
This runs in both directions, and both are worth knowing. Your team will need more recognition than
your instincts suggest — plan on saying something specific and appreciative most weeks. And your own
manager may be offering you far less than your work has earned, which usually reflects their habits
rather than their assessment of you.
When you give it, make it specific. “Good job” evaporates. “The way you handled that client when
they moved the deadline saved us a week” is something a person remembers for a year, and it tells
them exactly what to do again.
I received feedback at work and I want to process it properly rather than reacting to it.
WHAT THEY SAID: [AS CLOSE TO WORD FOR WORD AS YOU CAN REMEMBER]
WHO SAID IT: [ROLE AND RELATIONSHIP TO YOU]
CONTEXT: [WHAT PROMPTED IT]
MY REACTION: [HOW YOU HONESTLY FELT — INCLUDING IF YOU THINK IT WAS UNFAIR]
Help me:
1. Separate what was actually said from what I heard
2. Identify what is likely true in it, even if the delivery or the framing was poor
3. Identify what is genuinely not true or not fair, if anything
4. Work out what they were most likely trying to tell me, if the feedback was indirect or hedged
5. Decide whether this is a military-to-civilian style issue, a real performance issue, or something
about them rather than me
6. Decide what specifically to change, if anything — concrete behaviour, not attitude
7. Draft what to say when I go back to them, which should be short
Be honest with me. If the feedback is fair and I am resisting it, say so plainly.
Run this 24 hours after the conversation, not immediately. Your first reaction is rarely your best judgment.
I want honest feedback at work and I keep getting reassurance instead. Help me ask better
questions.
MY ROLE: [TITLE AND WHAT YOU DO]
HOW LONG I HAVE BEEN HERE: [TIME]
WHO I WANT FEEDBACK FROM: [MANAGER / PEERS / DIRECT REPORTS / A SPECIFIC PERSON]
WHAT I SUSPECT I MIGHT BE GETTING WRONG: [YOUR OWN GUESS, OR "NO IDEA"]
WHAT I SPECIFICALLY WANT TO KNOW: [e.g. am I ready for promotion, how do I come across, is my work
at the right level]
Give me:
1. Six specific questions that are hard to answer with "you're doing great" — tailored to this
person and this relationship
2. How to open the conversation so they believe I actually want a real answer
3. What to do in the silence after I ask
4. How to respond so that they will be willing to do this again
5. Who else I should be asking, that I probably have not thought of
6. A cadence for this — how often, with whom, without it becoming exhausting for everyone
Also tell me: coming from a military background, what am I likely to do in this conversation that
shuts the other person down without my noticing?
I need to give a colleague feedback and I want to get the delivery right. In the military I
would have been considerably more direct, and I know that will not work here.
WHO: [THEIR ROLE AND RELATIONSHIP TO ME — peer, someone I depend on, someone on another team]
WHAT HAPPENED: [SPECIFIC SITUATION AND BEHAVIOUR]
THE IMPACT: [WHAT IT ACTUALLY AFFECTED]
HAS IT HAPPENED BEFORE: [YES, HOW OFTEN / FIRST TIME]
OUR RELATIONSHIP: [GOOD / NEUTRAL / STRAINED]
WHAT I WANT TO CHANGE: [SPECIFIC OUTCOME]
Give me:
1. Whether this is worth raising at all, and whether it is mine to raise
2. When and where to do it
3. A script using Situation, Behavior, Impact — written the way I would actually say it out loud
4. How to ask permission to give the feedback without it sounding formal or ominous
5. How to end so it is a conversation rather than a verdict
6. How to handle it if they get defensive, disagree, or turn it back on me
7. What I should NOT say — including anything that would sound normal in a military context and
land badly here
Keep the script short. Four or five sentences, not a briefing.
I need to give my manager feedback and I am not sure how it will be received.
THE ISSUE: [WHAT IS NOT WORKING — THEIR BEHAVIOUR, A DECISION, A PATTERN]
THE IMPACT: [ON ME, ON THE TEAM, ON THE WORK]
HOW LONG IT HAS BEEN GOING ON: [TIME]
MY MANAGER'S STYLE: [OPEN / DEFENSIVE / BUSY / INDIRECT / UNKNOWN]
MY STANDING: [NEW / ESTABLISHED / ON THIN ICE]
WHAT I WANT TO CHANGE: [SPECIFIC ASK]
Tell me:
1. Whether to raise this at all, and honestly whether I have enough credit to spend on it yet
2. How to ask permission before giving it
3. A script — specific, behavioural, not personal, and short
4. How to frame it around impact on the work rather than on my preferences
5. How to offer a fix rather than just a complaint
6. What to do if they get defensive
7. What it tells me about my situation if they are simply not receptive to any of this
If this is something I should let go, say so and tell me why.
I have a performance review coming up and this is my first one in a civilian job.
MY ROLE AND TIME IN IT: [DETAILS]
WHAT I HAVE ACCOMPLISHED: [LIST EVERYTHING — DIG THROUGH YOUR CALENDAR, EMAIL, AND NOTES]
WHAT I KNOW ABOUT HOW REVIEWS WORK HERE: [FORMAT, RATINGS, TIMING, OR "NOT SURE"]
FEEDBACK I HAVE RECEIVED DURING THE YEAR: [ANYTHING]
WHAT I WANT OUT OF THIS: [RAISE / PROMOTION / CLARITY / JUST TO DO WELL]
Help me:
1. Turn my accomplishments into a self-assessment — outcome-led, quantified where I gave you a
number, no invented figures
2. Identify which of them my manager may not know about, and how to surface them without it reading
as a complaint
3. Prepare for the weaknesses that are likely to come up, and an honest response to each
4. Draft questions to ask: about the rating, about the criteria for the next level, about what to
focus on next
5. Understand how calibration works and what it means for me
6. Know what to do if the rating is lower than I expected — including what not to argue about
7. Set up what I should do in the first month afterwards
Also give me a simple weekly accomplishment log template so I never walk into this unprepared
again.
If you have not been keeping a log, reconstruct one now from your calendar, sent mail, and project tools. It takes an hour and it changes the conversation.
