Competency-Based Progression

¶The claim

Advancement should be based on what a person can demonstrably do, not on how long they have spent in training. This principle — obvious once stated — contradicts the dominant model of education, where progression is gated by semesters, credit hours, and seat time. Competency-based progression replaces the question “have they done enough time?” with “can they do the thing?”

¶The problem with time-based advancement

Most educational systems advance learners by time. Complete four years, receive a degree. Attend sixteen weeks, pass the final, move to the next course. This conflates exposure with competence. A student who mastered the material in week six and a student who never mastered it at all both advance at the same moment — the end of the semester.

Time-based systems emerged from institutional convenience, not learning theory. Carnegie units (1906) standardized the credit hour to make high school transcripts comparable across institutions. The unit measured contact time: one hour of instruction per week for one academic year. It said nothing about what the student learned. A century later, most educational credentialing still runs on this infrastructure.

The consequence is that credentials certify exposure rather than competence. A degree in engineering certifies that someone sat through engineering courses for four years. Whether they can engineer anything is a separate question, answered by professional licensure exams, portfolio reviews, or on-the-job performance — all of which are competency-based.

¶Bloom: mastery as the norm, not the exception

Benjamin Bloom’s “Learning for Mastery” (1968) challenged the assumption that ability follows a bell curve. Bloom argued that most students can master most material if given sufficient time and appropriate instruction. The bell curve of achievement reflects variation in learning speed, not variation in capacity. In conventional classrooms, time is fixed and achievement varies. Bloom proposed inverting this: fix the achievement standard and let time vary.

This is mastery learning. The learner works on a unit until they demonstrate mastery — defined by a specific performance criterion — before advancing. Slower learners take more time; faster learners move ahead. The result, Bloom claimed, is that the distribution of achievement narrows dramatically: most learners reach mastery, and the bell curve flattens.

Bloom’s earlier Taxonomy of Educational Objectives (1956) provided the vocabulary for specifying what mastery looks like. The taxonomy arranges cognitive operations in increasing complexity: remember, understand, apply, analyze, evaluate, create. A mastery criterion pegged to “remember” (recite the definition) is very different from one pegged to “evaluate” (assess whether a given design meets requirements). The taxonomy does not prescribe which level is appropriate — that depends on the domain and the role — but it makes the choice explicit.

¶Constructive alignment: connecting objectives, activities, and assessment

John Biggs’ principle of constructive alignment (1996) ties competency-based thinking into a coherent design framework. The idea: learning objectives, teaching activities, and assessment tasks should all target the same competency at the same level of complexity.

Misalignment is common. A course might state the objective “students will be able to design distributed systems,” conduct lectures about distributed systems theory, and assess with a multiple-choice exam testing recall of terminology. The objective is at the “create” level, the teaching is passive, and the assessment tests “remember.” No amount of passing that exam demonstrates the stated competency.

Constructive alignment demands that if the objective is “design a distributed system,” the assessment must require designing a distributed system, and the teaching activities must involve practice in designing distributed systems. This is backward design — Ralph Tyler’s (1949) insight that curriculum starts with objectives and works backward to activities — made rigorous.

¶Professional certification as competency-based progression

Professional certification bodies have long practiced competency-based progression, even as academic institutions resisted it. A licensed electrician must demonstrate specific competencies. A board-certified surgeon must perform procedures under observation. A certified public accountant must pass examinations that test application, not recall.

These systems share a structure:

1. Competency standards — explicit statements of what the practitioner must be able to do, at what level of complexity, under what conditions.
2. Evidence requirements — what counts as demonstration. Typically: observed performance, portfolio of work, structured examination, or some combination.
3. Independence from time — a candidate who can demonstrate competence in six months is certified in six months. One who needs three years takes three years.
4. Graduated levels — apprentice, journeyman, master; intern, resident, attending; junior, senior, principal. Each level has its own competency standards and evidence requirements.

The guild system that preceded modern professional certification was explicitly competency-based: the apprentice became a journeyman by producing a piece of work that demonstrated competence, not by serving a fixed term.

¶Implementing competency-based progression

A competency-based system requires three things that time-based systems do not:

Clear criteria. Every advancement gate must specify what the learner can do, not what they have experienced. “Completed the networking module” is time-based. “Can diagnose and resolve a DNS resolution failure on a Linux system” is competency-based. The criterion must be specific enough that two independent assessors would agree on whether it has been met.

Valid assessment. The assessment must actually test the competency. If the competency is “can weld a structural joint to code,” the assessment is a welding test, not a written exam about metallurgy. Biggs’ constructive alignment applies: the assessment and the competency must operate at the same level.

Flexible pacing. If advancement is not time-gated, the system must accommodate learners who move at different speeds. This is the hardest institutional challenge — cohort-based scheduling, instructor availability, and administrative systems all assume uniform pacing.

¶Limits

Competency-based progression does not solve the problem of deciding which competencies matter. Bloom’s taxonomy describes cognitive complexity but not importance. A system can be rigorously competency-based and still teach the wrong things. The question of what competencies to require is a question about values, roles, and purposes — not a question that competency frameworks themselves answer.

¶See also

• Backward design — designing from objectives backward
• Curriculum — the structure that organizes progression
• Scaffolding — graduated support during learning
• Zone of proximal development — Vygotsky’s account of readiness