The ABCD analysis, explained simply

Every people decision in a small company comes down to one question: which bucket is this person in? The ABCD analysis answers it with four letters instead of a scorecard full of numbers — and here it is in plain language, with nothing left out.

Four buckets, and nothing in between

Four is enough for every decision a growing company makes: who is ready for more, who carries the role today, who needs support, and who is in the wrong role. More categories do not make the answer better — they make two managers argue about the same person. A ten-point scale invites a conversation about a seven or an eight. Four buckets invite a decision.

What each bucket means

You define the four categories once, in your own words. From then on every manager reads them the same way.

• A — above the role. The person delivers more than the role asks today, and the evidence is there. An A says the role can grow, not that a promotion is owed.
• B — the role, delivered. The work matches what the role owns. Most of a healthy team sits here, and B is a good answer, not a consolation prize.
• C — partly there. Parts of the role are not met yet. The answer is support, a narrower scope or a clearer boundary — not a warning.
• D — not this role. Even with support, the work does not match what the role needs. That is a statement about fit, and it ends in an honest conversation about a different role.

The definitions matter more than the letters. Written down before the case is on the table, "she is a B" means the same thing in every room. Written down afterwards, it is an opinion — and opinions get re-opened.

The system makes sure it happens

A rating nobody repeats is worth nothing, and this is the part founders underestimate: the analysis is not the hard part, the calendar is. So the system runs the cycle. It reminds you when the next round is due, keeps the notes and the letters on the person, and shows what still has no rating — so a quarter cannot quietly pass without a decision. Ten minutes a week is the whole commitment.

Then it compares with the talent pipeline

This is the part a spreadsheet cannot do. Every letter is read against the pipeline beside it.

• An A and a role that can grow: the pipeline shows which role that person could step into.
• A C or a D: the pipeline shows who is already written down for that role, so a change never starts as a search from zero.
• Where the coverage is thin, the gap is visible before it becomes an emergency.

A category on its own is a description. A category next to a pipeline is a decision.

One example

A Customer Success Lead comes out a B: renewals above target, one boundary crossed. The next action is a boundary conversation, not a document. In the same view, the pipeline shows two names for the role above — the decision and its consequence sit next to each other, on one screen, in one sitting.

That is the whole method. Four buckets, defined by you, kept current by the system, and read against the people you would hire next.