Badges are shiny little certifications
[Some thoughts following Badge Working Group #2]
A badge – which I think of as a publicly-displayable symbol awarded by a group to an individual as a way to recognize an achievement meeting certain criteria – can be used in a learning context in a few different ways. Gamification is a hot topic right now, but while incentivizing participation can be a powerful tool for engaging learners in non-compulsory learning activities, it needs to be done carefully to avoid substantially undermining intrinsic motivation. Gamification aside, there’s another role for badges in a learning context: When a respected organization publicly recognizes the accomplishments of an individual, this says something about what that individual is capable of doing in the future. Badges can act like mini-certifications, exactly the sort of thing we aim to convey in a resume.
But if we already have grades and degrees on resumes, why would we need badges? Badges tell a different story. Badges identify strengths without focusing on weaknesses, whereas grades average both. Badges are designed to be displayed publicly and proudly, whereas grades are generally read privately and hidden promptly. What about degrees? While the presence of a college degree on a resume can be a signal of qualification to a potential employer, this signal is (a.) slow and binary, (b.) opaque, and (c.) only issuable by a small number of formal educational institutions. In comparison, badges are (a.) designed to recognize finer-grained accomplishments and proficiencies, (b.) make transparent both the criteria for award recognition and the raw evidence of student work meeting these criteria, and (c.) be issuable by any organizations that support learning, inside or outside of the classroom. In short, badges offer a way to make out-of-class learning more relevant by making it more visible. To find out, we have to test this out.
Several learning environments already award badges to recognize accomplishments (e.g. StackOverflow, Grockit, P2PU, Khan Academy), but each one has had to recreate a similar underlying software infrastructure to support this. If we, as a community, think that badge systems are worth exploring and evaluating, we can accelerate this by offering a simple, shared infrastructure that handles basic functionality: issuing, storing, sharing, and displaying. The Mozilla Foundation recently began a badge project and Open Badge Infrastructure to do just this. This could be incredibly useful, but it does hold two risks. First, sharing a single infrastructure may result in the community prematurely settling on one approach to badges before other promising alternatives have really been explored. Second, a software-based framework for badges can’t be leveraged by groups lacking the technical know-how or organizational infrastructure to interface with the framework. One proposed goal raised during the meeting was to build a system in which it is as straightforward to create and issue a badge as it is to receive and display one. When Mozilla’s infrastructure is in place, I’ll set aside some time to create a small website that anyone can use (without writing code) to create one-off badges that flow through the system. Nothing fancy, just functional enough to let anyone who is interested in testing out web-based learning badges within their own community actually be able to try it out.
Is “badge” even the right word? Should we use different words to differentiate between incentivization and certification?