Finally enroute back east after a quick and power-packed trip to San Fran for an awesome Summit to Reconnect Learning.
At the Summit, we announced a new venture to build a Badge Alliance. The Alliance is a network of organizations and individuals working together to build and support an open badging ecosystem. Members of the Badge Alliance will collaboratively tackle important issues, questions and opportunities to continue to push the work forward.
We also announced that I will be transitioning out of Mozilla to build and run the Badge Alliance. Over the the course of the year, I’ll move to the Alliance full time to drive this work.
I am incredibly excited about this opportunity - it really feels like the natural and necessary evolution of the badging work and of my role in it.
We really need this. The badges work relies on a robust ecosystem and while there are many many folks playing in the space, we aren’t leveraging each other enough. We aren’t sharing enough. We aren’t building a knowledge base. We aren’t moving the ball forward as quickly as we could. And that’s not because we don’t want to. It’s not your job. You each need the space to do your work, your slice, with your agenda, timeline and perspectives. Someone else needs to help connect the dots, set overarching goals, drive the conversations that need to happen. Well, now that’s my job. :)
So I am just thrilled. This is going to be fun!
As this has been unfolding, I keep getting pulled nostalgically back to a dusty corner in a Barcelona museum…we were at the Mozilla Festival in 2010 in “the Badge Lab” and posed a set of questions: What if we reimagined credentials to support a broader definition of learning? What if we thought about digital badges as a way to capture more about what we know and an do? Folks then wrote down the questions, issues and ideas that came to mind.
Now that was a relatively small group of people - maybe 15. But let me tell you, the amount of post its produced was astounding. We’d both hit a nerve but also hit on something worth talking about. And talk we did, we spent the next 3 days digging in.
This story is relevant to me right now for a couple of reasons:
First of all, many of the folks in those conversations then are still in conversations today. In fact, many were at the Summit with me. That day, we started a community, we started the ecosystem that is vital to the success of this work. That has grown significantly over the last 3 years. There are so many of you contributing to major ways to the work and that’s absolutely critical. And there is so much potential when we start to leverage each other. I feel so motivated and inspired by this opportunity to get up everyday thinking about how to support you, connect the work and move us all forward.
Second, many of those questions that were written on those post it notes are still open questions today. In fact, some are topics we spent the first day of the Summit talking about. We’ve been thinking about this stuff for a long time and we are at a moment where we can make decisions and really accelerate by more formally working together.
The Badge Alliance will operate through working groups that are facilitated by the Alliance team. This isn’t really new - as evidenced by the 300 people who showed up to the Summit to work through key issues - this is how we’ve been working already. The Badge Alliance will just layer in more intentionality, accountability and support.
We are going to hit the ground running. Today is the soft launch, with a formal launch planned for Q2, but in the meantime, we are going to kick off the initial working groups. These working groups will help us continue the conversations and work needed to move the ball forward on important issues. You can visit http://badgealliance.org to view the initial working groups, sign up to participate and suggest additional ones.
I may be taking a leadership role in the Alliance, but this is way bigger than me. Just as the Alliance is a network of organizations building the ecosystem, it needs those organizations to help shape it. It’s incredibly exciting to me that a number of organizations have already stepped up as founding members:
Huge hugs and high fives to these folks for their initial interest and support. And it’s not too late to contribute as a founding member. If you are interested visit http://badgealliance.org or email me at email@example.com.
Also, definitely sign up and secure your spot on the initial working groups that are important to you. You can do so at http://badgealliance.org.
Many many more posts to come from me with more information as this unfolds.
Just back from MozFest, where we announced BadgeKit, an Open Badges tool stack that will support the key pieces of the badging experience. This includes defining/designing, assessing, issuing, collecting/managing, sharing and using. BadgeKit will consist of open, lightweight tools that can snap together or be used alongside or within other sites or systems. Sunny and Jess both respectively wrote about it in more detail, but I wanted to dig into the “why”.
We’ve been pretty good about explaining the WHAT of our work, but I think we can be better about explaining the WHY. Often the WHY is because of feedback we’ve gotten from you, or because of a risk to ecosystem, etc. The WHY is always tied to our values. But I don’t think we talk about it enough. So, I wanted to take a second and jot some of my thinking on the WHY for BadgeKit down for folks to start that conversation:
 Despite the progress we’ve made with interest and buy-in with badges, the gap between I get it and I have it is way too big. Platforms have emerged that are big, closed and expensive, and there is a huge risk of segmenting or closing large chunks of the ecosystem. Despite us promoting the ‘open’ part of Open Badges, its increasingly EASIER to build a closed system because of the limited availability of tools. We need to fix that. The ecosystem needs simple, easy, open options to move quickly and do so in a way that benefits the entire ecosystem.
 And building from that, we need to bake our values into the core so that it is easy to build badges and systems that are open, interoperable, transparent, learner-centric, etc. By offering a set of tools to scaffold badging, we have a chance to support our values even further. For example, we care a lot about the open standard (and in fact think that’s the most important piece of all of this), so we should make it REALLY easy to build badges that are aligned with that standard. Easier than building badges that DON’T align with the standard.
 But that’s not all. This isn’t a new idea out of nowhere, this is actually WHAT WE BUILT FOR CSOL, but more standalone, more complete, and more valuable to the broader ecosystem. We actually ALREADY HAVE BADGEKIT - we have all of the foundations. We are now really working to build out these tools in a way that makes them easy and accessible.
 Oh yeah and there are TONS of other organizations, cities and groups that want to do what Chicago did or something similar. Networked or ‘connected’ badges are the future - that’s the secret sauce that badges provide but we need the systems to support it. There are so many variables with these badge systems, that it seems to make sense to try to have some shared pieces to help minimize the burden and maximize the speed and efficiency of these roll outs. Plus, a shared technology infrastructure makes for easy sharing and leveraging across these networks. And if that technology is open and extensible, we all win.
 Finally, we don’t have a bottom line. Building tools in a way that works well with other tools, and invites - even welcomes - competition, is not what any VC would recommend or support. Our priorities are ease of use, but also extensibility, interoperability and playing nice with others. We want to spend the time defining common interfaces so that you can use our issue tool with an assessment tool from somewhere else. Or pick up our build tool and make it better. We want more and better tools in the ecosystem, but the key is that they all work within the same open ecosystem. I don’t say all of this to be snobby, I think its a luxury that we can work this way. But also an obligation. That’s what makes Mozilla Mozilla, and I think we need to step up and build these foundational pieces to increase access and help everyone, including other open tool providers, thrive.
