The EOS People Analyzer: How to Evaluate Your Team Objectively
· Zentrix Team
Most founders do not struggle with the idea of evaluating their team. They struggle with making the conversation fair, specific, and useful. Everyone can feel when someone is in the wrong seat, when a core value is being bent, or when a capable person is quietly drowning in a role that no longer fits. The hard part is turning those feelings into a clear decision without turning the process into politics.
That is the job of the EOS People Analyzer. It gives leadership teams a shared language for looking at people decisions through two lenses: values fit and role fit. Done well, it makes the invisible visible. Done poorly, it becomes another spreadsheet everyone avoids because the scores feel arbitrary and the follow-up feels uncomfortable.
This guide is for founders and leadership teams who want to use the People Analyzer honestly without making it cold, punitive, or performative. The point is not to reduce people to scores. The point is to remove ambiguity so leaders can coach, clarify, promote, reposition, or part ways with more integrity.
What the People Analyzer is actually for
The People Analyzer exists because most companies make people decisions too late. A role feels off for months before anyone names it. A values issue gets discussed privately but never directly. A strong performer creates friction and leaders keep excusing the behavior because the numbers look good. A loyal team member gets praised for effort while quietly failing in a seat that requires a different kind of capability.
EOS tries to separate those situations into a practical frame. First, does this person consistently live the company's core values? Second, do they get, want, and have the capacity for the seat they occupy? That sounds simple, but it changes the conversation. Instead of saying someone has a bad attitude, the team can identify which value is not being lived. Instead of saying someone is not strategic enough, the team can ask whether they truly get the role, want the role, and have the capacity to perform it.
A strong People Analyzer conversation should create clarity, not drama. If the output is only a label, the process failed. If the output is a next action, a coaching path, or a seat decision, the tool did its job.
Start with values before performance
The first half of the People Analyzer asks whether each person lives the company's core values. This matters because skills can sometimes be trained, but repeated values friction usually spreads. If one person consistently violates the way your company has agreed to operate, the impact is not contained to their role. It changes what other people believe is tolerated.
The most useful version of this exercise is behavior-based. Do not ask, "Is this person a team player?" Ask, "What did we see in the last quarter that showed ownership, transparency, service, or whatever our values are?" Likewise, do not mark someone down because of a vague impression. Name the pattern. Values scoring should be rooted in observable behavior, not personality preference.
A practical rhythm is to define what plus, plus/minus, and minus mean for each value. Plus means the person regularly demonstrates the value without being prompted. Plus/minus means the person demonstrates it inconsistently or only under certain conditions. Minus means the pattern is clearly out of alignment and needs direct action. The standard should be high, but it should also be consistent across the team.
Founders should be especially careful here. In small companies, values often mirror the founder's instincts. That can be powerful, but it can also become subjective. The People Analyzer works best when the leadership team agrees on the behavioral standard before discussing specific names.
Then evaluate GWC: get it, want it, capacity
Once values fit is clear, EOS asks whether the person is right for the seat through GWC: Get it, Want it, Capacity to do it. These three questions prevent leaders from collapsing every performance issue into one vague judgment.
Get it
A person gets the seat when they understand the nature of the role, the problems it exists to solve, the decisions it owns, and the standards that define success. Someone may be hardworking and intelligent but still not get the seat. They may focus on the wrong priorities, escalate decisions that should be theirs, or miss the strategic context behind the work.
The test for "get it" is not whether the person can repeat the job description. It is whether they naturally see the role the way the business needs it to be seen. A sales leader who only thinks in individual deals may not yet get a seat that requires pipeline systems, coaching cadence, and forecast discipline. An operations leader who solves every problem personally may not get a seat that requires process design and delegation.
Want it
Want it is about genuine desire, not loyalty. Some people can do a job but no longer want the actual seat. They may like the title, compensation, or familiarity, but not the responsibilities. This is common when a company grows and the role changes. The early team member who loved hands-on execution may not want management. The founder who loves product may not want to run weekly accountability meetings. Acknowledging that honestly is healthier than pretending motivation will appear later.
Leaders often avoid this question because it feels personal. It does not have to be. Wanting a seat is not a moral judgment. It is a fit question. When someone does not want the work the business needs from that seat, everyone eventually pays for the mismatch.
Capacity to do it
Capacity is the most sensitive part because it includes skill, experience, emotional bandwidth, judgment, and sometimes raw cognitive horsepower. It asks whether the person can perform the role at the level the business now requires. This does not mean they are not valuable. It means the seat may have outgrown their current capacity, or the company has not given them enough support to grow into it.
Capacity should be evaluated against the future seat, not the old version of the job. A controller who managed finances well at $2 million in revenue may need different systems and leadership capability at $20 million. A department head who managed five people informally may need a different operating rhythm with twenty-five. The question is not, "Have they been loyal?" The question is, "Can they succeed in the seat we actually need now?"
Do not use GWC as a shortcut for avoiding coaching. If the expectation was never clear, if the role changed without explanation, or if the person never received feedback, the first action may be clarification and support, not replacement.
How to run a People Analyzer session
The best People Analyzer sessions are structured, calm, and prepared. They are not casual side conversations squeezed into the end of an L10. People decisions deserve focus because the output can affect careers, morale, and the company's ability to execute.
Start by confirming the list of seats, not just the list of people. If the Accountability Chart is outdated, the People Analyzer will inherit that confusion. Make sure each seat has a clear owner and a clear set of responsibilities. Then evaluate the person in relation to that seat. This distinction matters because a person can be right for the company and wrong for a specific seat.
Next, review the values definitions and scoring standard. Leadership teams often discover that they have been using the same values words differently. One leader may treat directness as a sign of ownership while another sees the same behavior as a lack of humility. Aligning on examples before scoring prevents the conversation from drifting into personal style debates.
Then work through each person one at a time. For values, ask for evidence. For GWC, ask what the role requires and what the person is consistently demonstrating. Capture disagreements, but do not let the loudest voice settle the score. If the leadership team cannot agree, that itself is useful data. It may mean the standard is unclear, the feedback history is thin, or different leaders are seeing different parts of the person's work.
Finally, assign a next action. This is the step teams skip most often. A People Analyzer with no follow-up is just documentation of discomfort. Each yellow or red area should translate into a conversation, coaching plan, seat review, hiring need, or timeline for a decision.
What to do with the results
The output of the People Analyzer usually falls into four practical categories. First, right person, right seat. These people live the values and fit the role. Your job is to retain them, develop them, and make sure they have enough clarity and support to keep winning.
Second, right person, wrong seat. These people fit the culture but do not fit the current role. This is where founders often find hidden opportunity. A person may be struggling because the seat demands something they do not naturally bring, while another seat would let them contribute at a higher level. The right move may be repositioning, redesigning responsibilities, or creating a transition plan.
Third, wrong person, right seat capability. These people can do the job but consistently violate the company's values. This is one of the hardest calls because performance can disguise damage. If leaders tolerate values misalignment from high performers, they teach the rest of the company that values are optional when numbers are strong. That tradeoff gets expensive over time.
Fourth, wrong person, wrong seat. These situations need direct action. That does not mean careless action. It means the company should stop letting ambiguity stretch indefinitely. The respectful path is clarity, documentation, a direct conversation, and a decision timeline.
The People Analyzer is most humane when it is used early. Early clarity gives people a chance to improve, move seats, or make informed choices before frustration hardens on both sides.
How to have the hard conversation
A People Analyzer score should never be the first time someone hears feedback. If it is, the leadership team has a feedback problem. The conversation should connect to patterns the person already has some awareness of, or at least to expectations that were clearly communicated.
Start with the role and the standard. For example: "This seat now requires a weekly metrics rhythm, proactive issue escalation, and coaching the team without me stepping in." Then describe the observed gap. Keep it factual. Avoid diagnosing motives. Instead of saying, "You do not care about accountability," say, "The last three scorecards were incomplete, and two customer issues reached the L10 without a proposed owner."
Then ask for their view. People often reveal whether the issue is clarity, desire, capacity, or constraints outside the role. Maybe they did not understand the standard. Maybe they want a different kind of work. Maybe they are overloaded. Maybe they disagree with the direction. The response helps leaders choose the next action.
Close with a specific path. That may be a thirty-day coaching plan, a revised seat description, a training commitment, a transition discussion, or a decision date. The key is to avoid ending with vague encouragement. "Do better" is not a plan. "Here are the three outcomes we need by July 31, and here is how we will review them every Friday" is a plan.
Common mistakes to avoid
The first mistake is scoring in isolation. If one leader privately fills out the People Analyzer and announces conclusions, the team loses the benefit of shared perspective. EOS is designed to create leadership team alignment. Use the tool together for the people and seats that matter most.
The second mistake is confusing likability with values fit. A person can be warm, loyal, and enjoyable while still not living a value that matters to the business. The reverse can also happen: someone may have a direct style that is not everyone's preference but consistently demonstrates ownership, discipline, and customer commitment.
The third mistake is postponing decisions because the person has history with the company. History deserves respect, but it does not remove the responsibility to build the team the business needs now. In fact, loyal people deserve honest clarity sooner, not later.
The fourth mistake is treating the tool as a termination mechanism. If everyone associates the People Analyzer with someone being pushed out, leaders will avoid it and employees will fear it. It should also be used to identify development paths, succession opportunities, and seats where strong people can thrive.
How software can make the process less political
A spreadsheet can capture scores, but it rarely preserves the context around those scores. Over time, leaders forget why a plus/minus was assigned, what coaching commitment was made, or whether the issue improved. That is where the People Analyzer becomes fragile. The data exists, but the operating rhythm around it does not.
A better system connects people decisions to the rest of the EOS cadence. Values concerns should connect to issues and follow-ups. Seat clarity should connect to the Accountability Chart. Coaching actions should become owned tasks. Quarterly reviews should show whether the pattern changed. When this information lives in one place, the People Analyzer becomes part of leadership execution instead of a once-a-quarter document.
Zentrix OS is built for teams that want that connection. The goal is not to automate judgment. People decisions still require leadership, courage, and context. The value of software is that it keeps the evidence, commitments, and follow-through visible so the team does not rely on memory or hallway conversations.
A healthier way to think about right people, right seats
Right people, right seats is easy to say and hard to practice because it touches identity, loyalty, and fear. Founders often wait too long because they care about their people. Leadership teams often soften the language because they want to avoid conflict. But lack of clarity is not kindness. It leaves strong people unsupported, struggling people confused, and the rest of the team wondering whether the standards are real.
The People Analyzer works when it turns private concern into shared clarity and shared clarity into action. Use it with evidence. Use it with humility. Use it before frustration becomes resentment. And always remember that the purpose is not to judge people from a distance. The purpose is to build a team where expectations are clear, values are real, and every person has the best possible chance to succeed in the right seat.
Make EOS easier to run every week
Zentrix OS connects vision, Rocks, scorecards, issues, meetings, and follow-through in one operating workspace.
Explore Zentrix OS