Why Eight Competencies and Not Eighty

Eight competencies are usually enough because the point of a competency framework is not to describe every possible strength, it is to produce usable evidence. A short shared set gives students, faculty, and employers a common language, keeps rating tasks manageable, and makes results comparable across programs and years. Once a framework grows into dozens of items, raters start guessing, skipping, or smoothing answers, and the data become harder to trust.

Why small frameworks work better

A competency framework should help three groups at once: the people being assessed, the people doing the rating, and the people interpreting the results. If the list is too long, all three groups pay the price.

Students need a framework that is specific enough to guide reflection but simple enough to remember. Faculty and employer supervisors need language they can apply in a busy work setting, often with limited direct observation. Assessment staff need results they can aggregate across sections, sites, majors, and terms. A short list of broadly applicable competencies is not a compromise to be avoided, it is often the only version that works at scale.

The eight NACE Career Readiness Competencies are a useful model for that reason. They cover the major skill areas employers regularly expect, but they do not fragment the assessment into dozens of micro-skills that are difficult to rate consistently. A framework with eighty items may look more precise on paper, but precision is not the same as measurement quality.

Rater fatigue is a real measurement problem

Rater fatigue is not a theoretical concern. It shows up when a supervisor is asked to complete a long form after a busy internship cycle, or when a faculty member is rating multiple students at the end of a semester. The longer the instrument, the more likely raters are to use straight-line responses, finish quickly without careful differentiation, or stop halfway through if the form is optional.

That matters because weak ratings are not just noisy, they can be systematically biased. Supervisors tend to rate generous students more favorably, students with more visible tasks more highly, or everyone in the middle of the scale when the form feels burdensome. When a framework is concise, raters are more likely to complete it fully and apply the same standard across students.

There is also a practical ceiling on attention. If a supervisor can comfortably distinguish eight domains, they may be able to give thoughtful feedback. If they are asked to judge eighty, many will collapse them into the same few impressions, which defeats the purpose of a detailed framework.

Comparability is one of the main reasons to standardize

Cross-institution comparability is hard to achieve if every college invents its own competency list. One institution may label teamwork, collaboration, and interpersonal effectiveness as separate competencies. Another may fold them into a single category. A third may define communication so broadly that it includes writing, presenting, listening, and professional etiquette. The result is not richness, it is incompatibility.

A shared framework makes it possible to compare results across programs, student groups, and years without spending weeks translating categories. That matters for accreditation reporting, program review, and institutional benchmarking. If you want to know whether engineering students are stronger in teamwork than business students, or whether sophomores improve after internship placement, you need the same definitions from one setting to the next.

A small shared framework also helps faculty and employers become better raters over time. When the same eight competencies appear in multiple courses or placements, people learn what each one means in practice. That consistency improves reliability more than a larger, bespoke framework ever will.

When a custom competency is warranted

A custom competency is justified when the work itself creates a skill requirement that a shared framework does not capture well enough. The test is not whether the competency sounds important. The test is whether leaving it out would hide a meaningful part of student performance or create a blind spot in supervision.

A nursing program may need a competency tied to patient safety protocols. An aviation program may need one tied to regulatory compliance and checklist discipline. A music conservatory may need one tied to ensemble performance, because the standard interpersonal categories do not describe the actual setting. In those cases, a custom competency can be appropriate if it is concrete, observable, and tied to the program’s outcomes.

The key is restraint. Add a custom competency when all three of these are true:

1. It represents a distinct performance area

If it can be evaluated adequately inside an existing competency, do not split it out. “Professional communication” may already cover much of what some programs want to call “client readiness” or “stakeholder engagement.”

2. Supervisors can observe it reliably

If raters cannot see the behavior, they will infer it from unrelated cues. That weakens validity. A custom competency should be visible in the setting where the assessment happens.

3. It will be used in decisions or improvement planning

If the competency will not affect coaching, curriculum revision, or reporting, it is usually just extra noise. Every added item should earn its place.

What to avoid when building a framework

The most common mistake is to create a list that reflects organizational preferences instead of measurable behavior. Competencies like “initiative” and “leadership” are often useful. Competencies like “being a good university citizen” are too vague to rate consistently.

Another mistake is over-splitting related skills. If teamwork, collaboration, conflict management, and relationship building all appear as separate items, raters will struggle to tell them apart. Students will also receive fragmented feedback that is hard to act on.

A third mistake is treating the framework as fixed forever. A shared core should stay stable long enough to support trend analysis, but programs can still revise language when the definitions are unclear or when a new field-specific requirement becomes too important to ignore. Stability and refinement are not opposites.

A practical rule for choosing the number

Start with the smallest set that covers the major outcomes you need to assess, usually six to ten competencies. If a proposed addition does not improve a decision, clarify a known gap, or reflect a truly distinct skill area, leave it out.

That rule is conservative on purpose. Most institutions do not have a data problem because they are missing enough categories. They have a data problem because they have too many categories, too little rater time, and definitions that no one can apply consistently.

A compact shared framework is not less serious than a custom one. It is often more serious because it is built for measurement, not for decoration. If your goal is credible assessment across courses, internships, and student populations, eight well-defined competencies are usually enough. When a program truly needs a ninth, it should be able to explain exactly what the new competency measures, who can observe it, and why the existing framework does not already cover it.