Using EOS and Company Operating Systems to Hire Better

If your company runs on EOS (the Entrepreneurial Operating System), Scaling Up, 4DX, or any structured business operating system, you already have something most companies lack: documented values, defined accountability structures, and a shared language for evaluating performance. What most EOS companies do not realize is that this framework is also one of the most powerful hiring tools available — if you know how to translate it into the recruiting process. EOS hiring, done correctly, means every candidate is evaluated against the same criteria your existing team is held accountable to, creating alignment from day one instead of hoping it develops over time.

This is the second post in our Company Culture series. If your company does not run on a formal operating system, you can still benefit from the frameworks described here — they provide a structured approach to values-based hiring that works regardless of whether you use EOS terminology.

What EOS Gives You That Most Hiring Processes Lack

The genius of EOS and similar operating systems is that they make implicit expectations explicit. In most companies, the standards for success are unwritten: you learn what matters by watching, asking, and occasionally failing. Operating systems document those standards so everyone is working from the same playbook.

For hiring purposes, EOS provides four assets that most companies have to build from scratch:

1. Documented core values. EOS requires companies to define their core values and use them operationally — not as wall art, but as evaluation criteria in quarterly conversations and the People Analyzer.
2. The Accountability Chart. Instead of a traditional org chart organized by hierarchy, the Accountability Chart organizes by function and clearly defines the five roles every seat requires. This gives you a precise definition of what success looks like in every position.
3. GWC (Get It, Want It, Capacity to Do It). This three-part filter evaluates whether a person is right for a specific seat. It separates understanding (Get It) from motivation (Want It) from ability (Capacity), which prevents the common mistake of hiring someone who can do the job but does not want to, or wants the job but cannot do it.
4. The People Analyzer. A structured tool for evaluating whether someone embodies the company's core values. It uses a simple plus/plus-minus/minus scoring system for each value, creating a clear, shared evaluation framework.

Most companies spend months trying to build these tools for their hiring process. If you run EOS, you already have them. The gap is in applying them to candidates, not just current employees.

How to Use the People Analyzer in Hiring

The People Analyzer is the EOS tool for evaluating whether someone lives your core values. In its standard application, you use it to evaluate existing team members in quarterly conversations. The manager rates each person as a plus (embodies this value most of the time), a plus-minus (sometimes embodies this value, sometimes does not), or a minus (does not embody this value) for each core value.

Applying this to hiring requires one modification: since you cannot observe a candidate's behavior over time, you need to create interview structures that surface evidence for each value rating.

Step 1: Define Behavioral Evidence for Each Value

For each of your core values, write three behavioral descriptions that correspond to each rating:

• Plus (+): What does it look like when someone embodies this value naturally? What stories would they tell? What language would they use?
• Plus-Minus (+/-): What does it look like when someone sometimes embodies this value? What inconsistencies would show up in their examples?
• Minus (-): What does it look like when someone does not share this value? What anti-patterns would appear in their answers?

Step 2: Design Two Interview Questions per Value

For each core value, prepare two behavioral interview questions that give the candidate opportunities to demonstrate (or reveal the absence of) that value. Use the STAR format (Situation, Task, Action, Result) and listen for the specifics.

For example, if one of your core values is “Do the right thing,” your questions might be:

• “Tell me about a time when doing the right thing cost you something — a deal, a relationship, a promotion. What happened?” A plus candidate has a specific, compelling story. A minus candidate either cannot think of an example or describes a situation where “doing the right thing” was also the easy thing.
• “Describe a situation where you saw something unethical or problematic at work. What did you do about it?” A plus candidate took action. A plus-minus candidate noticed but hesitated. A minus candidate rationalizes inaction.

Step 3: Rate the Candidate Using the People Analyzer Format

After the interview, rate the candidate on each core value using the same plus/plus-minus/minus system you use for current employees. Your hiring bar should match your employee bar: if you would not accept a plus-minus rating from a current employee on a particular value, do not accept it from a candidate.

The power of this approach is consistency. Every candidate is evaluated against the exact same values framework that governs your existing team. There is no gap between what you screen for in hiring and what you hold people accountable to after they start.

