How EOS Companies Should Hire: Integrating People Analyzer and GWC

If your company runs on EOS — the Entrepreneurial Operating System — you already have two of the most powerful hiring tools ever developed sitting in your L10 meeting notes. The People Analyzer and GWC (Get it, Want it, Capacity to do it) framework give EOS companies a structured language for evaluating whether someone is the right person in the right seat. The problem is that most EOS companies only use these tools after someone is already on the team, during quarterly conversations and annual reviews. By then, the damage from a bad hire is already done.

EOS hiring should start with the People Analyzer and GWC, not end with them. When you integrate these tools into your hiring process proactively, you stop relying on gut feel to evaluate candidates and start using the same disciplined framework that already runs the rest of your business. This post walks through exactly how to do that — step by step.

What Are the People Analyzer and GWC?

For readers who are newer to EOS, a quick primer. In Gino Wickman's Traction, the People Component is one of six key components of a healthy business. It is built on two tools:

The People Analyzer evaluates whether someone is the “right person” — meaning they share your company's core values. You list your three to seven core values across the top of a chart and rate each person with a plus (+), plus/minus (+/-), or minus (-) for each value. The bar in EOS is clear: someone must have mostly plusses and no minuses to be the right person. A single minus on any core value is a disqualifier, because core values are, by definition, non-negotiable.

GWC evaluates whether someone is in the “right seat” — meaning they fit the specific role on your Accountability Chart. The three questions are binary yes-or-no:

• Get it: Do they truly understand the role — the responsibilities, the challenges, the way it connects to the rest of the organization? Someone who “gets it” grasps not just the job description but the deeper purpose of the seat.
• Want it: Do they genuinely want to do this work? Not just for the paycheck, not just because it is a stepping stone, but because the day-to-day reality of the role energizes them.
• Capacity to do it: Do they have the intellectual, physical, emotional, and time capacity to perform the role at a high level? Capacity is the most misunderstood element — it includes skills and experience, but also the mental and emotional bandwidth to handle the seat's demands.

Together, the People Analyzer and GWC answer the fundamental EOS question: Is this person the right person in the right seat? The problem is when that question gets asked. Most EOS companies ask it retrospectively. The real leverage is asking it before someone ever joins the team.

Why Most EOS Companies Use These Tools Backward

Here is the pattern we see in almost every EOS company that comes to us frustrated with their hiring outcomes:

1. They hire someone based on a traditional process — resume review, unstructured interviews, gut feel, maybe a skills test.
2. At the 90-day mark or the first quarterly conversation, they run the People Analyzer and realize the new hire is a minus on one or two core values.
3. They run GWC and discover the person does not actually “want it” or lacks the capacity for a key aspect of the role.
4. Now they have an uncomfortable conversation, a performance improvement plan, or a termination — all within the first year.

This is like building a house without blueprints and then hiring an inspector to tell you everything that is wrong. The inspection tools are excellent. The sequencing is backward. The People Analyzer and GWC should be your blueprints, not your post-mortem.

The Integrators and Visionaries we work with often say the same thing: “We're disciplined about everything in EOS except hiring.” They have L10 meetings running like clockwork, rocks getting done every quarter, scorecards with measurable targets — but when it is time to fill a seat, they revert to the same ad hoc process they used before EOS. The People Component deserves the same rigor as the other five components.

How to Build a Hiring Scorecard Around Your Core Values

The People Analyzer is a scorecard. It just was not designed for candidates. Here is how to adapt it:

Step 1: Define What Each Core Value Looks Like in an Interview

Your core values probably have meaning to your team, but that meaning needs to be translated into observable behaviors that a candidate can demonstrate in a conversation. For every core value, write two to three behavioral indicators — specific things a candidate might say or describe that signal alignment.

For example, if one of your core values is “Own It,” your behavioral indicators might be:

• Describes past failures by leading with their own contribution before external factors.
• Gives examples of proactively solving problems without being asked.
• Shows discomfort with ambiguity by creating structure, not by escalating.

Do this for each core value. If you cannot define behavioral indicators for a value, the value is too abstract to hire against — and that is worth knowing, because it means it is probably too abstract to manage against as well. See our guide to hiring for core values for detailed questions and scoring rubrics for the most common EOS values.

Step 2: Write Interview Questions That Surface Each Value

