You Are Not Hiring a Team. You Are Building One.

Strategic hiring is not about filling seats. It is about building the capability your organization needs next, not just the one it has right now.

By Matthew A. Johnson · Fractional CTO & CPO, JHG Consulting

I know what you are thinking right now.

Two people just gave notice. The roadmap is slipping. The CEO sent you a message at 7am. And you are reading an article about strategic hiring that is probably going to tell you to slow down and think carefully about culture fit and values alignment.

Stay with me for a minute. Because I am going to make the urgency argument before I make the strategic one, and then I am going to show you why they are actually the same argument.

Here is the number that should stop you: the U.S. Department of Labor puts the average cost of a bad hire at 30% of that employee's first-year salary. For a specialized engineer or technical lead, CareerBuilder data puts the total loss between $17,000 and $240,000 depending on seniority. SHRM's 2025 Benchmarking Report shows the cost to replace an executive role has spiked to $35,879 on average, up 21% in three years. And that is before you count the lost productivity, the team morale hit, or the three months you spent convincing yourself it was going to work out.

Here is the harder number: 74% of employers admit they have made a bad hire, and 38% of those attribute it directly to speed pressure. Not incompetence. Not bad judgment. Pressure to fill the seat fast.

89% of hiring failures are now attributed to attitudinal misalignment, not technical skill deficiencies. The person could do the job. They just were not the right person for this team, at this stage, going in this direction.

So the urgency is real. The cost of getting it wrong under urgency is also real. And the instinct that feels like the responsible thing — just get someone in the seat now — is statistically the most expensive thing you can do.

This article is not theory. It is what I learned building and rebuilding technical teams over 25 years, including the hard lessons from the wrong hires I made in a hurry and the outsized returns from the right ones I took the time to find. There is a section specifically about the urgency trap and how to move fast without making it worse. But first, the foundational problems that urgency exploits.

Strategic hiring is not a process. It is a mindset. And the companies that get it right do not get it right because they have more time than you do. They get it right because they stopped treating every open seat as an emergency and started treating the team as the strategy.

---

The Clone Problem

When most managers describe the candidate they are looking for, what they are describing is a version of themselves. Someone who thinks the way they think, prioritizes what they prioritize, communicates the way they communicate. It feels like a good fit because it is familiar. It feels like a low-risk hire because there is no friction.

What it actually produces is a team that is very good at one thing and blind to everything else. The risks that the leader does not see, the team does not see. The problems that the leader would dismiss, the team dismisses. The opportunities that the leader is not wired to recognize, the team walks right past.

I have seen this play out in engineering organizations where every hire is a technically excellent individual contributor who thinks about problems the same way the CTO does. The team ships clean code and argues about architecture, and nobody is asking what the customer actually needs because that is not the lens any of them were hired through. I have seen it in sales organizations where everyone has the same style and the same background and the pipeline is full of the same kind of deal, because nobody on the team knows how to see a different kind of opportunity.

Hiring clones of yourself is not safe. It is the most reliable way to create an organization that cannot adapt.

The research on this is consistent across decades and industries. Cognitively diverse teams, meaning teams where people approach problems from genuinely different directions, outperform homogeneous teams on complex tasks. Not because diversity is a virtue in the abstract, but because hard problems require the ability to see them from multiple angles simultaneously. A team where everyone sees the problem the same way will solve the problem the same way, which means they will miss the solution that requires a different frame.

This does not mean you should hire people who are incompatible. It means you should hire people who are different in the ways that matter: how they think, what they notice, what they question, what assumptions they bring. The friction that produces is not a management problem. It is the mechanism by which good decisions get made.

---

The Succession Problem Nobody Wants to Talk About

There is a conversation that almost no manager wants to have, and that almost every good organization eventually forces. It is the question of who comes next.

Most leaders avoid succession planning for the same reason they avoid going to the doctor when something feels off. If you name it, it becomes real. If you name the person who could replace you, it feels like you are planning your own departure. If you name the person who could replace someone on your team, it feels disloyal, or presumptuous, or like you are undermining the person who is currently in the seat.

None of that is rational, but all of it is very human.

The military has understood for a long time that this instinct, left unaddressed, is operationally dangerous. Military units are built around the assumption that any leader at any level could be incapacitated at any moment, and the unit needs to continue functioning. The answer to that is not just training. It is a culture where every person understands not only their own role but the role above them, and where succession is treated as a normal and ongoing part of organizational health rather than a taboo topic.

If the only person who can do your job is you, then you have not built a team. You have built a dependency.

