Third quarter in a row. Same name, same +/- on the People Analyzer, same conversation in the parking lot after the session. GWC did its job — it surfaced the question. It just can't answer it: a Capacity "no" is one bit of information about a whole human being.
So the seat conversation stalls, the Issues List processes the same person again, and everyone quietly hopes next quarter reads differently. Before you rewrite the Accountability Chart, there are three questions the grid can't answer — and all three are answerable.
A Capacity "no" doesn't say whether the gap is a trainable skill, a missing kind of energy, or a fit that was never there. Those are three different verdicts with three different moves — coach, redesign, or exit — and the read on how the person is built tells you which one you're looking at.
Run the redraw test: if this seat were split at its hardest handoff, does the +/- disappear? A surprising share of "wrong person" verdicts are wrong-shaped seats — one role demanding two kinds of energy no single human carries.
Write what the seat really demands next to how the person is really built. When both are side by side, the coach-move-exit decision stops being a gut call after the L10 — it's made with data, in daylight, once.
So before you rewrite the chart, read the human. The people layer speaks EOS — ask it anything —
No. The grid stays — it's excellent at surfacing the question. This answers the part the grid can't: whether the person can change, whether it's the seat's shape, and whether to coach, move, or exit — decided with data on how the person is built instead of hallway gut-feel.
Yes — we partner with Implementers regularly. The install rides the client's existing cadence, nothing about the operating system changes, and the Implementer stays the architect of the business while we run the people layer.
Directly. Seats sit next to the read on each person — what they're built for, what drains them — so seat decisions get made with data. Rocks import as priorities, one to one.
Yes. Existing results import; the install completes the stack — StrengthsFinder (CliftonStrengths), DISC, the Enneagram, Working Genius — so the map reads the whole person, not one lens.