How to Use GWC in Job Descriptions and Interviews

GWC is one of the most underutilized tools in EOS companies' hiring processes. Most EOS companies use GWC to evaluate whether current employees are in the right seat. Far fewer use it to evaluate candidates before they accept the offer.

Get It: Does the Candidate Understand This Role?

“Get It” means the candidate fundamentally understands the nature of the role, the challenges involved, and what success looks like. This is not about skills — it is about intuitive comprehension of what the job actually requires.

How to evaluate in an interview: Describe the role honestly, including its least attractive aspects. Then ask: “Based on what I have described, what do you think the hardest part of this job would be?” A candidate who Gets It will identify the real challenge. A candidate who does not will either minimize the difficulty or focus on something superficial.

How to build into the job description: Write a section titled “What this role actually looks like” and describe a typical week, including the unglamorous parts. The candidates who Get It will not be deterred. The candidates who do not will self-select out.

Want It: Does the Candidate Genuinely Want This Specific Role?

“Want It” is the most frequently misjudged dimension. Candidates are motivated to present enthusiasm for any role they are interviewing for. The question is whether they want this specific role, with its specific demands and trade-offs, or whether they want a job and this one happens to be available.

How to evaluate in an interview: Ask “What specifically about this role excites you, and what gives you pause?” Candidates who genuinely Want It can articulate both — they have thought about the trade-offs and decided the positives outweigh the negatives. Candidates who are just looking for any job will give generic enthusiasm without specificity.

Also ask: “If you could design your ideal next role, what would it look like?” Compare their answer to the actual role. The closer the match, the higher the Want It score.

Capacity to Do It: Can the Candidate Actually Perform?

“Capacity” encompasses skills, experience, intellect, emotional intelligence, and time availability. It is the most commonly evaluated dimension in traditional hiring, which means most companies do it reasonably well already. The EOS addition is separating Capacity from Get It and Want It, ensuring you do not hire someone who can do the job but either does not understand it or does not want it.

How to evaluate: Use your standard skills assessment. Then explicitly score the candidate on all three dimensions separately. A candidate must be a yes on all three. A yes-yes-no (Gets It, Wants It, but lacks Capacity) might be developable. A yes-no-yes (Gets It, has Capacity, but does not Want It) is almost never fixable. Motivation cannot be manufactured.

How to Translate the Accountability Chart Into Hiring

The EOS Accountability Chart defines every seat in the organization by its five key roles — the five most important outcomes that seat is responsible for. This is more useful than a traditional job description because it focuses on outcomes, not activities.

To use the Accountability Chart in hiring:

1. Start with the seat, not the person. Before writing a job description, review the Accountability Chart for the seat you are filling. What are the five roles? These become the foundation of your job posting and your interview evaluation criteria.
2. Write interview questions around each role. For each of the five key responsibilities, prepare a behavioral question that asks the candidate to describe their experience delivering that specific outcome. Not “Can you do this?” but “Tell me about a time you did this. What was the result?”
3. Score candidates against the roles, not against each other. The Accountability Chart defines the bar. Each candidate either meets the bar for each role or does not. This prevents the common trap of choosing the “best available” candidate who still falls short of what the seat actually requires.

Scaling Up: Translating the People Decisions Framework

