How Decisions Actually Get Made

Military decision-making is one of the most refined systems humanity has built for a specific, demanding problem: acting decisively, together, under time pressure and incomplete information, where hesitation carries real cost. Authority is positional and explicit. Dissent goes up the chain before the decision. Once it is made, everyone executes. That design has been tested about as thoroughly as any organizational system ever has, and it works.

Civilian organizations are solving a different problem. Their people can leave at any time for a competitor, expertise is scattered across levels rather than concentrated at the top, and the cost of a wrong turn is usually money and time rather than lives. So they optimize for retention, consensus and reversibility, and they have built a system around persuasion instead of direction.

Understanding why it is built that way is what makes it navigable. Your manager will rarely direct you to do something; they will explain what is needed and expect your judgment to fill in the rest. Your peers have no obligation to help you and will anyway, if you give them a reason. Even as a manager, your team stays because they want to.

The currency here is influence, and the good news is that influence is a set of learnable behaviours rather than a personality type. This page teaches them.

The one-sentence version

In the military, authority arrives with the position and respect is what you build on top of it. In a civilian workplace the sequence runs the other way: you build credibility, relationships and a track record first, and the authority follows from them.

Knowing that order in advance saves you a frustrating first few months. Spend your early weeks earning the credibility, and the influence arrives faster than you would expect.

What actually changes

	Military	Civilian workplace
Who decides	The person in charge	Often unclear, and frequently negotiated
How it is communicated	An order, clearly	A meeting, a document, a chat thread, sometimes nobody tells you
Dissent	Before the decision, through the chain	Any time, from anyone, including after
What makes people comply	Authority and consequence	Agreement, trust, and self-interest
Speed	Fast once decided	Slow to decide, fast to reverse
Finality	High	Low — decisions get revisited constantly
If you disagree afterwards	You execute anyway	You may be expected to keep arguing
Who can stop you	Your chain	Almost anyone with a stake

The last row is the one worth sitting with. A peer in another department, with no position over you at all, holds real practical influence over your work — through what they choose to prioritize, what concerns they raise, and how quickly they reply.

This is why bringing people along is the core skill here. The effort you put into understanding what someone else is trying to achieve, and connecting your request to it, is the thing that turns a stalled piece of work into a finished one. It is a skill you already have from working across units and services; it simply becomes the primary tool rather than a supporting one.

The decision-making patterns you will meet

Consensus. The group keeps talking until nobody objects. Slow, sometimes maddening, but durable — because everyone has bought in. Common in smaller organizations and among peers.

Consultative. One person decides, but only after genuinely gathering input. The most common healthy pattern. Your job is to make your input count before the decision, not after.

Disagree and commit. Explicitly say your objection, on the record, and then fully support the decision anyway. This is the closest thing to a military norm you will find, and it is a genuinely good practice. Learn the phrase; it is widely understood.

Decision by document. Whoever writes the proposal frames the decision. The person who drafts the one-pager has enormous influence over the outcome, regardless of title. This is a real lever available to you from day one.

Decision by committee. Real authority is diffused across a group. Usually slow. Find out who the one or two people who actually matter are.

Decision by inaction. Nobody decides, so the default wins. Extremely common and rarely acknowledged. If you need a decision, sometimes the most effective move is to state what you will do unless someone objects by a date.

RACI or DACI. A chart naming who is Responsible, Accountable, Consulted, and Informed (or Driver, Approver, Contributor, Informed). Organizations reach for these when accountability has become unclear. If one exists for your work, read it.

The pre-meeting is the meeting

If you take one thing away from this page, take this one.

In most civilian organizations, important decisions take shape before the meeting where they are announced. They form in one-on-one conversations, so that by the time everyone is in the room the outcome is broadly agreed and the meeting confirms it.

When you first notice this happening it can look political. It is better understood as considerate. Presenting someone with a fully formed proposal in front of eight colleagues asks them to react publicly, without preparation, which tends to produce defensiveness rather than thought. Giving them the same proposal privately, a day earlier, lets them consider it properly, raise their concern without an audience, and arrive at the meeting ready to support something they helped shape.

