Badge system design can be considered in a variety of ways. I tried to come up with thirteen ways to discuss them so I could write a poem riffing on one of my favorite poems, Thirteen Ways of Looking at a Blackbird (Thirteen Ways of Looking at a Badge System) but I’ve had to settle for
seven eight (see addendum below).
Below you’ll find the seven different possible categorizations listed with a few representations of each type of thinking. This is not an exhaustive list by any means: it’s simply an opportunity to unpack our influences and perceptions as we begin the process of designing badge systems.
The methods outlined below include philosophical, conceptual, pedagogical, visual (aesthetic), technical, categorical, and ownership. The last one, ownership, feels a bit odd because it’s not quite parallel to the rest of the bunch. I like a system that has a nice balance and this one has a slight imbalance. Happily, this slightly odd fit serves to emphasize the importance of allowing for an outlier. The outlier will cause you to reconsider your system every time—and that’s a good thing. The outlier is the thing that keeps your badge system honest, keeps it moving and evolving. Because if you’re designing a system so as to keep everyone within a certain range, you’re trying too hard. And you’re deep in the midst of a lush forest.
In any case, I’m curious to hear your reaction to these potential sorting efforts. No doubt these groupings can intermixed and most certainly they can be layered, possibly interleaved with one another.
- representation: understood vs. hidden
- social acceptance vs. formal acceptance
- intellectual property vs. copyright free
- cognitive surplus vs. waste of time
- extrinsic vs. intrinsic
- carrot vs. stick
- top down vs. bottom up
- systems design vs. emergence
- corporate vs. academic
- amateur vs. professional
- rhythmic vs. erratic
- education vs. learning
- teaching vs. perceiving/absorbing/
- injection vs. osmosis
- project based vs standards based
- expert-taught vs. peer learned & assessed
- representational vs. abstract
- categorical vs. individual
- siloed vs. shared
- open vs. proprietary
- system vs. single
- formalized vs. free for all
- few categories vs. many
- organizational vs. personal
- owned vs. shared
Are there additional ways to consider the design of badge systems? Do any of these seem innate? Far-fetched? What do we gain by sorting through systems in this way? I continue working on questions like these and look for your feedback (which, according to Donella Meadows, is a good way to ensure that your system is running smoothly).
Still, I have to try it.
With apologies to Wallace Stevens
I know noble accents
And lucid, inescapable rhythms;
But I know, too,
That the Open Badge is involved
In what I know.
- – -
May 23, 2012 addendum: Recent thinking points to the fact that these categories exclude content. So now there are 8 ways to sort through badge system design. Some possible representations of that categorization include: language choice; content-driven vs. context-driven; formal vs. informal; system vs. one-off; single language vs. multiple languages; alliterative vs. rhyming vs. allusion-based, etc.