Higher education loves the phrase living document. It sounds healthy, adaptable, modern. But when it comes to credential taxonomies, that phrase can sabotage the very thing a taxonomy is supposed to do: make meaning stable enough to travel.
A credentials taxonomy that only exists as “the latest version” is a memory hole. It collapses your past decisions into your present labels, and then asks everyone else to pretend the meaning was always obvious.
And in digital credentials, meaning feels seldom obvious outside of institutional walls.
Taxonomies – as they exist today – feel akin to a band-aid over a broader “last mile” problem. Rob Coyle, of 1EdTech, recently referred to this need as “semantic interoperability” – an intermingling interpretation of credentials’ terminology, taxonomies, and utilization.
Or, plainly: what happens when a learner carries and presents credentials earned from across higher education and industry? How do we make sense of the sociocultural components?
Badges already struggle to communicate meaning outside your campus bubble
One of my in-progress research studies positioned that badges are designed to communicate quickly using consistent visual patterns, like a familiar “information architecture”. That structure helps, but it does not solve the bigger issue: interpretation depends on context that most external viewers do not have. Higher education badge systems often become “siloed ecosystems” shaped by local branding, which can hinder broader adoption and interpretation. As a side-effect, recipients may not understand the taxonomy logic or terminology behind what they are seeing.
Color-based progression cues often depend on seeing badges in sequence. When badges show up as standalone artifacts, that logic becomes ambiguous and requires additional context for accurate interpretation. More directly, interpreting the meaning of those cues may require someone to have a “full view” of the institution’s taxonomy.
So if interpretation already relies on taxonomy context, then your taxonomy itself cannot be a moving target.
The big problem: “living” taxonomies hide evolution
A taxonomy is not just a list of categories. It is your institution’s meaning-making system. When you update it without preserving historical context, you unintentionally:
- Mask internal evolution: yesterday’s credential was issued under a different structure, but the public only sees today’s structure.
- Hinder external interpretation: viewers already need extra context to interpret badge signals; shifting taxonomy definitions makes that gap worse.
- Obfuscate governance and change processes: decisions disappear into silent edits, which makes it harder to explain why something changed later.
If your taxonomy is always “current,” then older credentials become harder to interpret with confidence, because the reference system they depended on has been overwritten.
Higher education is no stranger to evolution. From branding revisions to strategic pivots, from core competencies to micro-credentials, campus organizations already face congruent tailwinds of change.
External impacts
End-user consumption: learners read taxonomies through the badge
Badges serve as high-level representations of achievement and are used in contexts where they are presented, reviewed, or audited at scale. Many badge meaning cues depend on understanding the taxonomy context behind them, especially when badges are viewed alone.
If learners have to carry the explanation in their heads because the taxonomy history is invisible, portability suffers.
Employer utilization: interpretation costs go up fast
Employers, learners, and instructors rely on credential designs to understand and evaluate accomplishments, but local badge ecosystems can become hard to interpret once the credential moves beyond the institution’s boundaries. If your campus credentials taxonomy has no easily accessible digital presence (e.g. a search query away), its meaning is obfuscated from who could use it most.
Every “what does Level 2 mean here?” moment is friction. A versioned taxonomy gives employers a stable reference point for what a credential meant when it was issued.
Ecosystem interoperability: standards help, but history still matters
We’re a long way from a technologically-driven semantic interoperability: machine-actionable taxonomies that support discovery, comparison, and trust for learners and employers, including maintaining and publishing comprehensive skills taxonomies. This kind of categorization, akin to 1EdTech’s CASE standard, underscores the value of assigning unique identifiers so competencies can be aligned across systems.
Publishing a taxonomy is not the same as making it interpretable over time. Versioning is how you keep “what this meant” stable even as “what we do now” evolves.
Internal use-cases
Versioning creates an audit trail of meaning
A versioned taxonomy lets you say: “This credential was issued under taxonomy X.” Without that, you are stuck reconstructing meaning after the fact. Without breadcrumbs to support discovery, each problem to solve becomes a digital archeological dig across emails, messages, documents, and hearsay.
Versioning supports governance and equity conversations
Versioning is not just technical hygiene. It is an equity and trust mechanism, because it makes change traceable rather than implicit.
Versioning reduces internal confusion across teams
Badges serve multiple roles, including signaling achievement and reinforcing institutional branding. Multiple stakeholders end up shaping taxonomy meaning, even indirectly. When the taxonomy shifts without clear versioning, different groups can unintentionally operate off different mental models.
Changing the culture
Here is the simple, practical shift in mindset:
Stop: “Our taxonomy is a living document.”
Start: “Our taxonomy is a versioned public reference with a clear change record.”
And yes, you can still evolve. You just evolve in the open, with traceable releases.
My recommendation, based on semantic versioning (which already works):
- Major changes when you restructure categories or redefine levels (meaning changes) that dramatically change meaning. If backwards compatibility is sacrificed, it is a new major revision.
- Minor changes when you add new items without changing existing definitions. Minor changes position refinement.
- Patch changes when you fix typos or metadata without changing meaning. In patches, you are fixing bugs, mistakes, or errors.
Even if you do nothing else, adopt this baseline habit: preserve snapshots and publish a changelog.
Version it. Publish it. Keep the history.
Because if you do not preserve the evolution, you do not just lose documentation. You lose meaning.