Think of it as the civilian equivalent of walking a plan around the staff before the brief. You have done this before — it just carries more of the weight here.

What this means for you:

1. Never bring a significant proposal to a group cold. You will get objections you could have resolved privately, and people will remember their objection more than your idea.

2. Socialize it first. Talk to the two or three people whose support matters, individually, before the meeting. “I’m thinking about proposing X — what am I missing?”

3. Let them shape it. Someone who improved your proposal will defend it in the room. This is the entire mechanism.

4. Handle the likely objector first. Find out what they need, and either address it or understand why you cannot.

5. In the meeting, let them speak. “Dana raised a good point about the timeline, which is why we’ve built in two extra weeks.” Now Dana is on your side publicly.

This one habit converts more frustration into results than anything else on this page. Build it early and a great deal of the friction people describe in their first civilian year simply does not happen to you.

Being assertive and accommodating at the same time

These sound like opposites and they are not, because they apply to different things: be assertive about your position, and accommodating about the outcome.

Say what you think clearly and back it with your reasoning. Then, once the group has decided, get fully behind the decision — including the one you argued against. Those two together describe someone people want in the room.

Most of us land a little to one side of that balance at first, and often on different sides depending on the day and the audience. Both tabs below are worth reading, because you will probably recognize yourself in each of them at some point.

Too assertive

How it shows up: Offering a conclusion where the room expected a view. Delivering an assessment with enough certainty that the conversation closes behind it. Reading continued discussion as indecision. Moving quickly because the answer looks obvious to you — and it often genuinely is.

Why it happens: These are the habits of someone trained to give clear, confident direction under time pressure, which is a valuable thing to be. In a setting where the discussion itself is how people arrive at commitment, that same confidence can end the conversation before others have contributed.

How it lands: Colleagues may describe you as very direct, or say that meetings go quiet after you speak. This often goes unsaid, and shows up instead as being included in fewer early conversations.

The adjustment is small. Keep the content and the confidence exactly as they are; change the framing. Offer your view as a view, say what would change your mind, and ask what you might be missing — genuinely, because sometimes you will be.

Instead of “That won’t work.” Try “I think that runs into a problem with X — but I might be missing context. What am I not seeing?”

Too accommodating

How it shows up: Going quiet once a senior person has spoken. Treating a manager’s passing suggestion as a directive. Holding back a real concern because the decision appeared to be made. Saying yes to every request. Deferring to the most senior person in the room rather than the person closest to the problem.

Why it happens: These are the instincts of someone who has learned to support a decision fully once it is made, which is a genuinely admirable discipline and part of why veterans are trusted at work.

How it lands: In a civilian setting, managers read continued input as engagement and judgment. Where they hear nothing, they tend to conclude you have no view — and they will stop asking.

The adjustment: Your manager hired you for your assessment. Give it to them, early and plainly, and then commit to whatever gets decided. That combination is exactly what they are hoping for.

Instead of silence. Try “Before we lock this in — I have a concern I’d rather raise now than in three weeks.”

The balance

Assertive about your position:

• Say what you actually think, clearly, the first time
• Own your expertise. You are in the room because you know something.
• Say no to work you genuinely cannot take, with a reason and an alternative
• Raise concerns early, when they are cheap

Accommodating about the outcome:

• Genuinely update when someone has better information
• Let other people own things and do them differently than you would
• Let the best idea win, wherever it came from
• Support the decision fully once it is made, even the one you argued against

The phrase that holds both together: “Here’s my view, here’s what would change it, and I’ll back whatever we decide.”

Disagreeing well

With your manager

Do it privately first. Be specific about the concern rather than the conclusion. Offer an alternative. Then let it go.

“Can I push back on the timeline? Based on what I saw on the last release, I think three weeks is optimistic and we’ll end up cutting testing. I’d rather ask for five now than explain a slip later. But you have context I don’t — if there’s a reason it has to be three, I’ll make it work.”

That is assertive, specific, offers a path, and closes with commitment. It is also entirely honest.