For each core value, prepare two to three behavioral interview questions. These should be open-ended and ask for specific past examples. The formula is simple: “Tell me about a time when...” followed by a scenario that would require the value in question.

For “Own It”:

• “Tell me about a project that did not go as planned. Walk me through what happened and what you did.”
• “Describe a time when you noticed a problem that was not your responsibility. What did you do?”

For “Growth Mindset”:

• “What is the most significant professional skill you have developed in the last two years, and how did you go about learning it?”
• “Tell me about feedback you received that was hard to hear. What did you do with it?”

Step 3: Use the +/+−/− Scale in Your Evaluation

After the interview, each interviewer rates the candidate on each core value using the same People Analyzer scale they already know:

• Plus (+): Clear evidence of alignment. The candidate gave specific examples that demonstrate the value.
• Plus/minus (+/−): Mixed signals. Some evidence, but also some concerns. The candidate may have given vague answers or described behavior that only partially aligns.
• Minus (−): Evidence of misalignment. The candidate described behavior inconsistent with the value, or could not provide any relevant examples.

Apply the same bar: mostly plusses, no minuses. If a candidate is a minus on any core value, they are not the right person. Full stop. The consistency between how you evaluate your current team and how you evaluate candidates is what makes this system powerful.

How to Evaluate GWC Before the Hire

GWC is trickier in a hiring context because you are evaluating someone's fit for a seat they have not occupied yet. But GWC is still the right framework — you just need different evidence sources.

Evaluating “Get It”

“Get it” means the candidate understands the role at a level deeper than the job description. To evaluate this in an interview:

• Share your Accountability Chart description for the seat — not just the title, but the five key roles and responsibilities. Ask the candidate to restate them in their own words and describe how they connect to the rest of the organization.
• Ask: “What do you think the hardest part of this role will be?” Candidates who “get it” will identify the real challenges, not the surface-level ones.
• Present a realistic scenario from the role and ask them to walk you through how they would approach it. Their reasoning reveals whether they understand the role's nuances.

Evaluating “Want It”

“Want it” is the most deceptive element to evaluate because every candidate in an interview will express enthusiasm. The key is to probe beneath the surface:

• Describe the parts of the role that are tedious, unglamorous, or stressful — and watch their reaction. Genuine interest in a role includes acceptance of its downsides. If a candidate only lights up for the exciting parts, they do not truly “want it.”
• Ask: “What would make you not want this job?” This counterintuitive question reveals self-awareness. Candidates who have thoughtfully considered what they do not want are more likely to have genuinely chosen what they do want.
• Look at their career pattern. Do their past roles show a trajectory toward this type of work, or is this a detour? Consistent direction is evidence of “want it.”

Evaluating “Capacity to Do It”

Capacity is the most straightforward of the three, but only if you evaluate all four dimensions:

• Intellectual capacity: Can they solve the types of problems this role requires? Skills assessments and case questions address this directly.
• Physical capacity: For roles with physical demands, this is straightforward. For office roles, it is about energy and stamina for the workload.
• Emotional capacity: Can they handle the stress, interpersonal dynamics, and emotional labor of the role? A customer service manager needs different emotional capacity than a data analyst. Reference checks are the best source for this dimension.
• Time capacity: Do they have the bandwidth to commit to this role fully? This includes outside commitments, commute, and life circumstances. A direct conversation is appropriate here.

Common Mistakes EOS Companies Make in Hiring

After working with many EOS-driven companies, we see the same mistakes repeatedly. Naming them is the first step to avoiding them.

Mistake 1: Treating GWC as Binary Only for Employees, Not Candidates

In EOS, GWC is yes or no. There is no “kind of gets it.” But in interviews, companies often tolerate ambiguity: “I think they get it... they seemed smart.” Apply the same binary standard to candidates. If you are not confident it is a yes, it is a no.

Mistake 2: Hiring for Capacity and Ignoring Want It

Technical roles are especially vulnerable to this. The candidate has the skills and experience, so the company assumes they want the role. Six months later, the developer who is perfectly capable is disengaged because they wanted to build products, not maintain legacy systems. Capacity without “want it” is a ticking clock.

Mistake 3: Not Sharing Your Core Values With Candidates

