Open Badges Values
We’ve been doing some strategy and planning work for Open Badges and the general badging work, and one thing that became clear was that we have some implicit values and principles that we have carried and/or want to carry with us into the future work.
We decided to write them down and turns out, that process alone was valuable for our strategy work. They have already been useful as a guide on our strategy and a litmus test for possible directions or opportunities. And that’s after just throwing them up on the fly. We want feedback and thoughts so that we can refine and agree on these, and in the process, set a direction that we can all work towards together.
Open Badges Values / Principles:
- Empower the learner. The end game is about helping learners improve their lives, get credit for what they do, and give them the data/ammunition necessary to do the things that they want to do. There are other ways we’ve talked about this - redefining learning, rethinking accreditation, but ultimately its about putting the learner in the driver’s seat.
- Agency. This is similar to the above and is specifically about control. The learner should control their data. They should control the interactions around that data. They should be able to collect and share any badges they want, even “smaller” or social ones that might mean something to them. They should decide who sees badges or what stories they want to tell about themselves (through the badges).
- Open. This is a loaded word, but its important in every meaning of the word. Badges should remain open in that anyone should be able to issue them. Many ask to restrict what can be badged so that its easier to establish equivalencies but that means we are restricting the possibilities for learners. The onus is on us to figure out how to make sense of that data. There should also be tools to support badging that are free and open source. As mentioned before, no proprietary or closed system should control the badges, the learner should. Open, open, open.
- Interoperable. A single badge might carry some value in some contexts, but a group of badges that tell a more complete story about a learner is so much more powerful. Especially when those badges are earned across experiences. This requires that badges be interoperable. This requires that badges align with the open standard. If we can have consensus at that lower level, then anyone can build tools on top of badges to make them more useable, more shareable, more valuable, etc.
- Distributed. We are working towards a more distributed ecosystem of recognition. That means each touchpoint in the ecosystem should be distributed - issuing, validating/endorsing, sharing, using badges, etc. Badges should be and go where the user is, and the badge information and value should follow.
- Credible. We think badges can be the real deal - can lead to real results like jobs and credit and advancement. We need to continually think about what gets badges to these standards without squelching the other features of badges. I have some thoughts on that here.
- Flexible/Innovative. (or “Weird.”) At the same time, we need to “keep digital badges weird”. We shouldn’t force all badges to be a one level or for one particular goal, we should build tools and frameworks to allow for innovative uses for badges.
- Community-driven. The community is gold. We can’t do this alone, you can’t do this alone. We are stronger together and a community that shares resources and findings, vets ideas and builds this stuff together is the community that wins. Our community is the lifeblood of the badges work and we need to codesign our future together. (*hugs!*)
- Something we are proud of. We are those feel-goody people that want to be proud of what we do. This means both not being evil, and also producing high quality stuff. On the former, I think we’re doing pretty well already but there is real risk of closed solutions segmenting or threatening the ecosystem and we should fight against this. On the latter, from the conceptual framework and the whitepapers, to the software and technical framework, to the toolkits and implementations, we want to walk away proud. There is a lot that we are proud of but turns out that this is pretty challenging to do all the time when there are so many moving pieces. But its a standard that we should all hold ourselves to and find ways to get there together.
What are we actively working against?
This list looks like the opposites of all of the above, but a few highlights:
- Data about the learner not for the learner. In our recent offsite, @iamjessklein had a revelation that most, if not all, of the data about learning out there is not for the learner. That’s really broken.
- Spy-ware. There’s a surge of attention around scouring the web to determine things about individuals or ‘score’ them, and then selling that information to employers. The individuals probably have no idea that this is happening. There is certainly some value in some cases, like the one in this recent NYT article, where some unsuspecting individual is rewarded for previous work or interaction with a job offer. But in most cases, its just spying and making decisions about people without giving them a chance to have their say. Badges should be all about giving people their say - letting them tell the story that they want to tell, but in an evidence-based, verified way.
- Replicating accreditation. A centralized system or body for judging or OKing badges would be bad for badges. If we are embracing open and distributed, as I hope we are, we need to find and open and distributed way to build trust and assurance into badges. I’ve written more about this here [referenced above].
- Closed and siloed. If badges do not meet the open standard or are stored in a system that is closed, we lose the real power of the ecosystem. To empower the learners, we need to let them have access to the broader ecosystem, craft their own pathways and write their own stories without predetermining the set they can work from or the constraints they are under.
We have a real opportunity for change and impact with the badges work, but we feel that the values/principles are important pieces for realizing that opportunity. As you can see from the list above, these principles do not define the solutions - there are still a lot of things to answer or figure out, but knowing the guiding principles can in some cases make those answers easy or keep us on course as we start to tackle them.
I’m sure the list is too long - maybe 3-5 is the magic number. Let us know what you think. Comment below or join us on the community call tomorrow to dig in.
The Evolution of Badges, DML-by-DML
The DML conference over the past few years has been a key milestone in the badge work. This year we formally launched the production version of Open Badges and it was awesome. As I was standing on stage announcing the badge work, I looked around the crowd and saw many many familiar faces. It made me reflective (and maybe even a little nostalgic) about the DML experiences over the years and the progress we’ve made together in that timeframe. In fact, if we use the DML Conference as a marker, its easy to see how the badges work has evolved and how far we’ve come:
(I threw in that last one because my team jokes that we can trace the lifetime of badges along with my son’s since they map quite nicely. I don’t know that that means but it makes it easy for me to remember how long I’ve been working on this stuff :)).
Looking through this list, you can see that the conversation around badges has certainly progressed in many ways - we’ve moved from solely badges 101 conversations into meatier topics like badge validation, and we’re now talking to policy folks, school boards, mayor’s, etc. about big implications and potentials of badges. The Open Badges technical work has advanced in that it didn’t exist (or was just in prototype form on Brian’s laptop) in 2011 and now its in 1.0, includes the open standard for badges and already has a significant level of initial adopters (over 700 issuers!). The DML Competition around Badges for Lifelong learning wasn’t conceived of yet in 2011 and now we have 33 grantees all demoing high quality badge systems and tools that will push additional job relevant and credit-worthy badges into the ecosystem. The team has also grown with the increasing momentum and resulting workload. We’ve come a long way.
There are places where we’re still spinning a bit. Mitch’s concerns echoed many of this thoughts last year, although I have to say that this year wasn’t anti-badge, but was more cautionary around ensuring that the badges represent learning and are thoughtfully designed. I’d have to agree with that wholeheartedly and in fact, have lots of ideas that I am going to pull into a separate follow-up blog post later this week. But it’s apparent that we’ve moved past the ‘what if’ on badges and now really need to dig into the ‘now what’. There is a great need for some knowledge sharing, research and toolkits around what ‘good’ badge system design looks like. A lot of this is already in the works, but we’ve got to make sure its accessible and actionable for folks. This has to be a community effort and the most valuable work will come from the people that are closest to the learning and assessment. Carla Casilli has stepped in on our side to help collect and curate this work, as well as put it into practice through our proof of concept badge systems like the City of Chicago and Webmaker.
I’m proud and excited about the progress we’ve made and also fully aware that there is much more work to do. My favorite part of it all goes back to the beginning of this blog post - all those familiar faces in the crowd - we’ve really built/accumulated a tight community - a family, really - of early adopters, advisors, skeptics and thinkers that have helped us get here and will need to help us get even further by next year (wherever that may be, hopefully somewhere warm!)
Open Badges 1.0 Launch
You may have heard but we launched Open Badges 1.0 on Thursday at the DML Conference. Here are some places to read more:
Here’s what 1.0 means to me, pulled from the talk I gave at the announcement on Thursday:
A digital badge is an online representation of a skill you’ve earned.
Open Badges takes that concept further, and allows you to verify your skills, interests and achievements through a credible organization.
And because the system is based on an open standard, you can combine multiple badges from different issuers to tell the complete story of your achievements — both online and off.
Badge earners can display their badges wherever they want them on the web, and share them for employment, education or lifelong learning.
So what does Open Badges 1.0 mean?
Mozilla Open Badges is made up of two things: a technical standard that anyone can follow to make their own Open Badges and free, open source software for issuers and users.
How does it work?
Right now, Open Badges gives enables issuers to issue verified, open badges and connect their users into this broader learning ecosystem.
It also gives users a way to collect, combine, and share their badges.
Finally, every badge is full of information: employers and others can dig into the rich data behind each badge and see who issued it, how it was earned, and even review the projects the user completed to earn the badge.
Let me walk you through the process of issuing, earning, and sharing a badge.
This is the badge backpack, where you collect and manage your badges.
So to begin, users can create a backpack with just an e-mail
Here’s an image of an empty backpack - eventually we will have links out to possible badges to earn or things to learn here. For now, let’s show you how we earn and collect a badge. We’ll use a Mozilla Webmaker badge as an example.
Here our user is making a web page with Webmaker. On the upper right you see that they’ve been awarded a badge for the skills they’ve applied while making the project. This is a good place to remind ourselves that badges are just recognizers on top of the learning and assessment - that is the meat behind the badge. In this example, a learner is learning HTML and CSS Basics while they are building a webpage and earning badges in the process.
The user then sees detail of the badge, and can accept it and add it to their backpack.
Now the badge has been added to the backpack.
Earners will be able to organize their badges into different collections
They can then create a public-facing portfolio page with their badges, and add notes about what they’ve earned
You can also share your badges on social media. Clicking the Twitter link brings up a box to write and send your tweet.
And there it is in our user’s twitter timeline.
A plug-in for Wordpress built by a community member also allows you to display your badges right on your blog. There is much more to come here as well in the next few months.
All of this is powered by free and open source software that anyone can use. And Open Badges sets a technical standard that any issuer can follow, which means their badges can connect to and add up to more substantial recognition and opportunity.
Why does this matter?
We think Open Badges will change how people think about recognition and achievement — from traditional institutions to leading organizations — and connect lifelong learning to real results like jobs and additional opportunities.
On the jobs front, we’ve talked to many employers, and they all say the same thing: undergraduate degrees are a check box, but they tell you very little about the skills that the particular person possesses; resumes are difficult to verify; and it is almost impossible to get an understanding of a candidate’s social or ‘softer’ skills.
Open Badges changes that, and gives us a way to tell a more complete story about who a candidate is, and what they bring to the table.
We are formally launching 1.0 but there are already hundreds of organizations working with Open Badges today - there are 600 orgs issuing badges and even more moving in that direction. Potential badge earners can now look for this symbol, which they’ll begin to display on their sites in the coming weeks.
And there’s lots more to come with new features, more social integration (Fb), more tools for issuing, new partners, and new ways to earn badges. We’re here to continue the conversation and collaboration, and build the ecosystem around Open Badges.
I want to give a HUGE shout out to the Open Badges team, which is still a pretty small, scrappy team. These folks get up everyday believing in this stuff and trying to change the world and I am so lucky to work with them. This was a herculean effort, and I can’t thank them enough.
I also want to thank our communications team which pulled out all of the stops to add the polish to our work and get the word out broadly.
Thanks as well go to MacArthur for the funding which is obviously important, but for also being an inspired thought partner on all of this work.
And last but certainly not least, we have to whole heartedly thank our community who works with us side by side to build and iterate on Open Badges. Through community calls, the mailing list and other channels, our community vets everything that we do and contributes to the broader conversation on a daily basis. They are also the ones developing high quality badges - we couldn’t do this or be to this point without them.
I look forward to your questions and feedback. I hope you’re as excited as we are to challenge our outdated ideas about what should “count” toward education, and empower people to create their own paths to success.
A couple quotes to leave you with
With Open Badges, you don’t have to just tell the world about how awesome you are—-you can prove it. (me :))
The more incidences of an “unaffiliated” (term used loosely) third-party creating web standards for credential sharing…the better off education will be. No two ways about it. (Techcrunch)
An Open, Distributed System for Badge Validation
We’ve released a request for comments on a proposal for badge validation, specifically, an open, distributed system for badge validation.
Here’s the direct link to the paper: http://bit.ly/badgevalidation
Here’s some extra commentary for all of you blog-loving folks:
There have been a lot of people that have claimed that badges could replace degrees. That collections of badges could serve as legitimate portfolios or pathways that tell the same story as a degree, and in fact tell a much more in depth story given that we can use badges to capture more granular learning and each badge is evidence-based. I get asked a lot if I believe that badges will replace degrees and it’s a tough question. It’s not what we are setting out to do necessarily, the use case for badges in informal learning spaces is a primary one since that learning is not currently recognized. But I know I do believe in the utopia where learners can craft their own paths across the many learning opportunities available - especially those that are free and accessible. Where on-the-job experience counts for you in a real way. Where all of the learning and experiences in your lifetime are connected and stitched together around your identity or identities. Degrees definitely do no do this for you, but badges could.
I guess I don’t really think degrees will go away anytime soon, but I do think that its possible for badges to function at that level for people. But in order to do so, we need some way to validate the learning behind the badge - to ensure it represents what it says it does. Another way to think about this is, we need to accredit badge issuers.
But remember that the point of badges is an open credentialing system. We want there to be lots of issuers of all shapes and sizes. We learners to earn badges across many different issuers and experiences. The one benefit of a monopoly - which formal education currently has on credentialing - is that you can super tightly control it. You can validate the learning from the top down and put the rubber stamps in the hands of a small group of people. This won’t work for badges, so how can we validate badges?
The proposal we have released relies on a similar model to current accreditation - standards, evaluation and evidence - but each piece is open and distributed instead of closed and top-down. It includes a set of technical requirements, as well as social requirements that cover:
- Standards - encouraging badge issuers to align with open standards or competency frameworks and store that information in the badge metadata.
- Endorsements (Evaluation) - allow third parties to review badges and sign them, or endorse the badge. This information then lives with that badge as additional valuation data.
- Reporting and Analytics (Evidence) - ways to view usage and consumption data of badges so that we see which badges are getting which jobs, which standards are most used or accepted, etc. Surfacing those badges/standards/issuers that are bubbling to the top .
The goal is to create a highly efficient and effective way of validating, valuing and comparing badges.
It might all come together like this:
Diagrams: All of the standards, endorsement (evaluation) and usage/adoption data (evidence) becomes more information that lives with the badge and travels with it across the web.
Webmaker Badges Roadmap
It’s roadmappin’ time again, folks. I’ve shifted my focus a bit to zero in on making badges a success and that has two pieces:
- Web literacy badges
- The Open Badge Infrastructure and wider badge ecosystem
This roadmap covers the web literacy badges plan for the rest of the year. Look for the OBI roadmap to follow shortly.
WEB LITERACY BADGES
Objective #1: Build the web literacy standard.
I’ve written about this before and done a bunch of thinking about it sense. This is a different spin on the work we’ve done so far to define the skills that we think are the core pieces of being web literate, or having those literacies. The goal is to co-create and maintain a learning standard with a bunch of partners - and then for us all to align to that standard and work together toward this common goal of creating a web literate planet.
We don’t yet know what the ‘product’ for the standard looks like, but we’ll be digging into that more deeply over the next few weeks. If you are interested in learning more, we’re hosting a virtual meeting next Thursday, Feb 7th. Join us!
Objective #2: Build more web literacy badges.
We rolled out the first set of web literacy badges last November through Webmaker, that covered some basic web competencies like HTML and CSS. Obviously, that is a small slice of our vision of web literacy and we want to expand the badge offering to cover more skills - ultimately to provide learning pathways and badges for all of them.
Objective #3: Build assessment pathways.
This is the fuzziest of our objectives because we could do it in lots of different ways. Ultimately, we want to give people a way to demonstrate the web skills they have, regardless of where or how they learned them, and get assessed and earn recognition (badges) for those skills. This could manifest as a mechanism for submitting a link to something you built to the Mozilla community to assess and then earning one of our badges. Or it could involve building mini assessments aligned with each competency/skill that you can come back to us to demonstrate your skills, or you could take those assessments and build them into your own curriculum, etc. Lots of things to decide on but lots of exciting potential directions.
Objective #4: Launch the New Backpack.
This is where the two roadmaps intersect a bit. The Backpack in the Open Badge Infrastructure is a repository and management interface for each badge earner. Right now, they can use their Backpack to collect badges across issuers, create groups and publish them and share out badges. It’s the, as we like to say at Mozilla, minimal viable product of what people could do with their Backpacks. We have lots of ideas of expanding on that to include dashboards, goal setting, discovery of other learning opportunities and finding mentors. We will most likely build this for Webmaker first and then role it into the broader ecosystem solution.
What Success Looks Like:
These are sort of cheating as far as success metrics go, but its still early and just want to give an idea of what we’d feeling like celebrating:
- Launch the learning standard for web literacy
- Have lots of other orgs and people aligning with it
- Offer learning pathways and badges for all of the competencies/skills
- See lots and lots of people earning and sharing these badges
How We Will Get There:
Tons of work to do and here’s how it will roll out over the year:
- Web Literacy Standard kick off and launch
- Early prep / prototypes for more badges
- Launch second wave of web lit badges
- Launch peer assessment
- Continued standard iteration and partner recruitment
- Launch larger Mozilla-wide badge system
- First prototypes of assessment pathways
- Additional integration in Webmaker
- Launch full set of web literacy badges
- Launch assessment pathways
- Launch Dashboard / New Backpack
Let me know what you think!
It’s that time of year again and I’ve been using the MoFoHoHo break to not only chase around a 14 month old and two chocolate labs, but also to reflect on my resolutions for 2013.
1) Set the groundwork (and standard) for a web literate planet.
We often say our work is aimed at ‘creating a web literate planet’, but this is the step before that - more about evangelizing the idea of web literacy, as well as creating and promoting web literacy as a standard, so that a bunch of people can work towards a web literate planet with us. The end goal is the same, but its a much more collaborative spin on how we get there. And my team’s contribution has been to build the foundations for this work and will pull together a collaborative working group early this year to iterate and build a standard that we can all use.
2) Tip Open Badges.
Open Badges has been steadily building up momentum and this is the year to curve jump or reach the tipping point. This will involve adoption work, to get high value badges and proofs of concept into the ecosystem, as well as consumption work, to see more organizations and institutions accepting and using badges for jobs or credit. We will also significantly improve and expand the Open Badge Infrastructure, as well as surface the information and connections required to make it easier and more effective to issue and use badges.
3) Be strong and kind, as a leader and a mother.
Our fearless leader Mark, has some great resolutions and I have borrowed my last one from him.
This one doesn’t need a lot of context - it’s beautifully eloquent and just dead on. I learned a lot last year about motherhood, leadership and work life balance. I had lots of great times with great people (and a particular baby) and some tough times as well. This year I want to roll all of those lessons and achievements into a more finesseful, confident and zen approach to my life and work. I want to be more present in each moment, carve out the time needed to give my full attention to things, take more time to really connect with people and as Mark said, generally be kind. At the same time, I want to be a rock and stay solidly focused on our growth, progress and goals for this year.
2012 was exhilarating and exhausting. So much change and momentum building. 2013 is a year of digging in and making things great. There is so much potential - I am very excited to do this together.
Open Standard for Web Literacy: A Vision for Webmaker
We’ve been doing a lot of planning and brainstorming and chatting about what Webmaker will look like in 2013. There are lots of good ideas floating around that you can see from a bunch of my colleagues here, here, here and here.
One thing I want to add into the mix is the vision for Webmaker as an open standard for web literacy.
That’s a mouthful so let’s work backwards and break that down a bit:
The Web Literacy part…
(Or as Doug reminds me, web literacies)
We’ve been talking for a long time about the skills that we think people need to be a webmaker. To be more producer-minded. To understand and love the Web. To express themselves in a way they can be proud of. To compete in today’s economy. To be an active citizen.
In addition to all of the flashy tools, content and branding we’ve been launching over the last year, we’ve also been doing some considerable ‘underbelly’ work to define the thing we are ultimately after: a generation of web literate people. Doug has been leading a lot of our initial work in this area, which looks something like this in its current iteration:
You can see that there is a mix of ‘hard’ skills like HTML and CSS - very specific skills that people need to know to make things on the web without wysiwygs or forms. But then there are also a lot of the more social or 21st century skills like sharing, collaboration and remixing.
The Standard part…
I think this is important work for more reasons than just enumerating the things that Mozilla cares about or may provide learning pathways and badges for, but as a definition that we, as in the royal we of the web world, can all get behind and all teach to. One of the issues with the digital literacy work that’s been around for some time, is that there isn’t a commonly agreed upon description of what it actually means from a skill perspective, or when we can draw a line and say, congrats, you are digitally literate! Some of that is beautiful - we want flexibility and room for innovation - but I think there needs to be a core definition that people can build from. I think that’s one thing that Webmaker can offer. You can use our tools if you want, but you can also use your own tools or other options out there - but if we all agree on the basic thing that we’re working towards, we’ve created a web-wide choose your own adventure for learners, with a success story that benefits them and helps us all reach our goals.
The Open part…
This is a loaded word and that’s intentional here. I think in order to be successful, this standard needs to be open in several ways, some of which I’ve already alluded to:
1) Open as in open source:
Mozilla cannot build and maintain this standard alone. In fact, we haven’t been - Michelle and now Doug, have been traveling the world, talking to experts and n00bs and everything in between to get a sense of what skills are important. Lots of people have contributed and we are going to be ensuring that this is even more of a community effort moving forward.
Additionally, this standard needs to be extensible. We should see this as the core and leave room for people to easily hang things off of it (i.e. design skills, game theory, etc.).
2) Open as in open ecosystem:
Mozilla can’t be the only place you come to learn this stuff. Lots of other people are already teaching people many of these skills and so let’s leverage each other to teach web literacy at web scale. In fact, as you look at that grid above, it’s highly unlikely that any one organization will teach all of those things, so again, it’s together that things become more comprehensive and more powerful.
We also aren’t saying that there are particular ways that people should teach this stuff. We are building some of our own learning pathways which will be very making-forward, but to appeal to everyone, there are a lot of other approaches that should be in the mix (for example, folks like Codecademy, Coder Dojo and Khan Academy), but also including approaches that aren’t even intended to be learning experiences. There is a lot going on through Twitter or Instagram that help people develop web skills like sharing or curating. Again, it will be important to leverage a lot of the work and options that are already out there and find ways to build the learning/recognition layer on top of things people already love to do.
3) Open as in Open Badges:
We are developing a set of badges that are aligned with this definition of web literacy, but again, if Mozilla sites are the only places that you can earn those badges, we’re limiting ourselves, and constraining learners. Recognizing the learning and skill development, and fostering reputation and identity development around web literacy is as huge part of all of this and that necessarily means that we need a solution for a more distributed set of badges. Good news is that our other day job is building and promoting Open Badges, so we have the infrastructure in place, but no one else in that ecosystem is sharing badges across organizations so solving for that will be an important challenge.
What we end up with is a co-designed, shared purpose with a much wider network with much wider reach…and a much higher likelihood of ‘winning’ together.
Lots of work to do on this moving forward - excited to work with all of you on it.