In a meeting

Disagree with the idea, never with the person, and do it in a way that keeps the conversation open.

“I see it differently — can I offer another read?” “I want to make sure we’ve stress-tested this. What happens if X?” “I’m not sure I agree, but I might be wrong. Help me understand the reasoning?”

When you have lost the argument

Say so plainly and move on. This is where military culture gives you an advantage — most civilians are bad at it.

“I still think the risk is higher than we’re pricing in, and I’ve said my piece. I’m on board — what do you need from me?”

That sentence builds more credibility than winning would have.

Spend escalation carefully

In the military, moving something up the chain is a normal and healthy mechanism — that is what the chain is for. In a civilian workplace it works differently. Because authority is diffuse and relationships carry the work, going above someone spends a large amount of goodwill in a single move, and people remember it for a long time.

So save it for the cases that warrant it: genuine risk, an ethical problem, or a true impasse after you have worked it directly and in good faith. For those, escalating is exactly right and people will respect it. For an ordinary disagreement where you were overruled, the better play is to say your piece, commit, and build the credibility that makes the next argument land.

Reading what people actually mean

Civilian workplace communication is more indirect than military communication, and a lot of veterans miss real signals because they are listening for a clear answer that never comes.

What they say	What it often means
“Let me think about that.”	Probably no, or not now.
“That’s an interesting idea.”	I am not convinced.
“Let’s take this offline.”	Stop discussing it here.
“We should circle back on that.”	I am parking it, possibly forever.
“I have some concerns.”	I have serious objections.
“Can you help me understand?”	I think you are wrong.
“This might be a dumb question, but…”	I have found a real problem.
“No worries if not!”	I would genuinely like you to do this.
“Per my last email…”	You did not read my last email.
“I’ll add it to the backlog.”	It will not happen.

Every one of these phrases is said in good faith. This is a culture that puts real value on letting people decline without embarrassment and disagree without confrontation, and the indirection is the mechanism for that.

Two things follow. First, you can keep speaking plainly — direct communication is genuinely valued and is often a relief to the people around you. Second, learning to hear the softer register is what keeps you from waiting three weeks on something that was quietly declined on Tuesday.

When you need a definite answer, ask for one warmly and directly: “I want to make sure I’m reading this right — is that a no, or a not yet?” Almost everyone will tell you straight when you make it easy for them.

Learning from people junior to you

In the military, rank and experience track each other closely — a senior NCO has, almost by definition, seen more than a junior one. It is a reliable signal and it lets you know whose judgment to weigh heavily in an unfamiliar situation.

Civilian organizations distribute expertise differently. It accumulates through tenure at that specific company, through specialization, and through whoever happened to build the system you now depend on. So the 26-year-old four years into the job may hold exactly the knowledge you need, and will usually wait to be asked.

Seeking that out is a strength, not a concession. You already know how to defer to the person who knows the ground — you did it with every local expert and attached specialist you ever worked with. The same instinct applies here.

A question that works well in the first month: “You’ve been here four years and I’ve been here four weeks. What should I know that nobody’s going to tell me?” People are almost always pleased to be asked, and the answer is usually worth more than a week of formal onboarding.

Six adjustments worth making early

Read silence as trust, and move. Your manager assumes that if you needed direction you would ask, so quiet usually means they are confident in you rather than testing you. Where something is genuinely unclear, ask plainly. Where it is merely ambiguous, choose the most sensible course and tell them what you have decided — that combination reads as exactly the judgment they hired.

Check whether a suggestion is a suggestion. When a senior person says “you might want to look at X,” they usually mean it as an idea worth considering rather than a tasking. A single clarifying question resolves it every time: “Is that a nice-to-have, or should I prioritize it above what I’m on now?”

Treat decisions as revisable when facts change. Many civilian decisions are working positions rather than final orders. Bringing new information back to the table is expected and welcomed — it reads as ownership, and the people who do it are the ones trusted with bigger calls.

Say “I” when you mean I, then credit the team. Crediting the unit is one of the better habits service gives you, and it is worth keeping. In an interview or a review, though, the person opposite is trying to establish what you contributed, and they can only work with what you tell them.