Some companies treat their core values like proprietary information. The opposite is true: sharing your values early in the process is the best way to attract aligned candidates and let misaligned ones self-select out. Your core values should be on the job posting, in the recruiter screen, and discussed explicitly in the interview.

Mistake 4: Using the Accountability Chart Title Instead of the Five Roles

The Accountability Chart does not use traditional titles for a reason. Each seat is defined by its five key roles/responsibilities. When hiring, evaluate GWC against those five roles, not against a generic job title. “Marketing Manager” means different things at different companies. Your Accountability Chart defines what it means at yours.

Mistake 5: Not Involving the EOS Implementer in Hiring

If you work with an EOS Implementer, involve them in defining the hiring criteria for key seats. They understand your People Component deeply and can help you translate it into interview criteria that your leadership team can execute consistently.

Building an EOS-Aligned Hiring Process

Here is the complete framework, end to end, for an EOS company that wants to hire with the same discipline it brings to L10s and rocks:

1. Before posting the role: Pull the seat from your Accountability Chart. Confirm the five key roles/responsibilities. Confirm your core values with behavioral indicators for each.
2. Job posting: Include your core values and a realistic description of the seat's day-to-day reality. Be honest about the hard parts.
3. Screening: In the phone screen, explicitly ask about alignment with one or two core values and probe “want it” with honest questions about the role's challenges.
4. Assessment: Use a personality or behavioral assessment to add data to the People Analyzer evaluation. Platforms like PersonaScore let you encode your company's core values directly into the assessment criteria, so candidate results are mapped against your specific DNA, not generic personality labels.
5. Structured interview: Two to three questions per core value, plus GWC evaluation questions. Every interviewer scores on the +/+−/− scale for values and yes/no for GWC.
6. Reference check: Ask references about specific values and capacity dimensions. “On a scale of plus, plus-minus, or minus, how would you rate this person on [value]?” People who know the EOS language will engage deeply with this question.
7. Decision: The candidate must clear the People Analyzer bar (mostly plusses, no minuses) and get three yeses on GWC. If either fails, it is a no — regardless of how impressive their resume is.

The People Analyzer in Practice: A Real-World Scenario

Consider a company with five core values: Own It, Grow or Die, Team First, Do What You Say, and Figure It Out. They are hiring a new operations manager. Here is how the People Analyzer scorecard might look after two interviewers evaluate a candidate:

Interviewer A: Own It (+), Grow or Die (+), Team First (+/−), Do What You Say (+), Figure It Out (+).

Interviewer B: Own It (+), Grow or Die (+), Team First (−), Do What You Say (+/−), Figure It Out (+).

The combined result shows a red flag on “Team First” — one interviewer saw mixed signals, the other saw evidence of misalignment. In a traditional interview debrief, this might get buried under “but they were so strong technically.” The People Analyzer makes it visible and non-negotiable. A minus on any core value is a minus. The team discusses the evidence and either confirms or resolves the discrepancy, but the framework prevents the team from ignoring it.

How This Connects to the Broader People Component

Hiring with the People Analyzer and GWC creates a continuous loop. New hires enter the organization already evaluated on your core values and GWC criteria. Their first quarterly conversation uses the same framework. Their annual review uses the same framework. Every quarterly conversation with new hires reinforces the same expectations that were set during the interview.

This continuity is powerful. There is no gap between what is evaluated in the interview and what is expected on the job. The new hire knows from day one exactly what success looks like, because the same criteria that got them hired are the criteria that will be used to evaluate their performance. For EOS companies that are serious about the People Component, this alignment between hiring and evaluation is the missing piece.

Moving From Gut Feel to Data-Driven EOS Hiring

The People Analyzer and GWC are fundamentally data tools. They replace subjective impressions with structured evaluation. But they only work as data tools if you use them consistently and early. Running the People Analyzer for the first time at a quarterly review is like checking the scoreboard after the game is over. Running it during the interview is like having the scoreboard live while you are still making decisions.

For a deeper look at using data to evaluate Right Person/Right Seat, see our companion piece on using data instead of gut feel for RPRS decisions. And if your company's values need sharper definition before you can hire against them, start with our guide on how Company DNA transforms hiring decisions.

This is part of our EOS and Hiring series, which covers how companies running EOS can bring the same discipline to their hiring process that they bring to everything else.