GWC: The Three-Question Seat Fit Test Every Leadership Team Needs

You probably have someone on your team right now who you’ve been quietly worried about for six months. They show up. They work hard. They’re a good person. But something about their performance in the role just doesn’t click, and you can’t quite name what it is.

You’ve probably also got the opposite pattern somewhere: a person who clearly has the talent for a seat but is visibly unhappy in it, dragging down their own output and the team around them without anyone saying so out loud.

Both of those situations are seat-fit problems. And both of them get easier to see, talk about, and resolve when a leadership team has a shared framework for diagnosing them. The GWC framework is that framework. Three questions, applied to every seat in the company, that separate a person problem from a seat problem and tell you what to do next.

What GWC Stands For

GWC is short for Get it, Want it, Capacity to do it. It’s a seat-fit diagnostic from the EOS and broader Business Operating System framework, and it’s the fastest assessment tool I’ve found for leadership teams trying to decide whether a person is in the right seat.

For every seat on the company’s Accountability Chart, the person in that seat needs to be a yes on all three:

• Get it: They understand the role. They grasp what the seat is responsible for, why those responsibilities matter, how the role connects to the rest of the business. You can explain the seat once and they mentally pick it up.
• Want it: They genuinely want the role. Not tolerate it. Not do it because it pays well or because they don’t have other options. They come in on Monday ready to do this work, and they don’t flinch at the parts of the role that other people avoid.
• Capacity to do it: They have the time, mental bandwidth, emotional bandwidth, and skill to execute at the standard the seat requires. Capacity is the one people underestimate. A person can get it and want it and still lack the capacity because the role grew past their skill ceiling or because they’re stretched too thin across multiple hats.

All three must be yes. Two out of three is not a pass. A person who gets it and wants it but lacks capacity will burn out or underdeliver. A person with capacity and want but who doesn’t get it will cause friction with the team because they’re solving the wrong problems. A person who gets it and has capacity but doesn’t want it will quietly disengage and take a year of your time before they admit it.

Why Two Out of Three Is the Silent Killer

Most seat-fit problems on leadership teams come down to a two-out-of-three situation that the team has been tolerating for too long because nobody wants to have the conversation.

Here’s the pattern I’ve watched play out repeatedly. A company promotes a strong individual contributor into a leadership role. The person has capacity (they’re talented) and gets it (they were close enough to the work to understand it). But they don’t actually want the leadership work. They want the individual contributor work dressed up in a bigger title. Nobody asks them directly. They accept the role because it pays more and because turning it down feels like a step backward.

Eighteen months later the team is struggling. The person in the new leadership role is still doing individual contributor work in the shadows because that’s the work they actually want. The people who report to them feel un-led. The team’s priorities drift because the leader isn’t actually leading. The founder is frustrated but can’t put their finger on why a clearly smart, talented person is producing mediocre team results.

GWC would have surfaced this at promotion time. A direct conversation using the three questions would have revealed that the person was a yes on Get It and Capacity but a no on Want It. That’s a seat-fit problem, not a talent problem. The right response would have been either a different role (individual contributor + bonus compensation) or a candid development conversation about what the person would need to genuinely want the leadership work.

The Ninety.io platform includes GWC as a built-in field on every seat in the Accountability Chart. Every leader can see the GWC status of every seat in their accountability tree. When used consistently, it forces the team to stop avoiding the conversation.

How to Actually Run GWC on Your Leadership Team

GWC is not a checkbox exercise. It’s a conversation, and the conversation needs structure or it devolves into politics.

Here’s the sequence I use with leadership teams implementing GWC for the first time.

Step 1: Build the Accountability Chart First

You can’t GWC a seat until the seat is clearly defined. Before any GWC conversations, the leadership team needs agreement on what each seat is accountable for. Not a job description. An Accountability Chart with 3 to 5 specific outcome-oriented bullet points per seat. For the pattern, see Right Person Right Seat.

If you can’t write down what the seat is accountable for in 5 bullets, you’re not yet ready to judge fit. The person probably isn’t failing; the seat is probably undefined.

Step 2: Self-Assessment First

Before the leadership team discusses each person, the person does their own GWC assessment. Three questions. Yes or no. Gut-level answers, not politically correct ones.

The self-assessment changes the dynamic. Instead of the team talking about a person, the team is talking WITH the person about their own read on fit. If they say yes-yes-yes and the team disagrees, that’s a specific, actionable conversation. If they say no on one, you’re already halfway to resolution before anyone else speaks.

Step 3: Team Assessment

Each member of the leadership team then rates each seat’s current occupant on GWC. Yes, no, or question mark. No “mostly” or “kind of” — the whole point is to force a binary judgment, because the ambiguity is where most seat problems hide.

If the team is unanimous yes-yes-yes, move on. If there are any no’s or question marks, that’s an issue that goes on the Issues List for the next quarterly or the next IDS session.

