Why we made gap analysis instead of a scorecard

Every performance tool wants to give you a number. A readiness score. A percentage. A star rating out of five. It's an easy thing to build, and it's an even easier thing to put on a dashboard — one glance, and you know where you stand.

We built one of these early on. And then we deleted it.

The number felt true. It wasn't.

Here's the problem with a single readiness score: it's an average, and averages are where information goes to die. Say you're an engineer aiming for a senior promotion, and your tool tells you you're "78% ready." What does that mean? Which 22% is missing? Is it evenly spread across five competencies, or is it one competency at zero and four at 100%?

Those two situations require completely different actions, and a single number can't tell them apart. Worse, it invites a kind of false confidence — 78% feels close, so it feels like small tweaks and time will close the gap on their own. If the real story is "you have zero documented evidence of cross-team leadership," no amount of waiting fixes that. Only doing the thing does.

We watched this play out with our own early users. People would look at a readiness score, nod, and go do more of what they were already doing — because the score didn't tell them what not to keep doing more of.

What a scorecard optimizes for

A scorecard's real strength is reassurance. It's designed to make you feel like the system understands you at a glance, and for a certain kind of casual check-in, that's genuinely useful. But we weren't building a mood check. We were building a tool meant to sit next to an actual promotion packet, an actual review, an actual conversation with a manager about what comes next — and reassurance was the wrong thing to optimize for in that context.

The moment a score gets used to make a real decision, its flattening becomes a liability instead of a convenience. A promotion committee doesn't ask "what's your readiness percentage." They ask "where's your evidence of X." A single number can't answer that question. It was never built to.

Coverage per criterion, instead

So instead of one number, LogPact's gap analysis shows a bar for every competency in your target level's rubric — Technical Depth, Cross-Team Leadership, Mentorship, System Design, Communication, whatever your rubric actually names. Each bar reflects how much documented evidence you have for that specific thing, not a weighted blend of all of them mashed together.

The bars that are short are short for a reason you can act on. Maybe you've genuinely done the mentorship work and never logged it — a five-minute fix. Maybe you haven't done any cross-team leadership yet at all — a much bigger, much more useful thing to know six months before a review than the week before it.

This is a small design choice with a real consequence: it turns "am I ready" into "what specifically am I missing," which is a question you can actually go do something about.

Why this matters beyond one feature

We think a lot of tools in this space — HR platforms especially — default to single scores because a score is what fits cleanly into a dashboard tile, a manager's one-on-one agenda, or a company-wide calibration spreadsheet. That's a legitimate need at the organizational level. But it's a different need than the one an individual has when they're trying to figure out what to actually go do next quarter.

We'd rather show you five honest bars than one reassuring average. The bars are less comfortable to look at. They're also the only version of this feature that tells you the truth.