Critical Thinking in the Workplace: How It Differs Between Team Members and Managers

Critical thinking in the workplace has the same basic goal at every level: make a sound judgment. What changes is the information, pressure, and responsibility behind it.

A team member spots a problem with a process and thinks, We could fix this easily. Their manager looks at the same problem and sees budget limits, another team’s workload, a client commitment, and three other priorities competing for attention.

Neither person is necessarily missing something. Each is working with a different mix of information, experience, priorities, and responsibility. What gets noticed, what gets questioned, and what feels urgent can differ greatly, depending on the role.

Team members are often closest to the work, so they may spot issues long before anyone else does. Managers have a wider view, and are responsible for deciding which issues need action, what trade-offs are acceptable, and what happens next.

There’s also something useful in understanding how the other role thinks. It can help you anticipate what information they’ll need, what concerns they may raise, and what pressures are likely influencing the decision. Over time, that kind of perspective-taking can make the whole team better at solving problems, making decisions, and working through competing priorities.

And, ironically, becoming a better critical thinker requires being willing to think critically about how you think in the first place.

Does critical thinking change when you become a manager?

The fundamentals don’t change, but the job you’re asking your critical thinking to do often does.

A team member is frustrated that a weekly reporting process takes three hours because data has to be copied manually between systems. From where they sit, the answer seems obvious: automate it.

They may be right.

The manager, however, may also know that IT has frozen all system changes for the quarter, another department relies on the current format, and there’s no budget for automation until the next planning cycle.

The team member’s job is to notice the inefficiency, question whether the process still makes sense, and bring forward a useful recommendation. The manager’s job is to consider that recommendation alongside the constraints, risks, and competing priorities that come with it.

Neither side has the full picture on its own.

Some of the best examples of critical thinking in the workplace start with people asking a few more questions before settling on an answer. What information am I missing? Who else is affected? What would have to be true for this idea to work?

Sometimes the best recommendation will still be the obvious one. Other times, those extra questions reveal why a simple fix isn’t quite so simple.

The shared goal: challenge assumptions without creating unnecessary friction

Sometimes the manager is the one asking, “Why are we still doing it this way?”

They may be looking across the team and seeing duplicated effort, unnecessary approvals, or a process that made sense two years ago but no longer does. From that vantage point, changing the process can look like an obvious opportunity to save time or reduce friction.

The team member may see something the manager doesn’t. That extra approval might catch a recurring error before it reaches a client. The awkward form may trigger an automation that sends information to another department. A step that looks inefficient from a distance may be solving a very real problem close to the work.

Of course, it can work the other way around too. Team members are often the first to notice when a process has become clunky, repetitive, or disconnected from how the work is actually getting done.

Both roles need to be willing to question assumptions. They also need to be willing to hear why an idea that seems obvious from one position may look very different from the other.

When that exchange works well, people can challenge how things are done without turning every suggestion into a tug-of-war.

Neither interpretation has to be completely right. The value is in stopping long enough to question your first assumption about why the other person is thinking that way.

The shared goal: move from problem to decision

A team member notices a project is slipping and brings forward three options: extend the timeline, reduce the scope, or add temporary support.

That’s strong critical thinking. They’ve moved past “we have a problem” and started weighing possible responses.

The manager’s job is different. They may know the client has already rejected a timeline change, the budget has no wiggle room to hire extra help, and cutting scope could affect another commitment. They still need to make a decision, but they’re doing it with a different set of constraints.

This is where good recommendations help. Team members don’t need to solve everything before raising an issue, but they should think through what they know, what they don’t know, and what options seem realistic.

Managers, meanwhile, have to decide when they’ve heard enough to act, and when a situation calls for coaching, feedback, or more direct action.

Waiting for perfect information can create just as many problems as deciding too quickly. Sometimes every available option carries a downside. Critical thinking then becomes a matter of comparing risks, weighing consequences, and deciding which option carries the least damaging trade-off.

The strongest decisions often come from both sides doing their part: one side bringing thoughtful options forward, and the other weighing those options against the broader picture.

The shared goal: think clearly when personal pressure is involved

Critical thinking gets harder when the outcome feels personal.

A team member may be thinking:

• Will I be blamed if this goes wrong?
• Will this affect my performance review?
• Can I realistically meet this deadline?
• If I challenge this decision, will I look difficult?

A manager has pressures of their own:

• Will the team hit the target?
• What happens if several people miss their deadlines?
• How will this affect the department’s results?
• What am I accountable for if this goes wrong?
• What are the consequences if we can’t get it done?

The pressure is different, and it can shape how people assess risk, how quickly they speak up, and which options feel acceptable.

A team member who’s worried about being blamed may stay quiet about a concern. A manager who’s under pressure to deliver may dismiss a warning too quickly because slowing down feels risky in its own way. Managing well under pressure means noticing that reaction before it starts driving the decision.

Good critical thinking asks us to notice those pressures rather than pretend they aren’t there. That doesn’t mean removing emotion from the decision. It means recognizing when fear, urgency, or self-protection may be narrowing the way we’re looking at the problem.

What happens when one side isn’t thinking critically?

When critical thinking is weak on either side, the other role feels it.

If a manager isn’t thinking critically, team members may find themselves dealing with priorities that keep shifting, decisions that don’t account for how the work actually gets done, or problems that disappear for a week and then come back in a different form.

If a team member isn’t thinking critically, the manager may end up fielding every problem, reopening decisions that should have stayed closed, or sorting through recommendations that haven’t been thought through far enough to be useful.

In either case, someone else ends up doing more work.

A manager who makes a quick decision without understanding the operational impact may leave the team to untangle the consequences. A team member who escalates every obstacle without considering possible solutions pushes more decision-making upward than necessary.

Over time, that can change how people work together. Managers may stop asking for input because they don’t expect useful recommendations. Team members may stop speaking up because they don’t think their perspective will be considered.

This is where critical thinking becomes more than an individual skill. The quality of one person’s thinking affects the quality, speed, and workload of the people around them.

So, who’s responsible for better critical thinking in the workplace?

Both, of course.

The goal isn’t for team members and managers to think the same way. It’s for each side to understand what the other is trying to accomplish, what their underlying concerns are, what information they may be working with, and where their own assumptions might be getting in the way.

That doesn’t mean everyone will agree. In fact, good critical thinking often produces disagreement. The goal is to make that disagreement useful.

If a team member can see why a manager is asking for more context without getting defensive, and a manager can see why a team member is pushing back on a decision without assuming they’re lazy, both are in a better position to think through the issue rather than react to it.

At PMC Training, we use the term carefrontation as a reminder to disagree with the idea, not the person. It’s a simple principle, but a useful one when strong opinions, emotions, and different points of view lead people to different conclusions.

And that’s really where the value sits: not in everyone thinking the same way, but in people bringing different perspectives to the same problem and testing the options from more than one angle.

Build stronger critical thinking and decision-making skills

PMC Training’s Critical Thinking and Problem Solving for Effective Decision-Making course helps participants assess information, challenge assumptions, evaluate options, and make stronger workplace decisions.

It’s designed for professionals who need to make decisions, recommendations, or judgments as part of their work.