The most successful companies I have watched operate this way. They do not wait for someone to leave to ask who is ready. They are continuously developing people for roles they do not yet hold, giving them exposure to decisions above their current level, letting them fail at manageable scale so they can learn without catastrophic consequences. They treat the bench as a strategic asset.

I learned a version of this at HID Global after the Bluvision acquisition. When you are operating inside a large organization with multiple product lines and a diverse customer base, the operational reality is that you cannot be everywhere. The only way the portfolio functions is if the people around you can make good decisions when you are not in the room. That does not happen because you hire smart people. It happens because you have invested in developing people who understand not just their own domain but the broader context of what the organization is trying to do and why.

The leader who never develops a successor is telling their organization something important: that they do not fully trust anyone around them. Teams internalize that signal, and they respond to it by not fully investing in the organization in return.

---

What It Actually Looks Like When You Get It Right

The best teams I have built shared one characteristic that had nothing to do with individual talent. Every person on those teams knew who was next in line. Not just vaguely. Specifically. The team knew that if I got hit by a bus tomorrow, the work would continue. And that knowledge changed everything about how the team operated.

It started with being explicit about career paths. I made a point of telling people not just what their current role was, but where it could lead and what that progression looked like. That conversation is one most managers avoid because it feels like making promises you cannot keep. I found the opposite to be true. When people understand the path, they invest in it. When the path is invisible, people start looking for it somewhere else.

More important than the individual path was the message it sent about the organization. When I sat down with someone and said here is what I see for you, here is who I think you could become on this team, what I was really saying was that my job is not just to extract work from you. My job is to develop you. That this organization is bigger than any one person, including me. That I will not always be here, and the team should be built to outlast any individual seat, including mine.

The team that knows who is next in line is not worried about what happens if you leave. They are focused on the work.

The effect on the team was not what I expected the first time I tried it systematically. I expected some awkwardness, maybe some anxiety about who was ahead of whom. What I got instead was a different kind of confidence across the whole team. When people know the organization is thinking about their future, they stop spending mental energy on it themselves. They stop looking sideways at what everyone else is doing. They focus forward.

It also changed how the team worked together. When succession is invisible, there is a natural tendency for people to protect their expertise. Knowledge is currency. The person who knows how something works has leverage, and sharing that knowledge feels like giving up something. When succession is explicit and the development of the people around you is part of how you are measured, that calculation flips. Helping someone grow does not threaten your position. It demonstrates that you are ready for the next one.

I watched this shift happen on more than one team. Engineers who had been protective about their domain knowledge started writing documentation not because they were told to but because they understood that their legacy was not the code they wrote. It was the capability they left behind. Product managers started pulling junior team members into decisions that they previously would have handled alone. The team got better not because I hired better people, but because the people I had started investing in each other.

When people feel like the organization is developing them, they start developing each other. That multiplier is the whole game.

The hit-by-a-bus test is a useful forcing function but I think it understates the real benefit. The question is not just whether the team survives your departure. It is whether the team is operating at full capacity right now because nobody is the single point of failure for anything critical. Organizations with deep benches do not just recover from disruption. They absorb it without breaking stride. The organization that has one person who knows how the critical system works is not just vulnerable to that person leaving. It is constrained by that person's bandwidth every single day they are present.

---

What Strategic Hiring Actually Looks Like

Strategic hiring starts before the job description. It starts with an honest assessment of what the team can and cannot do today, and what it needs to be able to do twelve months from now.

That assessment is harder than it sounds because it requires leaders to be honest about their own blind spots. The gaps that are most dangerous are usually not the ones you can see. They are the capabilities you do not have and therefore do not know to look for. A team that has never had strong design thinking does not usually know it is missing strong design thinking. It just knows that the product keeps feeling slightly off and cannot articulate why.

This is one reason why the best hiring decisions are often made by leaders who actively seek input from outside their own frame. Talking to customers about what they experience. Talking to people who have left the organization about what they noticed. Talking to candidates who declined offers about what they saw in the interview process. Each of those conversations surfaces information that the internal view cannot generate.

The best hire you ever make is often the one who sees something you cannot see. The worst hire is the one who confirms everything you already believe.

Once you have an honest picture of what the team needs, strategic hiring means being explicit about the traits and values that matter, not just the skills. Skills are trainable. The way someone thinks about a problem, the intellectual honesty they bring, the degree to which they argue for what they believe rather than what they think you want to hear, the curiosity they bring to things outside their domain, those are not trainable in any meaningful time frame. You either hire for them or you do not.

