Decision Making Examples: What Good Calls Look Like at Work

Most decision making examples at work are small and undramatic: choosing which of two urgent tasks to finish first, deciding whether a problem is yours to fix or your manager’s to hear about, flagging an error you found in a shared file, or backing a team plan you argued against. What turns any of them into a good example is the reasoning you can show behind it. If an interview has ever asked you to describe a decision you made and your mind went blank, that is usually because your decisions did not feel like decisions at the time. They were, and once you can see the few kinds they fall into, you will find more of them in your own week than you expect.

Five kinds of decision making examples at work

Workplace decisions look endlessly varied, but they sort into a small number of kinds. Noel Tichy and Warren Bennis, writing in Harvard Business Review, argue that the most important judgment calls fall into three domains: people, strategy, and crisis. They also argued that good judgment is not a single moment but a process, and that its first phase is preparation: framing what is actually being decided and bringing in the people who have a stake in it.

At the start of a career, the stakes are smaller, but the domains are the same. Add two kinds that shape almost every junior role, deciding whether a call is yours to make at all and deciding together with a team, and you have five.

People decisions

These are the calls about the people you work with: who to ask when you are stuck, how to respond when a teammate misses a handoff your own work depends on, whether to say something about a colleague’s behavior. The range runs from the everyday to the serious. In their book Judgment and Decision Making at Work, Scott Highhouse, Reeshad Dalal and Eduardo Salas list deciding whether to report a coworker for sexual harassment alongside choosing which job applicant to hire; both are workplace decisions, and neither is reserved for managers.

What sets people decisions apart is that the outcome rides on trust, so framing the issue and involving the right person matter more than gathering data. A good example: a colleague keeps being left off an email thread that affects her work. Instead of quietly forwarding everything yourself, or ignoring it, you mention it to the person who owns the list, which fixes the cause rather than the symptom.

Asking for help belongs here too. Andrew Likierman, also in Harvard Business Review, describes judgment as the ability to combine personal qualities with relevant knowledge and experience to form opinions and make decisions. Experience is one of the ingredients, and it is the one you have least of in a first job. Borrowing someone else’s, by asking a colleague who has faced the same call before, is part of deciding well, not a sign that you cannot decide.

Priority and direction decisions

These are calls about what gets done and how: which task to start first when two are labeled urgent, whether to try a new format for the weekly report, whether to keep going with an approach that is not producing results.

Their defining feature is that most of them can be undone. Every decision sits somewhere between reversible and irreversible, and the way to place it is to ask what it would cost to undo. Reversible decisions reward speed: make the call, watch what happens, adjust. Irreversible ones deserve slow, deliberate thought. For a new professional, most daily priority calls are cheap to reverse, so the more common mistake is overthinking them, spending an hour choosing between two tasks that would each take forty minutes.

The risk in this category is the sunk-cost trap: sticking with a direction because of the time already invested. A typical case is continuing to polish a presentation angle your manager has already questioned, because a week has gone into it. The week is spent whichever way you go; the only live question is which angle serves the presentation from here.

Decisions under pressure

These are calls made when something has gone wrong or time is short: you discover a mistake in figures that have already gone to a client, a deadline is about to slip, a system fails an hour before a handover. The decisions are what to do first, who to tell, and whether to fix it quietly or flag it.

Pressure and emotion both push toward rushing, so the discipline is to slow down just enough to see which options cannot be undone. Emailing the client a correction is hard to take back; telling your manager first is not. A strong example of a decision under pressure often looks like this: before replying to anyone outside the team, you tell your manager what happened, what you think caused it, and what you propose to do about it.

Authority and escalation decisions

Before any decision comes a quieter one: is this mine to make? Your role, your organization’s policies, and what your manager has delegated to you set the boundaries of your decision-making authority. Can you agree to a customer’s small request, or does it need approval? Can you change a shared template, or should you ask first?

Getting this wrong costs you in either direction. Deciding beyond your authority damages trust, and escalating everything signals that you cannot yet be trusted with judgment calls. For a newcomer, the hard part is that these boundaries are rarely written down.

I didn’t always know what was considered appropriate, and sometimes I was told that I wasn’t behaving in quite the way people expected.

It was often about very small things: when it was OK to approach a colleague with a question, when you should wait, how much you should interrupt, or when something was important enough to take to your manager.

I understood that there were unwritten rules about these things — don’t interrupt unnecessarily in meetings, don’t constantly pull your manager away from what they are doing, and be mindful of other people’s time.

The difficulty was that nobody had given me a handbook for any of it. I knew the informal rules existed, but I didn’t yet understand what they were, where the boundaries were, or the spirit behind them.

We heard that from one of the young people we interviewed about starting work, and it describes the escalation decision exactly: a string of small judgment calls about what deserves your manager’s time. The practical way through is to stop guessing call by call. Ask your manager once, directly, which kinds of decisions you can make yourself and which they want to hear about. That single conversation settles dozens of later decisions.

