Monday, October 21, 2013

BadgeKit: An Invitation to Innovation

Have you ever read an article, listened to a podcast or heard a speech that motivated you to perform some kind of action - only to realize that action was really difficult to accomplish? Well, that's kinda what's been going on for many people who try to implement a badge system or even something as basic as attempt to issue a badge to a single person. Often times, people are so inspired by the movement of badges that they take the next step and attempt to do something in their community to make badging real. This is fantastic - because Open Badges is both a social and technological movement. However, if the barrier to entry is so high - then we are making it difficult for those movers and shakers to, well you know, move. This common user experience helped us to identify an opportunity to design tools that make it easy as pie to dive into badging. The response to this is what we are calling BadgeKit. 


postcard

We are even making these postcards to announce this.


An Invitation to Innovation

BadgeKit will not only make it simple to get started with badging, but it also will provide lightweight, modular and open options for the community of badgemakers. So now that I have your curiosity, I want to gain your attention. We are framing badgekit around a set of action verbs. Each verb represents an invitation to innovation around defining and refining the user experience for the particular action that the user is attempting to do.  Here are the verbs: Build, Assess, Issue, Collect, Share, Discover and Use. You can read what Sunny Lee wrote more about the verbs here.

BadgeKit evolved out of several years of work in this field as well as LOTS of user testing and research. Our initial goal will be to develop proofs of concept for experiences for each of the actions. In order to develop a vision for this work, I looked at the work that we have been doing for the Chicago Summer of Learning, the Connected Educators Month and for the Mozilla Summit. Each project helped us to produce some great open source solutions for distinct badging experience ranging in size from one badge to thousands of badges being issued. With each project, we user tested, got feedback and iterated - so just think of BadgeKit as our next big iteration on our offering. If you are familiar with the tools that we currently offer through openbadges.org - it might be easier for you to digest this information through recipes.





What makes something "Badgeriffic"?

So now you know - what we are building and a little bit of why - but let me tell you a bit about how we are building it.  As a team of Mozilla and community designers, developers and people who have tried spinning up our own instance of badges - we have been trying to find our voice. Specifically, we asked ourselves "What makes something Badgeriffic?" Over the years we've had a hunch about what the answer is and over the past few weeks, I've done a bunch of initial exercises to help us to start to identify what our design values are. Even as I write this post, I don't have a definitive answer, but I am going to share with you our current thinking and ask you to give me some feedback and thoughts about what you value. 

We kicked this off with a virtual sticky note activity:


After people filled in what they thought made something "Badgeriffic," we clustered like-minded notes and came up with overall statements that we are calling values. Values give us a chance to say, "we did all of these things so we feel that ethically and aesthetically, this is a product that we can stand behind".  So, what I am starting to believe is that our values are aligning perfectly with the
Firefox Design Values


This makes sense because well, we are one Mozilla - and behind all of our work we have that heart connection that motivates us to work for a non-profit and we want to build things that make the web better.  On a high level, the BadgeKit offering will help to shape environments, build products, empower communities as well as teach and learn: the four pillars of our work at Mozilla that our Chief Lizard Wrangler Mitchell Baker recently presented at the Mozilla Summit.

In the next few weeks there will be an announcement about this work and we will be working on the action verbs proof of concept. In the meantime,  I would like your help: what do you value and what makes something "Badgeriffic" to you?

2 comments:

Emily Goligoski said...

Thanks Jess.

If you have thoughts to share, we'd love to know what you'd like to see included in BadgeKit! What serves your work? What is most critically important? Thoughts can be quickly shared here: http://bit.ly/1eXk8JG

Dagza said...

This is perfect timing! Well, actually if it had been announced 2 days ago it would have been even better timing as then I wouldn’t have lost a weekend to it ;-) but I feel my trials and tribulations with Open Badges, which I have started to document at http://digitaltumbleweed.wordpress.com , have helped me understand the process far deeper than if I had a set of simple tools. Don’t get me wrong - bring on the tools!

The introduction of technology should make it easier to carry around and keep your achievements and recognitions with you for the rest of your life. Our spare bedroom is full of the children’s certificates. 12 years ago the spare bedroom was full of vinyl. Open Badges is to certificates what the iPod was to Long Players and that is a good thing.

The problem is that when this whole process becomes easier issuers may start to throw them about like they are going out of fashion and this will reduce them to a novelty item rather than an item of value. The only way to prevent this is for learners to have the opportunity to receive badges from multiple sources. I can see some sources being more credible issuers than others - the same way it is with traditional qualifications.

For something to be badgeriffic it has to go beyond the technology and have intrinsic value to the learner. There is some value in using digital badges as an acknowledgement (present at an event). There is more value in using them as a carrot at the end of a stick (if you do what I want you to do I will give you a badge) but for something to be badgeriffic it has to be recognition of the learner achieving something monumental. That achievement could be subjective and probably has to be progressive.

I’m going to start introducing ‘present’ badges first at work as this is the would be the easiest concept for the learners to buy in to initially and I can link that with ‘carrot’ badges such as ‘attended 5 homework clubs’; I intend to very quickly move towards progressive subject based (computing) badges, probably based upon the Bloom’s taxonomy. I’m also going to be firm but fair when it comes to handing them out :-)