Step 4: The 90-Day Rule

If someone is a no on any of the three, the team commits to one of three outcomes within 90 days:

• Coach them up. Give the person specific, measurable development work to move the no to a yes. Timebox it. If no movement in 90 days, next outcome.
• Move them to a different seat. If they’re a no on Want It for the current role but would be a yes elsewhere, restructure the Accountability Chart. This happens more than founders expect.
• Move them off the team. Sometimes there isn’t a fit available. The conversation is hard but the alternative — another year of mediocre performance and team frustration — is worse for everyone, including the person.

The 90-day constraint is what makes GWC useful instead of decorative. Without it, “we need to talk to Maria about her seat” becomes a recurring item on the Issues List that never gets resolved.

What GWC Looks Like When It Gets It Right

A 75-person services firm ran their first GWC assessment six months into a BOS implementation. The leadership team had been politely avoiding a conversation about one of their Vice Presidents for more than a year. Strong tenure, good person, clearly slipping.

The self-assessment revealed what the team had been circling around. The VP rated themselves yes on Get It, no on Want It, and no on Capacity. The role had grown past what they’d signed up for three years earlier, and they hadn’t felt safe saying so.

The outcome was not the outcome the team had dreaded. It wasn’t a termination. The VP moved into a senior individual contributor role designing the company’s enterprise account strategy, which was the work they actually wanted to do. The company hired a new VP who was a clean yes-yes-yes for the people leadership the seat required. The former VP stayed with the company for another four years, producing some of the best strategic work the firm had ever shipped.

That outcome was available all along. GWC was the forcing function that made the conversation happen.

Signs Your Team Needs GWC Conversations This Quarter

• Your leadership team meetings have a recurring vague discomfort about one specific person that nobody names directly.
• A leader on the team is clearly underperforming but you keep telling yourself they’re “just going through a rough patch.”
• You promoted a strong IC into a leadership seat in the last 18 months and the team dynamic has gotten worse, not better.
• You inherited a leadership team from a previous owner or founder and have not formally re-assessed whether the existing team is right for the current stage of the business.
• The company has grown significantly (say, 30%+ headcount or a major product expansion) in the last year and you haven’t reviewed whether the original leadership team still fits.
• Someone on your team is doing three jobs because the company hasn’t hired fast enough, and their output quality is slipping across all three.

Any two of those and GWC will surface conversations your team has been avoiding.

How to Start GWC This Week

GWC does not require a full Business Operating System implementation to be useful. Here’s the minimum viable path.

1. Print the Accountability Chart. If you don’t have one yet, sketch it. Five seats for a small leadership team, no more than fifteen for a larger one.
2. Next to each seat, write three letters: G, W, C. Leave them blank.
3. Each leader fills out GWC for their own seat first. Yes, no, question mark. One column per letter.
4. At the next leadership meeting, each person reads their self-assessment aloud. The rest of the team reacts. Note every place where the team’s read differs from the self-read.
5. Every divergence goes on the Issues List. Resolve it within 90 days via coaching, seat change, or transition.

Do this once a year, minimum. Quarterly if the company is growing fast or the team has had recent changes. The hard conversations you’ll have in the first round will feel uncomfortable. The fifth-round conversations are 10 minutes and result in real decisions. That muscle is worth building.

Frequently Asked Questions

What’s the difference between GWC and a performance review?

A performance review evaluates outputs against goals. GWC evaluates fit against the role itself. You can have a person hitting their quarterly goals who is still a no on Want It, and GWC surfaces that in a way a performance review never will. They’re complementary tools, not the same tool.

Can someone be a yes on GWC but still underperform?

Yes. GWC is a necessary condition for success in a seat, not a sufficient one. A yes-yes-yes person can still underperform because of external circumstances (a broken process, missing resources, a bad market). But if they’re a no on any of the three, they will underperform regardless of external conditions. GWC is the foundation check.

Who judges GWC — the person, their manager, or the team?

All three. The self-assessment comes first because it’s the most honest signal. The manager’s assessment comes next because they have visibility into day-to-day work. The team’s collective read comes last and often reveals patterns the manager missed. Any significant divergence is a conversation, not a verdict.

Does GWC work for roles below the leadership team?

Yes, but it’s most valuable at the leadership team level because that’s where seat-fit problems cascade. A mismatched IC might underperform for a year. A mismatched VP can slow an entire department for the same year. Start GWC with the top 5 to 15 seats, then cascade it down as you mature.

How is GWC different from just “hire the right people”?

GWC applies to the people already on your team, not just future hires. Every founder can hire well some of the time. The question is what you do with the person who was the right hire three years ago and no longer is, or the person who was the right hire for version one of the company but not version three. “Hire the right people” is aspirational. GWC is the maintenance discipline that keeps the existing team honest about fit as the company changes.