It also means being willing to hire for the role you need in a year, not just the one you need today. The person who is perfect for the current state of the team may be the wrong person for where the team is going. That is a hard trade-off to make in practice, because the pressure of the current moment is real and the future state is abstract. But the teams that consistently build well over time are the ones where the leader is always thinking one step ahead of the hire.

---

Culture Is Not a Benefit. It Is the Work.

There is a version of culture that gets talked about in hiring processes that has almost nothing to do with actual culture. Ping pong tables, free lunch, flexible hours. These are perks. They are not culture.

Culture is what the organization actually values, as demonstrated by what it does when it is under pressure. Not what it says it values. What it does. A company that says it values quality and then ships something it knows is broken because of a deadline has told its employees the actual priority order. A company that says it values feedback and then punishes the person who gave honest feedback to the wrong person has told its employees the actual rules. People are very good at reading the difference between the stated values and the real ones, and they orient their behavior accordingly.

This matters for hiring because people join organizations based on what the organization says it is, and they stay or leave based on what they discover it actually is. High attrition is almost always a culture diagnostic before it is a compensation one. The people who leave first are usually the ones with the most options, which means high attrition is a selection mechanism that progressively removes the people who have the most choices and leaves behind the ones who do not.

The team you end up with is the sum of every hiring decision you have made and every departure you have tolerated. Culture is not declared. It accumulates.

Building a great product or a great technology platform requires a team where people feel safe saying what they actually think. Not safe in the sense that there are no consequences for anything, but safe in the sense that the person who raises the inconvenient question is respected rather than punished. That kind of safety does not happen because you wrote the right values on the wall. It happens because the leader models it, consistently, over time, and especially when it is uncomfortable.

I have seen technically excellent teams build mediocre products because the culture was one where disagreeing with the leader was career-limiting. I have seen technically modest teams build remarkable things because the culture genuinely rewarded people for finding the problem before it became a crisis. The technology and the skills matter. They are not sufficient.

---

The Collaboration Question

One of the most reliable predictors of team performance is how the team communicates when things are not going well. Anyone can communicate well when things are easy. The question is what happens when a deadline slips, when a technical decision turns out to be wrong, when a product ships with a problem that somebody saw coming and did not say loudly enough.

Teams that are built from clones tend to handle these moments by closing ranks. The shared frame means the shared conclusion is usually the same: the external circumstances were to blame, the decision was reasonable given what was known, and the way forward is to redouble the current approach. The friction that would come from someone with a different perspective is absent, and so the learning is absent too.

Teams built with genuine diversity of perspective handle these moments differently. The post-mortem is actually uncomfortable because people see it differently. The diagnosis is more accurate because the blind spot of one person is often visible to another. The corrective action is more durable because it comes from a richer understanding of what actually happened.

Collaboration, real collaboration, is not harmony. It is productive disagreement in the service of a shared outcome. The manager who is uncomfortable with disagreement will build a team that agrees with them and produces mediocre results. The manager who is comfortable with productive tension will build a team that challenges itself and produces something worth building.

You do not need a team that agrees with you. You need a team that is honest with you. Those are not the same thing.

The hiring implication is specific. You should be actively recruiting for people who will push back. Not people who are contrarian for its own sake, but people who have the intellectual confidence to say what they see, the communication skills to say it in a way that moves the conversation forward, and the values to care more about the right outcome than about being right. Those people are harder to manage, which is exactly why most managers do not hire them. They are also the people who build things that last.

---

The Urgency Trap

I know what you are thinking. This all sounds right in theory. And then Monday morning arrives, two engineers gave notice last week, the product roadmap is slipping, the CEO is asking questions, and the idea of taking three months to run a careful strategic hiring process feels completely disconnected from the reality you are living.

I have been in that moment. More than once. The pressure of an open seat is real. The cost of a delayed project is real. The impulse to hire whoever can start soonest is completely rational given what the calendar looks like.

Here is what I learned the hard way: a wrong hire does not solve the urgency problem. It relocates it. You spend six weeks onboarding someone who is not the right fit. You spend another six weeks managing the performance gap and trying to convince yourself it will improve. You spend three months having the conversation you should have had at month two, and then you are back to square one except now you are six months behind and the team has absorbed the disruption of a departure on top of everything else.

A bad hire in a hurry costs you the time you were trying to save, and then it costs you the time you spent fixing it.

The answer to urgency is not to abandon standards. It is to be honest about what the standards actually are for this specific moment. There is a difference between the ideal hire for a role and the right hire for where the team is right now. Sometimes those are the same person. Sometimes they are not, and being clear about which situation you are in changes the search entirely.

