I want an honest read on how I probably come across at work, so I can adjust deliberately
rather than finding out in a review.
ABOUT ME:
- Military background: [BRANCH, YEARS, ROLE, RANK]
- Current role: [TITLE, ORGANIZATION TYPE AND SIZE]
- How long I have been there: [TIME]
- How I would describe my working style: [YOUR OWN VIEW]
- Feedback I have received, if any: [WHAT PEOPLE HAVE SAID]
- Things I have noticed: [e.g. meetings go quiet after I speak, people go to someone else with
questions, I get left off invitations]
Tell me:
1. How my communication style likely reads to civilian colleagues who do not know my background
2. The specific habits from military culture that are probably helping me here
3. The specific habits that are probably working against me, being blunt about it
4. Where I am likely being read as more forceful than I intend, and where I may be too deferential
5. Three concrete changes — actual behaviours and phrasings, not "be more approachable"
6. Three strengths I should lean into harder rather than suppress
7. What I should ask colleagues to confirm or correct this read
Do not flatter me. I would rather hear this now.Soft Skills That Carry You
These are the skills that decide whether your technical ability ever gets used.
Your expertise is what gets you hired. What happens afterwards — whether people bring you into the room where things are decided, whether your proposals go anywhere, whether you move past the level where doing excellent work on your own is enough — runs on communication, judgment about people, and the ability to work through others.
Service gave you a great deal of this already, more than most people credit themselves with. This page starts with what you are bringing, then covers the areas where a little deliberate practice pays off quickly in a civilian setting.
What you already have
Section titled “What you already have”Start here, because these are genuinely uncommon and easy to overlook. When everyone around you for a decade had the same qualities, they stop looking like qualities at all. In a civilian workplace they stand out immediately.
Composure under pressure. When something goes badly wrong on a Tuesday afternoon, most offices contain very few people who have been genuinely steady in a genuinely serious situation. You have, repeatedly. People notice it within about a month, and they start routing the hard problems to you — which is how careers accelerate.
Reliability. You arrive on time, prepared, and you do what you said you would do by the date you said you would do it. You will clear this bar without thinking about it, and it builds trust faster than almost anything else you can do in a first year.
Accountability. Owning a mistake without deflecting is uncommon and it builds trust faster than almost anything else.
Teaching and developing people. If you trained anyone, you have done the thing most first-time civilian managers are worst at.
Briefing and being briefed. You can present to a senior person without falling apart, and you can sit through someone else’s presentation and extract the relevant part.
Working with anyone. You did not choose your team. You learned to work effectively with people you would never have picked, from backgrounds unlike yours. Civilian workplaces talk a great deal about this and practise it less.
Mission orientation. You will instinctively look for the point of the work and connect your piece to it. That habit makes you better at prioritizing than most of your colleagues, and it makes you someone worth listening to when a project starts drifting.
Operating with incomplete information. You are comfortable making a call with seventy percent of the picture and adjusting as the rest arrives. A great many capable people find that genuinely difficult, and in a fast-moving organization your comfort with it is a considerable advantage.
Name these in interviews and reviews, with a specific story attached to each. With evidence behind them they stop being generalities about veterans and become facts about you.
What usually needs work
Section titled “What usually needs work”Each of these is an area where the military environment rewarded one approach and a civilian one rewards a slightly different approach. Small, mechanical adjustments, and each pays off quickly.
Adding warmth without losing substance. Military communication is compressed and unambiguous for excellent reasons — in an operational setting, a sentence that can be read two ways is a hazard, and brevity under pressure saves lives. It is superb writing for its purpose.
Civilian communication carries more social padding, which does a job too: it signals goodwill in settings where people have to choose to cooperate with you. The adjustment is to keep your clarity and add a few words of warmth around it. Read a little further down for the specifics — it amounts to about one extra line per message.
Making your work visible. The military documented your performance on a schedule, through people whose job included doing it. In a civilian role that record is yours to keep, and the colleagues who keep one are the ones with specifics at review time.
Treat it as reporting rather than self-promotion, because that is what it is. See making your work visible for a two-minute weekly habit that covers it.
Working toward an objective you help define. You are practised at acting on incomplete information in pursuit of a clear objective. Civilian work often inverts that: abundant information, and an objective that is still being negotiated.
The skill to build is asking the questions that sharpen the objective — what does success look like, who decides, what are we optimizing for — and then proceeding. People value whoever brings that clarity to a room.
Choosing where to spend your energy on process. Some things will move more slowly than you believe they should. A portion of that you can genuinely improve, and improving it is a great way to build a reputation early. The rest is the weather.
Learning to tell those two apart quickly keeps your energy pointed at the things that will actually move, which is most of what effectiveness looks like in a large organization.
Small talk. A genuine professional skill, entirely learnable, and covered further down this page with actual sentences you can use.
Communication
Section titled “Communication”The highest-leverage area, and the one where small changes have outsized effects.
Writing
Section titled “Writing”BLUF is a gift and you should keep it. Leading with the conclusion is better than most civilian business writing, and colleagues will be quietly grateful for emails they can read in fifteen seconds.
Three small additions make it land even better here.
Add one line of context before the ask. Military writing can assume a great deal of shared situational awareness, which is what lets it be so compressed. Civilian colleagues in other departments often lack that context, and a single sentence supplying it turns a message that reads as abrupt into one that reads as considerate.
Instead of: “Need the vendor numbers by Thursday.” Try: “We’re finalising the Q3 budget on Friday. Could you send the vendor numbers by Thursday?”
Give short replies a little more warmth in writing. “Ok.” and “Noted.” and “Fine.” carry your tone of voice when you say them out loud, and lose it entirely on a screen. Adding two words — “Thanks, got it” — costs nothing and reads completely differently.
This is the most common small thing that gets in the way of competent, friendly people in their first civilian year, and it is also the easiest to fix.
Match the channel. A one-line answer belongs in chat. A decision with tradeoffs belongs in a document. Anything sensitive or emotionally loaded belongs in a conversation — never in writing, and never in chat.
Speaking
Section titled “Speaking”Say “I” when you mean I. Then credit the team. Covered in a few places on this site because it makes a real difference to how your contribution is understood.
Leave space in conversation. When you are quick and certain, you will naturally fill the pauses — and some of those pauses were someone else gathering the nerve to speak. Counting to three before you respond costs you nothing and surfaces information you would otherwise never hear.
Frame your assessment as an assessment. “That won’t work” delivers a conclusion and closes the topic. “I think that runs into a problem with X” delivers the same judgment and invites the other person to engage with your reasoning. Identical content, and the second one keeps you in the conversation.
Adjust register for the audience. An engineer, an executive, and a client need genuinely different versions of the same update. Executives want the conclusion and the risk. Practitioners want the mechanism.
Pitch to the room you are in. When you are the expert, the skill is calibration: finding the version of the explanation that a smart person outside your field can follow and act on. Start with why it matters to them, then go as deep as they want to go.
Emotional intelligence
Section titled “Emotional intelligence”An unfortunate phrase for something concrete: noticing what is going on with people, including yourself, and adjusting.
Self-awareness. Knowing how you land, which is often a little different from how you intend to. The only reliable way to find out is to ask, which is why asking for feedback is worth building into your routine.
Self-regulation. Noticing your reaction before you act on it. Service teaches this thoroughly under physical pressure and genuine danger, and you already have it in abundance there.
Worth applying deliberately in the smaller moments too — being talked over in a meeting, or hearing a confident opinion from someone who has not done the work. Same muscle, different setting, and a two-second pause is usually all it takes.
Reading the room. Who has gone quiet. Who keeps returning to the same point because they do not feel heard. When a meeting has stopped being productive.
Empathy that is practical, not sentimental. Understanding what someone is optimizing for — their deadline, their boss, their risk — and building it into how you ask.
Collaboration
Section titled “Collaboration”Share ownership genuinely. When something is going badly, the instinct to step in and handle it is strong, and it comes from exactly the right place.
Resisting it usually produces the better outcome. Stepping in teaches a team that you will step in, and they gradually stop reaching for the problem themselves. Coaching from alongside builds people who can handle it next time without you — which is the same thing you were doing when you developed junior troops.
Let people do it differently. If the outcome is right and the method is not yours, that is fine. This is harder than it sounds when you know a better way.
Let people fail safely. Small, recoverable failures are how people build judgment. Holding back on the ones that will not cost much produces a team that can operate confidently when you are not in the room — which is the whole point of developing people, and something you have done before.
Assume good intent, verify in writing. People miss deadlines because they are overloaded, not because they are indifferent. Confirm commitments with a name and a date anyway.
Learn from people junior to you. In a civilian organization expertise accumulates through tenure at that company and through specialization rather than through level. The person four years in knows the systems, the history and the personalities, and will happily tell you if asked. Seeking that out is the same instinct that made you listen to the local expert on the ground.
Modern workplace tools and etiquette
Section titled “Modern workplace tools and etiquette”Every workplace has local conventions for these tools, they are rarely written down anywhere, and people notice when you get them right. Here is a ten-minute orientation so you can arrive already fluent.
Slack, Teams, and the like.
- Channels over DMs. Posting in a channel lets others learn from the answer and prevents you becoming a bottleneck. DM for sensitive or personal things.
- Threads. Reply in a thread to keep the main channel readable. Not using threads is a common new-person tell.
- Do not send “hi” and wait. Ask the question in the first message. “Hi” followed by a pause is a small act of hostage-taking.
- Emoji are professional now. A thumbs-up reaction to acknowledge a message is normal and useful — it closes the loop without adding noise.
- Response time. Chat generally implies same-day, not same-minute. Nobody expects you to be online constantly, and if your workplace does, that is worth knowing about it.
- Tone runs cold. Add a word. “Thanks — got it” instead of “Got it.”
- Status and hours. Set your status. If you work different hours, say so in your profile, and schedule messages rather than sending at 11pm — otherwise you set an expectation you did not mean to.
- Subject lines that say the thing. “Budget approval needed by Friday” beats “Quick question.”
- Lead with the ask. Then context. Then detail.
- One topic per email. Two asks in one email means one gets answered.
- Reply-all sparingly. Think about whether all fourteen people need this.
- CC is political. Adding someone’s manager to a thread is a signal, whether or not you meant it as one.
- Response expectation is usually 24 hours, not immediate.
- Never write anything you would not want forwarded. It will be.
- Read the agenda; if there is none, ask what the meeting is for. Politely, in advance.
- Speak in the first ten minutes. If you say nothing early, it becomes increasingly hard to enter, and people register you as absent.
- You may decline meetings. “I don’t think I’m needed for this — happy to read the notes. Let me know if you’d rather I attend.” This is normal and nobody will be offended.
- Video calls: camera on for small meetings, generally optional for large ones. Mute unless speaking. Unmuting to speak creates a natural half-second pause that quieter people use to enter — do not fill it.
- Written pre-reads. Some organizations circulate a document beforehand and expect it read. If so, read it. Arriving unprepared is highly visible.
- Send a follow-up with decisions and owners. Whoever writes the summary shapes what was decided. This is real influence, freely available, and almost nobody volunteers for it.
- Over-communicate. In an office, being visible is passive. Remotely you must actively signal progress or you appear to have vanished.
- Short written updates beat long status meetings. Weekly, to your manager, three bullets.
- Async by default. Write it down so people in other time zones can act without waiting.
- Protect informal contact. The hallway conversations that build relationships do not happen by themselves. Schedule occasional non-agenda calls with peers.
- Set an end to the day. Remote work has no natural stopping point. See Time, Energy, and Boundaries.
- Show up in person when it matters. If your organization is hybrid, the days you are in the office are worth more than the days you are not.
Small talk, and why it is real work
Section titled “Small talk, and why it is real work”Small talk does real work. It is how civilian colleagues build enough familiarity to trust each other with the substantive things, and it runs on a similar principle to the time you spent getting to know the people in your section before you needed to rely on them.
The practical payoff is direct: the colleague who knows about your weekend is the one who picks up when you call them on a Friday afternoon needing something urgently.
A few things that make it straightforward:
Three topics will carry you. Something you are working on outside the office, something you are watching or reading, something happening locally. Charm is optional; having something ready is what matters.
Ask, then follow up later. Remembering to say “how was the trip?” a week afterwards is worth more than any amount of wit, and it is the single easiest way to be someone people enjoy seeing.
Share as much or as little of your service as you like. “Mostly logistics — a lot of moving parts” is a complete and perfectly good answer. Keep a short version for when you would rather not get into it and a longer one for when you would, and use whichever suits the day.
Five minutes is plenty. A short, warm exchange does the whole job.
Professional presence
Section titled “Professional presence”In uniform, a great deal of presence is carried by the uniform itself — the rank, the standards, the bearing that comes with all of it. It is an efficient system and you have lived inside it for years.
In a civilian workplace you build presence from your own conduct, and it turns out to rest mostly on consistency. The four things below are what people are actually reading.
Do what you said, when you said you would. This is the foundation and everything else sits on top of it. You already operate this way, which puts you ahead before you have done anything deliberate.
Be consistent. People trust predictable. Being the same person in a good week and a bad one is itself a reputation.
Have a point of view and share it. Reliability earns respect; a well-reasoned opinion, offered regularly, is what gets you into the conversations where decisions are made. Both together are the combination that moves people forward.
Dress one notch above the room until you know the room. Then match it.
Be easy to work with. Which is a different thing from being agreeable. It means people can reach you, you follow through, your mood is your own to manage, and working with you is uncomplicated. People build their projects around colleagues like that.
Prompts
Section titled “Prompts”I wrote the message below and I want to check how it will actually land before I send it.
Coming from a military background, I know my directness sometimes reads as harsher than I mean.
MESSAGE: [PASTE THE EMAIL, CHAT MESSAGE, OR DOCUMENT]
WHO IT IS GOING TO: [THEIR ROLE AND RELATIONSHIP TO ME]
WHAT I WANT TO HAPPEN: [THE OUTCOME]
CHANNEL: [EMAIL / CHAT / DOCUMENT]
Tell me:
1. How this will read to the recipient, honestly — including any line that will land colder than I
intend
2. Where I have assumed context they do not have
3. Where brevity is working for me and where it is working against me
4. Whether this is the right channel for this message at all
Then rewrite it:
- Keeping every bit of substance and the same level of directness about the content
- Adding only what is needed for warmth and context
- Not padding it with corporate filler
Give me two versions: one for a colleague I know well, one for someone senior I do not know. Tell me
which parts changed and why.Run your first few important messages through this. The pattern becomes obvious after five or six and then you will not need it.
I am new to a civilian workplace and nobody explains the unwritten rules. Help me work out
the norms here.
WHERE I WORK: [ORGANIZATION TYPE AND SIZE — e.g. 300-person government contractor, federal agency,
startup]
SETUP: [IN OFFICE / HYBRID / FULLY REMOTE]
TOOLS THEY USE: [SLACK / TEAMS / EMAIL / OTHER]
MY ROLE: [TITLE]
WHAT I HAVE OBSERVED SO FAR: [ANYTHING — how people message, meeting culture, hours, dress, tone]
Explain the norms I should expect for:
1. Chat — channels versus DMs, threads, response times, tone, emoji, after-hours messages
2. Email — subject lines, reply-all, CC, response expectations
3. Meetings — whether I can decline, camera on or off, speaking up, pre-reads, follow-ups
4. Working hours — what is actually expected versus what is stated
5. Dress
6. Social norms — lunch, coffee, after-work events, and how much to participate
7. Asking for help versus working it out myself
For each, tell me what a new person most commonly gets wrong.
Then give me five things I should simply observe for two weeks before deciding, and three questions
I could ask a friendly colleague without seeming lost.I find small talk at work difficult and I know it matters for building the relationships
that make everything else easier.
ABOUT ME: [INTROVERTED / EXTROVERTED, AND HOW YOU ACTUALLY FEEL ABOUT THIS]
MY SETTING: [OFFICE / REMOTE / HYBRID]
MY INTERESTS OUTSIDE WORK: [ANYTHING — SPORTS, HOBBIES, FAMILY, PROJECTS]
WHAT I FIND HARD: [STARTING / CONTINUING / ENDING / FEELING FAKE]
Help me with:
1. Three or four genuine topics I can actually talk about, drawn from what I told you
2. Openers that are not "how was your weekend," including for video calls and chat
3. How to keep a conversation going with questions that are not interrogation
4. How to exit gracefully
5. How much to say about my military service, with a short warm answer for when I do not want to
get into it and a longer one for when I do
6. What to do when someone says something clueless or awkward about the military
7. How to do this remotely, where there are no hallways
Give me actual sentences I could say. And tell me honestly how much of this genuinely matters
versus how much is optional.I need to communicate the same information to different audiences and I know it should not
be the same message each time.
WHAT I NEED TO COMMUNICATE: [THE UPDATE, DECISION, PROBLEM, OR PROPOSAL]
THE DETAIL: [EVERYTHING YOU KNOW, INCLUDING THE TECHNICAL PART]
WHY IT MATTERS: [THE STAKES]
Write four versions:
1. **For an executive** — conclusion first, the risk, what you need from them. Under 100 words.
2. **For my manager** — status, what is on track, what is not, what I am doing about it, where I
need help.
3. **For peers or a technical team** — the mechanism and the detail, assuming they know the domain.
4. **For a client or someone outside the organization** — no internal jargon, no blame, clear on
impact and next steps.
For each, tell me:
- What that audience actually cares about
- What to cut entirely
- The one sentence that has to land
Then tell me what I would most likely get wrong in each, coming from a military briefing style.I want to work out which single soft skill is most limiting me right now, rather than
trying to improve everything at once.
MY SITUATION:
- Role and level: [DETAILS]
- How long in a civilian workplace: [TIME]
- What is going well: [BE SPECIFIC]
- What is frustrating me: [BE SPECIFIC]
- Feedback I have received: [ANYTHING, OR "NONE"]
- What I want next in my career: [GOAL]
- Where I feel out of my depth: [HONEST ANSWER]
Ask me up to six diagnostic questions, one at a time, before you answer.
Then give me:
1. The one skill that is most limiting me, and the evidence from what I told you
2. Why this one matters more than the others for where I want to go
3. Four specific practices to work on it — things I can do in an ordinary week, not a course
4. How I will know in six weeks whether it is working
5. Who I should ask to tell me whether I am improving
6. The skills I should deliberately NOT work on right now
Be specific to me. I do not want a generic list of professional development advice.Related
Section titled “Related”How Decisions Get MadeInfluence, disagreement, and the pre-meeting that is the real meeting.
Giving and Taking FeedbackHow to collect the information that tells you which of these skills to work on.
Time, Energy, and BoundariesManaging yourself once nobody is managing your day.
Your First 90 DaysApplying all of this in the first three months.