Group decisions

Many decisions are made with others: a team choosing between two approaches, a meeting agreeing on a deadline, a project group deciding what to cut. Group decisions have their own predictable failures. The first opinion voiced, or the most senior one, anchors everyone else, and the quieter people stay quiet.

The countermeasures are simple to use at any level. Gather everyone’s view independently before the discussion starts. Deliberately invite the person who sees it differently. Have someone argue the other side on purpose. Ask the quiet people directly. Call a short time-out when a discussion is going in circles. A good junior example: you write down your preferred option before the meeting, so the first confident voice does not quietly become your view too.

What happens after the decision counts as well. Once the group has decided, the professional norm is to commit to the outcome and carry it out properly, even if you argued against it.

What separates a good decision from a lucky one

It is tempting to judge a decision by how it turned out. That is a poor test. A well-reasoned call can go wrong for reasons nobody could have foreseen, and a careless one can work out by luck. Good decision-making is judged by the process: whether you knew it was your call, sought the right input, and weighed the options honestly. When a sound decision still turns out wrong, the result is information for the next one, not proof that you decided badly.

A few predictable traps distort that process, and they matter most when you do not yet have a track record to check your instincts against:

• Confirmation bias: looking only for information that supports what you already think.
• Overconfidence: trusting your first read more than the evidence justifies.
• Anchoring: giving too much weight to the first number or idea you hear.
• The sunk-cost trap: staying with a failing approach because of what you have already put in.

Two habits guard against most of them: slowing down when you feel rushed or emotional, and accepting a good-enough option instead of waiting for a perfect one that never arrives. Everyone leans toward some of these traps more than others, and knowing your own is most of the defense. If you are not sure which ones catch you, a free assessment can show you where your judgment slips, and each of these habits is one you can train.

How to turn your own decisions into interview examples

Interviewers ask for decision making examples in forms such as “Tell me about a time you had to make a difficult decision” or “Give an example of when you used good judgment.” What they are listening for is not the size of the decision but the reasoning you can make visible:

• the situation and what was at stake
• the information you gathered
• who you consulted, and why them
• the trade-off you weighed
• what you decided
• what happened, and what you learned

A small decision explained well shows the skill better than a big one described vaguely. Say two teammates in a group project want to rebuild the analysis two days before the deadline. You check what the rebuild would change, ask the course tutor whether the current method is acceptable, and propose keeping the existing version with a clear note on its limits. The team agrees, and the project goes in on time. That covers the full sequence, with the trade-off in plain view.

The five kinds above are a good way to search your own experience. An escalation decision makes an especially strong answer, because it shows judgment about your own authority, not just about the task in front of you. A decision that went wrong can work too, as long as you can say what you changed afterward.

What makes these calls easier to get right

Look back across the five kinds and the same few things kept deciding how well a call went: how carefully it was made, whether the right person was making it, and how well the people involved decided together.

Decision-Making is the core of it. The skill is less about clever frameworks than about habits you can apply to an ordinary Tuesday: knowing your authority before you act, getting a second opinion (including from someone likely to disagree), slowing down when you are rushed or upset, settling for good enough when perfect is not on offer, and catching confirmation bias and the sunk-cost trap before they steer you. Those same habits are what make an example worth telling in an interview.

Working with Your Manager answers the question that sits under so many early-career decisions: is this mine to decide? Agreeing on your decision-making authority up front, and bringing a proposed solution along with each problem you raise, turns escalation from nervous checking or risky solo action into a deliberate choice your manager learns to trust.

Teamwork covers the decisions you do not make alone. It means speaking up with a different view while the decision is still open, keeping disagreement about the issue rather than the person, and then committing to what the team decides, even when your option lost. That is often the difference between a group decision that holds and one that quietly unravels.

The Job Skills Test measures all three of these, along with nine other workplace skills that show up in almost any role, and gives you a score for each. If you would like to know which of your skills need work before your next interview or your next real call, it takes a few minutes, and anything it flags is something you can learn.

Where your own examples come from

You may recognize some of these calls from your own life already: deciding which assignment to hand in late when two were due the same day, telling a project partner their section needed rework, working out whether a question was worth a lecturer’s office hours. None of it felt like decision-making then, but it was, and the habits behind it can be built on deliberately rather than left to chance.

That matters more over time. The decisions you are trusted with tend to get bigger and harder to reverse as your responsibilities grow, so practicing the process now, while most of your calls are still cheap to undo, is the easiest way to be ready for them. If you have ever sat on a question for a day because you were not sure it was worth your manager’s time, you have already met the escalation decision, and you already have an example to work with.

See how your decision-making measures up

The only thing left is to find out where you stand. The Job Skills Test is a free self-assessment of your workplace skills: it scores you across twelve of them, decision-making, working with your manager and teamwork among them, and shows you which ones would make the biggest difference for you right now.

Get my skills profile

Free, takes 7 minutes, and your results appear instantly.