On the why now piece, the demand really speaks for itself. But above and beyond that, I’ve been reflecting back on this entire wild ride. In late 2010 (2010!), when badges was merely a few months old, there was a lot of pressure internally and externally to build an issuing platform. Brian and I, the only Open Badges employees at the time, resisted this at the time because we were afraid that if we did that, we’d too greatly influence the development of the badge ecosystem. We didn’t have a really solid idea of what a good badge looked like or how badge systems could work at that point. And whatever decisions we made and built into the platform would have heavily weighted the ecosystem out of the gate. We showed this diagram (below) all the time and repeated over and over that the stuff in the boxes (with the big blue lines around them) was independent of us, by design. We wanted to build the necessary pieces to support and not confine innovation at the edges, where the learning was taking place.
And yet here we are building issuing tools. But I really think things are different now. We’ve seen a ton of badges and badge systems. We’ve built a ton ourselves. We’ve seen a market emerge around the tools, some done the right way, and some done the wrong way. We also know how to build more neutral systems, and our role in protecting and promoting the open standard. I still think that was the right decision initially, but also think that we’re really primed to do this now.
BadgeKit is already available for select partners - we’ve used it to support Chicago Summer of Learning, Connected Educator Month and Open Badges badges to date. We’ll continue to build out instances to support specific partners and campaigns that engage with us, but are aiming to release a free, open public beta of the standalone offerings in early March 2014.
We really do need feedback from folks on this direction, as well as the specifics of BadgeKit. We keep saying “simple” and “easy” but need some help defining exactly what that means to people, what they need. We will need help prioritizing all of the potential features as well. And more. So look for more from us, and in the meantime, reach out and tell us what you think.
The mornings are crisp and the leaves are turning rich colors here (you should come!)…it’s officially Fall. We’ve wrapped up the Chicago Summer of Learning and have had some time to reflect on how it went.
It was helpful to start the debriefing process with a look back at what our original goals were back in what feels like years ago, but was only February of this year. Looking at the numbers through that lens has helped us start to thoroughly evaluate this summer. We, of course, want to supplement the raw numbers with more real feedback from youth and organizations and research, all of which is forthcoming.
Internally, we also aspired to:
The CSOL numbers:
When I look through these numbers, the initial reaction is wow. We can go down the goals and check them off across the board. Over 100 orgs and 1000+ badging opportunities represents not only a lot of coordination and collaboration that I am still shocked that we all could pull off in just a few months, but also an incredible coverage across the city and a heck of a lot of learning opportunities. The badges themselves were really great - with only a few orgs issuing badges simply for participation*, but most badges focused on skill development with robust assessment and criteria. The Chicago organizations really stepped up and came into this summer and this new concept of badging with open minds and a dedication that was astounding. Huge kudos to all of them - they are the ones with the content, experiences and relationships with youth that matter. The badges are just the recognizer on top of that learning. That said, the badges were very strong and DePaul University has already stepped up to say that they will accept some of the badges for credit in their institution, and CPS is working to define rewards and advancement that they can offer for the badges.
(*Note: this is not to say that participation badges are *bad*. There are many reasons why rewarding someone with an initial participation badge could be valuable, including motivating additional work, recognizing time commitment, etc. But we wanted to hold ourselves to a goal of having the majority of the badges tied to a deeper assessment, which they were)
Orgs issued over 100,000 badges this summer - that represents a lot of learning and a lot of youth. And there is diversity among those youth. Time on the site shows that youth (and parents) were spending time searching for things to learn or digging into the self-paced challenges that were available for youth on the site, and the wishlisted badges show that some youth were setting goals and into learning more.
Even though we had set a goal around 1000 youth leveling up, I was pretty worried about this one given the fact that many programs started later in the summer and often required multiple weeks of participation and learning before a badge was issued. In order to level up, kids had to not only earn a badge, but earn several within the same category (Science, Technology, Engineering, Arts or Math). This most likely involved doing a combination of local learning programs and online self-paced challenges. So I was pleasantly surprised to see that almost 600 youth got to the city level badges and had access to the challenges, of which almost half of those completed challenges, which were not easy and required commitment and hard work.
The part I am less wowed by is the disconnect between the badges issued and the amount that have been claimed. This number is less stark as it looks but only about 50% of badges issued were claimed and added to Backpacks. To explain this a bit, badges were issued one of two ways: 1) through an issuing tool built by Mozilla called OpenBadger that had an admin interface for org representatives where they could issue badges to youth emails, the youth or their parent had to click through the link in the email to accept the badge and have it show up in the youth’s backpack. 2) Organizations with offline learning experiences could also hand out paper badges with unique claim codes printed on each. The earning youth then needed to log on to the website and enter the claim code to see it in the Backpack.
There is still some research to conduct, including some surveys and focus groups that folks are conducting to learn about what worked and didn’t work for kids this summer, but its likely that the lower number of badge acceptance most reflects breakdowns in the overall user experience. Many youth haven’t checked their emails, or didn’t click through links of the original, text-only emails. Some might not have had access to a computer at all to claim or accept the badges. Others may have lost the paper badges - its likely there are lots stuffed down in corners of physical backpacks - before they could claim them. Another option is that kids just didn’t care about the badges, or didn’t understand the value, so that’s something we’re exploring more.
While, as I mentioned, I was pleasantly surprised by the number of kids leveling up, we did not hit that initial goal of 10% of kids. Some of this can also be attributed to user experience design, some of this was the relatively short amount of time to learn and earn and level up. I also think there is an opportunity to design and promote challenges in a way that even more connects directly to youth interests and real opportunities. I’d love to see more challenges next year that show youth completing real projects for their neighborhoods or the city of Chicago. Or developing skills that are directly tied to career pathways, jobs and internships.
In general, the numbers were again, impressive, but I think we can do more. Through a combination of improved tools, better user experience design, more and better training and more marketing and communication, I think we can bring more organizations on board, reach more youth and see more accepted badges.
There is a big assumption in that last statement: that we are doing another CSOL in 2014. I think there was a resounding consensus in a recent meeting in Chicago that the results of this year’s summer were compelling enough to demonstrate the value and promise of this work. So there will be a CSOL 2014, and in fact, maybe something more on the lines of CYOL (Chicago Year of Learning or something like that). Lots of details to work out on the goals, roles and specifics for that work, but given that we are building from a foundation and set of findings, as well as starting those conversations in September instead of a few months before launch, to me, means the possibilities are enormous and exciting.
We’ve learned so much this summer about what it takes to build a badge system at this level, how we can better the tools, who to invite to the table from the get-go, and more. Lots of work to do to get to a 2.0, but there are a lot of pretty clear marching orders. Look from more blog posts from me and the team on these lessons learned and thoughts for moving forward on our pieces.
Also, turns out that Chicago is and will continue to be a hub for innovation and advancement with badging, but another exciting development is that more cities are interested in building something similar to CSOL in their neighborhoods and I think we’re going to see not only more geographical reach, but also a significant amount of more learning and youth impacted in less than a year.
As I’ve written often in the past, I believe the automation of recruiting, job seeking and hiring has exacerbated America’s employment crisis. Online forms and tools like the “apply with LinkedIn button” make it too easy for the wrong applicants to apply for jobs, and harder for employers to find the right ones. But when a job applicant’s position on the stack of resumes can be bought, the search for the best-qualified candidates is even further compromised, and so is our economy. —
Sounds like we need better, more verified tools for understanding skills and matching people to the right jobs. If only there was something….
My last post on the Badge Summit was more of a ‘here’s what happened’, but wanted to follow that up with some of my own reflections and inspirations.
Distributed leadership: We talk a lot transparency and community-driven development at Mozilla, and certainly within Open Badges. Our aspirations are so high, that it would be impossible to begin to even start to meet them without a movement, without markets, without more and more people not just involved, but driving things forward. We want to build a new system for credentialing and accreditation, we want to redefine learning - there’s no way one, or even three, organizations could do that. We need the full ecosystem fully realized and fully empowered. But one thing that became even more clear at the summit was that we are well on our way. I was awed by the leadership and work that folks in the room represented. There is so much that other people are already doing and contributing, we just have to make sure we are coming together from time to time to swap stories and celebrate the success.
Exemplars: The word of the day(s) at the event was “exemplar”. There were a few that even threatened to start a drinking game. But whether it was in the conversations about marketing and communications, or in a group focused specifically on higher education or workforce, it’s clear that the most critical way forward is to have working proofs of concept for each of the stories that we need to tell or use cases that we want to show. Exemplars allow us to scope and focus in on building something specific quickly, that then can be a model that other similar groups or organizations can follow. They also can also function as a laboratory where were are advancing the tools and experiences, while also learning a significant amount about what works and what doesn’t. CSOL is a great example of an exemplar because it includes a bunch of ‘new’ stuff that before were often only ideas or theories: network-level badging, earning badges across many informal learning experiences, leveling kids up through pathways and translating learning back into schools and local businesses. It’s a mini version of the ecosystem that we can see results of in a 3 month time period instead of 3 years, or whatever turns out to be. We need to do more of these. (And I don’t mean just ‘we’ as in Mozilla, but ‘we’ as the broader badging community. Mozilla will most likely do some but there are many that need to be defined, recruited for, designed, tested, communicated, etc.)
Local: Building off of the last one, there was a lot of interest in ‘cities’ at the summit - thinking about badges in a local context as a key set of exemplars. To me this is really exciting for a number of reasons, including the same thing I said before which is that we are building mini ecosystems, with all of the players - issuers, learners, validators, employers, schools, etc. - in the mix and at the table from the get-go. This is super powerful because it moves us away from some of the philosophical rabbit holes that we often get stuck in - like “How are badges validated? Do they have meaning?” - and make those questions concrete and addressable. City-level anything, let alone badge systems, are also really hard to do and there is tremendous learning involved. If we can make it work at the city level, then we’re in a good place for addressing needs at each org-level and even at the ecosystem-level in many ways. And finally, badges in the local community / city context have real meaning for those earners in their lives right away. So regardless of what happens in the broader ecosystem, those badges meant and will mean something to those learners. Let’s do more cities.
Small data: Another recurring theme, which I actually first heard at the DML conference, but then came up again at the summit was “small data”. The idea of personalized data tracking or even local community-level data, that can give you real-time feedback on who you are, what you can do, what you are doing, what role you play, etc., and help you choose your pathway or alter your behavior in the process. It’s the quantified self idea, but for learning. I’m not sure exactly what it means yet but I love the idea of learners owning their data and that being a powerful mechanism for driving choices, opportunity, evidence, etc.
Learning GPS: As we sketched out our own perspectives on the current state of the ecosystem a new role appeared several times across the sticky notes. The idea of a person or an organization that helps learners choose pathways. We dubbed it “learning GPS”. This exists right now in coaches or career advisors, but badges actually makes this an easier and more powerful role because they can surface the universe or ‘map’ of learning opportunities, all backed by information and data to show the value and endorsements of each step along the way. Exciting possibilities!
These were just a few of the themes and reflections that I left with. I’m sure there are more and will try to add to this as I continue to process all of the goodness that came out of the two days in Toronto.
This week kicked off with a meeting of badge minds in Toronto. Around 30 of us packed into the lovely Centre for Social Innovation to discuss the emerging badge ecosystem and how to drive the next era of the badge work together. We were, you know, socially innovating. :)
A common theme was that the badges work is bigger than one organization, certainly bigger than Mozilla. There is SO much to do, and there are many roles that need filling, and more everyday as the ecosystem and market(s) grow. We’re already seeing leaders emerging beyond the initial Mozilla, MacArthur, HASTAC work and this meeting was about celebrating and honoring that, as well as encouraging more ownership to tackle key pieces that the ecosystem needs.
Day 1 was about visioning (what’s our shared vision of success) and level setting (what’s out there already). Day 2 was digging into some of the key questions, opportunities and challenges, with the focus on building working groups around them and getting actionable plans in place.
Core topics included:
We also have plans for a shared user research framework and outreach plan, building the overall foundation of research and findings to back the work, creating a shared resource repository, encouraging innovative assessments within the badge ecosystem, and more. It was a busy two days…
There is a core documentation team that will be generating a report to share all of the conversations, plans, etc. Look for that in the next couple of months.
All-in-all, I was excited and inspired by the two days and really looking forward to keeping the momentum going. Many thanks to the participants who traveled from far and wide, including across oceans, as well as our fantastic facilitator, Gunner, who kept the motley crew on task.
Additionally, its worth noting that this event was by no means the comprehensive set of leaders in the badge work. We wanted to ensure that key perspectives and specialties were represented, but above and beyond that, last minute plans, summer schedules, budget, etc. also influenced the attendee list. We hope and plan to pull many more into the conversations and work as we go (if there are any up there that you know you want to be part of, let us know!). That said, don’t wait for an invitation - keep doing what you are doing, share your work, jump into conversations, etc. The only way we win is together.
More to come - thanks!
My two weeks of vacation conveniently ended with a fun, relaxing week with my team in a remote oceanside town in Northport, Maine. Not sure there’s a better way to get reintegrated after vacation.
The retreat, affectionately called Badge Camp, was focused on reflecting on the Chicago work, as well as digging into the core features and directions ‘next’. We all stayed in an old inn where turns out we had limited internet, no cell connectivity, one semi-working refrigerator and a barn with a DJ machine - all of which were unanticipated, and only one of which was a happy surprise (hint: karaoke!) Sounds like the makings of an incredibly UNproductive week, right? Not with this crew. We capitalized on the opportunity for uninterrupted facetime to take planning walks, hold paper prototype demo sessions on the front porch, make new prototypes with felt and glue guns, huddle over meals with project teams and host mini focus groups over the camp fire.
Before Badge Camp, we had broken people into core project teams and had them brainstorm for 3 weeks, and everyone arrived with solid thinking and prototypes. In addition to feedback and (of course) a much deeper dive on the overall ideas and details than anticipated (but most welcome), we ended with roadmaps from now through MozFest for each project (some artistically written with glitter glue and construction paper (soon to be transcribed into a digital format). Unsurprisingly, the team was eager, serious and excited about the next phases for us - we’ve all been anxious to get back to the core product and features for the broader badge ecosystem. All-in-all, we made some significant progress in our plans and thinking on key projects and features, most of which will be coming through blog posts from the team, but I’ll summarize and highlight the core areas here:
Production Backpack: cleaning up code, fixing bugs, finalizing 1.0 features that need more love, knocking off the low hanging fruit want-to-have features and ux improvements. Also includes building some acceptance tests, which will significantly improve our ability to monitor and test our stuff, but also hopefully give the community more insight into what features we have with each release and help them help us understand what’s not working the way its supposed to be, etc.
Prototype Backpack, or ‘Backpack 3.0’: the bigger vision for the Backpack including more tools and features for the earners. More to come on this as the thinking develops.
Federation: Allowing many Backpacks to exist across the ecosystem and still work together at the ecosystem level. This will require a standard for a Backpack and APIs for ‘registering’ Backpacks, all as seamless as possible to the end user.
Open Badges Badges: Wait, we’re the Open Badges team and we aren’t issuing badges?! Blasphemy! Don’t worry, Open Badges badges are on their way and they will not disappoint.
CSOL: Continuing to support and push CSOL through the end of the summer.
Endorsement: Endorsement is allowing third parties to sign badge classes to formally endorse the curriculum and assessment that they represent. This is in the P2s not because it isn’t as important, but it relies on some pieces from the projects above, namely Federation and Prototype Backpack that this extends from. We’ll be kicking off some user testing and research on this in the meantime.
Productizing CSOL: We now have a pretty solid ‘tool stack’ for issuing, including the Badge Studio, OpenBadger and Aestimia (peer assessment). We also have some really cool new Backpack features like recommendations and COPPA-compliance. But these were all really built and customized specifically for CSOL. So we want to go back in and make all of this stuff accessible, useful and available to the wider community and ecosystem. This is also very important but will most likely be something that gets more dedicated time through additional use cases and projects that we take on.
Community Site 1.0: Last May we launched a mini community site, meant to be a placeholder for a bigger, more community driven repository for examples, resources and celebrations. The latter clearly needs to be designed with and through the community so we’re looking forward to kicking that off soon.
User Research: We are kicking off a new approach to our work, that includes more user research from the beginning! How revolutionary of us! :) We’ve always tried to loop the community in from early on and get feedback along the way, and that works great for the issuing side of things, and we will continue to do that, probably even more targeted. But we also need to talk to other audiences that we don’t usually reach on an everyday basis like earners and employers, so Emily on our team, is stepping up to map out our research process and bake it into all of the projects outlined above.
Partnerships: This could also be called adoption, but its working with issuers to build and issue awesome badge systems, and with employers and institutions to use badges on the other end. We’ve been doing this since day 1 and will continue to make this an ongoing priority. We’ve now got a powerhouse team to help us drive this side of things, including a set of key emerging community leaders who are owning these conversations within particular sectors or locations. +1 to this.
Marketing + Documentation: We’ve got a firehose of inbound demand, with almost no marketing efforts. I can’t imagine that will change significantly given that we are grant-based, but there are definitely things that we know we can do to make things more accessible or approachable, and Meg has joined the team to whip us into shape here.
If you’ve ever been to one of the many educational conferences in the US, you will hear a lot about North American-centric issues and proposed solutions. While making change in our country/continent is important, we often fall into the trap of only building solutions for our particular context and miss bigger opportunities for global collaboration and scale. This is why I’ve been happily surprised at the upswing of interest and adoption of badges outside of the US. Badges are flexible enough to be used in many different ways, to solve many different problems, and we are seeing that in action as they are being adapted and implemented across the UK, Italy, Australia and more.
I’ve just returned from a quick, but power-packed trip to Milan, where we met with our innovative colleagues from the Hypermedia Open Center (HOC) Lab at Politecnico di Milano. They invited us to Milan to talk about the badge work in North America and kick off a national conversation about badging in Italy. I was impressed at the reception and interest from the many Italians in the room - not only to explore badges for their own schools and workforce, but also across countries in the EU. There were handfuls of initial pilots that attendees signed up to lead on the spot. There is real opportunity and momentum here.
(that’s me on the right with the translation headphones :))
At the same time, just a few countries and only one hour time difference away, badges are booming in the UK. Together with, Doug Belshaw, our resident UK spreader-of-the-badge-word, Tim Riches and the folks at DigitalMe have built a significant community there already exploring badges. They are doing really interesting things with badges because they are more tapped into the schools and really pushing buy in from the top. They recently launched “Badge the UK" which is a campaign to get organizations and institutions to issue and accept badges across all of the UK. It’s incredibly exciting and we are learning a lot from one another.
We’re also seeing interest emerge from Australia, China, Estonia and more.
We are excited about the globalization of badges and one thing that is a high priority on our end is a solution for localizing badges. Good news is that all of our tools are open source, so countries or organizations can set up their own, localized Backpacks relatively easily (although we still have a bit more work to do to make them easily localizable and federated). But there will be, and already are, badges that are meant to be used across languages or learners that span several localities and languages, and so thinking through how the badge and the metadata become localizable is important and top of mind.
Would love to hear other ideas on how to best localize the badging experience, as well as places you’d love to see badges expanded to.
We recently formally launched the Chicago Summer of Learning badge work. This has been a pretty big undertaking for us, to say the least, we started early conversations back in January and for the last 3 months, my team has been almost solely focused on it. The all-hands-on-deck was because the scope of work was so big (and ever-growing), but also because of the potential weight and impact of the work. I’ll detail each below to help explain why CSOL matters for us, for Chicago and for the world.
The Chicago badge work started as a ‘simple’ statement of work - overlay badges on top of all of the amazing programs and learning content that local organizations and cultural institutions already provide across the summer. The goals were:
The Mozilla contribution to the project was mainly two-fold. While we played a role in project management, we mainly focused our attention on 1) designing the overall badge system, including all of the organization-level badges and 2) building all of the technology components.
The Chicago badge system design was no small task. We had over 100 organizations all teaching different things in different ways across various age groups, some online and most face-to-face with limited connectivity. We needed flexibility in the badges to ensure that they reflected each unique organization and their offerings, and yet were still seamlessly connected for learners. We needed to make sure the badges were worth something and met some level of standards. And oh yeah, we need to have all of this defined and designed in 3 months time. No problem.
The (outdated) internal diagram for how this works:
The prettier, external napkin sketch:
(it’s worth noting that Carla Casilli built this thing from the ground up, including working through each of the 1000+ badges. She’s awesome. We also had tremendous input and support from Nichole Pinkard, Caitlin Martin and the rest of the DYN crew. Well done, team!)
The CSOL work had some complicated technical requirements, including servicing badge definition and issuing from representatives from more than 100 organizations; supporting kids 13 and over, as well as under 13 in collecting badges across experiences, with required parental controls where necessary; suggesting pathways and more learning opportunities; sharing badges with schools and social networks; and providing the end user ‘site’ to find learning, badges, track progress, etc. It was really multiple systems that we needed to build in parallel, and yet again, still needed a seamless experience for all of the participants over the summer. Oh yeah, and 3 months, something something.
Many thanks to my team and the extended CSOL team, including the City, DYN, MacArthur, Hive Chicago and more.
And thanks to our Open Badges community for your patience and support as we’ve focused in on this important endeavor. We are excited to get back to the core infrastructure in a big way. But I hope you’ll join me in congratulating the team, and congratulating Chicago for building something special.
President Clinton just stood on stage and told the world how important and ‘good’ the work on badging is. It was surreal. It was awesome.
We are at CGI America and he was announcing the commitment to action that we made with the MacArthur Foundation and UC Irvine, to drive 1 million jobs and 1 million education opportunities in the next 2 years through open badges. That means connecting individuals to real things - jobs, school credit, admission, etc. - through badges.
The commitment is super exciting because it’s open and welcoming to organizations and partners to plug in and help us get there. (Join us!) From the conversations at the first day of meetings alone, I don’t think its going to be hard to reach. Help us blow past 2M! Let’s go for more!
CGI is also an exciting stage to launch this on because this meeting includes over 1000 organizations that are zeroed in on workforce development and jobs. They are the movers and shakers. They have the pull and reach to really connect badges to real opportunities.
I need some champagne.