How OKRs inform hiring: How your goals decide who to hire next

Key Takeaway: The biggest cause of bad hires isn't bad interviewing. It's hiring without first being clear on what the company is trying to achieve. Goals come first. Then you figure out who you need to deliver them. Before opening your next role, write down the OKR (or KPI) that hire is supposed to move. If you can't name it, don't open the role yet.

When someone starts a business, they have a big idea, a dream if you will, that they'd like to realize. That idea is usually called the mission. The founders also have a certain company in mind that they want to build, typically called the vision.

The vision is not always clear from the beginning, but it will certainly develop over time. The mission may also change over time. Wikipedia was originally meant to be written by experts only. Hotmail started life as a database company. Twitter began as a podcasting company. Mission and vision evolve, sometimes dramatically, but in every case the goals come first.

That same logic should be guiding how you hire.

Goals come first, people come second

At the early stages of a company, it's crystal clear that goals come first. If it were the other way around, the people you hire would be defining your strategy. Your strategy then doesn't serve your mission and vision, it serves your people. That's not a winning formula for any organization, commercial or non-profit.

Most leaders agree with this in principle. In practice, the order gets reversed all the time, especially as the company grows. (For more on how companies should be thinking about the role of HR in OKRs, we've written about it separately.)

Here are the patterns I see most often:

• A team becomes too busy, so the manager opens a req for "more of the same."
• A talented person becomes available, so leadership tries to "find a role for them."
• Hiring quotas get tied to budget cycles instead of strategy cycles, so teams hire because they have headcount to spend.
• A function (sales, marketing, product) is "behind plan," so leaders default to hiring instead of asking whether the current team is working on the right things.

None of these starts with the question "what is the company trying to achieve, and who do we need to make that happen?" They all start with the people, and try to retrofit the goals.

This is the single biggest source of bad hires. Not bad interviewing. Not bad sourcing. Hiring without first being honest about what the company actually needs.

What a bad hire actually costs

This isn't just an abstract concern. The cost of a bad hire is real and well-documented.

Workforce research consistently puts the direct cost of a bad hire at a minimum of 30% of that employee's first-year salary. For many roles, that's $15,000 to $25,000 in immediate expense. Once you include recruiting costs, onboarding time, management distraction, lost productivity, and the cost of replacement, the total impact lands somewhere between 50 and 200% of annual salary.

And those numbers don't capture the human cost. Hiring someone for the wrong role, and then having to let them go, is a bad experience for everyone involved. I've made this mistake myself several times. It's almost always avoidable, and the way to avoid it is the same: be honest about the goals before you start the hiring process.

How OKRs should inform your hiring

OKRs are the cleanest lens for making this connection deliberate. Done right, they tell you exactly what the company is trying to achieve this cycle, which means they also tell you what kind of work the company needs to get done, which tells you what kind of people you need to hire.

Here's the simple sequence:

1. Set the strategy. What is the company trying to achieve over the next year or 2? This anchors everything downstream.
2. Translate to OKRs. What 3 to 5 Objectives this quarter will move the strategy forward? What measurable Key Results will tell you if you're winning?
3. Identify the work. What Initiatives are required to deliver those Key Results? What skills and capacity does that work actually demand?
4. Decide on the people. Now, and only now, is it the right time to ask: do we have the people to do this work? If not, what specific role would close the gap?

For more on how to set up this kind of OKR system properly, see our pilot program guide and our OKR examples for HR teams.

Compare that to the more common pattern: "We're growing, we should probably hire a head of growth." That sentence has a job title in it, but it doesn't have a goal. Without the goal, you'll interview candidates for "head of growth," hire one who looks great, and 6 months later discover that what you actually needed was a head of partnerships, or a stronger lifecycle marketer, or no head at all.

If you start from OKRs, you wouldn't make that mistake. The Key Results would have told you exactly what kind of growth and what mechanism it would come through, which would have shaped the role description from the start.

Examples of OKR-driven hiring decisions

This becomes more concrete with examples. Here's how the logic plays out in practice.

Objective: Become the most trusted brand in our category.
Key Result: Earn 25 high-quality backlinks from publications with DR 60+ this quarter.
Implied hire: A senior PR or earned-media specialist, not just "another marketing person."

Objective: Open up our next major growth segment.
Key Result: Generate $4M in qualified pipeline from the new mid-market segment.
Implied hire: An Account Executive with proven mid-market experience, not a generalist or an enterprise rep.

Objective: Make our platform the system of record for our largest enterprise customers.
Key Result: Ship 3 integrations into the top-used enterprise tools by Q3.
Implied hire: An integrations engineer with API and partner ecosystem experience, not "another full-stack engineer."

Notice how, in each case, the OKR makes the role specification sharper. The job title that emerges from "we need more growth" is generic. The job title that emerges from a specific Objective and Key Result is precise. Precise hires are easier to recruit for, easier to evaluate against, and far less likely to fail.

Skills, not just titles

Once you've identified the right role from your OKRs, there's a second shift that matters: hiring for the specific skills the work demands, not the credentials that traditionally come with the title.

Harvard Business School research found that when companies remove degree requirements from roles and hire on demonstrated skills, the non-degreed candidates they bring in have a 10-percentage-point higher 2-year retention rate than their college-educated coworkers (58% versus 48%, a 20% relative increase). And those workers see roughly a 25% increase in salary on average when they step into roles that previously required a degree, which is a strong sign that they're delivering real value.

The point isn't that degrees don't matter. It's that the right starting question is "what skills does this OKR require us to bring in?" not "what credentials are typical for this title?" When you start from the OKR, the skills become obvious. When you start from the title, you tend to copy what other companies are doing, which may have nothing to do with what your company actually needs.

What this means in practice

For Perdoo customers, the natural place this happens is at the connection between strategy, OKRs, and headcount planning. When the same team that sets the OKRs is the team that signs off on hires, the logic stays tight. When those functions are decoupled, drift sets in.

A few practical moves worth considering:

• Every open req should reference an Objective and Key Result. Not as bureaucratic overhead, just as a sanity check. If the hiring manager can't name the goal, the role probably isn't ready to be opened.
• Time-to-hire and quality-of-hire belong as HR KPIs tied to the broader strategy. Filling a role fast isn't success if it's the wrong role.
• Workforce planning should sit in the same cadence as OKR planning. Don't run hiring planning on the budget calendar and OKR planning on the quarterly calendar. They should move together.
• Use OKRs to decide what not to hire. Sometimes the right answer is "stop doing X" rather than "hire someone to do more X."

The one question to ask before opening your next role

Here's the concrete move for this week.

Before you open your next req, write down 1 sentence that completes the following: "We are hiring this person primarily to move X from A to B".

If you can fill in the blanks confidently with a specific Objective, a measurable Key Result, a current baseline, and a target date, the role is ready to open.

If you can't, the role isn't ready. The honest move is to step back and ask whether the goal is actually clear, whether the current team can deliver it without a new hire, or whether what you actually need is a different role than the one you were about to post.

The point isn't to make hiring harder. The point is to make sure every person you bring in is set up to win, because you've already done the hard work of being clear about what winning looks like.

You don't become a doctor because you studied medicine. You study medicine because you want to become a doctor. The same logic should be guiding every hiring decision your company makes.

Watch video