Hiring for Judgment, Not Tasks

A few years ago I was hiring for a marketing operations role at Visiting Media. We were somewhere around 35 people, working with a few hundred hotels, and I needed someone to own our campaign execution. I wrote a job description full of task-based requirements: manage the email calendar, coordinate with the design team, pull weekly performance reports, keep the CRM clean. Classic ops role spec. I hired someone excellent at all of it.

Six months later, every campaign still had to be approved by me or my VP because the person we hired would not make a call without checking first. Not because they were incompetent. Because the job I described was a task job, and I'd selected perfectly for it. The role said "execute." It didn't say "decide." So they executed, and waited, and the bottleneck was me.

That's when I started paying attention to a pattern I'd been too busy to name: most of my hiring specs were written around things I needed done, not around the quality of thinking I needed in the room. And as the company scaled, that gap was becoming a real problem.

The task trap

Task-based hiring makes complete sense early on. When you have eight people and need someone to handle customer onboarding, you write an onboarding role. You define the steps, you hire someone who can do the steps, and it works. The tasks are clear. The job is clear. There's not much ambiguity to navigate.

The problem is that companies keep writing the same kind of job descriptions as they grow, even when the environment has changed. By the time you're at 30 or 50 people, the tasks aren't always clear. The situation changes week to week. A decision made on Monday affects three other teams by Friday. What you actually need is someone who can look at an ambiguous situation and figure out the right move without a playbook telling them what to do.

Task people and judgment people can look identical on paper. They may have the same titles, the same years of experience, the same logos on their resume. The difference shows up in how they operate when the situation is unclear. Task people wait. Judgment people move.

What actually separates them

I've seen this play out clearly enough that I now think about it as a specific quality I'm screening for, not just a cultural fit vibe. Here's how it tends to manifest:

• Task people ask "what should I do here?" Judgment people ask "what outcome are we trying to get, and what's the fastest path to it?"
• Task people escalate problems. Judgment people bring problems with a recommendation attached.
• Task people optimize the process they were given. Judgment people question whether it's the right process.
• Task people are uncomfortable making calls they weren't explicitly authorized to make. Judgment people are uncomfortable not making them.
• Task people deliver what was asked for. Judgment people notice when what was asked for isn't what's actually needed.

None of this is a character flaw. Task orientation is valuable in plenty of roles, and some environments genuinely require it. But in a company that's growing and changing quickly, if most of your hires are task-oriented, you end up with a lot of execution capacity and very little distributed decision-making. That's a structure that works until the founders or senior leaders become the constraint on every meaningful choice.

The automaton problem

This distinction has become significantly more important over the last couple years, and I think most hiring managers haven't fully reckoned with it yet. The tasks that used to require a human hire are increasingly something you can route through a tool. Not all tasks, and not perfectly, but enough that the math is shifting.

At Visiting Media we've watched this happen in real time. Work that used to require a coordinator to manually pull together, format, and distribute is now largely automated. Work that required someone to draft, review, and send is faster with AI assistance. I'm not saying those roles disappear entirely. But I am saying that if someone's value to the organization is primarily "executes the repeatable tasks," that value is compressing faster than it was three years ago.

Judgment, on the other hand, doesn't compress that way. Deciding whether to push a major product release when you have a key customer negotiation happening next week requires understanding relationships, context, risk tolerance, and trade-offs that don't fit neatly into a prompt. Reading a situation and knowing when to escalate versus when to just handle it requires pattern recognition built from real experience. Knowing which customer complaints signal a systemic issue versus a one-off requires the kind of contextual awareness that doesn't automate well, at least not yet.

The people who bring that capacity become more valuable as tools handle more of the execution layer. The people whose primary value is execution become less differentiated. I'm not trying to be cold about it. It's just where the economics are going, and I'd rather be honest about it than pretend the hiring model from 2018 still applies in 2025.

How I changed the way I hire

I started rewriting job descriptions to describe decisions, not just duties. Instead of "manage the customer onboarding process," I'd write "own the customer's first 90 days and make the calls that determine whether they get to value quickly." That shift sounds minor but it attracts different candidates and sets different expectations from day one.

I also changed how I interview. I used to ask a lot of "walk me through how you'd approach X" questions. Those are fine for checking competence, but they don't tell you much about judgment. Now I ask more questions like:

• Tell me about a time you made a call you didn't have explicit authority to make. What happened?
• Describe a situation where you pushed back on what your manager asked you to do. What was your reasoning and how did it go?
• When did you last realize mid-project that the goal you'd been given was the wrong goal? What did you do?
• Give me an example of a time you had to make a decision with incomplete information and a real deadline. How did you think through it?

The answers to these questions tell you a lot more about someone's operating style than their resume. Task people tend to give answers where the authority to act came from above. Judgment people tell you about times they figured out what needed to happen and made it happen, sometimes despite friction, and can articulate clearly why they believed it was the right move.

I also started being explicit about this in onboarding. When someone joins my team now, one of the first things I tell them is: your job is not to do the tasks in your job description. Your job is to own the outcomes your role is responsible for and make good decisions in service of those outcomes. The job description is a starting point, not a ceiling. If you see something that needs to happen and it's in your lane, handle it. If you're wrong, we'll talk about it. But defaulting to inaction because you're waiting for permission is not what I need from you.

The caveat worth naming

I don't want to oversell this as a universal truth. There are roles where task execution is genuinely the job, and hiring someone who's always questioning the process would be disruptive in a bad way. There are also early career hires who are still building the experience base that judgment comes from, and they need structure and clear tasks while that develops. Judgment isn't something you can just tell people to have.

The principle applies at the level of the role design and the hiring bar for that role, not as a blanket statement that task orientation is bad. What I'm saying is that if you're building a leadership team, or hiring senior individual contributors, or trying to create an organization that can operate with some velocity and autonomy, you need people who bring decision-making capacity, not just execution capacity.

At Visiting Media, the hires that have had the most leverage haven't been the ones who were best at doing the thing. They've been the ones who understood why the thing mattered, could identify when we were doing the wrong thing, and had the confidence to say so and redirect. That combination is rarer than technical skill, harder to screen for, and worth more when you find it.

Where this leads

The companies that figure out how to hire for judgment at scale are going to have a structural advantage over the ones that keep hiring for tasks. Not because execution doesn't matter. It does. But execution is increasingly something you can get from tools, contractors, and highly structured processes. Judgment is still a human thing, at least for the decisions that actually matter, and the people who have it and can apply it in a complex, fast-moving environment are genuinely hard to find.

That scarcity means it's worth getting serious about how you identify and attract those people. Which means being honest in your job descriptions about what the role actually requires. Which means asking interview questions that surface how people think, not just what they've done. Which means building an environment where people feel safe making calls, because judgment atrophies in cultures where every decision gets second-guessed.

I've made the task-hire mistake more than once. I've also gotten increasingly good at recognizing the difference before I make an offer. The question I keep thinking about, especially as the execution layer of knowledge work continues to shift: what does a team look like when most of the tasks are handled, and the only thing left is judgment calls all the way down?