If you genuinely need bodies now, the most effective short-term answer is usually not a permanent hire at all. A contractor, a fractional resource, or a temporary augmentation buys you time to make the permanent decision well without letting the project bleed. It is more expensive per hour and it is the right call when the alternative is a permanent hire made from desperation.

For the permanent seat, there are three things I have found that compress the timeline without compromising the outcome. First, know exactly what you need before you start. Not a job description written in an afternoon, but a genuine conversation with yourself and the people closest to the work about what the team is actually missing. The more specific that answer is, the faster you can filter. A vague brief produces a long search because every candidate looks sort of right.

Second, use your network before you use job boards. The best hires I have made came from someone I already knew or someone in my network knew. Those candidates move faster, require less explanation of context, and tend to fit better because someone who knows you vouched for the fit. The job board is a last resort, not a first step.

Third, accept that the first thirty days of any new hire are slow regardless. The instinct in urgency is to hire someone who can hit the ground running immediately, which usually means hiring someone whose experience is almost identical to what you already have. But hitting the ground running in week one and being transformative in month six are different things, and in the urgency of the moment it is easy to optimize for the wrong one.

The hire who takes thirty days to find and thirty days to ramp will outperform the hire you made in two weeks every time. The math always works out the same way.

The deeper shift is a cultural one. The organizations that are least vulnerable to urgency-driven bad hires are the ones that never let the bench get to zero. They are always having conversations with people who might be right for the next seat before the seat opens. They treat relationship-building with potential future hires as an ongoing activity, not something that starts when there is a gap to fill. That is a habit that takes time to build and pays compounding returns once it is established.

---

This Is Exactly Why Companies Bring In Fractional CTO and CPO Leadership

Everything in this article is difficult to do while you are also running a product, managing a team, closing a fundraising round, and trying to ship something by the end of the quarter. That is not an excuse. It is a structural reality that most founders and executive teams face, and it is one of the primary reasons fractional technical leadership exists.

A fractional CTO or CPO is not a body filler. The right one is someone who has built organizations, made hiring mistakes at real cost, figured out what succession planning looks like in practice, and can sit across from your team and help you see the gaps you cannot see from the inside. That perspective is worth something precisely because it is outside the daily pressure you are operating under.

The hiring and organizational design piece is one of the most underestimated parts of what fractional technical leaders do. It is also one of the most consequential. Getting the org structure right, knowing what roles you actually need for the next stage of growth rather than the current one, building a hiring plan that maps to your roadmap rather than reacting to whoever just left, these are not HR activities. They are strategic decisions that determine whether the technical capability of the company can actually support where the business is going.

You cannot scale a company with an org chart designed for where you were twelve months ago. And you cannot raise capital with a team that looks like it was assembled under pressure.

This becomes especially visible in high-stakes external conversations. When you are sitting across from a PE firm or a venture capital partner, they are not just evaluating your product or your market. They are evaluating whether the team in front of them can execute at the next level of scale. The org chart questions come fast. Who owns engineering? Who owns product? What does the technical leadership bench look like? What is the plan if your VP of Engineering leaves? If those answers are vague, or if the honest answer is that you have not thought through it yet, the conversation goes in a direction you do not want.

The same is true for press and media. When a company gets the kind of attention that brings CNBC or the Wall Street Journal to the table, the questions that separate credible operators from lucky startups are almost always about the team. Who built this? Who is running it now? What does the organization look like at scale? A founder who can answer those questions with specificity, who can articulate not just who is in the seats but why those people are in those seats and what comes next, is a founder who sounds like they know what they are doing. Which they should, because they actually do.

A fractional CTO or CPO who has been through those conversations, who has sat in diligence rooms and press briefings and board meetings and knows what the questions are going to be, can help you build the team story before you need to tell it. Not as a PR exercise but as a genuine operating reality. The story has to be true, which means the work has to be done first.

The time to build the team that impresses a PE firm is not the week before the meeting. It is eighteen months before the meeting, when nobody is watching.

Most founders wait until the external pressure is already on them to think seriously about hiring strategy and organizational design. The meeting is on the calendar, the deck is in progress, and suddenly the realization lands that the team section is the weakest part of the pitch. At that point the options are limited. You can dress up what you have, which experienced investors see through immediately. Or you can be honest about the gaps and have a plan for closing them, which at least demonstrates self-awareness.

The better path is the one that starts earlier. Build the team before the scrutiny arrives. Know who is next in line before anyone asks. Have the org chart for the next stage already in your head, even if it is not fully staffed yet. Work with someone who has seen what good looks like at the next level of scale and can tell you honestly whether what you have is going to hold.