April 23, 2014
Open Badges Research & Badge System Design Call, April 23, 2014
Speakers: Dr. April Moore & Leanne Cuicchi, Corona-Norco School District; Dr. Karen Jeffrey, ForAllBadges
Dr. Moore joined us with her colleague Leanne and badge system consultant Dr. Karen Jeffrey to talk about the work being done in the Corona-Norco Unified School District with badges. We heard a brief overview from her team back in November (read more here), and returned for a deep-dive discussion of their work on this week’s Research and Badge System Design Call.
When we heard from April in November, the Corona-Norco Unified School District (CNUSD) offered 12 initial badges, split between the elementary, middle and high school levels. The badge system is now fully operational for Riverside County’s 54,000 students, and the district
The system was developed in partnership with ForAllBadges to allow for flexibility between the district’s schools, to allow instructors to develop badges for school-specific programs that recognize different skills and behaviors across grades K-12.
While elementary students can earn badges for attendance and behavior, middle schoolers are earning badges for meeting formal standards within specific subjects, as well as developing career or college plans. Once in high school, students can earn badges for fulfilling entrance requirements for colleges and for exemplary scores on the exit exam as they leave school. The district is using a
Due to COPPA's age restrictions on the badge backpack, the CNUSD badge system has been designed with students' privacy and confidentiality at the forefront. Once students are over 13 years of age, they can (choose to) push their badges to the Mozilla backpack and share them publicly from there.
Motivation and education
Throughout the badge system design and implementation process, April and her team have been looking at how the badges impact students motivation across the district, and t
April 23, 2014 09:54 PM
Open Badges Community Call, April 23, 2014
This week we were joined by our former Badges + Skills Lead Doug Belshaw, who is now the Web Literacy Lead, and a mentor, on the Webmaker team. Doug still writes about badges from time to time, but spends most of his days working on web literacy awesomeness - most notably the Web Literacy Map.
Badging those who teach others to teach others…
Mozilla launched the first set of Webmaker badges at the 2012 Mozilla Festival. Since then, the makers and mentors on the Webmaker team have been working to develop badges to recognize both those who contribute to the community, and those learning new skills and competencies that allow them to participate in the Web.
The team plans to
The badge system being developed by Mozilla for the Webmaker mentors and learners is based on
To check out the Webmaker Training platform and provide feedback, go to
Find Doug on Twitter at @dajbelshaw and check out his blog at literaci.es
April 23, 2014 08:58 PM
April 18, 2014
Welcome to your weekly roundup of badgeriffic news and updates!
This week’s calls were jam-packed with exciting project launches and badge system reports, generating lots of enthusiasm and discussion. The badging team at Penn State joined the Research & Badge System Design Call to share the thinking behind the Lifelong Learning Landscape developed by Dr Kyle Peck and Chris Gamrat to badge teacher professional development - read more here. On the Community Call, the Badge Alliance leadership shared updates on the working groups and the Cities of Learning kick-off - read more here.
What else happened this week?
That’s a wrap, folks!
Have a great weekend - Happy Easter to those who celebrate, Happy Chocolate Day to those who plan to indulge :)
April 18, 2014 03:56 PM
“A credential, like any common currency, is valued only because of the collective agreement to assign it value. The value of a college degree has been in question since the Great Recession, but there have yet to emerge clear alternatives for the public to rally the around. There are plenty of contenders, though, and it won’t be long before one of them crystalizes the idea for the masses that the traditional degree is increasingly irrelevant in a world with immediate access to evaluative information.”
- Michael Staton - Harvard Business Review (via worldofe)
April 18, 2014 03:08 PM
Open Badges Community Call, April 16, 2014
This week members of the Badge Alliance leadership shared details of some of the projects and meetings that kicked off in recent weeks, and members of the Open Badges team spoke about events they led.
Badge Alliance Working Groups kick-off
The Badge Alliance, announced at the Summit to Reconnect Learning, will collaboratively tackle important issues, questions and opportunities to continue to push the work forward, led by Erin Knight, formerly the Senior Director of Learning + Badges at Mozilla. The first task of the Alliance has been to develop working groups, sets of organizations dedicated to tackling important issues or driving specific campaigns to move the open badging ecosystem forward.
This week, two of the Badge Alliance working groups held their first meetings to introduce the leads of the group and start identifying goals for the first “cycle” of the Alliance calendar (March-September 2014). The working group on badges for educators kicked off today, and the group on the open badges standard launched their first call on Tuesday.
Chris McAvoy, Lead Engineer of the Open Badges project at Mozilla, is the Chair of this working group, and joined the community call to share his thoughts on the first working group meeting.
The group are drafting
Two key areas the working group will focus on:
The Alliance will launch fully in June 2014, but the initial working groups are hitting the ground running in these key areas (just click the group names to apply for membership):
Cities of Learning 2014
Last summer, Mozilla and partners worked with the City of Chicago to create a badge system to recognize summer learning achievements by youth in the Chicago Summer of Learning, to much success - over 100,000 badges were earned during the summer program.
This year, as well as an expanded Summer of Learning and Earning initiative, Mayor Emanuel has announced that Chicago will become a year-round City of Learning dedicated to recognizing informal learning experiences of Chicago’s youth beyond the summer.
As if this wasn’t exciting enough, the Badge Alliance is working other cities across the US to build summer learning badge pilots for this summer. There are currently about 5-7 cities who will be launching a Cities of Learning initiative in the coming months. Two have already launched: as well as Chicago (led by the Digital Youth Network at DePaul), Pittsburgh announced last week that their City of Learning badge pilot (led by the Sprout Fund) is launching this summer, and released an open call for organizations interested in awarding badges for summer activities.
Other cities slated to launch City of Learning initiatives in 2014 are L.A. (with Beyond the Bell) and Dallas (with Big Thought), and potentially Columbus, OH and Boise, ID.
Stay tuned for more information to be shared on this blog as the summer draws nearer!
Education Innovation in Finland
Last week, Mozilla’s Research + Design Lead Emily led a session and workshop on Webmaker Badges with Doug Belshaw and Melissa Romaine at Oppi Festival, as well as the Interactive Technology in Education 2014 conference in Finland.
Inspired by her conversations with educators, technologists and professional development enthusiasts in Finland, Emily wrote a blog post highlighting some resources worth sharing (copied below):
- Pasi Sahlberg’s book Finnish Lessons: What Can the World Learn from Educational Change in Finland? Sahlberg keynoted the OPPI conference which a few Mozilla Foundation colleagues and I presented at (photos at right), and I’m an admitted late but passionate fan of the primer he’s written. Here’s a teaser: “This book is about how Finland how the Finns transformed their educational system from mediocre in the 1980s to one of the models of excellence today. International indicators show that Finland has one of the most educated citizenries in the world, provides educational opportunities in an egalitarian manner, and makes efficient use of resources.” Our regular research and badge system design call now has a Goodreads group for sharing relevant recommendations (join us!), and this book was the first addition.
- Open Badge Factory for easy badge issuer reporting. Amongst the wide range of platforms for creating badges that align with the Open Badges Infrastructure, this tool has some of the neatest tracking tools for people who design and issue badges. Check out the cloud-based tool’s report generation to see how your badges are being claimed and put to use by learners. It’s generated some positive press in Finland, top right.
- The forthcoming Teacher’s Toolkit will be part of a public-private research partnership focused on sharing pedagogy and imagining future learners’ needs. I’m looking forward to seeing this open and prototype-based project, particularly as Mozilla thinks about offering its own portable toolkits for distributed contributors. This kit’s organizers explain that “Teacher’s Collaborative Toolkit is a virtual teachers’ resource net to which different mobile services, learning material and authentic resource repositories, such as digital archives, tutoring and mentoring support, professional peer learning practices, can be connected.”
Eric Rousselle joined the Community Call in December 2013 to talk about the thinking behind Open Badge Factory, due for first release on January 15, 2014. Open Badge Factory is a global cloud-based service from Discendum, which enables organizations to create and manage their Open Badges in a centralized repository. Check out a summary of his presentation here.
- It’s so exciting to see these projects progressing, and to see the expansion of the badges work manifesting in the Badge Alliance. Don’t forget to sign up for the Badge Alliance working groups that interest you, and join us for next weeks Community Call where Doug Belshaw will be talking about the amazing work being done to develop the Web Literacy Map!
April 18, 2014 02:48 AM
Open Badges Research & Badge System Design Call, April 16, 2014
Speakers: Chris Gamrat, Kyle Peck, Kyle Bowen, Chris Stubbs, Brett Bixler + Ken Layng, Penn State
Dr. Kyle Peck is the Director of the “Center for Online Innovation in Learning” (COIL) at Penn State, and Chris Gamrat is an instructional designer in the College of Information Sciences & Technology and the P.I. for the Lifelong Learning Landscape (L3) grant that started development of a digital badging platform for Penn State.
Kyle and Chris proposed the “Lifelong Learning Landscape,” a project that is a collaboration between the Penn State University College of Education, the Alumni Career Services, Continuing Education, and the Teaching and Learning with Technology Group to create a broad-based badging system for credit and non-credit topics. The Lifelong Learning Landscape is modeled after the NASA/NSTA “Teacher Learning Journeys” project Penn State produced for STEM teachers.
In one of our most passionate Research + Badge System Calls to date, Kyle, Chris, and the rest of the PSU team joined us to share the thinking behind the Lifelong Learning Landscape and their goals for the future.
Badges for Penn State
The team at PSU are raising a lot of important questions as they develop their badge system, exploring both learners’ and employers’ relationships with badges, the content and design elements of badge creation, as well as assessment and learning analytics:
Another way the team at PSU are exploring badges is looking at how badges could change the way educators manage the
They launched a pilot involving 36 teachers in grades K-12, and focused the majority of their case study research on 8 teachers (4 elementary and 4 middle school), looking at 52 written reflections as part of the teachers’ records of completed professional development activities.
Chris Gamrat described this pilot badge system for teacher professional development as having two levels of indicators: lower-level “stamps” required less rigorous documentation and assessment, and were related to surface-level activities for the educator, whereas higher-level “badges” were connected to things that “were going to change a student’s learning.” The bad
Overall, the team found that teachers often opted fo
To see the full discussion of this pilot system, check out the etherpad notes, and listen to the recording by clicking the link at the top of this blog post.
Read more about the PSU badge system pilot in their published case study: Catalyst For Change - A Penn State Case Study on Digital Badges
April 18, 2014 02:45 AM
April 15, 2014
Read the original post on Remake Learning.
This summer, Pittsburgh will join other Cities of Learning from across the United States in a groundbreaking initiative to pair learning opportunities for young people with digital badges in ways that allow learners to think about, pursue, and develop their interests.
The Cities of Learning initiative was piloted last year in Chicago, to great success. And last week, Chicago’s Mayor Rahm Emanuel announced that the Summer of Learning is being expanded this year, to become the City of Chicago Learning and Earning Initiative, aimed at engaging youth throughout the year.
In Pittsburgh this summer, badges will enable young people to take new paths of discovery, explore the city’s rich resources, and find out what they can learn, make, do, and ultimately become.
The Sprout Fund invites organizations from the Pittsburgh Kids+Creativity Network, schools, libraries, museums, and other youth-serving organizations offering summer learning experiences to apply to participate in this regional effort.
For more information on how your organization can get involved in the Pittsburgh City of Learning program, click here.
April 15, 2014 06:21 PM
April 12, 2014
Read the original press release here.
On April 9, Mayor Rahm Emanuel announced Chicago’s youth will now have access to an additional 10,000 academic and job training opportunities through partnerships across the City as part of 2014’s Summer of Learning and Earning, a citywide initiative to keep Chicago youth ages 4 to 24 active and engaged this summer. The “Summer of Learning and Earning 2014” will provide more than 215,000 opportunities for Chicago’s young people, including interactive activities at parks, libraries, schools, museums and cultural institutions, colleges and universities; community- and faith-based programs, jobs through at City and County departments and sister agencies; and self-paced, online learning activities.
“In the wake of last year’s incredibly successful summer programming, I am pleased to see our citywide summer initiatives growing and thriving as we work to support the educational and career goals of all Chicago students and young adults,” said Mayor Rahm Emanuel. “Providing additional opportunities in the summer months is an important way to keep our youth safe, active and engaged, and ensure our students are graduating 100% college ready and 100% college bound.”
The Summer of Learning and Earning will include the Chicago Summer of Learning, which the Mayor launched last year to call together the entire city to an all-hands-on-deck effort to make summer count and support science, technology, engineering, art, and math learning for students of all ages. One Summer Chicago will also add an additional 2,000 job opportunities. Since the Mayor has taken office, job opportunities for youth have increased from 14,000 to 22,000.
The Summer of Learning and Earning will once again engage youth by challenging them to earn digital badges to mark their successes. These badges are a tangible way for students to display their activities and achievements to teachers, college admissions officers or future employers, making learning pathways visible and recognizing student accomplishments. Last summer, Chicago launched the world’s first citywide digital badging system to recognize out-of-school student learning, and students earned approximately 100,000 badges.
Connie Yowell, Director of Education for U.S. Programs at the MacArthur Foundation, said that Chicago has become a model for the nation. “The first-ever program that treated summer activities as examples of connected learning and provided badges for youth participation and achievement, last year’s Summer of Learning was incredibly successful, awarding more than 100,000 badges to participants,” said Yowell. “In fact the program was so successful that now five other cities are replicating Mayor Emanuel’s signature program, coming together under the cities of learning banner to provide youth with learning and badging opportunities. “
April 12, 2014 08:02 PM
April 11, 2014
What should this copy say?
We’re shipping a new “explore” page for Webmaker. The goal: help users get their feet wet, quickly grokking what they can do on Webmaker.org. Plus: make it easy to browse through the list of skills in the Web Literacy Standard, finding resources and teaching kits for each.
It’s like an interactive text book for teaching web literacy.
The main writing challenge: what should the top panel say? The main headline and two blurbs that follow.
In my mind, this section should try do three things:
- State what this is. And why you care.
- Tell a story about the list of skills at left. When you hit this page, you see a list of rainbow-coloured words that can be confusing or random if you’re here for the first time. “Sharing. Collaborating. Community Participation…. Hmmm…. what does that all actually mean?”
- Focus on what users can do here. What does exploring those things do for you? What’s the action or value?
Here a start:
Teach the web with Webmaker
Explore creative ways to teach
through fun making and sharing, backed by the
global Mozilla community’s Web Literacy Standard.
Free. Open source. Fun.
Each skill has free resources and teaching kits anyone can use to teach others –
to help create a more web literate world.
April 11, 2014 08:22 PM
We hope the week has treated you all well - in most of our time zones, the temperatures are reaching very friendly temperatures, and you know what that means: daylight extends beyond work hours now!
We’ve had a great week with badges - this week on the Community Call we looked at some of the common challenges and lessons learned from those who have developed / are developing badge systems in the new ecosystem. We were joined by some of those we spoke to when writing our initial case studies, which was great!
Kim Carter joined this week’s Research & Badge System Design Call for a deep dive into the QED learning ecosystem and competency-based education with her colleague, Elizabeth Cardine, and a QED alumna, Raven Gill.
What else did we get up to this week?
In celebration of spingtime finally arriving, here are some dancing badgers for your Friday smile:
See you on Monday, everyone!
April 11, 2014 06:58 PM
April 10, 2014
Call recording: https://archive.org/details/April9CommCall
This week on the Community Call we looked at some of the common challenges and lessons learned from those who have developed / are developing badge systems in the new ecosystem.
Our Global Coordinator Jade worked with HASTAC’s Sheryl Grant to draft our initial case studies, which are published on the Summit to Reconnect Learning website. Nate Otto has been working with Dan Hickey and a team of researchers at Indiana Univeristy on the badge Design Principles Documentation project, which has looked at the badge systems developed by the grant recipients from the fourth DML Competition, “Badges for Lifelong Learning.” Nate has also started writing a set of working examples from these 30 grantees.
They were joined by a number of representatives from the organizations interviewed for both sets of case studies to dive into some common road blocks and lessons learned that might help future badge system designers.
It was great to hear people sharing their experiences on the call - click the link at the top of this blog post to listen to the call in full, or read on for a summary of the discussion!
Common Challenges and Concerns
There were many questions and concerns about how to start developing a badge system by those we spoke to. Here are three of the most common challenges foreseen or encountered as organizations began designing their systems:
This was a particular concern among those in schools and colleges, where faculty and staff are already very busy. How can an institution begin to integrate badges that require some level of staff engagement in such a way that is seen as valuable and rewarding to the staff?
- Lack of technical resources
This was a common challenge faced by early adopters of badges across numerous sectors. As much of the open badge standard requires some technical knowledge, many organizations recognized they would need someone on their team to provide technical support, or to form partnerships with another organization.
The recent release of BadgeKit was a result of acknowledging the technical barriers to badge issuing. Future versions will include even more features and accessibility, making it easier for organizations to join the ecosystem.
- How to ensure badges have value
Badge value (or rigor) is a concern of many who are new to the ecosystem. Carla Casilli recently laid out her thoughts on the ‘myth of the lightweight badge,’ where she argues all badges can play a valuable role in identity building as well as showcasing skills and recognizing various forms of learning. Many organizations developing badge systems had to address the question of whether their badges would be valued - by students, or teachers, or employers - and, in some cases, how to ensure their value extended beyond the learning environment.
Think about the potential for your badge system to expand, but don’t try and do too much, too fast. Start with the basics, the minimum you want to achieve with your badge system, and once you’ve built a strong foundation, it will be easier to expand. That could mean starting with one class or grade before expanding to badge an entire school, or focusing on a certain type of professional development or informal learning exercise before encompassing others.
It’s exciting to think of the many possibilities for badges when starting out, it can feel overwhelming to try and develop a system that covers everything from the beginning. Break it down so that your system development happens in stages, allowing you to build a robust foundational badge system and address feedback and potential problems before expanding.
- Focus on goals, and identify ‘success’ for your badge system
For badges to be valuable, they must be tied to valuable experiences. By thinking about the learning or development objectives for your badge system, you can think about the kinds of activities, criteria, and evidence that will be suitable for your community, whether that’s in a school, workplace or network.
Think about what it will mean for your badge system to be successful. Will it mean that students gain academic credit for informal or out-of-school activities represented by badges? Or is it a way for teachers (and students) to track students’ progress? Do you want your staff to be recognized for their professional development in a way they can show to employers and peers? Or a way to identify workers whose skill sets align with industry standards?
Once you’ve outlined your goals and identified what ‘success’ means for your badge system, you can start to think about how to get people there, and the role badges will play in that progression.
- Know your resources and limitations
As well as technical barriers, there are other potential limitations to consider, including time, money, and people needed to develop your badge system. This is a good reason to start small - the more complex your system, the more costly it will be to implement, so again, think about the minimum successful foundation of your system. This will give more time to gain wider acceptance, support, and resources for future expansion.
- Think carefully about partnerships
Partnerships can be immensely valuable in building a badge system, whether they provide technical support, funding, or endorsement of badges. However, it is important to make sure you find the right partner for your organization. Take your time, do your research, and find the partner that is best suited to your needs (or restrictions.)
- Think about existing frameworks
Badges are often slated as a disruption, designed to act instead of current methods of credentialing, when they often play a supplementary role. If your school, workplace, or network uses existing frameworks or standards to guide learning or development, this could be an asset. Not only can these structures potentially add value to your badges, they also provide a map of what is already there, so you can identify places where your badging objectives overlap, and gaps your badges can fill.
- Allow more time than you think you’ll need
Cliff Manning once wrote he suffered from “Badge Eye," a condition where he sees badges everywhere, and many badge enthusiasts and evangelists find themselves in similar situations.
As badges are a relatively new concept for many people, you may find that your team and community need time to “buy in” to the idea. Give them time - and provide resources to help educate, inform, and support those in your organization you want working with the badges.
Allow more time than you think you’ll need for faculty / staff / student / administrative / stakeholder buy-in. The more support you have going in, the smoother the process is likely to be.
If you are starting to develop a badge system - or thinking about it - there are many places to go for support, guidance, advice, and resources. We listed them in a recent blog post, and we’re easily reached by email at firstname.lastname@example.org
Good luck, badge pioneers. We look forward to seeing more exciting badge systems emerging!
April 10, 2014 09:57 PM
Open Badges Research & Badge System Design Call, April 9, 2014
Speaker: Kim Carter, QED Foundation
Kim Carter, who shared her work at the QED Foundation with the Community Call back in November, joined us again this week for a deep dive into the QED learning ecosystem and competency-based education with her colleague, Elizabeth Cardine, and a QED alumna, Raven Gill.
The QED Foundation’s work aims to encompass all learning, not just for youth, but also focusing on at-risk and adult learners as well as encompassing student-driven, competency-based learning strategies inspired by their Theory of Change.
The Making Community Connections (MC2) Charter School mission is “to establish a sustainable network of multiple preschool through graduate school pathways for high quality learning that are student centered, mastery based, and community oriented.”
There are 5 beliefs at the center of their approach:
April 10, 2014 08:42 PM
April 09, 2014
Open Badges: Lessons Learned in the Developing Ecosystem
Today’s Community Call will look at some common themes from lessons learned across different develop[ed/ing] badge systems. Join us!
April 09, 2014 03:12 PM
April 08, 2014
Micro-Credentials: Empowering Lifelong Learners
Edutopia published this piece by Krista Moroder yesterday. Check out this very important paragraph hidden in the middle of the article:
"[B]adges could be a way to demonstrate skills to potential employers, build identity and reputation within learning communities, and create pathways for continued learning and leadership roles."
Did you catch that?
- Badges can demonstrate skills.
- Badges can build identities and reputations.
- Badges can create pathways to opportunities.
That’s some pretty important stuff, if you ask us.
Let’s work together to build rigorous standards for badge assessments and strengthen the value of #openbadges at the ecosystem level.
Read the article in full by clicking the link above.
April 08, 2014 12:20 PM
This weekend, I’ll be leading a Webmaker
Training for the National Citizens Service
(NCS). NCS is an organization in the UK that provides learning opportunities for young people living in England and Northern Ireland – young people who are encouraged to lead positive change within their communities. For the first time ever, NCS has invited graduates from their programs to become Digital Champions,
a group of people who will lead social action projects and spread web literacy skills in their local communities.
This is the Teaching Kit we’ll be using to guide us during the event. Let me tell you why I’m SO EXCITED to be doing this:
This is the first official “Webmaker Training”
I run trainings all the time, but they’re always one-offs, offshoots, and truncated versions of my dream learning scenario. In 2013 we ran two prototypes – a live training for Mozilla Reps called Training Days
and an online training called Teach the Web
, both were hugely successful. My dream learning scenario combines these two initiatives. I think a blended-learning program that is open, inclusive, and pedagogically sound – something that helps people teach the culture, mechanics, and citizenship of the Web – is what a Mozilla professional development program should be. Why? Because open
The NCS has been great to work with
I expect the young people who participate in the NCS Community are amazing as well. The partnership started when one of our Sr Directors, the fantastic Paula Le Dieu
, opened a conversation with some folks at the NCS to explain that Mozilla isn’t just a technology company, and the Web is not just a delivery mechanism for content.
She talked to them about what it truly means to be part of the Open Community and our values resonated. We were asked if we could teach some of the values and skills around openness and web literacy
while overlapping with NCS values around social action, personal responsibility and leadership. Spoiler Alert: Yeah, we totally can and will!
I’m truly excited to share what I love about the open source community with the NCS Digital Champions, while helping them level up their social and technical skills. I’m excited to hear their ideas, push them to think bigger, and introduce them to the support networks on the web. I’m excited to learn from them.
As an educator, I view the goals of this partnership (and future partnerships centered on Training) as being less about specific skills and more about big brained theories of education that say things like “You are educated when you can confidently and empathetically participate in society and the world.
The Digital Champions will help us grow
Last year, the Training Days graduates and the Teach the Web participants ran hundreds and hundreds of events, spreading Webmaker and digital skills. Our community's honesty, participation and drive has made Webmaker what it is today.
The 42 NCS Digital Champions are committing to running their own Maker Parties later this year. They’re also committing to spreading web literacy within their local communities and among their peers in the NCS community.
We’ll be inviting them to become mentors within our online training initiatives. In May, we’ll be inviting any and every one to participate in an online learning experience that will help you teach the web and become part of the open community. I’m hoping that this weekend seeds enough interest for the NCS Digital Champions to want to play around with the new and improved Training content
and discussion platform
It's going to be fun!
People who know me, know that I don't really get invested in things that don't entertain me. One of the reasons I love teaching is because I think it’s fun. It's fun to watch people learn, see what people make, share ideas and talk about stuff. I even think it’s fun to watch myself fail at relating to people. It’s fun to learn about myself, other people, the world, technology…Our agenda
has random, fun activities (ahem
) that are designed to get people moving, thinking and growing. I’m enthusiastic about what I do, and enthusiasm is contagious
. So, yeah, it’s going to be fun for everyone involved.
All of this means more people will become web literate, more people will spread openness, more people will champion the values we have.
*If YOU’RE interested in helping made the online components of Webmaker Training better, help us test them
April 08, 2014 10:42 AM
April 04, 2014
We’ve been trying to figure this out for Webmaker. Here’s a proposal:
- 1) Start small. Figure out our product testing strategy *for Q2.* (Instead of “everything we need to do to get better at testing.” Which feels too overwhelming.) What are the most important things to test and learn this quarter?
- Proposal: start with the key Engagement Ladder stuff. We’ve said those calls to action are the most important — let’s make sure they’re clear and feel good for users, and identify where they’re bailing or getting stuck. For example:
- Sign up. Create an account.
- Create an event.
- Make a teaching kit.
- Issue a mentor badge.
- Why start here? Because we’ve said these pathways are the *most* important. In terms of reaching our 10k contributors goal. We should do usability testing to see where users are getting stuck here, and ship incremental improvements to address those.
- 2) Focus on testing with lead users. People teaching the web. These users are signing up for Webmaker training, and will be using and offering feedback on Webmaker stuff over the next several weeks. This is a prime opportunity. What do we want to feed in there? https://wiki.mozilla.org/Webmaker/Testing
- 3) Unstick usertesting.com. aka:
Let’s make it easy for people to test whatever the hell they want, all the time.
- It doesn’t seem like we’re really making full use of usertesting.com as an asset. Let’s figure out why. (e.g., not sure of process / don’t have log-in / don’t have time / need training / ?) How do we make it easy and permissionless for our devs and designers to play there?
- For example: when Aali wants to test right-to-left in Popcorn, why can’t he just go ahead and do it? How do we make running a test on usertesting.com as easy and standard as writing a blog post?
- 4) Optimize the process for sharing out the findings. Understanding what we’re learning from this testing. And then feeding it back into the product. That’s always the hard part. I think we win there by doing usability testing on the small number of things mentioned in (1), rather than “let’s test everything.”
- 5) Update the Webmaker get involved page. This is where we’re sending folks now. Review and optimize.
What’s missing / wrong? Please comment here.
April 04, 2014 09:42 PM
What’s the best way to support Mozilla right now?
5 simple suggestions:
- Tweet some love using #mozlove or #standwithmozilla
- Use the “MozLove” avatar. You can download it here: http://mzl.la/mozlove
- Download Firefox. Or encourage others to switch http://www.mozilla.org/firefox
- Make a donation. Mozilla is a non-profit community dedicated to protecting the open web. http://mozilla.org/donate
- Get more involved with Mozilla’s non-profit mission. http://www.mozilla.org/contribute
April 04, 2014 07:59 PM
What’s up, badgers?
We could make a terrible (and belated) April fools’ joke here about badges being gone forever…..but that would be just cruel.
We’re not going anywhere, and neither are badges! Just in case anyone doubts us - here’s what’s been going on this week:
What a great week for badges! We hope you all have a wonderful weekend, and we’ll see you next week.
Tweet us at @OpenBadges or #openbadges with your badge news, updates and stories - we love hearing about your badgeriffic adventures!
April 04, 2014 06:21 PM
The order they’re listed isn’t relevant. The posts are nuanced; I’ve just captured a small part. I encourage you to read them all and will keep adding throughout the day. And you can find more on Planet Mozilla.
“We fully support Mozilla, their mission, and trying to build back up the bridges that got torn down. We know many people are going to be upset by Eich stepping down, and some of them might send out a lot of hate. This has been a traumatic time for us, and we hope to never have to post anything about this again. We are software developers and we’d much rather spend our time building great software and helping people than being involved in a horrible mess like this.” – Hampton Catlin
“Our biggest problem is that the world does not know the story of Mozilla. Especially as a progressive at Mozilla, it was hard to watch as people who should know better pulled out the Chick-Fil-A playbook.” – Ben Moskowitz
“One of the parts that is hard about this situation for Mozilla is that we don’t know where to draw the line now. People are worried that this is now a slippery slope, or that anyone could be pushed out because of outside views. I think as a community we need to accept the truth that Brendan wasn’t a viable CEO and figure out where this leaves the lines.” – Kensie
“I’m a supporter of traditional marriage, and I work for Mozilla. … Many people who agree with me on this issue are very upset about what happened to Brendan Eich, our co-founder and, for two weeks, CEO of the Mozilla Corporation. … I am assured by sources I trust that Brendan decided to leave of his own accord – he was not forced out. My understanding is that the senior management of Mozilla (many of whom disagree with him on this issue) worked very hard to support him, even if I would not agree with all the actions they took in doing so. However, he eventually felt that it was impossible for him to focus on leading if he was spending all of his time dealing with the continued, relentless news and social media storm surrounding the donation he made. In other words, he wasn’t forced out from the inside – he was dragged out from the outside.” – Gervase Markham
“Brendan’s choice of what propositions and political parties to support do not match my personal choices and I’m sad when any restrictions affect only one group of people. But at the same time, in a democracy, people must be able to support and express their values. And hopefully, in the best of worlds, that leads to a good discussion and greater understanding.” – Robert Nyman
“Instead of addressing the issues at hand, he very clearly dodged them. I’m really not sure why and I’m at a loss to even speculate. Every one of my friends said that while they didn’t agree with his position, if he just apologized it could have been the end of it.” – TofuMatt
“On one hand, I disagree with Brendan’s personal views and think that his choice to step down is going to be ultimately good for us. … On the other hand, Brendan has always been a strong, (seemingly) just technical leader at Mozilla and I can’t help but feel that he was railroaded out, which isn’t right and also goes against what Mozilla stands for, in my eyes.” – Lizzilla
“Supporting Prop 8 is beyond the pale. But I don’t fully agree with the tactics that some of my friends have used in order to make that point. IMHO, rather than spending our energy attacking Brendan Eich and Firefox (which affected the entire Mozilla community) we should have devoted ourselves to supporting our friends within the Mozilla community as they grappled (many of them publicly) with the biggest crisis they’d ever encountered.” – Josh Levy
“Even as Brendan announced his departure, he provided next steps to advancing the mission by reaffirming Mozilla’s focus on users. The direction he provided could put the non-profit Mozilla as a users union leader to push back the bullying aspects of the Internet that prey on individuals (think of privacy policies or terms of services) and instead flip that around to be pro-user.” – edilee
“Wanted: New CEO for Mozilla. Qualifications: No history of being wrong, ever.” – Brandon Savage
“If we have to learn anything from the past 10 days, it is that we can only survive as a community if we interpret this mission only in its most narrow scope, where can and should find common ground. Attempting to read the Manifesto in the widest possible manner and presuming to find that all of our fellow Mozillians have done so in the same way is the road to failure as a group and a community. Our cultural differences are immense and things which we find self-evident can be unimaginable to other. We should group among the narrow set of goals that unites us, not among what divides us.” – Garf
“What has Brendan done? Many things intrinsic to the open web; he helped shape technologies used by countless numbers of users, including to write and read this very post. Also, a hurtful and divisive thing based on a conviction now at odds with the law of the land, and at odds with my own conviction…” – aruner
“[Eich] did not understand that in order to be a CEO of a company, you have to renounce your heresy! There is only one permissible opinion at Mozilla, and all dissidents must be purged! Yep, that’s left-liberal tolerance in a nut-shell.” – Andrew Sullivan
“As a volunteer moderating the Facebook page, it was evident that we had many users complaining and very little supporters. Now that Brendan has resigned, everybody has all of a sudden come out from a shadow. Unexpectedly to say at the least, is that we’ve got users telling us that we were no longer protecting Freedom of speech and that rights are taken away. Where have these people been hiding?” – Andrew Truong
“It takes courage to face adversity in society, and that’s not a virtue I possess much of. Though I’ve come to value difference. Though at the same time, its important not to see valuing difference vs. valuing similarity as a dichotomy where you have to choose only one. We’re all similar in so many ways and sometimes, the difference is small.” – Chris Crews
“…what happened during the last days seems to be a negation of democracy. One should be able to express legal opinions without having to face a witch-hunt-like repression.” – Daniel Glazman
“Brendan Eich is one of the most inspiring humans that I have ever met. He is a true hero for many of us. He invented a programming language that is the heart and soul of the most open communications system the world has ever known… It’s important to remember that all heroes are also human. They struggle. And they often have flaws. Brendan’s biggest flaw, IMHO, was his inability to connect and empathize with people.” – Mark Surman
“If you tried, I don’t think you could engineer a situation that could throw the Mozilla community so thoroughly off-center. A lot of folks at Mozilla work here because we want to do what’s right. Doing the right thing can be hard, but overall we’re comfortable with taking on hardship to do the right thing.” – Dave Camp
“Follow the Mozilla mission on your own terms, because you know it’s the right thing to do. Do the right thing because it is the right thing.” – Ben Adida
“When the outrage was how a person with a different belief and – to me – very doubtful political action got made CEO people ganged up on Mozilla, my colleagues and friends and me how that could happen and how we can allow that. This was unfair.” – Christian Heilmann
“When suddenly the life my wife and I have built together seemed under any kind of threat, the monument of our public commitment to each other was the main thing to hold on to. Very often, critics of the notion of same-sex marriage seem to feel it can be reduced to something empty, as though symbolism carries no weight. As though legal constructs around civil partnerships, common law marriages, tax codes, inheritance rights and so forth suffice. All of that misses what’s important.” – Patrick Finch
“Because bringing diverse people with opposing views together, and asking them to fight for just what they agree on while looking past what they don’t, is how movements are built, and how they succeed. Period. Not how some of them succeed, it’s how all of them succeed.” – Ryan Merkley
“Soon, we were in the midst of a crisis, with the voices of reason so overwhelmed by outright nonsense that they couldn’t be heard. Several of us tried. We failed. Brendan, overwhelmed by the waves of negative press and outright hate mail he was getting, gave up and resigned. The mob won, and Mozilla lost its founding father.” – Sheppy
One of the things that is most painful to me about this is the sheer volume of misinformation out there. We all know that people are wrong on the internet all the time. It is probably hopeless to fight that, but for the record, these are the facts as I understand them, along with my interpretation of those facts.” – David Flanagan
Filed under: Mozilla
April 04, 2014 04:12 PM
Open Badges Research & Badge System Design Call, April 2, 2014
Speaker: Carla Casilli
We were fortunate to have Carla on the call, taking us on a deep dive into her work developing a foundational badge system design, which she has written about prolifically on her blog, which is a great one to bookmark if you are interested in badge research and system design: http://carlacasilli.wordpress.com/
The 3 Part Badge System
Over the past few years, many conversations have centered around badges and rigor – organizations are concerned about maintaining their public brand (and identity) which can sometimes limit the development of badge systems within those organizations. These are issues Carla had to address to help develop Mozilla’s 3 Part Badge System, nicknamed the 3PBS.
Much of Carla’s work into the 3PBS came out of her work developing the Mozilla-wide badge system, where there is both an all-encompassing voice, or brand, as well as a variety of teams within the organization that each have nuanced brands and voices. In developing Mozilla-wide badges, Carla was aware that these teams need badges which accurately reflect their own communities without being overshadowed by the organization-level badges.
To achieve this, Carla developed a badge system in three parts (details copied from Carla’s blog post):
- Part 1: Company / organization badges
Many companies and organizations have specific needs and concerns about branding. This system addresses those concerns directly. In this proposed system, an advisory group defines, creates, and governs the highest level of badges—the company / organization badges—providing control over the all-important corporate or academic brand. While not all systems have a need for such strict brand maintenance requirements, this approach allows for conceptual levels of badges to be created while interacting in organic and meaningful ways with other types of badges. An advisory group creates and vets these badges based on the organization’s foundational principles and values. The company/organization badges transmit the most important values of an institution and they address organizational concerns regarding brand value and perceived rigor.
- Part 2: Team / product badges
Few organizations exist that do not have some middle layer accomplishing the bulk of the work of the organization; the 3PBS proposal recognizes the team / product groups as necessary and important partners. In addition to acknowledging the contributions of this collection of folks, 3PBS engenders them with the ability to respond to their public through badges. Different teams and products groups can clearly and unequivocally communicate their closely held qualities and values through the creation and issuance of their own badges. These badges are created entirely independently of the Part 1 company / organization badges. In a bit we’ll discuss how the team / product badges play a role in influencing other aspects of the 3PBS.
- Part 3: Individual / community badges
So your organization is comprised only of management and teams? Of course not. The 3PBS honors the folks who are on the front lines of any organization—the community—by empowering them to define their values internally as well as externally. These badges operate outside the requirements that define the Company/organization badges and the Team/product badges. The community badges can be created by anyone within the community and do not hew to the visual requirements of the other two subsystems. What this means is that an individual or community can create any types of badges they like. In other words, it provides the ability to publicly participate—to have a voice—in the system.
To further explain these, let’s return to Carla’s blog post. Check out the call notes for the full conversation.
To read the original post on Carla’s blog, click here.
Introducing the 3 Part Badge System
This badge structure is the one that I developed for the Mozilla badge system that we are in the process of building. I’m calling it the 3 Part Badge System (3PBS). It’s composed of three interlocking parts and those three parts create a flexible structure that ensures feedback loops and allows the system to grow and evolve. Or breathe. And by breathe, I mean it allows the system to flex and bow as badges are added to it.
While some community member organizations have expressed a desire for a strict, locked-down, top-down badge system to—in their words—guarantee rigor (and you already know my thoughts on this), this system supports that request but is also designed to include active participation and badge creation from the bottom up. I’d say it’s the best of both worlds but then I’d be leaving out the middle-out capacity of this system. So in reality, it’s the best of all possible worlds.
This approach is a vote for interculturalism—or the intermingling and appreciation of cultures—in badge systems. Its strength arises from the continuous periodic review of all of the badges, in particular the team / product badges as well as the individual / community badges.
Don’t tell me, show me
It’s easier to talk about this system with some visuals so I’ve designed some to help explain it. Here is the basic 3 part structure: Part 1) company / organization badges; Part 2) team / product badges; and Part 3) individual / community badges. This approach avoids a monocultural hegemony.
The basic components of the 3 Part Badge System
How the three different parts influence one another in the 3 Part Badge System
How do these parts interact? In order to communicate how these subsystems can affect each other, I’ve created some color based graphics. You’ve already seen the first one above that describes the initial system.
But first a little basic color theory to ground our understanding of how these subsystems work together to create a dynamic and powerful system. The basic 3 part structure graphic above uses what are known as primary colors, from the Red, Yellow, Blue color model. Centuries of art are based on these three colors in this color model. The following graphics further explore the RYB color model and move us into the world of secondary colors. Secondary colors result from the mixing of two primary colors: mixing red and yellow results in orange; mixing yellow and blue results in green; mixing blue and red results in purple. Now that we’ve established how the color theory used here works, we can see how the parts represented by these colors indicate intermixing and integration of badges.
Individual / community badges influence team / product badges
The 3PBS concept relies on badge development occurring at the individual and community level. By permitting and even encouraging community and individual level badging, the system can will continuously reform itself, adjusting badges upward in importance in the system. That’s not to say that any part of this system is superior to another, merely that these parts operate in different ways to different audiences. As I wrote in my last post, meaning is highly subjective and context-specific.
Individual / community badges influencing the team / product badges in 3PBS
This graphic illustrates the team / product created and owned badges assimilating some badges from the individual / community created and owned badges. The graphic also indicates that the company / organization badges can be held separate from this influence—if so desired.
Periodic review by the team / product groups of the individual and community badges likely will reveal patterns of use and creation. These patterns are important data points worth examining closely. Through them the larger community reveals its values and aspirations. Consequently, a team or product group may choose to integrate certain individual / community badges into their own badge offerings. In this way a badge begins to operate as a recognized form of social currency, albeit a more specific or formalized currency. The result of this influencing nature? The team and product group badge subsystem refreshes itself by assimilating new areas of interest pulled directly from the larger, more comprehensive and possibly external community.
Team / product badges badges influence company / organization badges
Company and organization level badges operate in precisely the same way, although the advisory group who is responsible for this level of badge can look across both the team / product badges as well as the individual / community badges. That experience will look something like this in practice.
Team / product badges influencing company / organization badges in 3PBS
Periodic review of the team / product badges by the advisory group responsible for company and organization badges may reveal duplicates as well as patterns. Discussion between the advisory group and the teams responsible for those badges may indicate that a single standard badge is appropriate. Considering that teams and product group badges are created independently by those groups, apparent duplication among teams may not necessarily be a bad thing: context is all important in the development and earning of badges. That said, examination and hybridization of some badges from the team and product groups may create a stronger, more coherent set of company and organization level badges.
Individual / community badges influence company / organization badges
In addition to being able to examine and consider team and product level badges, the advisory group responsible for the company / organization badges can also find direct inspiration from individual and community created badges. Since there are few to no rules that govern the creation of the individual / community created and owned badges, insightful, dramatic, and wildly creative badges can occur at this level. Because they come through entirely unfiltered, those sorts of badges are precisely the type to encourage rethinking of the entirety of the 3PBS.
Individual / community badges influencing company / organization badges in 3PBS
Here we see how the individual / community created and owned badges can significantly color the company / organization badges. Since the company / organization badges communicate universal values, it’s vital that those values remain valid and meaningful. Incorporating fresh thinking arising from individual and community badges can help to ensure that remains true.
Three parts, one whole
So, if we loop back to the original system, prior to the (color) interactions of one part to another, we can see how each part might ultimately influence one another. This is the big picture to share with interested parties who are curious as to how this might work.
The 3PBS model with different types of influence.
Badge Alliance Working Group on Research
We are in the process of developing a working group focused on research which Sheryl Grant has kindly agreed to chair. This work will kick off in a few weeks. More about this a bit later in our call.
If you are interested in joining the working group mailing list, please reach out to Carla at email@example.com
To express interest in the other initial Badge Alliance working groups, fill out the form at badgealliance.org
April 04, 2014 10:21 AM
In 2012 the southern fried chicken restaurant Chick-Fil-A became the unlikely battlefield for marriage equality in America. Through a strange turn of events, same-sex marriage advocates and opponents converged on Chick-Fil-A franchises across the country. People lined up to buy chicken sandwiches in solidarity or to stage a boycott.
One thing’s for sure. If you eat at Chick-Fil-A, your money will support anti-gay causes. So if the long march of progress makes a fast food drive-thru a site of civic participation, well, that’s surreal—but it’s democracy in action.
This evening draws the conclusion of 11 disheartening days at Mozilla: the brief tenure of its co-founder as CEO. So why am I thinking about chicken sandwiches?
Eich is one of maybe a dozen living individuals who can claim to have built the open web. In 15 years of working at Mozilla, Eich never let his personal beliefs color his work. He and others grew Mozilla from a hobby into a world changing social movement. And, incredibly, they did it in a completely apolitical way.
But Eich as CEO was symbolic to a lot of people. It’s why people like Hampton Catlin and his husband, co-owners of a web development firm, took a stand. They and others called for Eich to apologize for funding the Prop 8 campaign or to step down. (I have complete respect for Hampton and have enjoyed several very constructive conversations with him over the past two weeks.)
The crisis that emerged over this issue was partially self-inflicted. We failed to manage the crisis. And a lot of our own people acted badly—from the top on down. We acknowledge this:
We didn’t act like you’d expect Mozilla to act. We didn’t move fast enough to engage with people once the controversy started. We’re sorry. We must do better.
At the same time, gestures from OKCupid and others show that our biggest problem is that the world does not know the story of Mozilla. Especially as a progressive at Mozilla, it was hard to watch as people who should know better pulled out the Chick-Fil-A playbook.
Contrast Chick-Fil-A with Mozilla. The Atlanta-based company has donated upwards of $5 million dollars to PACs opposed to same-sex marriage, and the company’s chief operating officer is on record that same-sex marriage advocates were “inviting God’s judgement on the nation.” Mozilla is a collective of happy mutants who want to make the world better, whose original logo was designed by Shepherd Fairey.
Mozilla was never Chick-Fil-A. A user’s decision to use Firefox would never fund anti-gay causes. The first reason is that we’re not a profit-seeking organization. The second reason is that we would never fund anti-gay causes!
We watched this week as Mozilla, a global non-profit and volunteer community making a free product to benefit humanity, was stained with the taint of homophobia, retrograde opinions, and hate.
It was an expensive moral panic. And though I am heartened that people like Andrew Sullivan feel the same:
Will he now be forced to walk through the streets in shame? Why not the stocks? The whole episode disgusts me – as it should disgust anyone interested in a tolerant and diverse society. If this is the gay rights movement today – hounding our opponents with a fanaticism more like the religious right than anyone else – then count me out. If we are about intimidating the free speech of others, we are no better than the anti-gay bullies who came before us.
…it’s still our fault. This was a critical test of our ability to tell our story, and we failed.
To many of the people who drew incorrect conclusions about Mozilla and our character, we might as well be selling chicken sandwiches.
What do we do from here? Mozilla needs to do a better job of explaining how we’re different. We need to play to our strengths—community, disruptive innovation, doing things in unconventional ways. Even in this storm, you could see some of those silver linings.
Mozilla needs to re-embrace the core of who we are and where we came from. In our products, in our initiatives, in our leadership. Let’s take on big challenges and pick fights again. Let’s not be like the other guys, and make sure the world knows it.
The great irony of all this is that Brendan Eich would have been the best person to return to us to these roots.
For the record, I don’t believe Brendan Eich is a bigot. He’s stubborn, not hateful. He has an opinion. It’s certainly not my opinion, but it was the opinion of 52% of people who voted on Prop 8 just six years ago, and the world is changing fast.
Most of this is ambiguous. Some of it is painful. I am equally disappointed in Mozillians and in demagogues who didn’t see the irony in hounding someone for their private opinion because of “intolerance.”
But one thing is clear: we need to treat all good people with respect and dignity, regardless of who they are or what they believe. I am glad now that the world will have a chance to know our character. And I am grateful to Brendan Eich for all that he’s done for the open web. I hope that in time he will find a way to return to the project and provide the technical leadership that Mozilla, and the world, so greatly needs.
April 04, 2014 12:49 AM
April 03, 2014
Open Badges Community Call, April 2, 2014
- Kate Radionoff & Leslie Voigt, Madison Area Technical College
- Phil Barker & Lorna Campbell, CETIS
This week we heard some updates from an exciting - and expanding - badge system at Madison Area Tech College, and kicked off a conversation about LRMI and badges.
Badges for non-credit learning
Kate Radionoff joined us in September 2013 after Madison Area Tech College (MATC) announced it would be launching digital open badges for their continuing education and non-credit professional development courses. This week, she returned with her colleague Leslie Voigt, the instructional designer behind MATC’s badge system, to take a deep dive into the work they’ve been doing and share some lessons learned along the way.
At MATC Kate was trying to shift focus away from seat time towards more meaningful assessment methods with non-credit learning. When she began exploring the potential of open badges, she began designing a way to integrate badgeable assessments into the existing non-credit learning experiences at MATC.
Around the same time, Pearson was preparing to launch their Acclaim platform and were looking for beta testers. After struggling to find a platform that worked within the school’s restrictions on open source code, the MATC system began using Acclaim, transitioning existing badges over to the new platform and adding new ones as students earned them. As of January 2014, the system is fully functional, badges and all.
As they move forward, they are looking to expand their badge system to a network of colleges using badges, including Anne Arundel Community College in Arnold, MD, and Harper Community College in Palatine, IL. Within MATC, the goal is for all professional development courses to be badged, to build industry partnerships, and continue in their efforts to inform and educate employers on the potential uses and value of badges.
Kate and her team recognized from an early stage the clear importance of alternative credentials and building learning pathways to translate non-formal learning into accredited recognition of learning. To help her design the MATC badge system, Kate enlisted the expertise of Leslie Voigt, who walked the group through the system and outlined the process badge earners go through in order to showcase their non-credit learning achievements.
Their badge system is in the process of expanding to include new classes, so they are focused on defining which classes will be badged – and how – including defining assessments and detailing learning outcomes to be aimed for. There are 120 badges to be rolled out this summer, encompassing multiple assessments within 25-30 new classes not currently part of the system.
Other features to be built out in the coming months are sharing badges to public profiles, expanding their network of colleges, and accessing data on the badges. As Leslie told the group: “people want to see numbers” – that means generating reports on the number of badges awarded, accepted, and published. They also hope to begin analyzing what badge earners are doing with their badges: what opportunities are the badges helping make accessible? Are employers valuing the badges? What learning or career pathways are their badges supporting?
Kate outlined a number of lessons she learned throughout the process of designing and implementing the MATC badge system:
- It might be useful, or even necessary, to find an instructional resource: it can be helpful to have a point person within the educational institution designing the badge system who can help guide others who may be issuing badges (in this case, the faculty)
- It is important to keep in mind that full time instructors are very busy, and will likely need someone to take the lead and connect with them about the badges
- Know your resources: you must factor in staff resources and work within the limitations of these
- Figure out your badge business model and design strategy ahead of time: by clearly defining your goals at the start, it is easier to work out the steps needed to get there, as well as defining what “success” means for your badge system. By doing this beforehand, you avoid ‘chasing your tail’ throughout the design and implementation process
- Faculty buy-in: allow time for gaining faculty buy-in and provide plenty of information and training sessions for them
- Employer buy-in: look at existing value structures or standards that can add value to badges and, if appropriate, work with these to strengthen your badge system
To read more about the MATC badge system, check out http://madisoncollege.edu/badges
To view or download Kate’s slides, click here.
LRMI and badges
Phil Barker recently pointed to the possibilities for connecting badges to LRMI (Learning Resource Metadata Initiative) in the Community Google Group, and joined this week’s call to kick off that conversation with the assembled call attendees.
Phil and his colleague Lorna Campbell both work with the Centre for Educational Technology, Interoperability and Standards (CETIS) on the Learning Resource Metadata Initiative (LRMI) which is funded by the Gates Foundation and led by Creative Commons and the American Association of Publishers. The platform is schema.org and the goal of this platform is to help identify different tagged attributes for resources on the web, from authorship to content.
The key feature that Phil sees as a potential link to badges is the alignment object, which indicates how a learning resource aligns to educational frameworks (e.g. identifying the structure of the Web Literacy Map and aligning resources to those components.) Phil and Lorna suggest it would be useful to align the Mozilla Alignment object with the LRMI Alignment object by drawing a connection between what both are addressing. LRMI is concerned with learning materials, and open badges are concerned with how to recognize learning. Phil asks: how can we accentuate the similarities?
LRMI tagging makes it possible for digital (learning) resources to show up in search engine results - it’s about discoverability of content. Extending that discoverability to types of badges available to be earned, tied to that content or to other existing standards, could be an interesting avenue to explore.
To read the discussion notes on LRMI and badges from the Community Call, click here https://openbadges.etherpad.mozilla.org/CCApril2.
Phil wrote about his experience on the Community Call on his blog: read it here.
To continue the discussion, head over to the Open Badges Google Group: http://bit.ly/OBgoogle
April 03, 2014 11:49 PM
Badges: New Currency for Professional Credentials
Session Session 8: Introducing Mozilla BadgeKit
This week on the #openbadgesMOOC, New Currency for Professional Credentials, Sunny Lee walked through Mozilla BadgeKit, the new set of open, foundational tools to support the entire badging process currently available in private beta for select partners developing badges for their communities. You can view Sunny’s slides here.
As many of our community members have already read, seen or listened to many different presentations introducing BadgeKit, we will take this opportunity to address some more frequently asked questions that we didn’t get to in our BadgeKit announcement.
What is BadgeKit?
BadgeKit is a set of open, foundational tools to make the badging process easy. It includes tools to support the entire process, including badge design, creation, assessment and issuing, remixable badge templates, milestone badges to support leveling up, and much more. The tools are open source and have common interfaces to make it easy to build additional tools or customizations on top of the standard core, or to plug in other tools or systems.
BadgeKit builds on existing technologies that have evolved out of several years of work and user testing, including Chicago Summer of Learning. In fact, specific tools within BadgeKit are currently being used for key partners within the badges ecosystem (i.e. Connected Educators.)
Mozilla BadgeKit is now available in private beta for select partner organizations that meet specific technical requirements. And anyone can download the code from GitHub and implement it on their own servers.
- Improves the badging experience for issuers, learners and consumers, by making badging easy to do.
- Closes the current gaps in the ecosystem by providing free, open badging tools to support the needs of issuers.
- Provides foundational tools needed to help grow and develop the open badges ecosystem.
- Builds our values of openness, interoperability, agency, choice, and connectedness into the way we recognize learning and skills, and helps shape emerging badge systems.
BadgeKit is open source, so improvements made by community members benefit everyone, from bug fixes to new features and more. It is also easily extendable, working seamlessly with other open tools and systems as they emerge.
While open badges technology has been gaining momentum - with more than 2,000 organizations issuing badges that align with the Open Badges system - there are still ways we can make it easier for organizations to join the ecosystem.
Today, there are too many gaps in the badging experience and many of the existing options are too closed, too expensive or too big. In fact, given the current options for organizations interested in issuing badges, it can be harder to make an open badge than a closed badge!
What tools does BadgeKit include?
BadgeKit provides modular and open options (standards) for the community of badge makers to use and build upon within their existing sites or systems. Currently, BadgeKit supports key points in the badging experience, including:
- Design: A tool for defining all of the metadata, including criteria pages, and finalizing visual design for each badge.
- Templates: Visual and metadata designs that can be remixed by anyone creating a badge.
- Milestones: The ability to have a group of badges level up to a larger, more significant badge.
- Assess: A tool for mentor or peer assessment that includes issuer defining rubrics and criteria for a badge, the ability for learners to apply for a badge by adding information and evidence, as well as access for assessors to manage applications and enable review and scoring.
- Issue: A tool for awarding badges to learners and hosting assertions to enable badges to be pushed to Backpacks.
- Collect: A “Backpack” for collecting badges across various experiences or organizations.
Throughout 2014, we will be adding additional tools to BadgeKit, including:
- Discover: A directory of available badges with features for searching, filtering, wish listing and endorsing badges.
- Share: A tool to enable easy sharing of badge on various sites across the web (i.e. Facebook, Twitter, Tumblr, etc.).
- Collect: Backpacks will become “federated”, meaning that different instances still plug into the broader ecosystem and can share data across.
How can I use BadgeKit?
Mozilla BadgeKit is now available in private beta for select partner organizations that meet specific technical requirements. And anyone can download the code from GitHub and implement it on their own servers.
SOFTWARE AS A SERVICE: At BadgeKit.org, you’ll be able to access BadgeKit: a hosted version of the tools to build out badges, remix badge templates, create badge levels, issue badges, etc. APIs will make it easy to then pull the badges and end user interfaces into your own website. All of the backend pieces are hosted, supported and updated by Mozilla, and you’ll have complete control over the experience of your end users through your own sites.
DOWNLOAD: Easily download the code from https://github.com/mozilla/openbadges-badgekit and install the tools on your own server.
What’s the difference between downloading the code from Github and using the private beta version of BadgeKit?
In downloading the BadgeKit code, you will be in charge of the backend and hosting of BadgeKit, and will be able to customize and extend the tools as much as needed.
For the private beta version of BadgeKit, all the backend pieces are hosted, supported and updated by Mozilla, while you still have complete control over the experience of your end users on your own sites through our APIs.
Is BadgeKit available now?
Yes - Mozilla BadgeKit is available in private beta for select partner organizations that meet specific technical requirements. Visit www.badgekit.org to learn more and apply for private beta access.
And BadgeKit code is currently available on Github, with additional features set to be added in the coming months. To download the tools, visit Github: https://github.com/mozilla/openbadges-badgekit.
How can I sign up for BadgeKit?
Mozilla BadgeKit is available in private beta for select partner organizations that meet specific technical requirements.
To apply for private beta access, visit www.badgekit.org. Given your organization meets the specific hosted version requirements, you will receive a follow-up email with full details on how to get started.
What are the technical requirements for the hosted version of BadgeKit?
The technical requirements necessary for private beta access to the hosted version of BadgeKit are:
- You have a front end website or have resources to develop one
- You have technical resources on staff to integrate the BadgeKit APIs into your experience
- You intend to build or roll out a badge system for your community and organization in 2014
How are you selecting partners for the private beta?
Right now we’re making that decision based on each organization’s technical resources and capacity. But by the end of 2014, the hosted version will be available to any organization looking to implement a badging system!
Who is BadgeKit for?
BadgeKit is currently in private beta and can be used by any issuing organization that meets specific technical requirements. It is aimed at organizations that are building full badge systems and want to leverage their own sites and systems on the front end, as well as have access to technology resources. Tool providers might also be interested in leveraging BadgeKit to extend their own tools, or build additional customizations on top of BadgeKit.
I am a middle school teacher looking to issue badges. Can I use BadgeKit?
Not yet. Today, BadgeKit is currently in private beta and meant for organizations that have access to technology resources and are looking to implement a full badge system. We are exploring ways to create a lighter weight version of BadgeKit that could be used by individuals, and hope to have it ready later this year. In the meantime check out the additional community driven issuing platforms at http://bit.ly/platform-chart to help you get started.
I want to issue a badge to a large group of people at one time. Is that possible?
Not yet - but we’re working on it! You can track progress in Github here: https://github.com/mozilla/openbadges-badgekit/issues/205.
I need help. Is there someone that can help me?
We have a variety of ways we can help. You can simply select the option that best meets your needs:
You can download a printable version of this FAQ to share with your communities, and Sunny’s slides from the live session are available here.
April 03, 2014 08:11 AM
April 01, 2014
My latest post for DMLcentral is up. Entitled Why I still believe in badges, it’s a response to a comment by a Philosophy professor (who will remain anonymous) that Open Badges are merely a way that for-profit companies can get a slice of the action in Higher Education.
A quotation from the article:
While badges could, potentially, be used for nefarious purposes, it’s my belief that the open, distributed architecture of the code and community means that we can seek to improve our education both inside and outside the walls of institutions. This is not about ‘disrupting’ education for the sake of it or for private profit. This is about providing another way of doing things to promote human flourishing.
You can read the whole thing at DMLcentral. Please do comment over there (I’ve closed comments here).
April 01, 2014 09:20 AM
March 31, 2014
It goes without saying that Mozilla is an open organization, they promote the open web, promote open source software, and advocate for open learning, open journalism, and even have a pretty badass manifesto. Given the enormous number of companies involved in the badging ecosphere, (see above) who do you want to develop the plumbing that keeps all this together? A company that sees every eyeball as a dollar sign? Or a foundation built on the principals of open source?
I wrote the above soon after joining Mozilla. I still agree with it. Mozilla is the best community I’ve ever been a part of. I care deeply for it. On Thursday, March 27th, almost exactly two years after I wrote the above – and a short time after participating in a Mozilla Foundation discussion about the appointment of Brendan Eich as CEO of Mozilla, I tweeted:
The wording of the tweet was provocative. “I am an employee of @mozilla” makes it clear that my voice in this situation has more power and more responsibility than a non-employee. I chose that wording. I wanted to be clear and unequivocal. Other wording was just as intentional. I didn’t ask Brendan to resign, I asked him to step down as CEO. I didn’t demand, I asked.
When Brendan was announced as CEO, my hope was that he would explain himself, maybe apologize or recant his actions of 2008. Six years is a long time; maybe now he understood the larger context of Proposition 8 and its terrible effect on thousands of Californians. Instead, he was wholly unprepared to speak about the issue. We waited, being told he would write a blog post that would clear things up. The post came, but was underwhelming, and he neither apologized nor offered an explanation for the donation.
In the meantime, Christie Koelher wrote an amazing post explaining that though she disagreed with Eich on the subject of same-sex marriage, she trusted him, and the organization, to not let his personal views cause harm to Mozilla employees. Fundamentally, I agree with Christie – it would be impossible for Brendan to discriminate within Mozilla; he wouldn’t be allowed to exercise his personal views of same-sex marriage in a way that discriminates against employees. There are plenty of checks, both within Mozilla and legally that would protect employees from Brendan’s personal views.
I didn’t ask for Brendan to step down because I was worried he’d discriminate against those in his reporting chain. If that was the case, I would have asked in 2012 when this story originally broke (just a few short weeks after I joined the organization).
So why tweet at all? This morning, Mark Surman, one of the key people who make me proud to be a Mozillian, wrote “I worry that Mozilla is in a tough spot now. I worry that we do a bad job of explaining ourselves, that people are angry and don’t know who we are or where we stand. And, I worry that in the time it takes to work this through and explain ourselves the things I love about Mozilla will be deeply damaged. And I suspect others do to.” I agree with him, we as Mozilla are in a tough spot now. So again – why did I tweet? Why risk damaging a community I love so much? I want to be absolutely clear: I never meant to hurt this community, everything I’ve done has come from a place of love, love for this organization, love for the community it built, and most importantly, love for the people who make it possible.
This very public debate about Brendan’s appointment points to a divide in Mozilla’s identity, which I’d characterize as Mozilla as tech company versus Mozilla as activist organization, which is the fundamental reason why I believe the Brendan Eich that contributed to Prop 8 isn’t the CEO that Mozilla needs. Our power as an organization comes from our ability to assert technology as activism. Webmaker, Open Badges, Web Literacy, a smart phone that puts the web in every hand, the protection of privacy and identity in the face of attacks from every corner.
Mozilla is a leading organization in the fight for an open web. That’s well established. Less known is Mozilla’s role in open education, open journalism open research / science and web literacy. An open web is a tool to empower individuals. To paraphrase Woody Guthrie’s guitar, “This [internet] machine kills fascists.” That’s the open web we’re fighting for, a machine that ends human suffering, a machine that won’t let a government stop our sons and daughters from loving who they choose. An open web not tied to a mission like essential human freedom and empowerment is an empty web.
Our manifesto is vague on this point, “The Mozilla project is a global community of people who believe that openness, innovation, and opportunity are key to the continued health of the Internet.” We promote the health of the internet, but never make the bigger connection to the health of humanity. We interact with organizations who accept that goal, but take it one step further, their goals aren’t just the health of the Internet, their goals are the health of humankind, of the planet, of our place in history.
Mark once quoted Mitchell as describing projects as rockets. A rocket is a thing, but in every rocket, there’s a payload. The payload can be anything, a belief that the web should be open, that open source is a fundamentally different paradigm of work. Paraphrasing, “a rocket without a payload isn’t worth anything.” The payload of Mozilla is human freedom through technological empowerment. Those are my words, my interpretation of the Manifesto, but I can’t imagine anyone in the organization, even Brendan, disagreeing with them.
In a blog post yesterday, we go beyond the Manifesto and state, “Mozilla’s mission is to make the Web more open so that humanity is stronger, more inclusive and more just. This is why Mozilla supports equality for all, including marriage equality for LGBT couples. No matter who you are or who you love, everyone deserves the same rights and to be treated equally.” Maybe Brendan can lead us on that path by showing how a person can change, as an example of how a community can change.
March 31, 2014 02:41 AM
March 28, 2014
What a week it’s been at Mozilla. We are so lucky to be part of such a varied and supportive working community - especially on the badges team (though we might be biased!)
Here’s what we’ve been up to this week:
- On our Community Call this week Barry Joseph kicked off a great conversation about how to foster communication across our networks - for a full summary and a link to the audio download, click here
- On our Research + Badge System Design Call Verena Roberts took us through her work on integrating informal and formal learning with competency-based learning and badges - for a full summary and a link to the audio download, click here
- Erin Knight, Executive Director of the newly formed Badge Alliance, dug into the Alliance tagline and how it’s going to drive the initiative
- Jade outlined some of the team’s transitions from the badges team to the Badge Alliance leadership group
- Lucas Blair wrote a guest post for the Open Badges blog on the Discovery Project interview process and how people’s stories become their learning pathways
Badges have had some shout-outs in the wider world this week too:
It’s been a long week: go and enjoy your weekend, relax, dance, sing, read, sleep - find your happy places - and we’ll see what Monday brings!
March 28, 2014 11:04 PM
Research & Badge System Design Call: March 26, 2014
Speaker: Verena Roberts
Verena Roberts spent the last six months working on a final project for her Masters in Educational Technology Degree with the University of British Columbia. Much of her work investigated integrating formal and informal learning and how to develop learning pathways for m101, a pilot course in mobile learning at UBC. Open badges plays an important role in the research and proposal suggestions, which can be found on her blog.
To see Verena’s presentation document, click here.
This question was at the heart of Verena’s work, and her presentation to the research call attendees. Originally, Verena was more
Conclusions & next steps
March 28, 2014 09:09 PM
Community Call, March 26, 2014
- Barry Joseph, Associate Director For Digital Learning, Youth Initiatives, American Museum of Natural History
This week we opened up an important discussion around how to strengthen and expand the badging ecosystem through increased knowledge-sharing and platforms for communities to come together and learn from the experiences of others.
Let’s keep talking
In a recent blog post, Barry made a call to action - or rather, a call to conversation:
"If we advancing digital badging systems want to solve the major challenges before us — badging networks that link learning organizations to each other and to career and academic opportunities; badge system designs that can offer different value to different youth; comprehensive, elegant and flexible tools; and more — we need to start painting the full picture. Let’s welcome newcomers to this important project not by asking them to rebuild the wheel but to learn with us through public and honest self-reflective practices."
In his own badging explorations, and those of others he has worked with and spoken to, he found that many who are starting out with badges seem to come up against the same obstacles, and wonders if there is a way to avoid or diminish these blocks by sharing more about what we know, how we got there, and lessons learned along the way.
In 2008, Barry was working at Global Kids on a project to help youth develop metacognitive skills, for which they would earn badges. He has since worked with the first Hive network, in New York, and now works on digital learning programs for youth through the American Museum of Natural History.
In each of these endeavors Barry has worked with badging programs, and has heard the same struggles many times. In participating in badging initiatives, he has observed that much of the dialogue has been split, with the positives of badging being presented publicly - and often in response to a general set of concerns, whether actual or perceived. On the other hand, the problems faced by those building badges were often discussed internally rather than shared
There are weekly Community Calls that explore many open badges topics, including new and ongoing open badges projects and related initiatives
We also host weekly Research Calls that dig deep into varied projects related to badges, and the development of badge systems across numerous sectors
We also have a number of active social media channels that are monitored daily and can be a source of news, updates, answers, and resources:
We even have spaces for the technical among us to explore new ideas, report issues and collaborate to make the open badging ecosystem stronger from the inside out:
- The Open Badges Tech Panels are held on the 2nd Wednesday of each month. These calls are a place for our team and community contributors to explore technical topics within open badges. It provides our developers and engineers a chance to share prototypes and new ideas, and for community members to raise questions and give feedback in an informal setting
March 28, 2014 06:36 PM
Is not a conversation about inclusion. That was settled long ago. And Mozilla, unlike many organizations, treats our mission and our guidelines as sacred texts.
It’s also not a conversation about quality of life and the culture of the workplace. I’ll let my colleagues speak for themselves.
So if it’s not about the applied and the tangible, it’s about the symbolic and the intangible.
Our conversation is about rights.
Specifically, two rights: Equality and Free Speech. And which one this is.
The free speech argument is that we have no right to force anyone to think anything. We have no right to prevent people from pursuing their lives based on their beliefs. That what matters is their actions. And as long as they act in the best interests of the mission, as long as they don’t impose their beliefs on those around them, they are welcome.
The equality argument is that this isn’t a matter of speech. That believing that 1/n of us aren’t entitled to the same rights as the rest of us isn’t a ‘belief’. That the right to speech is only truly universal if everyone is equal, first.
Both sides are well represented inside Mozilla. Often by the same, conflicted people.
Our current situation is forcing us to choose between them.
And that sucks more than most of us can express in words. And we’re desperately trying to find a path forward that doesn’t wreck this beautiful thing we’ve built.
Filed under: Mozilla
March 28, 2014 05:13 PM
Best tweet I saw yesterday
Mozilla needs your love and help right now. More than just a debate about our CEO, this threatens to divide us in other ways if we let it. We need dialogue, and to bring open hearts and minds around the two crucial issues here — both of which are meaty and substantive and vitally important to Mozilla:
- (1) We don’t need to agree on everything — or force ideological consensus — in order to work with others. That’s a vital part of Mozilla’s open culture and mission. A lot of people have fought for this principle. It’s at the heart of what makes open source vibrant, diverse and practical. And it’s a fragile thing worth protecting.
- (2) But there are limits to that openness — and those limits center around basic rights. The world has changed. For many (including me), marriage equality is now a rights issue — and no longer just a speech or “personal opinion” issue. So when colleagues frame this purely as a matter of personal opinion, they signal to others that they don’t understand or haven’t considered this difference. That’s why simply doubling down on “freedom of speech” or personal opinion arguments will not work as a way to work past this. The situation requires more.
This is hard. It deserves to be treated that way. Many of us feel very strongly about either or both of these issues — and so it requires nuanced, Mozilla-style reasoning that weighs both sides to find a solution.
That’s why I’m so proud of thoughtful, emotionally complex posts from colleagues working this through in the open. Like this, or this. And disappointed by stories like this one.
If you believe in (2), as I do, I think we’re served by demonstrating patience and compassion here. The difference between marriage equality as a right versus a matter of political or personal opinion is nuanced, historically recent, and culturally complex for a global community like Mozilla’s. And it’s on us to demonstrate that we understand and show respect for (1) as well, and not skip it over casually. For a lot of people, it’s at the heart of the Mozilla project.
Our ability to work this through — together in the open, with open hearts and minds — is even more important than any decision about our CEO. It will determine our strength once all this is done.
March 28, 2014 04:29 PM
March 26, 2014
Lucas Blair, an educational game designer and badge curriculum superstar, has been working with Chloe Varelidi, Mike Larsson and others to drive the Open Badges Discovery project. The project team recently joined us for a Community Call in which they gave an overview of their process and findings thus far.
Below is a guest post from Lucas that takes us through the interview process and how people’s stories become their learning pathways.
Follow Lucas on Twitter: @LucasBlair
Tell us your story
Collecting real stories and turning them into pathways has been an important part of the Open Badges Discovery project. The stories allow us to test our designs against real use cases and some will even launch with the tool as examples. In this blog post I will share the process that we use and some tips to get the most out of your pathway interviews. Keep in mind that this process is written in a blog, not in stone. Like everything that comes out of Mozilla, you are encouraged mix it up or discard it entirely for a process that you like better. If you do find a better way, please share it with us and the community.
Pathways are stories. Sometimes those stories come from issuers that would like to see specific skills in their applicants or others who want to help their current employees grow. Some stories come from earners recalling the experiences that got them to where they are now. Other tales are aspirational, like those of students who set goals with their pathways, by identifying badges that they want to earn some day. No matter who is telling the story, to effectively capture it you have to ask the right questions when the interviewee needs your help and get out of the way when they don’t.
We decided to make a distinction very early in the process between issuers and earners because they have different needs and will have different stories. Issuers create pathway templates that make suggestions about the the types of badges they would like to see. Earners complete the pathway templates with the badges they have earned and fill free spaces with unearned badges that are goals. The good news is that the interview process is the same, just from different angles. For example you ask an issuer “what skills do you want to see?” and you ask an earner “What badges have you earned?” For both questions, as an interviewer, you are trying to identify badgeable moments.
After introductions I start interviews off by defining what badges and pathways are. Remember that what we are building is still relatively new to most people. I say something like:
- Digital badges - A visual representation of your skills and experiences. A digital credential.
- Pathways - A collection of digital badges organized in a way that gives additional meaning beyond the information provided by the badges alone. (Metaphors work well here too, like constellations or trees).
I take some notes up front so I can easily identify the interview later. Typically things like name, current occupation, and a determination of whether the person in an issuer or an earner. For the last part what you are really asking is are you capturing someone’s story or are you trying to determine what they look for in a candidate (hiring or admissions for example). Then it is time to dive in. Ask interviewees to start from the beginning. Take notes as they speak and don’t be afraid to ask them to repeat a section, add detail to a section, or redirect them if they get off track. Do not feel like you have to identify all of the badgeable moments during the interview. There will be plenty of time afterwards to turn your notes into badges and pathways.
Using the badge types
Over the course of our interviews a few badge “types” or groupings have emerged. The groupings are used during the interview process to make sure we don’t miss any important details. Before you begin interviewing, going through the list of the badge types may help your interviewee tell their story and will make the interviewers job of identifying “badgeable moments” easier.
- Jobs/Volunteering - Badges for doing specific job or volunteering
- Interest/Project/Hobby - Badges that identify an interest, a project, or a hobby
- Group/Affiliation - Badges for activities done in a group or identifying affiliation with a group
- Events - Badges for attending or participating in events or traveling
- Attribute/Habits - Badges that define character traits or attitudes
- Awards/Honors/Titles - Badges that identify a certification, an award, or a title
- Skill/Knowledge - Badges that represent a skill or possession of knowledge
Don’t be content working only in the past tense. When an interview ends always ask them “what’s next?” This will make them think about their goals and give you an idea of the trajectory of their pathway.
Using the pathway types
Stories have a shape and as you listen to someone’s pathway story you should be able to fit them into one of, or a combination of, our pathway types. These pathway types, just like the badge types, have changed during the course of the project. You don’t have to identify the pathway type during the interview but if you are able to, it can help you guide the conversation.
- Linear - These pathways are the easiest to follow. They move sequentially through time. I try to identify natural stopping points to go back and ask for additional details.
- Tiered - The tiers are often times the “natural stopping points” from the linear pathway. They are like chapters in a story (e.g. Middle school, High school, College, First job, Second job).
- Freeform - Badges floating in space in no particular order. These are the hardest interviews to follow because interviewees just start listing badgeable moments. I try to push these interviews to at least follow a timeline.
- Cluster - Clusters are a way to add some structure to freeform pathways. Think of a cluster as a way to add gravity to the freeform badges that float into space by grouping badges that share a type. For example someone saying “These are my leadership skills” or “This area is for communication skills”
- Hybrid - A combination of some of the pathway types above. For example, interviewees in many of our early conversations listed jobs, projects, and skills in order (Linear and Tiered) then at the end listed attributes (Clusters). This lead to the creation of a new pathway type we call the RPG pathway because of it’s resemblance to role playing game interfaces.
It is time to break out the post-it notes! If you have the opportunity to do interviews in-person, paper prototyping pathways is a great way to capture a story. You will start by explaining badges and pathways. Then give the interviewee post-it notes, a marker, and a flat surface. During the prototyping sessions you can ask for additional information like having them draw connections between different badges or arrows to show prerequisites. These sessions are also great for asking things like “If you could leave the past version of yourself a message along this pathway what would it be” great for capturing mentoring moments.
I just want to end by saying that almost every person that I have interviewed for this project has begun our conversation with some variation of the phrase “Just so you know my pathway is pretty unique”. I have to say that so far they have all been right and that has been one of the biggest takeaways for me during this project. Every person has a great story, an important need, and some inspiring goals if we just take the time to listen and create tools that make their stories come to life.
March 26, 2014 02:23 PM
Read the original post here.
When we decided to soft launch the Badge Alliance at the Summit to Reconnect Learning, my Communications Director had about 5 days notice to pull everything together. She did, of course, pull everything together as she always does, but there was definitely some throwing ‘good enough for now’ words up on a site at the last minute. As we are starting to more formally kick off some branding work, we went back to the tagline we used. While it might not be where we end up, there was and is a lot of truth in those words, and there are layers that really get to the heart of what we’re trying to do (and I suppose, what we’re now on the hook for doing!)
The Badge Alliance is “a network of organizations working together to build and advance an open badging ecosystem”
Let’s break that down a bit…
"The Badge Alliance is a network of organizations…"
The Badge Alliance is made up of organizations that want to work on these issues together, want badges to succeed, believe in a similar vision. These organizations (and in some cases, individuals) are volunteering to contribute to working groups, to roll up their sleeves and do the work necessary to move the badging work forward. They are the lifeblood of the Alliance, and of the ecosystem we are building.
After a relatively low profile soft launch, we already have close to 300 organizations that have not only expressed interest in the Badge Alliance, but have signed up to participate in at least one working group. In many cases, they have signed up for several. The initial response has blown me away and I am more convinced than ever that the Alliance is so important and timely.
One of the reasons we have created the Badge Alliance is that this work is so much bigger than any individual organization. It’s going to take a village. It’s going to take an ecosystem. That means non-profits, tech providers, agencies, institutions, schools, corporations, foundations have a role to play. It’s only through connection and collaboration across these organizations and sectors, that we will make significant progress for learners and workers across their lifetimes.
As I mentioned before, we’re pretty serious about the collaboration part. So much so that the Badge Alliance is completely built around working groups. All of the work is/will be done through working groups. All of the key issues are tackled through working groups. Most of our job will be to facilitate, recruit for and shepherd working groups. Working groups, working groups, working groups! We’re all probably going to start getting so sick of hearing those words, we’ll have to make up some others. Constellations! Action teams! Etc. But for now, working groups.
It’s a super exciting approach with lots of potential. We’ve already got a really healthy mix of organizations that seem energized and ready to dig in. But its also a little scary. I’ve always been of the ‘if it needs doing, I’ll just do it" mentality, but now our role will to wrangle, recruit and ultimately rely on lots of different players to move the ball forward. Again, together is the only way we succeed. We’ve been spending the last couple of weeks trying to create some guidelines and process to create a layer of accountability and confidence in working group outcomes, which we’ll share in the next week or so, but really these are working theories. This is going to be a constant work in progress, with payoffs so much bigger than any of us could accomplish on our own.
"…to build and advance…" (Or "…to build and grow…")
This is a pretty heavy piece. Building and advancing. What does that mean? Where do we start? What does success or advancement or sufficient growth look like? One deliverable that we are on the hook for, with our Steering Committee, is an initial definition of umbrella goals, strategy and metrics for the badge ecosystem, that we will then vet with the broader network. This will help to provide a larger context for all of your work, while also connecting work across the ecosystem, highlighting gaps or new opportunities to put some attention into and giving us all way to determine if we are winning.
But we don’t need that, and frankly, can’t wait for that to keep the momentum going. Each of you can probably list a few things that you think are needed to advance the broader badge work, or maybe even your own badge systems. Issues that need tackling, hurdles that are in the way, use cases you need to see, questions you need answered…I guarantee if you all did write them down, there would be a lot of overlap. And I can also guarantee that we’ve probably been talking about many of them since very early on. So let’s stop talking and dig in. That’s the purpose of a working group. Let’s pick one of these key issues and work together on it. Let’s set concrete goals and divide and conquer.
With our soft launch of the Badge Alliance, we tried to capture what to us felt like some of the most critical issues/topics through the initial working groups:
- Open Badges Standard - shaping the evolution of the open standard for badges
- Endorsement - how to build functionality and practice around third party endorsement of badges
- Cities & Network-wide Badge Systems - how to support network level badging systems
- Badges Messaging - how we talk consistently and effectively about badges to different audiences
- Globalization, Localization & Badge the World - how to encourage and support badging in other countries and cultures
- Web Literacy & Digital Literacy Badges - a shared badge system(s) for promoting and recognizing important digital skills
- Badges for Admission to Higher Education - how to get badges into the admissions evaluation process
- Recruiting Next Generation Workforce & Acceptance by Employers - linking badges to jobs, internships, career advancement and other opportunities
- Badges for Educators & Professional Development - granularrecognition for teachers and educators
This initial set of working groups isn’t comprehensive, of course, but reflects where we and the broader community sense some the biggest urgency or heat. It’s a healthy mix of driving adoption on the issuing side, while also really starting to dig in on the ‘consumption’ or currency side of the ecosystem as well. We already have begun to identify a fast follow set of working groups that will most likely include things like research, validation (although this one is too big for one working group), K12/schools (also too big), pathways and privacy/data.
(you can still participate in these working groups - visit http://badgealliance.org to sign up. You can also suggest additional topics/working groups you think should be represented).
"…an open badging ecosystem…"
Oh you thought the last part was heavy? Wait for this one! :)
An open badging ecosystem. I could write several blog posts on the meaning/importance of that phrase, probably at least one post on each one of those words (the one on “an” would be a page turner ;)).
But while we *could* (and I am sure at some point *will*) get existential and philosophical, this doesn’t have to be that complex. If we agree that ultimately this is about recognizing and connecting learning of many (and of more) kinds across contexts and across lifetimes, and leveraging that recognition to better connect people to jobs, additional learning, personal growth, advancement, social connections and more, then there are some pretty obvious and important lines in the sand, but only a few. Two actually.
1) Badges must be interoperable. In this case, that means badges must align with the open standard, which is the ‘information model’ for badges.
2) Earners must own their badges and have control over where they are stored, how they are shared, etc.
That’s it really. If we all agree on those two points, then we have the makings for a healthy ecosystem. If badges are interoperable, then they are stackable, we can ensure we have enough information for making sense of them and we can always build tools and processes on top of them to better issue, manage, understand, etc. And if earners are in control, then badges cannot get ‘stuck’ in a silo and we can continually build in more connections and opportunities for that badge earner. The work doesn’t stop with these two ‘principles’, but these are the minimum required to ensure that the ecosystem can grow up around the badges in a way that places the learner at the center.
We haven’t gotten so far as to finalize a manifesto or formalize any requirements for membership, but I can’t imagine these two NOT being in there in some shape or form. We’ll be co-creating these types of things with our Steering Committee and Alliance members, so obviously much more to come here.
So…we didn’t do so bad with our first tagline. There’s a lot in here, maybe some of it is controversial. Certainly some of it I intend to dive into much more deeply in subsequent blog posts. But don’t wait for that - I’m definitely interested in getting feedback and hearing more from you on these somewhat rambling thoughts. Where do you agree? Where do you disagree? What are other working group priorities? What does open ecosystem mean to you? What other names for working groups should we use? :) This is a pretty critical juncture in the Badge Alliance and the overall work so now’s the time to weigh in!
And don’t forget, another way to get involved is to participate in one or more of the working groups. You can sign up on the site http://badgealliance.org
Much more soon.
March 26, 2014 01:58 PM
Read the original post here.
We knew that the soft launch of the Badge Alliance at February’s Summit to Reconnect Learning would bring some exciting new changes to the Open Badges team at Mozilla.
Since Erin Knight’s announcement at the Summit, the initial Badge Alliance working groups have been formed and members have been recruited from across numerous sectors and continents to focus community efforts on the key questions and issues facing the open badges ecosystem, working together to keep us moving forward. We anticipate the official launch of the Alliance in June 2014, and there will be plenty to keep us busy between now and then!
Erin’s transition f Mozilla to the Alliance, there are some other changes we can share with you:
- Megan Cole, our marketing rockstar at Mozilla Open Badges, is joining the Badge Alliance as Director of Marketing + Operations;
- Carla Casilli, who led badge system design, research, and implementation on the Badges team, now acts as Director of Design + Practice at the Badge Alliance
- As you may have guessed, I (Jade) will also be transitioning to the Alliance as the Social Media + Community Manager
As you might imagine, with these changes comes a lot of loose ends to gather and tie up before the Badge Alliance fully launches in June.
Megan and Carla have already joined Erin full-time at the Alliance and are doing a stellar job of helping the transition go smoothly as we hit the ground running with setting up the initial working groups and reaching out to potential partners and group members.
My new role, for now, won’t include too many changes. My day-to-day workload will stay the same for the next few months, leading the Open Badges community calls and filling the social media feeds, as well as helping to build the Badge Alliance community before the official launch.
On the Open Badges side, Product Lead Sunny Lee and Partnership + Policy Lead An-Me Chung will be stepping up to the plate to lead the Open Badges team moving forward, working closely with engineer extraordinaire Chris McAvoy and design guru Jess Klein to drive the product in future evolutions.
All these transitions and changes will progress throughout 2014 as we gear up to the Badge Alliance’s public launch this summer and the next phase of product roll-outs from Mozilla, including new features and functionality within BadgeKit, as well as the Discovery and Directory tools.
So stay tuned to our blogs and Twitter feeds as we solidify our new roles within both the Badge Alliance and the Open Badges team - there is lots more to come from all of us!
Individuals and organizations interested in joining the Badge Alliance and contributing to the efforts of the working groups can visit badgealliance.org
For questions about the Badge Alliance working groups, please email Megan directly at firstname.lastname@example.org
For any questions about Mozilla Open Badges or related products, please email email@example.com
March 26, 2014 01:56 PM
March 25, 2014
As we head into Q2, let’s build a better “workbench” and online scrum board for Webmaker.
- Check out the freshly udpated Webmaker Wiki. It’s one-stop shopping for key roadmaps, planning documents, tickets, and scrums. And will help provide more transparency and co-ordination across teams going forward.
- It clearly lays out Webmaker’s key components. And how they all fit together. From teaching kits and training to localization, badges, and Maker Party. These will provide the main tracks for our scrum board as we go forward.
- Shifting to real time production, instead of static documentation. The new wiki is a production document. The main goal is to provide a clear view of *what we’re building now.* Week by week, quarter by quarter. Instead of a static repository for documentation that quickly goes out of date.
- Project scrum boards. To that end, each individual project page will lead with a virtual scrum board at the top of the page. We’ll embed Bugzilla tickets to do this, and use Bugzilla components and whiteboard tags to do it in a smart, automated way. (If you don’t use Bugzilla, just include links to wherever you’re tracking the work.)
Why are we doing this?
- This past quarter, we’ve clarified Webmaker’s scope, component pieces, and team roles. The new wiki reflects that progress.
- Fewer “status updates,” more transparent agility. If we do this right, it’ll mean we no longer need to do “status updates” in our weekly Webmaker.org calls. The wiki pages will take care of that. Instead, we can focus more on the brainy stuff: coordinating moving pieces, clearing blockers, and refining our strategy and tactics.
- One link to rule them all. No more URL spaghetti — if it’s important to your work, it should be intuitive and findable from your wiki page. This solves for a key challenge we’ve faced to date: co-ordinating often requires a confusing jumble of etherpads, blog posts, Google Docs, Bugzilla tickets, and stand-alone wiki pages that live in someone’s head. No more.
This is all a work in progress
- And not even close to “done.” There’s stuff missing. It needs your love, missing links and co-ownership. This post is about signalling the intention and getting your help.
Everybody loved the last Webmaker work week. Why? Because:
- We broke the project into key tracks. Webmaker is a complex product. You need to carve it up in smart ways to tackle and make sense of it.
- We sorted our roles and leadership for each track. Prepping for the work week forced us to get our RACI (Responsible, Accountable, Consulted, Informed) together for each track, and attack fuzziness.
- We worked well across teams. Dividing things up into smart functional components (like “Engagement Ladder”) forced us to work across teams, instead of sticking in our little org chart boxes. This drives a holistic view of the product.
- We scoped, documented and ticketed well. The prep work we did laid out the groundwork and scope. And because we tied all the work to Bugzilla and shareable online artefacts, it was easier to keep momentum after everyone went home.
- The scrum board provided clear visual progress. We moved a huge number of individual tasks across the board, from “to make” to “making” and “made.”
Together, these things sent a larger signal:
All that matters is scoping clear, achievable pieces of work — and then moving them across the line together.
So let’s keep working that way
That worked well — and led to a lot of completed work in Q1. So let’s do it more intentionally as we head into Q2. And build a Webmaker scrum board that never stops!
That’s what your project wiki page should lead with going forward: a scrum board that updates as you go. Along with the handful of key links, context or artifacts your colleagues need to help you push those well-defined tasks to completion.
Laying out Webmaker’s key components
Webmaker is an open source product with a dozen or so key component pieces. The main Webmaker Wiki page is visual and navigational — it lays out these key components. This in itself is useful — think of it as an X-Ray of the projects major bones, muscles and heart. And our key scrum tracks going forward.
In addition, the updated landing page includes links to:
- The high-level roadmap. Each individual component has their own goals and deliverables — but this is the one roadmap to rule them all, tying it all together.
- Our story. What are we doing in 2014? What’s the larger goal?
- Our contributor dashboard (NEW). Our #1 goal is growing 10,000 contributors this year. This new dashboard prototype will track that in real time.
Here’s a rough template to follow for each page:
1) Your scrum board
2) Key links
3) All else
Each component has their own page. Going forward, we’ll strive for each of the pages to follow the same basic template:
- Lead with your scrum board. This will provide the most up to date view of what’s happening, right at the top of your page.
- Include links to key documentation. It doesn’t have to be perfect — and links are fine. You *don’t* have to duplicate or copy / paste stuff, or wrestle with wiki mark-up, or whatever — just paste in the links. If your page contains *nothing* other than one or two links to wherever you’re documenting or tracking the work, that’s just fine.
- All else. Push the static, evergreen copy down the page, or move it to sub-pages. These are production pages — they’re meant for busy people to quickly grok what’s up now. And not public-facing pages that need to be pretty, rhetorical or overly polished.
Who’s all this for?
Who’s the main target audience for this new Webmaker wiki? Builders and production people.
Who are these wiki pages primarily for? The answer: builders. The people planning and building Webmaker on a daily basis. The kind of people who show up to the weekly Webmaker.org call. Or colleagues and hardcore contributors who’ve been at this a while, and already have a good level of familiarity with what we’re doing.
This is a bit different. In the past, we’ve used our wiki primarily for contributors, and contributor documentation. We’ve now mostly outgrown that. Our contributor documentation and platforms now live in other, more polished places – on Webmaker.org, on SUMO, in our updated even guides, new training pages, Git Hub, etc. That’s a good thing. Contributors shouldn’t have to dig through a wiki to find what they need — we should be serving them in more polished ways on the web.
That frees our wiki to focus on production and co-building. That means: less context and explaining, more diving into the work.
More to come
This post will be the first in a series on “Working Open with Webmaker.” In the mean time, let’s hack and update the new wiki together.
March 25, 2014 07:38 PM
March 21, 2014
All right, folks, let’s get you ready for the weekend - because we all know you can’t start your weekend without your roundup of what we’ve been up to with badges!
This week’s Open Badges calls were spectacular! Chloe Varelidi led the Research & Badge System Design Call in a discussion of gamification, game design principles, play, and badges - you can check out a summary and listen to the audio here.
On this week’s Community Call, Mark Otter and Julie Keane joined us to walk us through the global ready education program using badges within VIF International Education. They went into great detail about how they developed their program on the call - you can check out a summary and listen to the audio here.
Here’s the rest of this week’s badge action:
- Gail Corbett, who took a course from Professor Ian O’Byrne that issued badges, reflected on this first badges experience in this neat storify
- Parchment announced they are adding $10m to expand their digital credentialing platform
- Deeper Learning MOOC badges are here!
- Soozy Miller at Bright Hub asked the question of whether badges will become the standard for displaying credentials
We also held our final BadgeKit Training Sessions - if you missed them, don’t worry! They can be found on the Open Badges YouTube Channel, and future sessions will be held as we roll out more features throughout 2014.
A million high fives to the team for hosting these sessions!!
Have a good one, you guys.
See you next week!
March 21, 2014 06:03 PM
March 20, 2014
Open Badges Community Call, March 19, 2014
VIF International Education, the leading provider of global education programs for K-12 schools, launched their badge system in December 2013. The VIF learning center, a social learning platform featuring the Global Gateway professional development (PD) system for educators, makes it possible for teachers anywhere in the world to earn digital badges as they learn to effectively integrate global project-based inquiry into their core instruction.
Badges for Global Educators
VIF is in its 27th year, and has served roughly
March 20, 2014 08:05 PM
Open Badges Research & Badge System Design Call, March 19, 2014
Speaker: Chloe Varelidi
This week, our resident game design superstar and spokeswoman for playful design, Chloe Varelidi, led the group in a conversation around gamification and play, the principles of game design, and how badges fit into all of the above.
What is a game?
Chloe dared the group to define a game - and as a system, what parts combine to make up a game. Brett Bixler wrote a blog post exploring this question, in which he also defined educational games as a subset within the broader scope of what a game is. Educational games are, according to Bixler, designed for learning with a mix of educational content, fun, and learning principles.
Below are some of the answers the group compiled. A game is/has:
How can badges be part of games?
Of course, we didn’t get very far into a discussion of achievements and progress within games without bring badges into the mix. The group discussed the various roles of badges in games, from marking progress and acting as milestones, to being rewards and recognition of accomplishments or completion of game activities.
According to the Bartle Test of Gamer Psychology,
Gamification vs. game-based design?
Gamification as a term (and a concept) has gotten a lot of criticism, both within our community and in the broader learning networks we often hear from. Badges are often assumed to be necessarily about gamification, using badges as game-based motivators for achievements. While this certainly is one use for badges in game-based learning environments, many badge issuers and earners use badges as recognition of progress and feedback, rather than just as trophies to be collected.
Emily pointed out that language is very important - how we talk about these ideas can greatly affect how they are received and implemented.
Some argue that
Engagement was mentioned a number of times in this week’s discussion - as a better term for fun as well as for gamification. Within games, game-based learning, and badge systems for learning, continuous engagement is the goal - how this is achieved can vary according to the learners, the broader context and environment of the game / system, and the language we use to communicate the goals and components of the system.
To read the discussion in full, check out the call notes while listening to the audio.
March 20, 2014 07:25 PM
This blog post from Carla generated a lot of discussion on- and offline: it was retweeted by many members of the community and discussed on this week’s Research & Badge System Design Call.
The ‘lightweight badge’ is something we are asked about a lot on the Open Badges team - many are concerned with so-called ‘worthless’ badges, often holding badges to higher standards than existing credentials. Carla does a great job of exploring these concerns and effectively arguing why all badges can hold value as part of an ongoing identity-building process alongside achievement recognition.
Go to Carla’s blog to read the comments there and post your own.
The development of the open badge ecosystem is at the heart of all of the work that I do. I am deeply invested in ensuring that the ecosystem grows and thrives. During the time I’ve been focused on this work, folks have repeatedly declared deep concern about badge rigor, usually expressed as an underlying fear of the ecosystem-imperiling power of the “lightweight” badge. I’d like for us as a community to investigate and dispel the myth of the meaningless, lightweight badge before it becomes ingrained into the ecosystem as an alleged truth.
First let’s begin by discussing badge types. Certainly there is a lot to be said about proposed and future badge typologies and I’m hoping that we can engage on them here at a later date. For now, though, let’s talk about the much maligned “participation” type badge. Participation badges are typically earned through a simple act of attendance. They usually have no associated criteria aside from physical or virtual attendance. Mozilla has issued MozFest Reveler badges for exactly this type of interaction. Considered by many in the badge community to be throwaway badges with little to no social meaning, in fact participation badges are markers and data points in the larger, more complex concept of self.
Am I who you say I am or am I who I say I am?
During the process of badge system development, implementation, or interpretation, certain types of badges like participation badges may appear to be devoid of much or any value. Let me say that again with emphasis: may appear to be so. They are not. All badges have some value. Badges layer upon each other: no badge is entirely independent of any other badge—at least not to the badge earner. Just as all badges operate in contextual ways, participation badges live alongside other badge types. They can and do interconnect in ways that may be far outside of their issuer’s original intent. This is one of an open badge’s best features—they act as connectors! Perhaps even better, all badges act as touchstones for the earners.
The concept of accretion will be readily understood by the scientists, accountants and financial thinkers among us. Here I’m using it to indicate the continued layering effect of badges being earned throughout a length of time. Earn a badge. Earn a badge. Earn three badges. Earn another badge. Accretion operates on a meta, ecosystem level as well as a smaller system wide level, and its power should not be underestimated. Why? Because the continued layering of earned badges from many different issuing organizations and experiences—the accretion—means that value arises in unexpected and emergent ways.
The multiplication factor
For example, while it may be possible to know how one badge is perceived by its earner in its original context, it is not possible to estimate how three badges from three different organizations may be perceived by an earner. Consequently, that “lightweight” badge that Josefina earned while attending The Museum of Natural History during a class trip may become a connector to an online natural sciences webinar may become a connector to a robotics class held at the local library. Combined, these “lightweight” badges begin to highlight potential pathways and future area of interest.
Weak signals, strong network effects
Interest-driven participation badges communicate in subtler ways than skill or competency badges do but they are sending signals to the earner as well as the larger social structure. They act as windows into alternate interpretations of self. Not only do they work to represent past experiences but also possible future selves. They accumulate and in their accumulation they tell different stories to both the earner as well as the public.
So, the next time you hear someone note a concern about “lightweight” or meaningless badges, think about Tennyson’s “Ulysses” quote below. Ask yourself if you’re not the composite of everything that you have experienced, large and small.
I am a part of all that I have met;
Yet all experience is an arch wherethro’
Gleams that untravell’d world whose margin fades
For ever and forever when I move.
Et voilà. The myth of lightweight badges is dispelled.
Tennyson, Alfred Lord. (n.d.) Ulysses. Retrieved from http://www.poetryfoundation.org/poem/174659
March 20, 2014 03:51 PM
March 17, 2014
The Mozilla advocacy and campaign teams are meeting this week to plan a multi-year “privacy, security, surveillance” campaign. We’re searching for an issue where we can make a real impact.
I am pushing for “security” to be tip of our campaign’s spear. Something like “we want to know that our devices, communications, and Internet/web services are secure against compromises and attacks from governments or criminals. We don’t want them to contain any deliberate or known weaknesses or backdoors.” This is the kind of principle that resonates across ideological divides, gets people nodding their heads at the watercooler, and gets the red-meat internet people fired up about backdoors in Microsoft products. No public figure wants to be on record saying “a vulnerable Internet is a good thing.”
Intelligence and defense are pouring enormous resources into making the internet communications of our adversaries more vulnerable, which makes everyone more vulnerable. It’s counterproductive. It’s why Yochai Benkler talks in terms of an autoimmune disease; “the defense system attacking the body politic.” This problem is illustrated in ongoing leaks that suggest agencies are looking to deploy malware at mass scale. “When they deploy malware on systems,” security researcher Mikko Hypponen says, “they potentially create new vulnerabilities in these systems, making them more vulnerable for attacks by third parties.”
This is why I think we should put our energy behind “securing the internet.” We can’t stop spying, but we can affect a state change in internet security.
“How to Act”
But even in a perfectly secure internet, users’ behavior leaves them vulnerable to any number of privacy harms. “Privacy” is not the kind of value that gets codified in software; it takes user awareness and action. So our campaign must be centered on educating users about specific actions they can take to address the problem.
“Privacy” is a collective problem. We need to be the change we want to see.
We need to teach people how to act in an information society. We need young people to understand this part of “citizenship” on the web; how even seemingly passive usage of the web forms a profile, a trail, an exposure.
A “privacy civics” education should be part of every high school curriculum—like home economics or traditional civics.
Mozilla is developing a Web Literacy Map and associated curriculum. Privacy will be the toughest part of this map to teach, because it’s unbelievably abstract. When “Connecting,” for instance, a web literate person should have competencies like:
“Managing the digital footprint of an online persona.”
“Identifying and taking steps to keep important elements of identity private.”
But “digital footprint” “user persona” and even “privacy” are abstractions. To introduce these abstractions, you need stories and metaphors to explain these concepts, to build on the understanding, and ultimately form a consciousness and an understanding of the user’s privacy context in the wider web. For example, we might explain the exposure that a user gets from metadata because “it’s like having a guy parked outside your house with binoculars. He might not know exactly what’s happening inside, but he can take notes and find patterns.”
It’s not hard to imagine worksheets or 2001 era CD-ROMS to use these stories address these competencies. But this is 2014, and we can do way better. We should be able to make this kind of thing less abstract, more tangible, using the web.
A Mozilla-Style Privacy Education? Lessons from MozFest 2013
What does a Mozilla-style privacy education look like? What should it feel like?
Clearly, it should be hands-on, interactive, instructive. We couldn’t teach this stuff in a boring way. When we teach HTML, we invite kids to hack webpages or remix hip-hop videos. Maybe when we teach privacy/security workshops, we should invite kids to be an NSA analyst on their own metadata? Or to perform a man-in-the-middle attack or tailor advertisements to their peers?
I don’t know for sure, but I do know that a Mozilla privacy education should be much cooler than reading a book.
MozFest is a great place to test hypotheses, work with communities, and intuit where we ought to be going. We use MozFest to learn from the open web communities and get smarter.
The 2013 Festival featured a track on privacy and user data. I helped organize with Alex Fowler and Alina Hua. We called it “Look Who’s Watching,” in a nod to the Stop Watching Us coalition. “Look Who’s Watching” suggests an educational complement to that activist project. Internet users should look around, undergo a process of discovery, and better understand how they expose themselves when they use the web. To understand who’s watching your online movements is an essential part of being an informed, empowered user.
The Privacy Track at MozFest 2013 was billed as an opportunity to “shape a full response to modern privacy problems.” These problems include but are not limited to behavioral targeting, information leakage, data correlation and generic attacks to privacy, location and mobility tracking, profiling and data mining, surveillance, and good old fashioned oversharing.
Lots of privacy educators showed up with their own theories of change. Each has strengths, weaknesses, and pedagogical baggage. Let’s take stock of a few:
Lightbeam shows how third-party cookies enable a web of tracking
The highest profile public education initiative that Mozilla has done to date is Lightbeam, in collaboration with the Ford Foundation.
Lightbeam is a Firefox add-on that visualizes how you’re affected by third-party commercial tracking. As you browse, Lightbeam reveals how third-party cookies paint a picture of your online activity, and how that’s not transparent to the average user.
We have billed this as being explicitly educational, but we don’t yet have a theory of how Lightbeam should be presented in workshop setting. Getting Lightbeam workshops in place throughout the Webmaker network is seriously low-hanging fruit.
However, Lightbeam is sort of stuck in time, and will cease being valuable when the ad titans move away from cookies and toward fingerprinting. It’s overly mechanical. More importantly, it doesn’t get to the deeper problems implied by this knowledge graph falling into the wrong hands.
Don’t get me wrong—I’m a huge fan of Lightbeam. It’s individualized and interactive, and illustrates a specific problem. But it’s not yet the kind of integrated, interactive, innovative privacy education that we need.
Trace My Data Shadow?
Me and My Shadow offers a way to measure the invisible and abstract
The more latent, scary stuff is hard to measure (or explain). At MozFest, we were fortunate to have Becky Kazansky representing Tactical Tech, who have created resources like “Security-in-a-Box” and “Me and My Shadow.”
Me and My Shadow is a well-designed curriculum that gets to the meatiest problems in privacy: how your data shadow can be used against you.
A lot of people conflate the loss of privacy with oversharing on social networks. But smart people know the problem is not what you purposefully put into social media—it’s the data trail that you (unavoidably) generate as a web user. MyShadow.org includes a set of tools to measure your data shadow. Once you’ve measured your shadow, it points to ways to “explore your traces,” “resize your shadow,” and ultimately “turn the tables.”
Shadow Tracers Kit
“Teaching privacy” involves helping people develop a mental model of mechanics of the web. Understand exposure and trust. Develop transactional intelligence about their data. In a perfect world this would be about leveling everyone up, informing a smarter conversation and smarter usage at all levels—ultimately reaching policymakers. My Shadow is getting a little closer to the sweet spot, but it’s a little too fragmented. It’s not yet cohesive or well-integrated with a campaign. Maybe we can help.
There's a cryptoparty in your neighborhood
CRYPTOPARTIES are about people understanding the consequences of their own behaviors and adjusting. Around the world, small groups of people attend teach-ins where they learn skills in small groups: PGP encryption, Tor anonymous browsing, OTR secure communications. To me it seems a little hard to make this mainstream—though Cory Doctorow probably has ideas about how to make this cool. The bigger problem is that anonymization is not necessarily the change we want to see—it sets up a frame where there are privacy-haves who justifiably wear tin foil hats, and privacy-have-nots who think that they’re weird.
But there’s a big opportunity to more systematically bring privacy teaching, learning and crypto-parties into the Webmaker network.
Take This Lollipop makes it personal
Privacy drama is about take invisible, abstract problems and make them immediate in personalized narratives. You could imagine a documentary that uses your data and APIs to demonstrate how you would be subject to price discrimination, for instance. We brainstormed a list at MozFest, and there are interactive proofs-of-concept, like Take This Lollipop (which spins a privacy scare narrative from your Facebook data) and the privacy documentary side-project of Mozilla’s own Brett Gaylor.
I’ll be expanding on some of these ideas in a talk to the Tribeca Film Institute in April. Will do a post later on.
Hands-on computer science education?
Immersion will enable you to analyze your email metadata, the way an NSA analyst would
Another approach suggests that the best way to understand security vulnerabilities is to “do it yourself,” having a visceral hands-on experience.
At MozFest, we had a session that taught participants to use Wireshark to perform a man-in-the-middle attack on their own mobile phones. Participants learned this basic interception technique to reveal how the mobile apps they use are ‘phoning home’ — enabling mobile tracking without consent. But after performing this exercise, participants should understand the risks of having their traffic intercepted, and will probably want to see that HTTPS is active before ever typing a password.
Another team from MIT (the Immersion project) set out to explode the myth that user metadata is “just metadata”:
What can someone learn from what you write on your “virtual envelopes”? After an introduction to the MIT Immersion tool, you’ll perform a metadata analysis of your own inbox. Participants will gain insights about surveillance of metadata through some simple coding exercises (Python) if you have Gmail, try Immersion here.
After performing a metadata analysis of your own inbox, a facilitator can ask leading questions like: “Is that female with whom you communicated the most in 2012 your girlfriend? I see you didn’t communicate at all in 2013—did you break up?” Having a personal experience like this will show that patterns and content can be inferred from metadata, and that such power can be exploited by advertisers and law enforcement.
On display are varying pedagogical theories. They can all co-exist. But how should Mozilla concentrate efforts?
I am convinced that we need an answer, and to lead a “privacy civics education” for the world.
No Mozilla campaign would be complete without mobilizing users to take direct action on this very collective problem.
March 17, 2014 09:57 PM
March 14, 2014
During our planning for 2014, a need that came up over and over again was for better data tracking across the board. This included managing our contributor targets, engagement funnels, campaigns, partners, etc.
We decided we needed a CRM. And ‘CRM’ quickly became a dumping ground for a huge wish list of features and unmet needs.
Since then, a small group has been working to figure out what we actually need, whether it’s the same thing that other Mozilla teams need, and which of us is going to do the work to put those systems in place.
Adam Lofting, Andrea Wood, and I have come up with a framework we’re going to pursue. It splits ‘CRM’ into three functions and proposes a path forward on each. We feel this represents the best use of our resources, lets us hit our priorities, and ensures that we continue to work under a ‘One Mozilla’ model.
1.) Partner Management
- What this means: Traditional CRM features such as shared contact lists, joint documents, status updates, and communications management.
- How we’d use it: To manage our relationships with Webmaker partners, BadgeKit adopters, and institutional funders.
- The plan: Mozilla’s IT department is leading a CRM implementation to manage deal flow and other relationships behind the FFOS Marketplace and emerging content partners. The Foundation will adopt whatever system is put in place from that process. This is based on the assumptions that (i) ‘partner management’ is a fairly standardized process, (ii) the Foundation’s needs can be mapped onto whichever tool IT selects, and (iii) there are benefits to be had from working within the same framework as our colleagues in business development.
2.) Campaign Management
- What this means: E-mail, small dollar fundraising, activism, standalone campaign web sites, event registration, and other outreach and engagement activities.
- How we’d use it: To promote our events and programs, to manage registration for events, to run activism campaigns, and to anchor our small dollar fundraising.
- The plan: The Foundation and Corporation engagement teams are working to combine budgets, gather requirements, and launch an RfP process to select a platform to run both programs. We already work together on the design and implementation of campaigns, and a shared technology platform will make that collaboration more efficient and avoid current, user-impacting issues resulting from multiple tools managing multiple e-mail lists.
3.) Contributor Management
- What this means: Outreach, engagement, metrics, and recognition behind the Grow Mozilla goal of reaching 1 million contributors to our project.
- How we’d use it: Metrics and analytics on engagement ladders, measuring contribution numbers, and rewarding and recognizing our contributors.
- The plan: This is the area where we will probably have to build our own, Mozilla-wide solution. The People, Engagement, Business Intelligence, Foundation, and Open Badges teams are currently working together to figure out what that will entail. The solution will most likely involve some combination of program-specific engagement funnels, metrics and analysis through Project Baloo, and reward and recognition through Open Badges. More as it unfolds.
Does this sound right? Are there things missing? Please ask in the comments.
Filed under: Mozilla
March 14, 2014 08:36 PM
Happy Pi Day, everyone!
Last week we were busy running around at two separate conferences, releasing BadgeKit and prototyping the Discovery project. This week, we had the chance to sit down, breathe, and get back into a normal routine.
This week’s Research & Badge System Design Call took a deeper look at BuzzMath’s Common Core badges, and their Creative Director JP Choinière joined us to share updates from their developing badge program. For a full summary and a link to the audio download, click here.
After an exciting demonstration at DML, the Discovery team joined us for the Community Call this week to take us through their research, design, content and technical process. It was great to get such a detailed look at the work this team is doing to build the Discovery and Directory tools that are going to help so many people access badges. For a full summary and a link to the audio download, click here.
What else have we gotten up to?
- The Jisc Digital Festival (DigiFest) took place in Edinburgh, Scotland earlier this week. OBSEG community members spoke about badges in workshops and “surgeries” to help people dig into badges.
We’ve also been hosting BadgeKit Training Webinars all week, and there are two more live sessions scheduled for next week - check out the schedule and register here. If you can’t wait, or can’t make it to a live session, we have recorded the sessions. Here is the video from yesterday’s tutorial:
Have a wonderful weekend, everyone - and remember, there’s no such thing as too much pi(e):
March 14, 2014 07:31 PM
This is the second in a series of blog posts where Mozilla’s Senior Director of the Webmaker Community details plans for a global network of Hive activity. The first post is here.
Over the last two years MacArthur and Mozilla have grown Hive NYC and Hive Chicago, helped on-board Hive Pittsburgh and Hive Toronto and responded to a growing chorus of communities eager to incorporate Hive values, ideas and platforms, or as we have dubbed it, “Hivey-ness.” As a result, we’ve developed a three-tiered engagement ladder, outlining ways to contribute to Hive as well as the path towards creating and sustaining a Hive Learning Network.
Tier 1: Hive Learning Events
These are learning gatherings that bring network practice and connected learning principles to life for an inter-generational audience. Examples include Pop-Ups, Hack Jams, media production sessions, Maker Faires and other events. We brand these events in two ways:
Hive Pop-Ups have an intentional program design towards fostering a “Hanging Out, Messaging Around, Geeking Out” (HOMAGO) experience. For more on HOMAGO check out this handbook written by the Yollocalli Arts Center and Hive Chicago. At these events, multiple organizations come together with some of their best programs and deliver activities via learning stations tailored towards three levels of users:
- A smaller but focused group who lock into one activity for the duration of the event (Geeking Out)
Participating educators get to both contribute to and observe what it’s like to see youth self-direct their learning and design their own experience in a networked space. Often the question, “Why Hive?” is better answered after seeing a Pop-Up in action: adults see youth interacting and learning with peers, remix and re-interpret their programs, become part of the energy in the room, and perhaps most importantly, see youth travel from different activities/interactions guiding their own path through the controlled chaos. We have distilled the Hive Pop-Up into a Webmaker Teaching Kit and this video details the Brooklyn Public Library Storymakers Maker Party/Hive Pop-Up.
Maker Party is the second event category, based on Mozilla’s global campaign to engage, excite and educate people about a production-based culture. Maker Party seeks to broaden access and equity to both digital as well as analog practices. Maker Parties are used to grow the community of people aware of connected learning and as cultivation strategy for new Hive Learning Communities.
Recently the Hive Research Lab has been studying Hive Events (Pop-Ups, Hack Jams and Maker Parties) through the lens of their two primary research areas: how Hive can foster Youth Interest-Driven Pathways and how it can act as effective infrastructure for Networked Innovation. Based on early fieldwork, Hive Research Lab has come up with design suggestions for how educators can more effectively use these events to reach these goals, ones that relate to outcomes for whole networks, member organizations and network-affiliated youth.
These events have been catalysts in helping new Hive communities emerge and we’ll share some specific examples in an upcoming post.
Tier 2: Hive Learning Communities (HLC)
Hive Learning Communities begin to use the connected learning principles and the practices of Hive to operationalize a learning network. They draw heavily from the experience of existing Hive Learning Networks whose leaders function as consultants and mentors sharing information about structure, program design and strategy. Local facilitators then adapt tools, practices, frameworks to their local contexts. They are free to self-identify themselves as Hive and use the branding assets and developmental resources that are openly networked.
Specific characteristics could Include:
The Hive concept has really developed into a grassroots movement with Hive Learning Communities forming around the globe. Current examples include Hive India, Hive Bay Area, Hive Berlin and others.
Tier 3: Hive Learning Networks (HLN)
Hive Learning Networks are city-wide vehicles for implementing and spreading connected learning ideas, tools, practices and values. These networks are fully operationalized with a staff, sources of funding, ways to seed innovation projects and a system for convening its membership. They accept the responsibility to be engaged in the stewardship of Hive Global. New Hive Learning Networks will be admitted through a review process of the Hive Global stewarding body, MacArthur, Mozilla and a panel of independent stakeholders.
The minimum requirements for Hive Learning Networks are:
Demonstrated alignment and programmatic commitment to connected learning values and principles
At least one dedicated, full-time staff member
An operational budget of at least $150K/year
A grantmaking apparatus that seeds no less than $15K into ecosystem
Participation in Hive Global stewardship beyond home city
Specific characteristics of the networks include:
From our experience consulting and participating in nascent communities, we know the components of successful Hives share common categories and characteristics. We recently circulated a collaborative document to surface a common set of self-emergent values, and here are just a few:
We are currently working in the open towards the better articulation, operation and adaptation of these three tiers as a strategy to establish Hive practices as a key driver of the spread and scale of connected learning. We’ll continue to share more plans, details and resources in the coming weeks, and we’re also interested in your feedback. If you’re already working towards building a Hive in your community, or have been considering it, we’d love to know what resonates with you, or what questions you have regarding information we’ve shared so far or even specific details to help you get started. Feel free to comment below or reach out to me directly via email.
The post The Three Tiers of Hive appeared first on Hive NYC.
March 14, 2014 05:22 PM
YALSA [An Open Badges Case Study]
In the spring of 2012, the Young Adult Library Services Association (YALSA), a division of the American Library Association (ALA) that supports library services for teens, was awarded funding to develop a badge system to recognize, improve, and enhance the skills of library staff working with teens as part of the Badges for Lifelong Learning Competition.
The YALSA badge program helps library staff develop skills related to the Competencies for Serving Youth in Libraries, which YALSA developed for librarians who serve young adults.
YALSA’s badge system creators Linda Braun and Nicole Gibby Munguia wanted a valuable way to recognize the work library staff are doing and encourage them to demonstrate their achievements to colleagues and employers.
We are thrilled to include YALSA in our initial set of working case studies that we published last month. Click the link above to read more!
The Badges for Lifelong Learning Competition was administered by HASTAC with support from the MacArthur Foundation, and in partnership with Mozilla.
March 14, 2014 03:33 PM
The Young Adult Library Services Association (YALSA), a division of the American Library Association (ALA), has turned over its @YALSA Twitter account to a different partner each day of this week, and we’re super excited to be taking part all day today!
As part of Teen Tech Week, different partners have taken this opportunity to inform and engage YALSA’s 22,000+ Twitter followers about relevant issues from their perspectives as well as share resources of interest to YALSA’s audience.
On Monday, Make It @ Your Library (@MakeItLib) took over, followed by the Urban Library Council (@UrbanLibCouncil and @Learning_Labs_)on Tuesday. Wednesday saw Best Buy’s Geek Squad (@GeekSquad) take the reins, and then on Thursday tweets came from the Office for Information Technology Policy (@ala_oitp), which helps secure information technology policies for the ALA.
And today it’s our turn!
Follow @YALSA today to see tweets from us, and scroll back through the week to see tweets on various topics, including connected learning, makerspaces, practical tips for using digital tools, technology policies, and of course badges.
YALSA developed a badge system to recognize, improve, and enhance the skills of library staff working with teens. We were thrilled to include them in our initial case studies published last month. Read more about YALSA’s badges here: http://bit.ly/Case_YALSA
About Teen Tech Week:
Teen Tech Week is a national celebration that offers libraries the chance to highlight all of the digital tools, resources and services they offer to teens and their families. It will be celebrated with the theme “DIY @ your library.” To learn more about Teen Tech Week, visit www.ala.org/teentechweek, or check out #TTW14 on Twitter.
For more than 50 years, YALSA has worked to build the capacity of libraries and librarians to engage, serve and empower teens. For more information about YALSA or to access national guidelines and other resources go to www.ala.org/yalsa, or contact the YALSA office by phone, 800-545-2433, ext. 4390; or e-mail: firstname.lastname@example.org. For more information on YALSA’s badge system, go to http://yalsa.ala.org/blog/tag/open-badges/ and check out this article from the School Library Journal.
March 14, 2014 03:17 PM
Over in the Mozilla Webmaker Google+ community it’s the final day of our online discussion as part of Open Education Week. Today’s prompt asks: Do we need to protect the Open Web and Open Education? If so, who or what from? How do we do that?
My short answer to this would be yes we do need to protect Open Education and the Open Web. We need to protect them from commercial, proprietary providers looking to profit from creating silos. How do we do that? I’d argue by innovating in ways that are different from those looking to make a quick buck.
It’s obvious, but worth stating: I’ve no problem with people charging for services. The issue is more to do with the overall landscape. If all you’ve got is shiny silos from which to choose, it’s a frustrating pseudo-choice. Openness proposes and provides a different way to do things than following the logic of the market.
The problem is that ‘Open’ is an ambiguous term and seems to have become the latest fad. Martin Weller points out that in many ways ‘Open’ is the new ‘green’:
The old “open vs. proprietary” debate is over and open won. As IT infrastructure moves to the cloud, openness is not just a priority for source code but for standards and APIs as well. Almost every vendor in the IT market now wants to position its products as “open.” Vendors that don’t have an open source product instead emphasize having a product that uses “open standards” or has an “open API.
As Audrey Watters has eloquently stated, the fight is now who gets to decide what counts:
This battle involves the ongoing struggle to define “what is open.” It involves the narratives that dominate education – “education is broken” and “disruption is inevitable,” for example – and the “solutions” that “open” purports to offer. It involves a response to the growth of corporate ecosystems and commercial enclosures, built with open source technologies and open data initiatives. And all of this, I would argue, must involve politics for which we shouldn’t let “open” be an easy substitute.
As the term ‘MOOC’ (Massive Online Open Course) has shown, you can’t have it both ways: if a term includes enough ambiguity and flexibility to be widely adopted, then those who originally defined it no longer have control over the definition. It’s out in the wild. Like a virus, the definition mutates over time.
It’s not the word ‘Open’ we need to protect, it’s the spirit behind it. We’re fighting a losing battle if we expect a word to mean the same thing for all eternity. Instead, as a community we should create, sustain and release new terms to help shed light on the things we believe to be important and hold dear.
Finally, as Audrey reminds us in the quotation above, to align yourself with an agenda of Openness is a political statement. As such we should be prepared to get our hands dirty and fight for what we believe.
Image CC BY-NC-SA John Carleton
March 14, 2014 12:14 PM
March 13, 2014
Open Badges Research & Badge System Design Call, March 12, 2014
Speaker: Jean-Phillippe (JP) Choinière
BuzzMath’s Creative Director JP joined us for the Open Badges Community Call in January, and came back this week to dive deeper in the work BuzzMath has been doing with their badges on the Research & Badge System Design Call.
To see JP’s presentation slides, click here.
Common Core BuzzMath Badges
JP and his small 15-person team are based in Montreal, and launched BuzzMath about two years ago to help students develop math skills. They soon saw that many learners were having trouble seeing ‘where to go’ in terms of their progress through the activities, and saw a opportunity to use badges to not only identify challenges and things to be achieved, but also to recognize soft skills and motivate learners to do more.
There are 56 available badges that allow middle school students to share earned knowledge and accomplishments through BuzzMath's programs, within three categories: Content Knowledge Badges, which include over 3,000 activities that are aligned to components of the Common Core Standards; Process Knowledge Badges, which are awarded by teachers for soft skills related to mathematics; and Achievements Badges for the completion of a set of activities.
There are two basic levels of achievement within the BuzzMath platform: when learners complete activities they earn stars which unlock challenges. These challenges, upon completion, lead to the earning of a badge.
Within the Content Knowledge Badge challenge activities, there are learning tracks students progress along to earn badges and prove concept mastery. There are u
The focus of the BuzzMath program is for the learners to have fun with math, rather than focus on their progress being reported back to their teachers. By combining national standards with 21st century & soft skills recognition, BuzzMath is helping learners capture a fuller picture of their skills as well as motivating them to continue learning.
Challenges and Next Steps
Some challenges JP and the BuzzMath team faced were related to building value within the badge system and trying to encourage collaboration. Many saw coverage
March 13, 2014 06:35 PM
Open Badges Community Call, March 12, 2014
- The Open Badges Discovery Team:
The Discovery Team took over this week’s Community Call, sharing their work on the Discovery app and their findings from research and prototyping they have been doing over the past few months.
Discovery, Pathways & Playful Design
As Mozilla’s games rock star, Chloe Varelidi is passionate about playful learning design and has done some wonderful work for Mozilla on learning games and more - which you can read about on her blog.
Last summer, Chloe and others on the Open Badges team started exploring the idea of pathways more deeply as we prepared to softly launch BadgeKit at MozFest. Then, with funding from the Bill & Melinda Gates Foundation, this work picked up momentum to become a really exciting part of the next evolution of the Open Badges product offerings, due to launch in June 2014.
Chloe, Lucas and Mike tested their pathways framework at the Open Badges Summit in February and their clickable prototype at DML last week. During this week’s presentation, they shared their work and process on research, design, content and tech for the new Discovery app they are creating, as well as the Directory component that will accompany it.
At it’s core, the Discovery app aims
Within the Discovery framework, a badge issuer could create templates and statements of needs, in order to find better candidates for jobs. On the flip side, an earner can fill in pathways with badges to tell their story, show their goals and plan their progress towards a career. They would also be able to explore and ‘fork’ or remix other users’ pathways to suit their needs.
The interview process included listening to the stories of employers, workers and students and identifying what the team calls “badgeable moments” - the points at which informal or self-motivated learning contributes to the story of a person’s skills or knowledge but has yet to be fully recognized, showcased or used to advance the learner’s progress. Through listening to these stories, the team (and interviewees) were able to
Provisional badge types developed by the team
Mike Larsson spoke about the technical side of the project, detailing the two necessary components of the product: as well as Discovery, there will be a Directory, to help gather as many badges as possible to feed into the Discovery app.
The Discovery tool is due to launch later this year in June, and will feature pathways tools and a growing badge directory. You can track the team’s progress a number of different ways:
Next week we will be joined by Mark Otter from VIF International, which launched its badge system for global educators at the end of last year. Stay tuned for news of the second speaker!
March 13, 2014 05:14 PM
March 12, 2014
As my business card says, I have an affection for the world wide the web. And, as the web turns 25 this week, I thought it only proper to say to the web ‘I love you’ and ‘I want to keep you free’.
From its beginning, the web has been a force for innovation and education, reshaping the way we interact with the world around us. Interestingly, the original logo and tag line for the web was ‘let’s share what we know! — which is what billions of us have now done.
As we have gone online to connect and share, the web has revolutionized how we work, live and love: it has brought friends and families closer even when they are far away; it has decentralized once closed and top-down industries; it has empowered citizens to pursue democracy and freedom. It has become a central building block for all that we do.
Yet, on its 25 birthday, the web is at an inflection point.
Despite its positive impact, too many of us don’t understand its basic mechanics, let alone its culture or what it means to be a citizen of the web. Mobile, the platform through which the next billion users will join the web, is increasingly closed, not allowing the kind of innovation and sharing that has made the world wide web such a revolutionary force in in the first place. And, in many parts of the world, the situation is made worse by governments who censor the web or use the web surveil people at a massive scale, undermining the promise of the web as an open and trusted resource for all of humanity.
Out of crisis comes opportunity. As the Web turns 25, let us all say to the web: ‘I love you’ and ‘I want to keep you free’. Let’s take the time to reflect not just on the web we have, but on the web we want.
Mozilla believes the web needs to be both open and trusted. We believe that users should be able to control how their private information is used. And we believe that the web is not a one-way platform — it should give as all a chance makers, not just consumers. Making this web means we all need access to an open network, we all need software that is open and puts us in control and we all need to be literate in the technology and culture of the web. The Mozilla community around the world stands for all these things.
So on the web’s 25 birthday, we are joining with the Web at 25 campaign and the Web We Want campaign to enable and amplify the voice of the Internet community. We encourage you to visit www.webat25.org to sign a birthday card for the web and visit our interactive quilt to share your vision for the type of web you want.
Happy Birthday to the web — and to all of us who are on and in it!
ps: Also, check out these birthday wishes for the web from Mozilla’s Mitchell Baker and Brendan Eich.
pps: Here’s the quilt: the web I want enables everyone around the world to be a maker. Add yourself.
Filed under: drumbeat
March 12, 2014 05:06 PM
It’s Open Education Week. In addition to facilitating a discussion on behalf of Mozilla, I’ve got a guest post on Brian Kelly’s blog entitled What Does Working Openly on the Web Mean in Practice?
Here’s a preview:
Working open is not only in Mozilla’s DNA but leads to huge benefits for the project more broadly. While Mozilla has hundreds of paid contributors, they have tens of thousands of volunteer contributors — all working together to keep the web open and as a platform for innovation. Working open means Mozilla can draw on talent no matter where in the world someone happens to live. It means people with what Clay Shirky would call cognitive surplus can contribute as much or as little free time and labour to projects as they wish. Importantly, it also leads to a level of trust that users can have in Mozilla’s products. Not only can they inspect the source code used to build the product, but actually participate in discussions about its development.
Go and read the post in full. I’d be interested in your comments (over there – I’ve closed them here to encourage you!)
Bonus: The web is 25! Remix this
Image CC BY-NC Glen Scott
March 12, 2014 02:25 PM
2013 was Mozilla’s most successful fundraising year ever. We grew our core operating grants and more than doubled the size of our donations campaign.
This is a shared, project-wide accomplishment. More than 40 Mozillians from across the foundation, corporation, and community pulled together to make it happen. And I’m proud of what we accomplished.
We still have a long way to go. We’re overly dependent on a few key funders and there’s a big gap between our current revenue and our goal of matching Wikimedia’s fundraising program.
But 2013 was an indication that we’re on the right path, with the right team, and a mission our community loves.
Click to enlarge
Filed under: Mozilla
, Pitch Geek
March 12, 2014 02:28 AM
March 11, 2014
I’m currently moderating a discussion as part of Open Education Week on behalf of Mozilla. In today’s discussion prompt I asked:
What do you see as the link between Open Education and the Open Web? Does the former depend on the latter?
It’s a question that depends on several things, not least your definition of the two terms under consideration. Yesterday, in answer to the first discussion prompt, I used Mozilla Thimble to make this:
The above would be my current (brief) definition of Open Education. But what about the Open Web? Here I’m going to lean on Mark Surman’s definition from 2010:
Open web = freedom, participation, decentralization and generativity.
That last word, ‘generativity’ is an interesting one. Here’s part of the definition from Wikipedia:
Generativity in essence describes a self-contained system from which its user draws an independent ability to create, generate, or produce new content unique to that system without additional help or input from the system’s original creators.
As an educator, I believe that the role of teachers is to make themselves progressively redundant. That is to say, the learner should take on more and more responsibility for their own learning. Both teachers and learners can work together within an Open Educational Ecosystem (OEE) that is more than the sum of its parts.
The more I think about it, this is how the Open Web is similar to Open Education. Both are trying to participate in a generative ecosystem benefitting humankind. It’s about busting silos. It’s about collaborating and sharing.
Does Open Education depend upon the Open Web? No, I wouldn’t say it that strongly. Open Education can happen without technology; you can share ideas and resources without the web. However, the Open Web significantly accelerates the kind of sharing and collaboration that can happen within an OEE. In other words, the Open Web serves as a significant catalyst for Open Education.
What do you think? What’s the relationship between Open Education and the Open Web?
Join the discussion!
March 11, 2014 10:30 AM
March 10, 2014
Often it’s difficult to get contributions to open projects because some people aren’t quite sure what contribution means or how to go about doing it. Other folks don’t know what “Open” means, and thus they don’t know they can contribute at all. Perhaps it’s the nomenclature of “Open” that confuses people. Perhaps it’s just an “Open” marketing problem.
In any case, my suspicion has been that in order to activate people to teach the web, Mozilla would need to help people learn how to participate in an open community.
Connecting to a specific community online requires a certain…persistence. There are also social skills at play that weren’t necessarily encouraged in our formal school systems.
[caption id="" align="alignnone" width="500"]
photo by Doug Belshaw[/caption]
It isn’t necessarily that I think people don’t know how to teach or even that they didn’t know how to teach digital skills, it’s just that in order to be intentional about teaching the skills and competencies that make up the Web Literacy Map
, people need to understand concepts that underpin all of the work that we do. People also need to understand how to use web technologies in support of openness
, and those two things together are, perhaps, more complicated than they sound.
I want to help people teach the web in an open and participatory way, which means that process would have to be opened up. I was thinking about what a kind of Technical Training program for the web would look like,
and to me, it looked like an open community.
Our people - a globally diverse group of passionate educators and technologists - believe in the web as a platform for learning, sharing, connecting and making, and they believe that open practice and participation are key elements to becoming a citizen in the digital world. Our community members are eager to spread web literacy in their local contexts, but participating in the global movement means that one needs to navigate through a complex and sometimes confusing ecosystem of digital human communication.
[caption id="" align="alignnone" width="500"]
TeachTheWeb MOOC was an online prototype we ran last year. Click the picture to learn more about it![/caption]
Our Training program
is designed to give people an easy in to the types of online communication and participation I’m talking about. We want to design a way for people to experiment and fail forward.
We’d like the online component to support the offline actions and vice versa. This is the reason that everything in Webmaker Training is optional and that it’s all centered around making and connecting around what you make. This is also the reason that we are trying to encourage the peer to peer aspect of learning.
To help us do that, Mozilla is once again partnering up with P2PU
, a group of incredible connected educators who are helping bake peer to peer interaction into the Webmaker Training content. Together, we’re working on a Training platform
and program that will make it easy for anyone to jump in and see what the Webmaker community
is making to support learning web competencies. We’re running ongoing feedback and testing sessions through this open Wiki
and by talking about this program in the Teach the Web Community Calls
To get involved, you can join our community calls
or post your interest to any one of our monitored channels (#teachtheweb
, the G+ Group
, the Webmaker Newsgroup
…). And if those options don’t appeal to you, you can send me an email and I’ll help you get started!
I see a lot of potential in the modular, remixable way we’re designing our trainings to be.
We’re building the content hosting platform using GitHub Pages, which will make it easy for us to bake in YOUR feedback early and often. It also means that anyone can contribute to Webmaker Trainings by sending a pull request.
You can already build teaching kits
for your specific organization or audience, and in the future, you’ll be able to build entire courses via remix. Using GitHub pages will allow us to build modules (e.g. courses) so that enthusiastic community members and partner organizations can remix them to run modified versions. Imagine if you could easily copy a single module, remix it to add your own lens, branding or curriculum and publish it.
Then imagine that that action earned you a badge. Ideally, you will be able to save your new module to your Webmaker Profile, thereby giving you a URL where your module exists.
When this functionality is working, we’ll have an Open Educational Ecosystem
(OEE, I just made up a new term!) that has learner-focused resources (starter makes), full scale lesson plans for in the classroom (Teaching Kits), and a courseware platform (Training Modules) for online learning. And the icing on the cake? It’s all remixable, it’s all truly open and it’s all built with the Webmaker Community.
We’d love to know what you think about this idea, so leave a comment or get in touch using the channels listed above!
March 10, 2014 04:34 PM
This week is Open Education Week 2014:
Open Education Week is a series of events to increase awareness of open education movement. The third annual Open Education Week takes place from March 10-15, both online and offline around the world. Through the events and resources, we hope to reach out to more people to demonstrate what kind of opportunities open education has created and what we have to look forward to.
Mozilla is playing a role, through a week-long online discussion entitled Open Education and the Open Web. There’ll be a new question to prompt conversation each day in our Google+ Webmaker community.
What does it mean to participate on the open web? How can we encourage others to take agency over the opportunities the open web provides? This discussion led by Mozilla’s Doug Belshaw will explore the participatory culture of the web, why it matters, and what we can do to protect and cultivate it.
Today’s prompt is simple. We’re just asking people to introduce themselves and respond as to what ‘open education’ looks like in their context.
You should join us. It’s totally fine to dip in and dip out. Take the first step:
Click here to join the Mozilla Webmaker Google+ community
Image CC BY mozillaeu
March 10, 2014 09:39 AM
March 08, 2014
We were traveling far and wide this week to spread the badge love! Four members of our team were in Austin at the beginning of the week for the Digital Media + Learning (DML) Conference, ending the week with announcements, share-outs from ongoing projects, and talking badges with just about everyone!
Conference. Then we gathered in Boston for the
On Tuesday, Meg joined for Is Being Tech-Savvy The New MBA? where they looked at some of the unique and innovative ways in which schools and members of the business world are coming together to help prepare students for today’s tech-heavy world.
On Wednesday, Emily and Sunny joined for Osharing examples of badges “in the wild” and digging into what has and hasn’t worked for large-scale international digital assessment programs. Mark will be giving this talk again on a Google Hangout on March 11 - tweet him for more details!
On Thursday, as the DML Conference was kicking off in Boston, An-Me was joined by As we say all the time in the Open Badges community, learning occurs anywhere, everywhere, and throughout our lives. This session looked at how learning and credentialing is expanding, giving an overview of the range of alternative credentials emerging today to help lifelong learners demonstrate what they know and can do.
The second half of our week was spent in Boston for the 2014 DML Conference, which was framed around the theme of ‘connecting practices’ this year.
At this year’s conference - which marked the one-year anniversary since the launch of Open Badges 1.0 - we were thrilled to share two big projects we’ve been working on.
The biggest announcement, of course, was the launch of BadgeKit, available in private beta to organizations for now, with more features and accessibility being built in over the coming year.
We also shared the latest in Open Badges Discovery, a result of the hard work of our team and community, led by our Chloe Varelidi and with essential research, design and technical support from Emily, Jess, Mike, Lucas Blair and more.
We shared demos and discussions of these two exciting evolutions of Open Badges at the Mozilla Science Fair on Thursday, where we were joined by a whole host of other amazing organizations showcasing their work, including Hive, Webmaker, and more.
Yesterday, our community superstars Dan Hickey, Nate Otto and the rest of the Indiana team presented findings and thoughts from their work looking at the Badges for Lifelong Learning grant recipients and developing the badge Design Principles Documentation Project - read their Interim Report to learn more. In their session, titled "It’s Not (just) About the Badges," the team shared their biggest lesson learned: that it really isn’t just about the badges, but about learning ecosystems, and creating pathways within and across these systems, using badges "to highlight nuanced learning and understanding that traditional grading systems do not."
Nate shared his surprise and excitement that the session - which they expected to draw around 20 people to - was attended by 117 people! With this year’s announcement of BadgeKit and the echoes of last year’s Open Badges launch at DML, many at the conference this year were eager to talk about badges and the journey we’ve taken, from a year ago, to today, and onward to future developments.
If you missed any sessions at these conferences, don’t worry! Selected recorded sessions from both conferences are available on the SXSWedu website and the DML YouTube channel. DML concludes today, so if you’re in Boston, check the schedule to see what else is going on today.
Thank you to everyone who braved the bitter cold to join us this week - we look forward to seeing what you all took away from the experience!
March 08, 2014 03:21 PM
This was originally posted on the Summit to Reconnect Learning website.
The 2014 Open Badges Summit to Reconnect Learning brought together nearly 300 participants from around the world to work together on setting the course for the next evolution of Open Badges, a new approach to assessing learning and recognizing skills and competencies wherever they are learned—in school, on the job, in the community, or online.
Since emerging through a series of pilot projects like the Chicago Summer of Learning and supported by research initiatives like HASTAC, Open Badges have demonstrated the potential for disruptive innovation in the way we learn in today’s connected, digital world. Held February 12-13, 2014 in Silicon Valley, the Summit to Reconnect Learning was the first event to focus on moving Open Badges from the edges of innovation to the mainstream.
For K-12 schools, out-of-school programs, colleges and universities, as well as businesses and professional organizations, open digital badges are an increasingly popular way to verify and document skills and achievements that are not adequately measured by standardized tests and traditional resumes or diplomas.
“We have incredible learning resources, but they are highly fragmented and disconnected. What we desperately need is to connect the learning resources we have to the most important parts of kids’ world. That’s why badges are important,” said Connie Yowell, Director of Education at the John D. and Catherine T. MacArthur Foundation, speaking during the opening session of the Summit to Reconnect Learning.
In addition to Yowell, speakers at the Summit to Reconnect Learning included David Theo Goldberg of HASTAC, Nichole Pinkard of the Digital Youth Network, Michael Strautmanis of the Walt Disney Company, Jonathan Williams of Intel Corporation, Miguel Salinas of the Adobe Foundation, Cathy Lewis Long of The Sprout Fund, and more.
Throughout the two-day summit, a wave of new business and education partners made public pledges committing to help accelerate the spread and scale of digital badges for learning.
Leading the pack of commitment pledges was the announcement of the formation of the Badge Alliance, a network of organizations and individuals building and enhancing an open badging ecosystem. This new entity will take lead responsibility for stewarding the Open Badges movement as it continues to evolve. Erin Knight, Director of Learning at Mozilla, will lead the Badge Alliance.
Among the other major announcements made at the Summit to Reconnect Learning, several major global education companies including Pearson, Blackboard, edX, workforce.io and others committed to integrating the Open Badges platform into their digital credentialing systems.
For a full list of organizations and initiatives announced at the summit, visit reconnectlearning.org/pledge.
The next evolution of the Open Badges for learning movement commenced immediately following the Summit to Reconnect Learning with the newly formed Badge Alliance recruiting working group members to dig into key issues, unanswered questions and important use cases. Individuals and organizations interested in joining the movement and contributing to the work of the Badge Alliance can become a member by visiting badgealliance.org.
On the ground, extensive badging systems will be deployed in cities throughout the US through the Cities of Learning initiative, an evolution of the successful 2013 Chicago Summer of Learning that used Open Badges to recognize participation and learning achievements in summer learning programs throughout the city.
About the Summit
The Open Badges Summit to Reconnect Learning was hosted by The Sprout Fund, supported by the John D. and Catherine T. MacArthur Foundation, and sponsored by the Information Technology Industry Council (ITI). Additional event partners include Mozilla, HASTAC, Digital Promise, and NestGSV.
March 08, 2014 10:00 AM
March 07, 2014
This is the first in a series of blog posts where Chris Lawrence, Mozilla’s Senior Director of the Webmaker Community, details plans for a global network of Hive activity. These posts will provide an overview of Hive, as a philosophy and as a Webmaker strategy. They will detail Mozilla’s ongoing involvement and map a path for how Hive will spread to new cities, from initial interest to the creation of sustainable and connected networks.
The Hive Learning Network project is a global set of values, strategies, tools and design principles. Hive has become an integral part of Mozilla’s work and has connected hundreds of organizations and tens of thousands of youth engaged in interest-based production. In line with Mozilla’s mission, Hive also helps people know more, do more, and do better.
We believe 2014 will be a pivotal year in establishing Hive as a global effort linking local educators to an international community through the advancement of connected learning, web literacy, and digital skills.
Together, Mozilla, MacArthur Foundation and other key stakeholders plan to increase Hive participation at the individual, city, and global level by activating educators and empowering them with the tools, community, culture, and practice to re-imagine learning in the cities in which they live.
We have a responsibility to optimize how youth learn.
The inspiration and design of the Hive model springs from a fidelity to connected learning, an emergent educational theory that recognizes the need for a new approach to learning. It is defined by its core values, learning, and design principles. We also know that the technology and the culture of the web is critical to learning in a connected world—helping all young people become citizens of the web is an issue of justice and equity. Our experiences, whether digital or analog, are informed by the web. The web is so integrated into our collective daily lives, we believe that web literacy is essential for youth and the adults who interact with them to be positioned for success in our ever changing world.
We need a Global Hive to spread tools and practices from existing Hives and to help people who want to start Hives in new cities.
Through the work we have done over the past two and a half years with Hive NYC, and more recently with Hive Chicago, Hive Pittsburgh, and Hive Toronto, we have learned:
That there exists a great appetite to iterate proactively on the pedagogies and principles that best prepare people for a rapidly changing world
That too often innovative work and people sit inside silos with little chance to connect their work to others
That we need more collaborators, co-designers, and constituents to advance our collective goals
That there is a growing sophistication of purpose in the types of people, organizations, and communities who gravitate to Hive
The strength of a unifying brand and identity, which is open and available to adopt, adapt, and replicate in order to expand a distributed network
Hive is the city-based strategy within Mozilla’s Webmaker initiative.
Mozilla will house, operate, and co-fund Hive Global to function as a “big tent” for educators and organizations with diverse approaches to come together around connected learning and web literacy. Having a local and grassroots approach with Hive allows us to build momentum for and global adoption of the philosophy, tools, and strategies of connected learning.
As steward of the Global Hive network, Mozilla will construct and convene a governance structure, create materials, offer badges, run events, provide web platforms, and collect metrics that support the work of local Hive leaders.
Our roadmap for Hive Global in 2014
In the coming months, we will be working to identify and document best practices from existing Hive Learning Networks that can be shared with others globally. We’ll share more details and resources for those interested in exploring what a Hive might look like in their city.
Our immediate priorities are to:
Fully integrate the Hive Global plan, situated within Mozilla’s Webmaker initiative.
Expand the pipeline of new cities interested in Hive.
Build core materials and systems that make it easier and faster for people interested in Hive to get involved.
In my next post, I will share thoughts on a tiered engagement model that outlines what contribution to Hive looks like, and how those interested in activating local communities around this model might start on that path.
We’re extremely excited about the progress we’ve made in the past two years, and in the rising interest we’ve seen and heard from people and organizations around the world who have an affinity to our work. In many ways, we’re working to meet the demands of the opportunity to share and spread the Hive model, and so we’d love to hear your feedback or comments on these initial plans–please feel free to add them below or to email me directly.
The post Taking Hive Global appeared first on Hive NYC.
March 07, 2014 09:08 PM
Open Badges Community Call, March 5, 2014
This week, the Open Badges team and community were in Austin for
Emergency Hack Jam & Community Aid Badging
Jess led sessions on community aid badging and emergency hack sessions at last year’s MozFest and some great work came out of that in-person and online group:
"During times of crisis, such as the aftermath of Hurricane Sandy, relief work can be really complicated - even if people are really well intentioned. One of the hugest problems that I encountered with Rockaway Help was a lack of a feedback loop between us (the grassroots organizers), the individuals in need and the volunteers. This is crucial for many reasons but to name a few : efficiency with task management, ability to acknowledge volunteer skillsets, the ability to match volunteers with appropriate tasks, and the ability to identify mentorship opportunities.
By connecting volunteers directly to members of affected population through Open Badges, we empower people who need help to engage in the relief effort, and maintain involvement before and after they have received aid.”
In the aftermath of Hurricane Sandy, which hit Jess’ hometown of Rockaway Beach, NY, Jess saw a huge disconnect between the thousands of people wanting to help with the relief efforts and the needs of the affected communities, particularly when it came to putting those with the right skills in place to be most effective.
Badges, Jess saw, could be the key to
As project coordinator, Jennifer has been exploring Open Badges and other digital tools to develop a set of educational resources to support trainers and learners within schools and the community. She has proposed the use of Open Badges for “evidence based, granular accreditation for the training elements of the project.”
Jennifer’s project looks at three key areas:
Inspired by the Scottish Qualifications Authority’s exploration of badges
, Jennifer set up a test site at to start looking at how they might start credentialing the skills, literacies and other competencies represented by badges. The Commonwealth Games will bring a lot of media attention to the area, and Jennifer would like others to see this as an opportunity to accredit digital storytelling and use badges to capture what’s being told, learned, and shared.
This test site will be brought to schools in the coming weeks, and after a testing period it is hoped that the system can be expanded out by handing it over to others to build upon for their own schools and learning communities.
March 07, 2014 08:04 PM
Yesterday we announced the release of BadgeKit, a set of open, foundational tools to support the entire badging process. We’re super excited to start helping people get badge systems up and running using one or more of these tools.
As part of our efforts in rolling out the private beta launch, we will be hosting a series of general BadgeKit training sessions over the next two weeks.
These sessions will look at how all the tools in BadgeKit will work, and we will be hosting more in-depth training sessions on the individual tools in the following weeks.
There will be five sessions held over the next two weeks:
- Monday March 10, 9-10am ET
- Wednesday March 12, 4-5pm ET
- Thursday March 13, 8-9pm ET
- Tuesday March 18, 1-2pm ET
- Wednesday March 19, 4-5pm ET
Please register for the date and time that works best for you by clicking this link: https://attendee.gotowebinar.com/rt/8459989167167596034
Looking forward to having you there!
March 07, 2014 06:25 PM
March 06, 2014
We’ve talked a ton about BadgeKit over the past few months from its initial announcement back in October at Mozfest to BadgeKit MVP defining, tech defining, user experience design, to more recently BadgeKit for Cities.
Many of these posts pointed to BadgeKit being made available at the Digital Media & Learning conference, this year taking place in Boston from March 6 through 8.
And we’re finally here! We will be making BadgeKit available to organizations interested in issuing open badges. As previously mentioned, this initial release of BadgeKit targets organizations, like cities, who want to stand up larger-scale badge systems. This was a natural evolution of the work we did for Chicago Summer of Learning last year and the tools we developed to support that initiative such as Badge Studio (badge design tool), Open Badger (badge defining and issuing tool) and Aestimia (badge application and assessment tool).
So what will this initial release of BadgeKit entail for issuing organizations?
* Enable access control
The issuing organization can create an uber admin login and from there grant some level of access control like who gets to issue a badge and who gets to assess/review a badge. We are thinking about adding more granularity down the road with ongoing user feedback and issuer requests.
* Design a badge
The issuing organization can get started on designing and defining their badges. BadgeKit will support the full badge life cycle states from draft form, published to archived. The badge design and defining experience will be scaffolded through the introduction of templates. An example of templatizing badges can be found in the badges designed and issued as part of Chicago Summer of Learning. These badges all shared a hexagonal shape and a Chicago city banner that hung across it.
This is an example of templates used to create consistent badge design but they can also be used for content creation. Some badges that are part of the same program may share similar information, like issuing organization name, program name, including elements of criteria. Rather than the issuing organization having to rewrite this information with each new badge, templates can help build on templatized content. We think templates can greatly help streamline the badge creation process for organizations.
* Create badges that level up
Not only that, issuing organizations can build in leveling up features into their badge system. We are calling these milestone badges. An issuer can define the set of badges that together unlock a larger badge, which we are calling a milestone badge.
* Issue a badge via email
The issuing organization will be able to issue a badge using the earner’s email. However, as perviously mentioned, BadgeKit is intended to be a backend admin support for issuing orgs who have existing sites where their communities reside. When a badge is issued to an earner via email on BadgeKit, this information is relayed to the issuing org’s application for the issuing org to determine how the badge will actually be delivered, whether via email, SMS or message in a bottle. Badge issuing via email is supported through the BadgeKit API with the issuer, customizing specific experiences according to their community needs and desires.
* Display a badge on Issuer site via BadgeKit API
The issuing organization will be able to pull all the badges they have designed and created on BadgeKit onto their own website through an API and customize the badge interaction experience for their community of badge earners.
* Support earners to apply for a badge on issuer site via BadgeKit API
When an earner is on the issuer site and comes across a badge that she would like to earn and can apply for online, she can do so. The earner, or prospective earner in this case, can click through and see the badge criteria and apply for the badge by submitting relevant information and evidence. This experience is supported by the BadgeKit API.
* Assess a badge
Once the prospective earner has submitted all relevant information on the issuer site, that badge application becomes accessible on the badgekit.org site to badge assessors/reviewers who have been granted the appropriate access controls from the issuing organization. Assessors/reviewers can then see the queue of badge applications and start evaluating them based on pre-defined criteria and/or rubrics. They can provide feedback and determine whether to issue or deny the earner of the badge. As mentioned in bullet 4, the earner experience of the actual delivery of the badge is defined by the issuer.
* Support earners to send their earned badges to federated backpacks
n.b. Federated backpack feature will come later this month
Because BadgeKit is integrated with the open badges standard and APIs, the earner has the opportunity to send their earned badges to federated backpacks where they can decide how they want to further share it out to various social media channels.
In addition to all this, it’s worth noting the brand definition work that our designers took on. We have a nice streamlined BadgeKit logo that is cohesive with the parent brand of Open Badges as well as Mozilla. This work was led by our designer Adil Kim with the guidance of our Creative Lead, Jess Klein who has written about this in greater detail in her blogpost: http://jessicaklein.blogspot.com/2014/03/on-designing-badgekit.html
We’ve made a lot of progress in the past few months but we still have a lot of work to do. As you can see, this initial release is focused on issuing organizations who have some level of technical resources and have an existing community-facing site into which they can integrate their badge system. Thereby it seemed appropriate to call this release private beta.
However, the goal is to make this more widely accessible in subsequent releases. As you well know, we develop and design in the open so all our code, sketches, wireframes and staging information are in fact out there for anyone to keep an eye on and poke holes at.
We’re excited to have reached this major milestone and look forward to feedback from issuing organizations who start to plug in!
n.b. We realize there may be a bunch of questions so we’ve put together some FAQs so take a look! http://badgekit.org/help Thanks to you all and as per yooszh, more to come!
March 06, 2014 06:59 PM
Today we are really excited to officially announce the release of BadgeKit, a new set of open, foundational tools to support the entire badging process for organizations developing badges for their communities.
While open badges has been gaining momentum - with more than 2,000 organizations issuing badges that align with the Open Badges standard - there are still ways we can make it easier for organizations to join the ecosystem, with free, flexible, open badging tools that support the needs of issuers, learners and consumers. There are too many gaps in the badging experience and many of the existing options are too closed, too expensive or too big. In fact, given the current options for organizations interested in issuing badges, it can be harder to make an open badge than a closed badge!
That’s why Mozilla is happy to launch BadgeKit. BadgeKit will:
- Support key stages in the badging experience including creating, designing, assessing and issuing;
- Include remixable templates and milestone badges allowing for easy customization;
- Provide modular and open options (standards) for the community of badge makers to use and build upon within their existing sites or systems;
- Build our values of openness, interoperability, agency, choice, and connectedness into the core and help shape emerging badge systems.
BadgeKit builds on existing technologies that have evolved out of several years of work and user testing, including the Chicago Summer of Learning. In fact, specific tools within BadgeKit are currently being used by key partners within the badges ecosystem. We anticipate opening up Mozilla BadgeKit access throughout 2014.
We softly released BadgeKit at last year’s MozFest, and we’ve shared our progress along the way through blog posts and Github milestones. We are thrilled to be reaching this milestone today in the release of BadgeKit.
Mozilla BadgeKit will be available in two forms:
- A hosted version of Mozilla BadgeKit is available in private beta for select partner organizations that meet specific technical requirements.
- Anyone can download Mozilla BadgeKit code from GitHub and implement it on their own servers.
What tools are included in BadgeKit?
BadgeKit provides lightweight, modular and open options for the community of badge makers to use and build upon within their existing sites or systems, including:
- Design:A tool for defining all of the metadata, including criteria pages, and finalizing visual design for each badge.
- Templates: Visual and metadata designs that can be remixed by anyone creating a badge.
- Milestones: The ability to have a group of badges level up to a larger, more significant badge.
- Assess: A tool for mentor or peer assessment that includes issuer defining rubrics and criteria for a badge, the ability for learners to apply for a badge by adding information and evidence, as well as access for assessors to manage applications and enable review and scoring.
- Issue: A tool for awarding badges to learners and hosting assertions to enable badges to be pushed to Backpacks.
- Collect: A “Backpack” for collecting badges across various experiences or organizations.
In the coming year, we will be developing additional tools for BadgeKit, as well as minimizing the technology requirements needed for access. Tools coming soon include:
- Discover: A directory of available badges with features for searching, filtering, wish listing and endorsing badges.
- Share: A tool to enable easy sharing of badge on various sites across the web (i.e. Facebook, Twitter, Tumblr, etc.).
- Collect: Backpacks will become “federated”, meaning that different instances still plug into the broader ecosystem and can share data across.
The tools are open source and have common interfaces to make it easy to build additional tools or customizations on top of the standard core, or to plug in other tools or systems.
Who is BadgeKit for?
BadgeKit is currently in private beta and can be used by any issuing organization that meets specific technical requirements. It is aimed at organizations that are building full badge systems and want to leverage their own sites and systems on the front end, as well as have access to technology resources. Tool providers might also be interested in leveraging BadgeKit to extend their own tools, or build additional customizations on top of BadgeKit.
Initial technical requirements:
- You have a front-end website or the resources to develop one
- You have technical resources on staff to integrate the BadgeKit APIs into your experience
- You intend to build or roll out a badge system for your community and organization in 2014
We are exploring ways to create a lighter weight version of BadgeKit that could be used by for individuals and small organizations in 2014, but in the meantime, you can check out the additional community driven issuing platforms at http://bit.ly/platform-chart to help you get started.
How do you get started?
We have a hosted version of Mozilla BadgeKit available in private beta for select partner organizations that meet specific technical requirements. And anyone can download the code from GitHub and implement it on their own servers.
BadgeKit can be accessed in two ways:
- Software as a service: At BadgeKit.org, you’ll be able to access a hosted version of the tools to build out badges, remix badge templates, create badge levels, issue badges, etc. APIs will make it easy to then pull the badges and end user interfaces into your own website. All of the backend pieces are hosted, supported and updated by Mozilla, and you’ll have complete control over the experience of your end users through your own sites.
- Download: Easily download the code from https://github.com/mozilla/openbadges-badgekit and install the tools on your own server.
What’s the difference between these two options? Well, if you choose to download the code, you will be in charge of the backend and hosting of BadgeKit, and will be able to customize and extend the tools as much as you need. For the fully hosted version of BadgeKit, all the backend pieces are hosted, supported and updated by Mozilla while you still have complete control over the experience of your end users on your own sites through our APIs.
We will be hosting a series of webinar trainings in the coming weeks to further dive into how BadgeKit works. Stay tuned for more details!
March 06, 2014 06:23 PM
This has been a crazy week for the open badges team.
Amongst our team members, we are covering 3 conferences: ATP Innovations in Testing, SXSWEdu and the Digital Media and Learning conference.
This includes 3 panel discussions, 1 interactive talk and presentation, 1 ignite talk, 2 Science Fair booths preparation, not to mention 1 BadgeKit private beta release and 1 Discovery prototype showcase.
WE CAN DO THIS!
I wrote this while I was on a plane with colleagues Meg from the Badges team, Matt Williams from SF Hive and Dustin from Sprout Fund. We had departed an unseasonably frigid Austin, having survived SXSWEdu, and were headed to an even more frigid Boston for DML.
So where are we at this midway-ish point in the week?
- I think we’re pretty good to go with BadgeKit Private Beta release. More to come on that through several of our channels.
- We’re excited to showcase the Discovery prototype at DML and to get feedback from conference attendees.
- We have 1 panel at ATP, 2 panels at SXSWEdu under our belt now and have 1 more SXSWEdu panel, 1 ignite talk at DML and 2 Science Fair booths to go.
Reflections on the panels and sessions so far:
I couldn’t help but notice that the badges and digital credentialing conversation has come a long way. The ATP Innovations in Testing has not been a conference we had participated in the past. It is attended by the well-known guardians of high stakes testing, assessment and accreditation like Pearson, ACT, ETS etc. I popped into a couple sessions and was surprised to see the level of interest around digital credentialing and also its increasing relevance. On the actual panel that I had the honor of being a part of, it was clear that the badges conversation had expanded beyond the esoteric and was reaching a broader audience.
*** A session at ATP Innovations in Testing about the Changing Landscape of Recruiting in Industries, mentioned Digital Credentialing and Mozilla Open Badges.
I would say the questions fielded and the level of interest and enthusiasm shown at our SXSWEdu sessions would corroborate that.
A lot of work remains, both in the near term (this week) and longer term (getting wider adoption of open badges as complementary digital credentialing). While extremely tired right this moment, I’m also still pretty excited and looking forward to all the adventures ahead.
March 06, 2014 04:27 PM
After several months of hard work by the Open Badges team, we are announcing that BadgeKit is available for access to Private Beta. This means that BadgeKit is now available in two forms: a hosted version of Mozilla BadgeKit available in private beta for select partner organizations that meet specific technical requirements, and anyone can download the code from GitHub and implement it on their own servers. BadgeKit is a set of open, foundational tools to make the badging process easy. It includes tools to support the entire process, including badge design, creation, assessment and issuing, remixable badge templates, milestone badges to support leveling up, and much more. The tools are open source and have common interfaces to make it easy to build additional tools or customizations on top of the standard core, or to plug in other tools or systems.From a design perspective, this milestone represents refinements in user research and testing, user experience, user interface and branding.
In preparation for this release, we conducted extensive user research to define the needs and goals for badge issuers. This work, led by Emily Goligoski, helped to define requirements for the BadgeKit offering as well as inform the user experience. The research was done using a variety of methodologies, however, it is worth noting that all of this work was done in the open. Emily organized distributed user testing in key markets such as New York, Chicago and Toronto to do everything from needs analysis to accessibility and functionality testing. The Open Badges weekly community calls were leveraged to pull in input from the highly motivated research and practitioner cohorts. Much of the work is documented both on her blog and in github. We paired every implementation milestone with some form of user testing and iteration. While this may sound obvious, it was a new way of working for our team, and I can unequivocally say that the product is better because of this practice. User research and testing did not happen in a bubble, but rather it became completed integrated with our design and implementation cycle. As a result, developers and designers became comfortable making informed iterations on the offering, as developers, designers and team researchers all participated in some form of user testing over the past three months. As a direct result of the extensive research and testing, the user experience for the entire BadgeKit offering was deeply refined. This work, led by Matthew Willse introduced some new features, such as badge “templates” which give the ability for any badge issuer to clone a badge template and remix it. This gives us the unique ability to offer template packages based on common badge requests from the community, as well as eventually to empower the large Open Badges ecosystem to develop badge templates of their own (and perhaps explicitly state how they are comfortable with their content being shared and remixed). One component of this work that evolved as a direct result of testing, was the increased attention to copy. Sue Smith led this work, which entailed everything from tool tip development and a glossary to API documentation. Considering that BadgeKit takes an issuer from badge definition and visual design to assessment and issuing
|We did user testing with members of the Hive in Brooklyn.|
,designing the user experience was no small effort and the attention to detail combined with designing in the open - proved to be a solid approach for the team. Perhaps the most obvious design component of this release is the user interface design and brand definition. Adil Kim kicked off this work with an exploration of the brand identity. BadgeKit is under the parent brand of OpenBadges, which sits under the even larger parent brand of Mozilla - which gave us the constraints of designing within the brand guidelines. After exploring options to represent the visual metaphor for this modular system, here is the new logo:The logo is meant to evoke the imagery of both a badge as well as a tool in one glance. For the untrained craftsperson (ahem) - while gazing into the mark - you will see a bolt . This connotes that BadgeKit is a tool, something that allows you to dive into the details and construct a badge, and a system for your community. The logo incorporates the palette from Mozilla Open Badges, in a playful mobius - at once implying that while this is a handcrafted experience, it is also a seamless one. This logo nicely fits into the larger brand family while reading on it’s own, as if to say, “hey, BadgeKit is the offering for badge MAKERS, dive in and get your hands dirty!” The brand is in turn extended to user interface design. The overall art direction here was that this needs to be clean, yet approachable. We know that many organizations will not be using all of the components in the interface directly on badgekit.org, however, the design needs to take into account that everything needs to be accessible and read as remixable. Some details to note here are the simplified navigation, the palette and subtle details like the ability to zoom on hover over thumbnails. It’s worth noting that while Emily, Matthew, Sue and Adil , as well as Carla, Meg, Erin, Jade, Sabrina Ng, Chloe and Sunny were invested in much of this design work, there was an intentional yet organic partnership with the developers (Zahra, Erik, Andrew, Chris, Mavis Ou, Mike and Brian + many, many community contributors) who were doing the implementation. We had weekly critiques of the work and often engaged in conversation about design as well as implementation on github. Another component of this work is looking ahead towards future features. Chloe Varelidi lead work here thinking through the potential for badge and skill discovery. Under a grant from The Bill & Melinda Gates Foundation, Chloe and her team are thinking through ways to represent earner pathways. This eventually will be leveled up into the core BadgeKit offering, but you can start to dip your toes into those features by checking out the work here.
And the good news is that design never ends! Design isn’t just a destination, it’s an invitation to a conversation. Check it out, let us know what’s working and importantly, what’s not.
March 06, 2014 09:27 AM
March 03, 2014
Way back in October, you voted for the four Open Badges proposals up for nomination for the 2014 three sessions were accepted to the conference - so thank you!
Conference + Festival. All that voting paid off -
If any of you are heading to Austin next week for SXSWedu, look out for Meg, Emily, Sunny and An-Me at the conference next March.
Below are details of the three sessions our team will be speaking on, including dates, times, locations, and some sample tweets to help us get the word out.
To access the full schedule, go here: http://schedule.sxswedu.com
Is Being Tech-Savvy the New MBA?
Tuesday, March 4
10:30AM - 11:30AM
Hilton Austin Downtown Salon D
With the tough economy and staggering costs of higher education, more and more college students are opting out of postgraduate degrees and plunging headfirst into the job market. But are they really prepared for what’s out there? In today’s hyper digital world, graduates need to have the tools today’s businesses require: like online skills and savvy. Here are just some of the unique and innovative ways in which schools and members of the business world are coming together to tackle the issue.
Meg will join for Is Being Tech-Savvy The New MBA?
Open Badges Go Global: Building Valuable Pathways
Wednesday, March 5
9:00AM - 10:00AM
Hilton Austin Downtown Salon A
We’ll share badges “in the wild,” what has and hasn’t worked for large-scale international digital assessment programs, and ways employers are using this technology to identify talent. In this Core Conversation participants will also design their own systems to empower youth in times of transition.
Emily and Sunny will join for O
Enabling Stackable Credentials: The Future is Now
Thursday, March 6
9:00AM - 10:00AM
Hilton Austin Downtown Room 400/402
Today more than ever, learning occurs anywhere, everywhere, and throughout our lives. This new, expanded learning ecosystem means credentials related to documenting learning are evolving too. Join Parchment, Open Badges, the American Council on Education (ACE) and Western Governors University to gain an overview of the spectrum of alternative credentials emerging today and how lifelong learners can demonstrate how much they know and how well they know it.
An-Me will join
- Join us @SXSWEDU in Austin: @megcolek @anmechung @soletelee + @emgollie talk #openbadges on 3 sessions || schedule.sxswedu.com #SXSWedu
March 03, 2014 09:01 AM
Those keeping track will know that last year I moved teams within the Mozilla Foundation. I moved away from the Open Badges team to focus on (what is now) the Web Literacy Map. Despite this, I still have close ties to the Open Badges team. In fact, I’m currently helping design Webmaker and Web Literacy badges.
The big news at the start of 2014 on the Open Badges front is that there’s a new Badge Alliance to grow and develop the wider ecosystem. The Badge Alliance is a non-profit organisation to be led by Erin Knight, co-founder of the Open Badges Infrastructure (OBI). Over the next few months she’ll be joined at the Badge Alliance with a few members of the current Open Badges team. There’s more detail in Erin’s blog post.
Happily, Mozilla will continue to develop and nurture the open source technical stack behind the OBI. The next milestone is the release of BadgeKit in the next few months. This should remove any remaining friction from issuing Open Badges. For more on BadgeKit be sure to follow the blogs of Sunny Lee and Chris McAvoy. And, as ever, you should also follow Carla Casilli’s posts on badge system design.
If you want to keep up with what’s going on with Open Badges in general, the easiest thing to do is to keep tabs on the Open Badges blog. The weekly ‘Badger Beats’ in particular is a useful round-up of news from the world of badges. There’s also a good deal of conversation within the Open Badges discussion group. This is a friendly forum for those planning to dip their toes into the water for the first time.
Having joined Mozilla in 2012 to work both on the Open Badges project and (what’s grown into) the Web Literacy Map. I’m delighted that the former has been incubated with such success. I’m also pleased that the latter is to underpin both the next iteration of Webmaker and Mozilla’s aims to create a more web literate planet.
If you’d like to get involved with Mozilla’s work to create a better web then we’d love to have you onboard! The easiest way to get involved with the two projects I’ve mentioned is to join their respective weekly calls. The Open Badges community call is every Wednesday, and you can join us for the new #TeachTheWeb community call every Thursday.
Questions? I’ll do my best to respond to them in the comments below.
Image CC BY-NC-SA RSC Scotland
March 03, 2014 08:18 AM
February 28, 2014
It’s been another busy week for Open Badges as we gear up for the 2014 Meg, Emily, Sunny and An-Me, who will be speaking at three sessions between the four of them!
Conference and Festival in Austin, Texas next week. If you’re joining us, look out for
See where and when on the SXSWedu schedule: http://sxswedu.com/conference/sessions
The DML Conference is also happening next week - stay tuned for some exciting announcements coming out of Boston towards the end of the week!
Here’s what we’ve been up to this week:
On Monday Anne Derryberry hosted the second of this year’s Open Badges MOOC sessions on assessment - a full summary and link to the recording is available here.
- This week’s Research & Badge System Design Call featured a presentation from Ugochi Acholonu, a postdoctoral researcher working with the Digital Youth Network (DYN) who shared her thoughts on equity and badges. A full summary and a link to the audio download is available here.
On our Community Call we were joined by Nancy Latimer, who works at Mountain Lakes High School in New Jersey, which has recently started an “Online Academy” where students earn digital badges for taking free online courses. A full summary and a link to the audio download is available here.
- Our Director of Badge System Design + Implementation Carla Casilli wrote a blog post on the ‘myth of the lightweight badge' in which she argues that all badges can have value as part of a larger identity-building process that badges can help facilitate.
See what I meant about it being a busy week?
Check out the links above, feel free to tweet us anything badgeriffic you see over the weekend, and we hope to see you at SXSWedu and/or DML next week!
And now…..it’s time for the weekend!
February 28, 2014 09:30 PM
Badges: New Currency for Professional Credentials
Session 8: Assessment Strategies for Effective Badge Systems
Session Recording: http://bit.ly/OBmooc8
This week was the second 2014 session of the #openbadgesMOOC, New Currency for Professional Credentials with a presentation on Assessment Strategies for Effective Badge Systems led by Anne Derryberry,.
When building badge systems, assessment is one of the key components that must be considered. Before a badge can be awarded, issuers must have a way to verify that a badge earner has acquired the skills or competencies represented by the badge. That verification happens through evidence-based assessment, placing the emphasis on a demonstration of mastery rather than the recall of learned information. As Anne pointed out in her introduction, “badges don’t care where the learning happens” - as long as the individual can demonstrate competence and provide evidence to back it up, they have earned the badge. Those badges can then be stacked, representing granular achievements that combine to lead to mastery of a complete skill set.
During this session, we looked at various strategies for assessment, including traditional vs. authentic assessment.
Most of us are familiar with traditional assessment: taking tests where learners don’t have to know the answer to questions as long as they can recognize it from a selection. Learners may have to write short answers or essays that require the recall or regurgitation of information, providing indirect or abstract evidence, in an environment structured by the assessors or instructors. These tests can be largely evaluated by non-experts, and are frequently scored by ‘machine readers’ using keywords to determine competence.
By contrast, authentic assessment focuses on learners’ abilities, and includes performance tasks, capstone projects, and portfolios. It requires demonstrating the application of learned skills and essential knowledge in real-world scenarios using direct evidence in an environment structured by the learner. Rubrics are often used to evaluate these tasks to determine the assessment outcome.
You can see the differences laid out in this graphic below:
Authentic assessment tends to be the preferred type for badge systems, but as Anne Derryberry noted, it can be harder to evaluate and score within this kind of assessment framework. Many use a combination of traditional and authentic assessment methods when designing their badge systems for learning - as long as learners can demonstrate competence and evidence of mastery, the means of establishing this can fall anywhere on the spectrum between traditional and authentic assessment.
Many in our community are familiar with Dan Hickey’s work at Indiana University (alongside Rebecca Itow, Nate Otto and a team of others) on the badge Design Principles Documentation Project. Through looking closely at the developing badge systems that grew out of the Badges for Lifelong Learning Competition, they have identified a set of principles for assessing learning that leads to digital badges, including the use of ‘leveled’ badge systems to show progress, aligning assessment with existing standards, the use of e-portfolios and rubrics, and getting students involved in designing badge criteria at the granular level.
Anne introduced the group to a real-world example of one of these badge systems being built at UC Davis for the Sustainable Agriculture & Food Systems Major (SA & FS). These efforts are led by Joanna Normoyle, the Experiential & Digital Media Learning Coordinator at UC Davis Agricultural Sustainability Institute.
The SA & FS badge system has five types of badges: skill, knowledge, honor, experience, and competence. Each type has a set of pre-determined badges that were designed based on program requirements, but the system also allows both faculty and students to develop other badges within each badge type.
Assessment within the program includes a portfolio component as well as the badges, and the plan is for the system to allow for peer assessment and review of portfolios as the program and badge system grows. Currently, badges are earned through the evaluation of an application that uses portfolio work as evidence of learning that is evaluated by faculty and mentors:
The assessment itself is still primarily offline - students present their work to a panel of faculty who evaluate the badge submissions - but the online platform allows for the collection, documentation and distribution of students’ work. Through the community elements of this platform, students are able to access other students’ shared work and learning pathways, to see connections to their own work and opportunities for further growth, and allow students to create a learning experience that suits their interests.
The SA & FS system allows students to design badges as part of the system, which opens up the discussion of the vigor of the badges being created. As Joanna pointed out, there are many ways that students are learning that mentors and instructors are not always aware of - particularly in a more independent learning environment like the one fostered at the Agricultural Sustainability Institute. These student-designed badges (which are moderated by a faculty member, currently Joanna) can reflect the learning happening in other courses, internships, or informal experiences that have value to the students.
Currently, the SA & FS badge system and online platform is not connected directly to university and graduation requirements. The program itself has been working towards competency-based learning and self-assessment for a number of years, and so they wanted to treat the badges as an extension of this exploration of students’ interests and development. Rather than tying them to traditional grades, they have chosen so far to keep them in the realm of ‘alternative’ credentials.
To find out more about the UC Davis Agricultural Sustainability Institute, check out the website: http://asi.ucdavis.edu/students/front-page
We look forward to continuing this course with you! See below for details of the next session.
Go to http://badges.coursesites.com/ to access more resources, information, and challenge assignments to earn badges.
Monday, March 31, 2-3:00 ET:
Introducing Mozilla’s BadgeKit
BadgeKit is a new set of open, foundational tools that will make the badging process easy and simple. BadgeKit will be launched by Mozilla’s Open Badges team in March of 2014. This session will provide a general overview of BadgeKit, including: Why BadgeKit? What is BadgeKit? A deeper look at BadgeKit tools, and more!
February 28, 2014 07:47 PM
February 27, 2014
Open Badges Research & Badge System Design Call, Feb. 26, 2014
Speakers: Ugochi Acholonu, DePaul University, + Dan Hickey, Indiana University
This week’s Research & Badge System Design Call featured a presentation from Ugochi Acholonu, a postdoctoral researcher working with the Digital Youth Network (DYN). Along with Dan Hickey, Ugochi has been doing research into learning analytics and badges and began a discussion around equity and badges. They are making a particular distinction between equity and access.
February 27, 2014 08:26 PM
Open Badges Community Call, Feb. 26, 2014
- Nancy Latimer, Educational Technology Specialist, Mountain Lakes High School
This week we were joined on the Community Call by Nancy Latimer, who works at Mountain Lakes High School in New Jersey, which has recently started an “Online Academy” where students can take free online courses (such as those offered via MOOCs or OER) and earn digital badges.
Mountain Lakes Online Academy Badges
Students participating in the Online Academy search for learning experiences via MOOC providers and other courses of extra- or co-curricular education, then present a “demonstration of learning” in order to earn badges as recognition of course completion. There were eight students who took part in the first semester of the Academy, exploring various different subject areas, including poetry, algorithms, philosophy, foreign languages, medical neuroscience and international development.
The badges earned in the Academy were not representative of academic credit, which Nancy found the students were supportive of, with some even voicing a preference for the badges being non-credit learning offerings. This was an interesting result, as many of our community members who have used badges in education have found that obtaining academic credit is often a goal of a new badge system, an indicator of external recognition or value of the badges.
Even though the badges were not related to academic credit, Nancy ensured the badge activities and criteria were robust.
You can also check out this example of an Online Academy Certificate and an Online Academy Evidence of Learning Document to see how Nancy has structured the criteria and evidence components of the Academy.
Join us next week to hear from
February 27, 2014 08:23 PM
February 26, 2014
As our Mozilla team prepares for SXSWEdu and the Digital Media & Learning conference next week, we’ve been deep in usability testing for BadgeKit. This software toolstack is intended to improve the issuing, visual design, and assessment of digital open badges. We’re focusing user testing on two core audiences:
- Cities: Last year, the Chicago Summer of Learning was a city-wide experiment in recognizing learning that takes place during out-of-school months. It has ignited excitement across the country and from cities from New York to Dallas. Product lead Sunny Lee has more to say about the expansion of badge-able summer learning programs, and we’ll be hearing from cities more about their needs through live user testing in Boston next week.
- Mozilla teams: This year we’re planning to support three types of “Mozilla-wide” badges: 1) organization-issued badges; 2) team/product badges (to directly recognize contributors across different Mozilla offerings, including Engagement and Webmaker); and 3) individual/community badges created by non-staff members to celebrate their collective efforts. I’m working with our badge system design lead Carla Casilli in thinking about templates and tools–including BadgeKit–for the #1 and #2 effots. This spring we may be doing a Mozilla roadshow of sorts, talking to product teams about what they’ve learned in trying to recognize their contributors and how badges might further that work.
Testing with these audiences has involved lots of in-person reviews of the BadgeKit staging site. In recent weeks, we heard a few complaints about the site menu, which we tried to indicate with the “hamburger” icon you see at top. Some people thought it didn’t suggest a set of options to them. Others complained about the placement, which we had placed on the left side of the site navigation. We noticed enough feedback on this particular design choice that our designer Matthew Willse reimagined a more evident set of menu options. We’re grateful to the people who gave us this valuable information, and I’m lovingly calling them “Hamburglars.” The feedback on the change has been positive (read: many people haven’t gotten stuck trying to figure out where they might go next). This has freed them up to tell us about other things they’ve bumped up against, including language choices, which we’ll be tackling next.
This listening work is very important as we look to help badges have real impact in more earners’ lives. It’s related to the pursuit of larger reach that Frank Catalano described in a thoughtful piece in EdSurge this week. Do read it, and share your thoughts.
Thanks for this unique bottom visual goes to the Perth-based motorcycle team that created it.
February 26, 2014 03:22 AM
February 25, 2014
Frank Catalano | Digital Badges Need Mass to Matter
Parts of the edtech world are abuzz about “open”€ digital badges. But despite the excitement about, and real potential of, these intelligent graphics in education they will need more than current passion or even eventual ubiquity to succeed. They will need to mean something to more than just those who give them or get them.
One of our regular community contributors Frank Catalano published this column on EdSurge today, raising the important question about what gives open badges their value with a good dose of skepticism to keep us all on our toes.
It’s been an exciting start to 2014 for Open Badges, and at the recent Summit to Reconnect Learning, the Twittersphere was flooded with news of high-profile commitments from organizations such as ETS, edX, Workforce.io, and Pearson to integrate badges alongside our growing community of independent badge issuers.
We are often asked about the value of open badges, and there are many factors that impact badge value: issuer reputation, quality of criteria, type of evidence submitted…..but ultimately, as we’ve heard time and time again from those in our badge issuing community, if there is no market need for badges, they lose value and a badge system can’t grow or truly serve those participating in it. Badges are a great way to recognize skills and achievements, but if there’s no-one to recognize the badges, what are they worth?
Frank captures this in his column, where he iterates that “badges, to truly take off and make the best use of their portable, verifiable and stackable qualities, need to be valuable to a third party. They need mass.” (Our italics.)
Read the column in its entirety here.
You can follow Frank on Twitter at @FrankCatalano
February 25, 2014 06:42 PM
February 21, 2014
Welcome to the [almost] weekend!
Pushing forward with the momentum of last week’s Summit to Reconnect Learning, we’ve been sharing details of the new Badge Alliance, announced at the Summit as an independent network that will oversee the growth of the open badge ecosystem. Read reflections from the Summit here, and more about the Alliance here. For more information on the commitments pledged at the Summit, go to the Mozilla blog.
Here’s a quick run-down of what else has been happening in the past week or so (just in case we missed a few things with the Summit last week):
- On this week’s Community Call we were joined by Elizabeth Merritt, Founding Director of the Center for the Future of Museums, where she has been developing badges for museum staff training. We were also joined by Josh Finkel who founded the Tech Foundry and is looking to develop a summer learning program to train kids for IT jobs and use badges to recognize tech and soft skills. Read the summary and download the audio here.
On the Research & Badge System Design Call, Flavio Escribano and Jordi Moretón led a discussion on badge rank and score based on work they’ve been doing in Europe on Badge Culture. We also heard from Chloe Varelidi and Lucas Blair, who shared updates on their work on discovery and pathways. Read the summary and download the audio here.
Nate Otto wrote a blog post on the ongoing progress of the badge Design Principles Documentation Project - read more and sign up for regular updates here.
- We Are Snook announced that the Badge Maker Project (one of our favorite offline tools form MozFest and the recent Summit) will be fully launching in early March, with exciting badge baking capabilities on their beta platform!
The CAE (Council for Aid to Education) will be issuing digital badges using ProExam Vault for their flagship assessments: the Collegiate Learning Assessment (CLA+) and College and Work Readiness Assessment (CWRA+) in college and K-12.
Robert Moran of the Huffington Post wrote a piece on inequality, automation and the political class, citing education as the key to closing the skills [and equality] gap, and Open Badges as an example of “a free market response” where “an alternative learning and credentialing system” focusing on skills can operate alongside the formal education system.
Sen. Marco Rubio of Florida recently called accreditation a “biased and broken system,” calling for more out-of-school learning to be recognized in a flexible, efficient way. Oh, if only…..
Also - don’t forget to join us on Monday for the second session of the 2014 Open Badges MOOC offerings, on Assessment Strategies for Effective Badge Systems.
February 21, 2014 05:46 PM
Last week, we shared the exciting news and announcements coming out of the Summit to Reconnect Learning, including new commitments from major players in education, workforce development and community engagement, nine new Cities of Learning, and the forming of the Badge Alliance, to be led by our fearless badges leader, Erin Knight.
Erin wrote a blog post on her thoughts about the Badge Alliance as “the natural and necessary evolution of the badging work” and reflected on her role up to and beyond this announcement:
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.
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:
It’s an exciting time for badges: the high energy and excitement of the Summit is now propelling us forward to continue the amazing work being done both within Mozilla and beyond in the global community that we’ve built.
Many important voices in that community can be seen in the above photo, where the founding members of the Badge Alliance stood behind Erin at the Summit. One of those members is Blackboard, who publicly announced their commitment to the Alliance yesterday, citing badges as the “key enabler of competency-based learning and approaches that empower learners.” Blackboard will be joining Mozilla, HASTAC, the MacArthur Foundation, and Summit organizers the Sprout Fund, as well as other leaders in learning to shape the future of open badges and to grow, sustain and promote the global badges ecosystem.
Erin has led the open badges movement from its inception in the “Badge Lab” at the 2010 Mozilla Festival in Barcelona, where a 15-person working group started the conversations that would lead to a movement that has gathered support from educators, technologists, community leaders and strategists from around the globe.
Now, the movement has grown bigger than one organization. The Badge Alliance will better reflect the organic development of working groups we’ve already seen in our community, and will give them the freedom to work on their projects with clear direction and purpose. Most importantly, as Erin highlighted in her blog post, the Badge Alliance will be a valuable resource - not only for those who were at the table from the beginning, but also for those who joined us along the way and those still to come - so we can share our good ideas, and build on them to make great ones:
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!
We’re thrilled too - and we can’t wait to see how the Alliance work will support all our community’s efforts. To sign up and show your interest in any of the initial working groups that are important to you, go to http://badgealliance.org.
Stay tuned for ongoing updates here, on Erin’s blog or on Twitter.
February 21, 2014 03:54 PM
February 20, 2014
Open Badges Community Call, Feb. 19, 2014
This week’s Community Call featured presentations from the founding director of the Center for the Future of Museums (CFM) on their badging initiative, and from Josh Finkel, who is looking to develop a badge-based summer learning program to train kids for tech jobs with the Tech Foundry.
Badges for Museums
Elizabeth Merritt became increasingly interested in digital badges over the past two years while working in her role as director of the CFM, which is part of the American Alliance of Museums (AAM).
The AAM serves museums across the US, ranging from zoos to traditional museums to technology centers. With a field that wide-ranging, it can be hard to offer training programs that effectively serve all they need to reach. The AAM has a
Josh Finkel works at the Tech Foundry, where they are planning to create a summer curriculum for kids that are going into their senior year in high school. The program would integrate soft skills and technical skills development for a learning period of 6-7 weeks, and the hope is to offer badges for the skills learned in the program. Josh joined the Community Call to share his thoughts on how this might work and to ask for feedback from the group.
The Tech Foundry works with IT experts
Join us next week, when we’ll be joined by Nancy Latimer from Mountain Lakes High School in New Jersey, who will be sharing her work on developing badges for the Mountain Lakes online academy offering free online courses.
February 20, 2014 08:48 PM
Open Badges Research & Badge System Design Call, Feb. 19, 2014
Speakers: Flavio Escribano + Jordi Moretón; Chloe Varelidi + Lucas Blair
This week we kicked off the Research & Badge System Design Call with a discussion around Badge Rank and Badge Score as part of a project being developed in Europe. Then our own Chloe Varelidi presented some of the work she’s been doing with Lucas Blair on the Open Badges Discovery project.
Following the kickoff of the BadgeCulture project, Flavio and Jordi asked themselves: What is an Open Badge worth? Starting with this question, they wrote a blog article exploring the ways in which badge rank and score will become an increasingly important consideration within badge system design. You can read the (translated) article in the Open Badges Google group: http://bit.ly/OBGrank
In their work on education and environmental research, Flavio and Jordi identified two problems facing their communities:
- Students had difficulty guiding and choosing their learning paths
- Employers had difficulty assessing résumés
The first of these, Flavio and Jordi saw as related to
Other ways to connect badges, and learners, through badge criteria include users’ interests, learning pathways, career goals and progress, and badge searches or queries.
It’s great to see our international community members working on these issues of badge rank and score - questions the Open Badges team have been tackling - and we look forward to continuing this work. If you are interested in joining the conversation, check out the etherpad notes, Flavio and Jordi’s presentation, or join the conversation in the Google Group.
assess the full spectrum of a candidate’s capabilities, including non-cognitive skills. Learners are struggling with not knowing what career opportunities are out there, and those without access or exposure to resources and opportunities are unknowingly limiting themselves.
By building badge pathways tools, there will be increasing ways to connect these groups with the resources, candidates and opportunities they need. On top of these connections, pathways can also identify cross-career competencies, motivate learners to explore things they wouldn’t have known about, and identify role models of professionals and peers. Pathways can also act as a data collection tool for gauging learners’ interests, identifying gaps and suggesting content to fill them.
They compared top industries from three perspectives - economic, learning and employment - in order to see overlapping interests in industries employers identified as ones that would highly benefit from badges pathways:
February 20, 2014 07:47 PM
February 19, 2014
As journalism continues to break new ground on the web, news organizations large and small are hiring developers, designers, and others who bring new skills and ideas to journalism. Growing the community of talented developers working in news is one of the things we try to do at OpenNews. Our Fellowship program, our sponsorship of hack days, our website Source—it’s all part of trying to build the community of folks coding in news. Today we’re taking a very direct path to that: We’re launching a new section on Source that will list the latest journalism-code jobs.
Source is designed (from the database up) around the people building journalism on the web. Jobs is a natural compliment to the project breakdowns, behind-the-scenes articles, Q&As, and learning pieces that we feature on Source: you can learn how it’s done, and then you can go and do it in some of the best newsrooms around the world.
The listings are lightweight: a one-sentence job descriptions and a link to the full listing on an external site. They’re also self-serve. Today we’ve also opened up an organizational backend on Source so news orgs can list their own jobs. Erin Kissane explains how to get the keys to your organization page on the official announcement.
This is an exciting time for journalism and an exciting time to code in news. We’re thrilled to be able to play a small part in helping to bring talent into newsrooms. And we can’t wait to see the code all these new jobs produce!
Source Jobs is the first of many new features to come on Source, all possible thanks to our renewed grant that puts additional emphasis on community building and Source in particular. Expect much more to come soon—including dates and a location for the SRCCON conference, which we’ll be announcing at the NICAR conference next week.
February 19, 2014 03:49 PM