So lead with the first person — “I decided,” “I built,” “I led” — and then name the people who made it work. You get full credit for the judgment and full credit for the leadership, which is accurate on both counts.

Report progress more often than feels necessary. In the military, quiet frequently meant things were running properly and reporting was reserved for exceptions. Civilian managers read silence differently — with less visibility into your day, they tend to assume a project has stalled.

A three-line update once a week, even on a quiet week, keeps you visible and costs almost nothing. Most people send far less than that, so it also makes you noticeably easy to work with.

Confirm commitments in writing. People are warm and enthusiastic in meetings and then return to a workload that has other claims on it. Nothing dishonest is happening; the commitment simply never got anchored.

A short follow-up message listing what was agreed, who owns each piece and by when, turns good intentions into a plan. Volunteering to write that summary also quietly makes you the person who shapes what everyone remembers was decided.

Copy every prompt on this page

Prompts

Map the decision-making culture where you work

• Collaboration
• Start here

Copy

I am new to a civilian workplace after [YEARS] years in the military, and I am trying to
work out how decisions actually get made here so I can be effective rather than just busy.

What I have observed so far:
[DESCRIBE — who runs meetings, how things seem to get approved, whether people disagree openly,
how your manager operates, anything that has confused you]

My role: [TITLE AND WHAT YOU ARE RESPONSIBLE FOR]
Organization: [SIZE AND TYPE — e.g. 200-person contractor, 50,000-person agency, 40-person startup]

Help me understand:
1. Which decision-making patterns this sounds like — consensus, consultative, decision by document,
 committee, or decision by inaction
2. Who the real decision-makers probably are, versus who has the title
3. How I should be bringing ideas forward in a culture like this
4. What my manager most likely expects from me that they have not said out loud
5. What I am probably getting wrong right now without realizing it, coming from a military
 background
6. Five things I should observe over the next two weeks to confirm or correct this read

Ask me clarifying questions if what I have described is ambiguous.

Prepare to propose something

• Collaboration
• Influence

Copy

I want to propose something at work and I want to do it in a way that actually lands,
rather than getting picked apart in a meeting.

WHAT I WANT TO PROPOSE: [THE IDEA]
WHY IT MATTERS: [THE PROBLEM IT SOLVES]
WHO IS AFFECTED: [TEAMS, PEOPLE, WHOEVER HAS A STAKE]
WHO DECIDES: [IF YOU KNOW]
WHO IS LIKELY TO OBJECT, AND WHY: [YOUR BEST GUESS]
MY STANDING HERE: [NEW / ESTABLISHED / SENIOR / JUNIOR]

Give me:
1. Who I should talk to one-on-one before any group conversation, in what order, and what to ask
 each of them
2. A short script for those pre-conversations that invites them to improve the idea rather than
 approve it
3. The three strongest objections and how to address each honestly — including which ones I should
 simply concede
4. A one-page written version of the proposal: problem, options considered, recommendation, what I
 need
5. How to open the group conversation
6. How to handle it if it gets deferred rather than decided
7. What to do if the answer is no

Be realistic about my standing. If I am too new to propose this directly, tell me and give me the
version that works instead.

The pre-conversations are the whole game. A proposal that three people have already improved does not get ambushed.

Disagree with your manager

• Collaboration
• Difficult conversations

Copy

I disagree with a decision my manager has made and I need to raise it without damaging the
relationship or looking like I am refusing to follow direction.

THE DECISION: [WHAT THEY DECIDED]
WHY I DISAGREE: [YOUR REASONING AND ANY EVIDENCE]
WHAT I THINK SHOULD HAPPEN INSTEAD: [YOUR ALTERNATIVE]
THE STAKES: [WHAT HAPPENS IF I AM RIGHT AND NOTHING CHANGES]
MY RELATIONSHIP WITH THEM: [NEW / GOOD / STRAINED]
THEIR STYLE: [DIRECT / INDIRECT / DEFENSIVE / OPEN — IF YOU KNOW]