If your company runs Scaling Up (Verne Harnish's framework) rather than EOS, the principles are the same with different vocabulary. Scaling Up's approach to people decisions emphasizes:

• Core values alignment — evaluated through behavioral interviews, similar to the EOS People Analyzer.
• BHAG (Big Hairy Audacious Goal) alignment — does the candidate get energized by your 10-25 year vision? This is the “Want It” dimension applied at the organizational level.
• KPIs and critical numbers — can the candidate deliver the specific measurable outcomes this role requires? This is the “Capacity” dimension with quantified expectations.
• One-page personal plan — Scaling Up encourages each person to have a one-page plan that aligns personal goals with company goals. In hiring, you can assess this alignment by asking candidates what they want their career to look like in three to five years and evaluating whether your company can realistically provide that path.

4DX: Hiring for Execution Discipline

The 4 Disciplines of Execution (4DX) is less a comprehensive operating system and more a framework for achieving critical goals. But its principles have direct implications for hiring:

• Discipline 1 (Focus on the Wildly Important): Does the candidate have the ability to prioritize ruthlessly? Can they distinguish between what is urgent and what is important? Ask: “When you have more tasks than you can complete, how do you decide what to focus on first?”
• Discipline 2 (Act on Lead Measures): Does the candidate understand the difference between lag measures (results) and lead measures (activities that drive results)? Ask: “In your last role, what daily or weekly activities had the biggest impact on your results?”
• Discipline 3 (Keep a Compelling Scoreboard): Is the candidate data-driven? Do they track their own performance? Ask: “How did you know whether you were doing a good job? What did you measure?”
• Discipline 4 (Create a Cadence of Accountability): Is the candidate comfortable with regular accountability rhythms? Ask: “How often do you prefer to check in with your manager? What does a productive check-in look like for you?”

Common Mistakes EOS Companies Make in Hiring

Mistake 1: Using Operating System Language in Job Postings

Saying “must GWC the seat” or “will be evaluated on the People Analyzer” in a job posting is insider language that confuses external candidates. Translate your operating system concepts into plain language. Instead of “must GWC the seat,” write “must deeply understand what this role requires, be genuinely excited about the work, and have the skills and capacity to deliver results.” The candidate does not need to know EOS to be evaluated with EOS tools.

Mistake 2: Only Evaluating Core Values, Not GWC

Some EOS companies use the People Analyzer in hiring but skip GWC. This produces hires who share the company's values but cannot actually do the job — or can do it but do not want to. All three dimensions must be evaluated. Values alignment without capability is just a culture hire who cannot deliver.

Mistake 3: Not Updating the Accountability Chart Before Hiring

When a seat becomes vacant, most companies immediately start recruiting for the same seat. But if the Accountability Chart has not been updated since the last person was in the role, you may be hiring for yesterday's needs rather than tomorrow's. Review the Accountability Chart for the seat before opening the requisition. Update the five roles to reflect what the seat actually needs now, which may be different from what it needed when it was last filled.

Mistake 4: Treating Operating System Adoption as a Hiring Requirement

Some EOS companies want to hire people who already know EOS. This unnecessarily narrows the candidate pool. EOS is a learnable framework. The underlying qualities — accountability, values-driven behavior, outcome orientation — are what matter. Hire for those qualities and teach the system.

Putting It All Together: An EOS-Aligned Hiring Process

Here is how a hiring process looks when it is fully integrated with your operating system:

1. Role definition: Pull the five key roles from the Accountability Chart. Define GWC criteria for the seat.
2. Job posting: Translate the Accountability Chart roles and core values into plain-language job description. Describe the actual working environment honestly.
3. Screening: Evaluate resumes against the five roles (Capacity) and look for values signals in career history and cover letters.
4. Assessment: Administer a personality or behavioral assessment to surface working style data that complements the interview. Platforms like PersonaScore can be configured to evaluate candidates against your specific operating system criteria.
5. Interview round 1: Core values evaluation using the People Analyzer framework. Two behavioral questions per value.
6. Interview round 2: GWC evaluation. Assess whether the candidate Gets It, Wants It, and has the Capacity for this specific seat.
7. Final evaluation: Score each candidate on the People Analyzer and GWC independently. Require plus ratings on all core values and yes on all three GWC dimensions. If the candidate falls short on any dimension, do not make the offer.

This process takes no longer than a standard two-round interview process. It simply adds structure and specificity to the evaluation, using tools your company already has.

You Already Have the Tools. Now Use Them.

If your company runs on EOS, Scaling Up, 4DX, or any structured operating system, you have already done the hardest work: defining your values, documenting your accountability structures, and creating evaluation frameworks. The only remaining step is extending those tools to the hiring process, where they can prevent misaligned hires before they happen rather than managing them out after they start.

For a deeper look at how to define the values themselves, see our previous post on defining company values that actually mean something. And for the broader framework of encoding company identity into hiring, revisit our post on how company DNA transforms hiring decisions. Next in our Company Culture series: why candidates ghost you and what your culture has to do with it.