Why do gut-feel hiring decisions go wrong so often?

Because an evaluation with no record rewards whoever felt most familiar rather than whoever met the requirements. Without a shared frame, personal bias quietly outvotes what the role demands, and the subtle red flags, a vague project account, an inflated ownership claim, a story that does not reconcile, evaporate because nobody wrote them down.

What does skipping interview documentation cost?

Months fixing what five minutes of notes would have caught. Undocumented interviews produce decisions you cannot compare across interviewers, red flags that surface on the jobsite instead of in the debrief, and bad matches that generate performance issues, team disruption, and a second search.

How much documentation does an interview really need?

About five tactical minutes, not a novel. Capture whether the person clears the must-haves and the one strength or concern that stands out most, tie the assessment to the job spec so the question is whether they meet what the role demands rather than whether you liked them, and give the team one written reference point so everyone argues from the same evidence.

Does documenting interviews slow down hiring?

No, it speeds decisions up, because a documented process removes the ambiguity that makes teams hesitate and rehash the same debate days later. It also sharpens the instinct you already trust: gut paired with a written record becomes judgment, while gut alone is a guess with good lighting.

Gut vs. Strategy · Ambassador Group

In this piece

1.What skipping the structure actually costs
2.Reflection isn't a chore. It's the discipline that protects your judgment.
3.What the discipline returns

About the author

TJ Kastning

Founder & Managing Partner

TJ founded Ambassador Group after years recruiting for construction organizations, watching misaligned leadership decisions cost projects, margin, and morale. He believes hiring is a deep leadership discipline, not just a transactional function. It shapes culture, capacity, and long-term outcomes. His work with clients focuses on clarifying expectations, surfacing assumptions, and helping leaders think more clearly about the environments they are creating. TJ is involved in every search as guide and thought partner.

More writing

Find the articles that fit you: answer a couple of questions and a live reading list narrows to match.

A 2-minute read

Are you ready to hire? Reading this with a hire in mind? A 2-minute check on whether the role, the comp, and the team are set up for it. Take the readiness check →

Trusting your gut feels efficient. It usually isn't. I've watched sharp construction leaders make a hire in the hallway after a forty-minute conversation, certain they read the person correctly, then spend the next nine months unwinding the damage. The instinct that felt like speed was the slowest path available. The reason it fails is not the candidate. It's the leader running an evaluation with no record of what they actually saw.

Here is the trade most leaders refuse to name out loud: they won't spend five minutes documenting an interview, but they'll spend a quarter rehabilitating a bad hire. The quality of that hire was never going to be decided by the candidate's polish. It was decided by whether the person across the table was honest enough with themselves to write down what they noticed and check it against the job. Gut isn't the problem. Gut with no mirror is.

What skipping the structure actually costs

Decisions you can't compare. When every interviewer runs on instinct, hiring becomes a guessing game dressed up as judgment. You believe you're spotting the right person. What you're often doing is rewarding whoever felt most familiar. Without a shared frame, personal bias quietly outvotes the actual requirements of the role.

Red flags that evaporate. A firm handshake and confident answers are not competence. The real signals are subtle: a vague account of a past project, an over-inflated claim of ownership, a story that doesn't quite reconcile. Those tells usually surface only when the team compares notes afterward. With no notes, they disappear, and you discover them on the jobsite instead.

Time poured into the wrong problem. Five minutes capturing what you saw, or months fixing what you missed. A bad match produces performance issues, team disruption, and eventually a second search. That costs far more than the reflection you skipped to feel fast.

Reflection isn't a chore. It's the discipline that protects your judgment.

The objection I hear is that documentation slows things down. It doesn't. It sharpens the instinct you already trust. Three moves are enough.

Keep it tactical. Skip the novel. Capture the few things that matter: does this person clear the must-haves, and what strength or concern stands out most.
Tie it to the requirements. The job spec exists for a reason. Use it as the spine of your assessment. The question is never whether you liked the candidate. It's whether they meet what the role actually demands.
Give the team one reference point. A written assessment means everyone argues from the same evidence. No rehashing the same debate three days later, no second-guessing a call nobody recorded.

What the discipline returns

Leaders who underwrite a hire against clear criteria, rather than a feeling, end up with people better suited to the role who stay longer. The decision gets faster too, because a documented process removes the ambiguity that makes teams hesitate. Over time, a team that decides on evidence builds a reputation for sound hires instead of lucky ones, and that reputation compounds.

Your gut still has a role. Paired with a written record of what you saw, it becomes judgment. Left alone, it's a guess with good lighting.

Those few minutes of structured reflection are not a luxury. They're the insurance policy against the hire that eats your next two quarters. And the leader who is willing to write down what they noticed, and be held to it, is the one whose instinct is actually worth trusting.

You already know which of your last five hires you can't fully explain. The next one is the place to change that.

Questions, answered

The short version.

Why do gut-feel hiring decisions go wrong so often?: Because an evaluation with no record rewards whoever felt most familiar rather than whoever met the requirements. Without a shared frame, personal bias quietly outvotes what the role demands, and the subtle red flags, a vague project account, an inflated ownership claim, a story that does not reconcile, evaporate because nobody wrote them down.
What does skipping interview documentation cost?: Months fixing what five minutes of notes would have caught. Undocumented interviews produce decisions you cannot compare across interviewers, red flags that surface on the jobsite instead of in the debrief, and bad matches that generate performance issues, team disruption, and a second search.
How much documentation does an interview really need?: About five tactical minutes, not a novel. Capture whether the person clears the must-haves and the one strength or concern that stands out most, tie the assessment to the job spec so the question is whether they meet what the role demands rather than whether you liked them, and give the team one written reference point so everyone argues from the same evidence.
Does documenting interviews slow down hiring?: No, it speeds decisions up, because a documented process removes the ambiguity that makes teams hesitate and rehash the same debate days later. It also sharpens the instinct you already trust: gut paired with a written record becomes judgment, while gut alone is a guess with good lighting.