Give me:
1. Whether this is worth raising at all — be honest, some things are not
2. Where and when to raise it: privately, in writing, in a one-on-one, or in the next team meeting
3. A script, written the way I would actually say it out loud
4. How to lead with the concern rather than the conclusion
5. How to give them a way to change course without losing face
6. Exactly how to close it if they hold the line — the words for committing fully to a decision I
 argued against
7. What would make this serious enough to escalate, and why escalation costs more in a civilian
 workplace than in the military

Keep it short. I would rather say four sentences well than deliver a brief.

Get things done without authority

• Collaboration
• Influence

Copy

I need something from people who do not report to me and have no obligation to help me.
In the military I would have had a mechanism for this. I do not now.

WHAT I NEED: [THE SPECIFIC THING]
FROM WHOM: [WHO — ROLE AND TEAM]
WHY THEY MIGHT NOT PRIORITIZE IT: [THEIR COMPETING PRIORITIES, IF YOU KNOW]
MY DEADLINE AND WHY IT IS REAL: [DETAILS]
WHAT I CAN OFFER IN RETURN: [ANYTHING — TIME, CREDIT, RECIPROCITY, MAKING THEIR LIFE EASIER]

Give me:
1. How to frame the request so it connects to something they already care about
2. The actual message or conversation opener
3. How to make it as easy as possible for them to say yes
4. What to do when they say yes and then nothing happens — the follow-up that works without nagging
5. When and how to involve their manager, and why that should usually be a last resort
6. How to build the relationship now so the next request is easier

Also: tell me what I am likely doing that reads as demanding rather than asking, given a military
background.

Decode something confusing that happened

• Collaboration
• Reading the room

Copy

Something happened at work that I cannot read, and I do not want to respond wrongly.

WHAT HAPPENED: [WHO, WHAT WAS SAID OR DONE, THE CONTEXT, HOW IT ENDED]
HOW I INTERPRETED IT: [YOUR READ]
WHY I AM UNSURE: [WHAT IS CONFUSING]
RELEVANT BACKGROUND: [ANY HISTORY BETWEEN YOU AND THIS PERSON]

Tell me:
1. Three plausible readings of what actually happened, including ones I have not considered
2. Which is most likely in a civilian workplace, and what makes you say so
3. Whether this is a military-to-civilian translation issue or a genuine problem
4. If someone was communicating indirectly, what they were most likely actually saying
5. What to do next, in specific words
6. What NOT to do
7. Whether to address it, let it go, or wait and watch

Be practical. I am not looking for reassurance — I want to read this correctly.

Rehearse a difficult conversation

• Collaboration
• Practice

Copy

I need to have a difficult conversation at work and I want to practise it before I have it
for real.

THE SITUATION: [WHAT IS GOING ON]
WHO I AM TALKING TO: [THEIR ROLE AND RELATIONSHIP TO ME]
WHAT I NEED TO COME OUT OF IT: [YOUR GOAL]
WHAT I AM WORRIED ABOUT: [YOUR CONCERN — e.g. coming across as aggressive, being dismissed,
damaging the relationship]

Role-play it with me. You play the other person, realistically — including being defensive,
deflecting, or disagreeing if that is likely. Stay in character and respond to what I actually say.
Do not break role to coach me.

When I say "END", give me:
1. How that conversation would likely have gone in reality
2. Where my phrasing helped and where it escalated things
3. Anywhere I came across as more forceful or more passive than I intended
4. Specific replacement wording for the two or three moments that mattered most
5. How to open and how to close it

Start by having me open the conversation.

Do this out loud. The gap between what you can write and what comes out under pressure is the whole point of rehearsing.

Related

Giving and Taking FeedbackThe other half of collaboration — and the part with the steepest learning curve.

Soft Skills That Carry YouCommunication, presence, and the skills that determine whether your expertise gets used.

Your First 90 DaysThe tactical onboarding version: who to meet, what to change, what to leave alone.

Civilian Workplace GlossaryRACI, stakeholder, alignment, bandwidth — decoded.