From Richard: Hiring Mistakes

I want to tell you about the most expensive lesson I've learned in fifteen years of building companies.

In 2019, I hired an operations lead for Morphic Fit. His resume was immaculate—startup experience, MBA from a top program, numbers that looked right. He interviewed well. Confident. Articulate. He said all the things I'd want to hear about scaling processes and building teams.

Six months in, I was managing his anxiety daily. A year in, I was cleaning up cascading mistakes. He wasn't lazy. He wasn't malicious. He was fundamentally misaligned with what the role actually required.

Looking back with the framework I now use every day, I can see exactly what happened.

The role demanded a Navigator—someone who thrives in ambiguity, who can make decisions with incomplete information and course-correct in real-time. What I hired was an Architect. The job required someone comfortable with 20 simultaneous variables, daily pivots, and the cognitive chaos of a scaling company. His cognitive profile was built for deep, methodical system-building. He needed to understand a problem fully before acting. The role gave him none of that luxury.

More specifically, his Cognitive Load Tolerance was nowhere near what the position required. He had high Pattern Recognition—he could see systems problems with remarkable clarity. But when the job asked him to hold multiple complex threads while making fast decisions, he froze. His Execution Drive looked good on his resume; in reality, it only activated when he had the mental runway to plan thoroughly. That runway didn't exist in a fast-moving startup.

His Collaborative Resonance was also low. He worked best in focused, independent concentration. The role needed someone who could synchronize with the team constantly, absorb information in real-time, and adjust based on shifting priorities. Instead, I had someone who needed to retreat to process before responding.

The mismatch cost me $180,000 in salary over 18 months. It cost me more in opportunity—projects delayed, momentum lost, two good team members burned out trying to compensate. One of them eventually left. And the hardest cost: I kept him too long because letting go meant admitting I'd made a mistake. I was emotionally attached to my own judgment.

Here's what I now understand: the resume told me his history. The interview showed me his confidence. Neither told me whether his cognitive architecture matched the job's actual demands.

The real question I wasn't asking was: "What is the actual cognitive complexity of this role, and does this person's mind work the way this work needs to work?"

I was hiring based on credentials and chemistry. What I should have been doing—what The Scanner now lets me do—is map the Demand Signature of the role against the candidate's actual cognitive profile. Not what they can do in an interview. Not what they've done before. What they can sustain under the specific pressures this job will create.

The most expensive hires aren't the incompetent ones. They're the competent people in the wrong cognitive configuration. The person who would thrive in a structured environment, placed in chaos. The Strategist placed in a role that needs a Catalyst. The Sentinel who sees every risk, asked to drive rapid execution.

I've made this mistake more than once. What changed wasn't my intuition—it was building the discipline to measure before I commit. Now I always define the cognitive demands of the role before I look at a single candidate. The complexity level, the decision cadence, the collaboration intensity. Then I match.

That hire in 2019? He eventually went to a larger company with more structure. He's thriving there. The right role exists for every cognitive profile. The mistake was mine for not defining the role clearly enough before I went looking for someone to fill it.

The question isn't whether someone is good. It's whether they're good for this.