Do You Actually Know What Your Team Can Do?

Most managers think they do. They have training records, completion rates, maybe a quiz score or two. But if someone asked you right now which people on your team could handle a situation confidently, and which ones would struggle - could you answer that?

For most teams, the honest answer is no.

This guide covers the main approaches to understanding your team's actual capability, what each one tells you, and which is worth your time.

---

The Problem With Asking People How Good They Are

The instinct is to ask. A quick survey, a self-rating, a form at the end of onboarding. It feels like data.

The problem is that people are consistently poor at accurately judging their own ability - and the gap tends to be biggest where it matters most. Research by Kruger and Dunning (1999) found that people with less knowledge in a domain tend to overestimate their competence, while those with more expertise tend to underestimate it. The same gap in knowledge that causes someone to perform poorly also makes it harder for them to recognise they are performing poorly.

In practice, this means your self-assessment data is probably compressing everyone towards the middle, missing the people who are quietly struggling, and giving you more confidence than you should have.

It is a useful conversation starter. It is not evidence of capability.

---

What Different Approaches Actually Tell You

	Quantitative	Qualitative
What it is	Scores, ratings, multiple choice	Conversations, open responses, demonstrations
What it tells you	Where someone thinks they are	What they can actually do
Speed	Fast	Slower
Reliability	Low for self-report	Higher when well-designed
Best for	Tracking change over time	Understanding where someone actually is

The problem is not using one or the other. It is using quantitative methods to answer qualitative questions.

A completion rate tells you someone sat through something. It does not tell you whether they would handle the real situation well.

---

Surveys vs Conversations

Surveys are easy to send and easy to ignore. People are often filling in surveys repeatedly - fatigue sets in, answers become automatic, and the data becomes less reliable over time.

A conversation takes longer but tells you more. When someone has to explain something in their own words, apply it to a real situation, or respond to a follow-up question, you find out quickly what they actually understand. You can push where something sounds thin. A survey cannot do that.

	Survey	Conversation
Time	5 minutes	10-20 minutes
Depth	Surface level	Contextual
Scalable	Yes	Harder without the right tools
Evidence produced	Completion record	Demonstrated understanding
Gameable	Yes	Much harder
Fatigue risk	High	Lower

---

The Middle Ground

If you need scale but want more than a rating scale, add qualitative questions to your survey. Asking someone to describe a situation where they applied a skill, or explain what they would do in a given scenario, is harder to game and more revealing than a number.

It will not replace a proper conversation. But it is a more honest picture than most teams currently have.

Approach	Best Used When
Rating scale only	Tracking change over time across a large group
Rating scale + open questions	You need scale but want some real insight
Structured conversation	You need to understand individual capability properly
Observed demonstration	Capability needs to be proven, not reported

---

The Question Worth Sitting With

If someone asked you to demonstrate your team's competence tomorrow - not their completion rates, their actual competence - what could you show them?

That is the standard worth designing towards.

See also: The Questions That Tell You If Someone Really Gets It