Showing posts with label Badges. Show all posts
Showing posts with label Badges. Show all posts

Digital Badge Design Principles for Recognizing Learning

Cross-posted at HASTAC

by Andi Rehak and Daniel Hickey


This post introduces the design principles for recognizing learning that are emerging  from the Design Principles Documentation Project (DPD).  A previous post summarized how the DPD project derived these principles. This is the first of four posts, to be followed by posts outlining the principles for using badges to assess, motivate, and study learning.


First and foremost, digital badges serve to recognize some learning or accomplishment.  As succinctly put by Mozilla's Carla Casilli and Erin Knight in their EDUCAUSE Brief, "badges signify accomplishments such as completion of a project, mastery of a skill, or marks of experience."  An important distinction here was made by David Wileywhen he pointed out that "badges are not assessments…badges are things we award to people who pass assessments.”

In more formal educational contexts, this practice is usually called "credentialing."  We are using a more general term of “recognizing” to emphasize that many of the practices for recognizing learning with badges are more informal.  For example, while a Girl Scout badge is technically a credential, few would call it that.  The different DML projects recognize various types of learning.  The way that learning is recognized and who recognizes it also varies. These differences then have consequences for assessing, motivating, and studying learning.

Our Process for Identifying these Principles
We first identified the intended practices for recognizing learning in each project's proposal.  As project teams began implementing those intentions, we interviewed them to uncover their enacted practices.  The 5-10 enacted practices for each project were then sorted into a manageable set of more general principles.  We debated categories and subcategories ourselves. We then discussed and refined them at a half-day workshop before the DML conference with 45 badge project team members.

This resulted in the preliminary set of design principles listed below, starting with the ones that were most widely represented.  These principles are not set in stone.  The principles and (eventually) sub-principles will continue to evolve as we work with them, identify resources that are relevant to each, share them with projects, and begin sharing them more generally.  We seek your questions and suggestions.  Please post comments directly on the blog.

Nine Principles for Recognizing Learning with Digital Badges
The following principles are ordered by prevalence in the current badging practices of the DML Competition 4: Badges for Lifelong Learning awardees. While these principles were developed based on the practices of the DML awardees, these principles should be useful in helping organize efforts to design and refine any badging system. The usefulness of the principles will (hopefully) increase as they are connected to existing literature on credentialing of learning experiences as the DPD team delves into that phase of the project.

1. Use badges to map learning trajectories.  Most of the projects used badges to organize curriculum and learning experiences by either determining levels of badges or offering meta-badges. Alternatively, some projects allow for a more learner-directed process that encourages students to create their own trajectory.

2. Align badges to standards.  Many of the projects used national or international standards to increase the external value of the badge. Alignment to standards is presumed to improve transparency of the credential and help to facilitate better communication of earner knowledge and skills. Some of these standards were more formal such as, the Common Core State Standards, while others were the less formal such as "21st Century Skills." Sometimes the alignment was very formal but other times it was very informal.  Highlighting the relationship between recognition and assessment, the formality of this alignment was usually defined by the formality of the assessment practices involved. 

3.  Have experts issue badges.  Having experts issue badges increases the credibility of the badge and likely influences the usefulness of the credential outside of the issuing community.  At some level, some expert is associated with issuing badges.  But the nature and role of this expert varied quite a bit, as did that way that the expert was him or herself credentialed.  Sometimes the expert held an external credential, while other times the expert was credentialed by the community; some projects include both. 

4. Seek external backing. External backing is presumed to increase the usefulness of the badge as name recognition is a driving force in getting schools or employers to recognize the badge. In the projects that sought external backing, this seemed different than just using badges as a means of external communication. Whether or not the badge is actually externally endorsed, existing formal relationships can increase its external value. (For those wishing to have formal credit granted for a badge, this is the first step.) Partnerships increase communication of the learning recognized in the badge and thus increase the importance/usefulness of the badge for earners. In some cases, a badge is formally endorsed and carries the insignia of the endorsing institution.

5.  Recognize diverse learning.  Credentialing a broad spectrum of experiences helps to legitimize these areas and recognizes knowledge and skills which would otherwise only be implicitly noticed or not at recognized. While this principle could be uncovered in nearly all of the projects at some level, we highlighted several projects that embraced it explicitly. These projects recognized skills and learning outside of what is traditionally recognized in formal learning environments, giving badges for both "hard" and "soft" skills.

6.  Use badges as a means of external communication of knowledge and/or skills.   As with the previous principle, most projects did this at some level.  But some projects really made a concerted effort to increase communication of the learning or accomplishment that the badges represent.

7. Make badges permanent.  While many projects did not explicitly discuss whether or not their badges would expire or require upgrading, a few made strong cases for learners being able to have permanent credentials that will always exist to recognize that specific skill, knowledge, or experience.

8.  Recognize educator learning as well.  Some of the projects awarded badges specifically to educators.  This is a different principle that relates to the several projects where additional badges were included alongside student badges.  These were sometimes that same as the badges for students and other times they were specific to the educators.  Generally speaking, these badges were used to recognize the educators’ participation in the broader learning ecosystem.

9.  Award formal academic credit for badges.  In a few projects, badges were used as a supplement to a formal grade for in-school experiences. Currently, only a couple of projects have successfully created partnerships that allow a badge to directly result in formal academic credit. This of course greatly increases the value of the badge for badge earners.

A Design Implication
We conclude by introducing a dilemma we faced in this process.  This dilemma was embodied in the distinction between (a) integrating badges into an existing curriculum and (b) creating a badge system and a curriculum at the same time.  For a while we treated this as a design principle for recognizing learning.  But we came to see it more as a “design implication.”  This difference seems to have great impact for the design of the badging practices (and likely for the learning ecosystem that results).  But this distinction was largely a result of the context in which badges were being introduced, rather than a deliberate choice.  As such it did not seem like this qualified as an actual design principle. When badges are being added to a pre-existing curriculum, the curriculum will constrain the way learning is recognized. For example, if an existing curriculum is not aligned to standards, it is very difficult to align a badge to standards. Alternatively, when the curriculum is being developed alongside badges, the options for both may seem limitless and overwhelming. A pre-existing curriculum can importantly help to structure design decisions. There are specific advantages for either approach.
We would love to hear what people think about this distinction or about our design principles for recognition of learning with digital badges.

Badges Design Principles Database Project: Update on New Principles


by Daniel Hickey

This post is cross-posted at HASTAC. 
This post is a brief update about the design principles that have emerged in our analyses and interviews of the 30 DML badges awardees. We will begin posting the initial set of design principles for using digital badges to support learning. Specifically we will put up consecutive posts about the principles we have found for using digital badges to recognize, assess, motivate, and research learning. The first blog on recognizing learning with digital badges us up at HASTAC and Remediating Assessment.

A previous post introducing our project elaborated on how we were going to identify intended practices for using digital badges by the DML badge awardees. We did that and then interviewed projects to uncover their enacted practices as they put their ideas into place within their particular program or school. We identified practices in four aspects of learning for each project: recognizing, assessing, motivating, and researching. 

We then sorted each set of practices into more general design principles. This is intended to help projects learn what they have in common and link outside resources with particular principles. We hope this will be helpful for building a community of practice around digital badges and help make connections across existing and new badge design projects. Our ultimate goal is a self-sustaining open network organized around an evolving set of principles and resources.

In the coming days, we will post four articles listing the initial set of design principles in each of the four areas. We will describe the principles and the rough proportion of projects that explicitly described corresponding practices. For some principles, we will include an example of a corresponding practice from one or more of the projects that has endorsed our characterizations.i We have been debating the structure and names, and we are getting ready to formalize them, so we really hope people will provide input and suggestions. 

The next phase of our project is identifying outside resources (i.e., research papers, articles, blog posts, etc.) that seem relevant to each of the design principles. We will start by linking principles to the 170 resources in the Annotated Research Bibliography by Sheryl Grant and Kirsten Shawgo. Before doing so we hope to finalize our current set of design principles.ii

Here is our tentative order of posts and authors that we plan to post over the next several weeks.

Design Principles for Recognizing Learning with Digital Badges, by Andi Rehak & Dan Hickey

Design Principles for Assessing Learning with Digital Badges, by Rebecca Itow & Dan Hickey

Design Principles for Motivating Learning with Digital Badges, by Katerina Schenke, Cathy Tran, & Dan Hickey

Design Principles for Researching Learning with Digital Badges, by Dan Hickey

We look forward to hearing from you!


iThis is one of the most challenging aspects of our project. We want to give projects and teams credit for their insights and we want to help people connect with the projects and teams who are enacting practices they are interested in. But we also want to characterize projects and practices accurately. We have been asking (and perhaps begging) team members to review, edit, and endorse our characterizations of individual projects and practices. Once projects are satisfied with the current characterizations, we are asking projects to allow us to share those characterizations widely and publicly. As you can imagine, this is difficult given the number and diversity of projects and their continuing evolution. If you are involved in a project and have yet to review your characterizations, please visit the project website at http://iudpd.indiana.edu/ . And even if you have reviewed and approved our characterizations, you might wish to again visit the new Badge Design Principles section to see which design principles are associated with your project.

iiWe emphasize that these principles will continue to unfold as we learn more about them. Numerous decisions were made in deciding which practices go together and what each principle should be called. We are trying to use more general labels and everyday language for the principles. One of our more general project findings is that the process of identifying practices and principles becomes more subjective and more academic across the four categories of principles. Thus:

It was fairly straightforward to identify the principles for recognizing learning and characterize them with everyday language (e.g., recognizing rather than credentialing). That is to say that every project articulated the learning they were going to recognize and most articulated how they were making those decisions. These practices and the more general principles that emerged can be explained in everyday terms.

Projects were less clear about how they were going to assess learning. More importantly the practices and principles for assessing learning can’t be characterized without using some of the language and distinctions from the assessment research literature (i.e., formative, summative, transformative, etc.).

As for motivating learning, many projects did not offer explicit motivational strategies. This meant that the implicit practices and principles for using badges to motivate learning could only be inferred from the perspective of current research literature on motivation.

Few projects articulated plans for studying learning. This means that the potential practices and principles across the projects were almost entirely inferred from the existing literature and assumptions about educational research.

This reality has some complicated consequences that we are just beginning to understand. For example, some projects have already told us that they are enacting principles for assessing and motivating learning that they did not specifically articulate; it seems likely that projects that explicitly indicated that they were enacting those practices are best positioned to share their insights with others. This also means that that the design principles for studying learning are almost entirely speculative; by defining principles for doing so openly and with lots of community input, we hope that our project will yield a framework for organizing the research now getting underway, and organizing future research as this community evolves.

Digital Badges Meeting at the NSF Headquarters Hosted by NYSCI


by Katerina Schenke
This post describes a meeting at the National Science Foundation where sixty leaders in education and research from around the country gathered to discuss digital badges and education.  Three of use presented the initial set of design principles from the Design Principles Documentation Project.
Monday April 1stwe travelled to the NSF headquarters in Arlington, VA. There, Michelle Riconscente and Margaret Honey from the New York Hall of Science hosted a meeting with an impressive list of attendees. STEM educators, members from after school programs, researchers, professors from all different disciplines (computer science, educational psychology, learning sciences) among others met to discuss the current and future research surrounding badges.

Rebecca Itow, Cathy Tran, and I were invited to attend as members of the Badge Design Principles Documentation project and had been asked to serve as official note takers of the meeting. We ended up doing Dan Hickey’s presentation on the project and about digital badges research because Dan instead had to attend to a death in his family.  Our presentation went over well and the audience was very interested in the initial set of design principles emerging across the 30 projects funded by the Gates/MacArthur Badges for Lifelong Learning initiative

Along with discussions about the logistical concerns about the use badges such as how to manage these various systems (Erin Knight from Mozilla), on-the-ground depictions of badge systems (Alejandro Molina from the Providence After School Alliance, Marc Lesser from MOUSE, Inc, and Akili Lee from the DigitalYouth Network, just to name a few), and the potential for badges to optimize student learning (Barry Fishman).  We candidly spoke about some concerns about badging such as “what is the life expectancy of a badge” (Avi Kaplan), and “what are some of the challenges and what are some of the insights as a result of this work?” (Michelle Riconscente).

As someone who is interested in what badges can do for student motivation, a question from Learning Sciences legend Allen Collins really stood out:

“Badges is a low stakes enterprise but at the other end we think about using badges to make decisions like colleges, employers which are kind of high stakes decisions and we kind of know that when you put high stakes on things it distorts the way the system works. It leads to cheating and all of that. So the question is how can the badge community resolve this tension?”

Given that some of the badges efforts are already planning for high-stakes uses, this is a huge question.  Unlike course grades and diplomas, digital badges contain detailed evidence and hyperlinks to more evidence about the issuer and what the individual did to earn the badge.  While this won’t prevent these concerns, it will certainly cause them to unfold differently. Should we resist turning badge systems into high stakes pursuits? Is there a way to design these systems in such a way where badges contain outside value to the learner yet still emphasize the learning process within the badge system?

Comments? Thoughts?



Incorporating Open Badges into a Hybrid Course Context

By Dan Hickey
I recently incorporated digital badges into the online aspects of my doctoral course on educational assessment (“Capturing Learning in Context”).  There are two aspects of this effort that readers might find useful.  The first aspect concerns the way students award simple “stamps” to highlight significant contributions or insights from classmates. I use those stamps to award three “one-star” badges each week; I will use the one-star badges to determine how to award three two-star badges at the end of the semester.  I will elaborate on this in a later post.  I also removed the section on using the Mozilla Open Badge backpack to another post as well. This post is already going to be pretty long! 

In this post I want to describe how I used ForAllBadges (from ForAllSystems, a small Chicago firm) to issue digital badges within a typical online course management system (CMS).  Anyone who wants to issue badges that comply with Mozilla’s Open Badge Infrastructure (OBI) can easily sign up for a free account at http://www.forallbadges.com/.  The account can be used as a stand-alone site, or it can be accessed from within any CMS that lets you access outside websites.  I am using OnCourse, the Sakai-based open-source CMS that Indiana University helped develop.


Incorporating ForAllBadges into OnCourse

ForAllBadges Interface Inside of OnCourse
(Click on the images to enlarge them)

After my account was set up, I just had to enter the browser address into the OnCourse Web Content tool and labeled the link ForAllBadges.  Then my students just had to click the link to access that site within my class site.  I added each student as a participant by entering their email address and a default password. 


   


Creating Badges
Six Badges Created for my Class
One of my doc students, Rebecca Itow, helped me to create these badges (Rebecca's experience in P2PU's Badge Maker course was a great help in this process). In order to create badges, we first needed images.  We used a shareware program called InkScape (a tool introduced to us in the P2PU course) to create the images for each badge.  Given the nature of the badges and the class, we did not worry too much about aesthetics.


Interface for Creating Badges

Once the images are created, we just had to click on Manage Badges and then Add Badges to create the badge.  We only used the Name and Description fields. We left the Criteria field blank so it could be filled in when the badge was actually awarded.  You can see that we could have included a lot of information by using the other fields.  What makes ForAllBadges “OBI-compliant” is that these fields are consistent with the metadata structure that the Mozilla Foundation’s Open Badges projectdefined in 2012 as part of the MacArthur Foundations Badges for Lifelong Learning initiative.





 Issuing Badges


One-Star Collaborative Engagement Badge from my Class
Once the participants were added and the badges were created it just took a couple of clicks to issue a badge.  Because of the way I set up the badge, I entered the actual criterion when I issued each badge.  This was simply an explanation of why I awarded that badge to the specific student.  The students can easily see which badges each of them has been issued, and can click on any badge to see the criterion upon which it was awarded. 

I have been playing around some with the wording of the criteria each time I award a badge. This is a nice example why digital badges have such transformative potential.  Because I knew this badge might be “pushed” out beyond my class, I was forced to think about the information that the badge would contain.  And while I had decided to not make badges part of the course grade, I certainly hoped that students would value them. Particularly because every student could inspect every badge that I awarded, it was important that the criterion be credible at least in the context of the class. I still have some work to do to make the badges credible beyond the context of my class.

When I first issued badges, I included links back to the comments from classmates that led me to award the badge.  Those links would work for the students who were enrolled in my class and only then while they were inside my OnCourse site.  While those links supported credibility within the class, they were rather unwieldy.  More importantly, a dead link would undermine the credibility of a given badge when viewed outside of the class context.  So I removed the links. I will write more about credibility in the future, but for now check out Carla Caslilli’s excellent post about credibility and validity for digital badges.

In addition to credibility, I had to think about privacy. When I removed the links, I initially left in the first names of the awardees classmates whose comments led me to award the badge.  But I realized that if the badge was viewed outside of the class context, that some students might object to being identified. Even though it was just the first name, I suspect that putting such identifying information might violate FERPA rules that strictly protect the privacy of anyone enrolled in a public school classroom. The example above shows the badge I eventually awarded.  I left only the awardee's first name in the badge (it is obscured in the picture).  But I provided enough detail so that the students in my class could recognize whose endorsements I was referring to.

I am not sure how meaningful my one-star badges will be to anyone outside of my class.  But I have nine weeks to figure out how to make the three two-star badges more generally meaningful. I now realize that the challenge, if I want to be a badge-savvy educator, is to make the two-star badges so meaningful that the awardee might push it out to Facebook, Google+ and Twitter, so that others might see it and comment on it.  (I hope that this is the point where confused or skeptical readers start to realize why people like me are so excited about digital badges.)

If this is not clear or not helpful, or if you have comments, please let me know!  Now go forth and play!







   

Pushing Badges from ForAllBadges to a Backpack and Beyond

By Dan Hickey and Andi Rehak

In a separate post, Dan explained he used ForAllBadges to issue OBI-complaint badges within the Oncourse course management system.  This post explains how these badges earners can "push" their badges out of the class and into their open badges backpack and beyond to Facebook, Google+ and Twitter.

This post is intended to be a very concise explanation for using backpacks when using the ForAllBadges platform.  In particular it highlights the fact that badge earners must have an open badges backpack before they can push their badges to it.

For more general guidelines, check out Mozilla's wiki on badges, information for badge issuers and the open badges FAQs. P2PU's Open Badges 101 sprint and  Mozilla Open Badges google group are also very helpful. If the terms like "issuer" and "earner" are confusing, check out Carla Casilli's blog on the open badges lexicon


Create a Mozilla Open Badges Backpack
The Open Badge Infrastructure (OBI) made it possible for Mozilla to create virtual “backpacks” where earners can store and display their badges, or push them out to other locations such as Facebook.  Initially Dan's students were a little confused about creating backpacks, but this is because the very idea of a virtual backpack is entirely new.  Once he created step-by-step instructions like the ones here, it was pretty simple to create the backpack before pushing a badge to it. Hopefully badge earners will be able to use these instructions as well.


Open Badge Backpack Login
First you go to to Open Badges.org.  There is stuff here that you can play around with but click in the middle where is says Visit Your Mozilla Badges Backpack. Or just go directly to the Open Badges Backpack  Click on the green sign in.

Mozilla's Persona Identity Verification System
This launches Mozilla’s Persona identification system.  Users must log on to open badges with the same email address at the one associated with that person at the ForAllBadges site (or whatever badging platform being used) that issued the badge.  Persona then asks for a password. Users can use whatever password they like but are likely to use the same one as they use for that email address.  

Persona then sends verification to the email address.  Clicking on that address verifies the users identity and leaves them in the Persona account manager.  This step is a little confusing, because from there the users need to go back to http://beta.openbadges.org/

Pushing Badges to the Backpack
Accepting a Badge from ForAllBadges into Backback
From the badge management page, users can click on their magnifying glass and then click again to send the badge to their backpack by clicking the blue Yup.









Prompt to Create a Backpack
If there is no backpack with the email address associated with the badge (shown in red),  the issuer is prompted to create one.  If so, clicking the blue Cool Lets Go takes uses to the steps above for creating a backpack.  Users need to create a backpack with that email address, and that first badge has to be pushed a second time.  At this point, I realized that many students might have preferred me to use their more Gmail address than their university email address. This gets at the crucial issue of permanence that the open badges community is dealing with right now.


Badge Added to Backpack
After a badge is pushed to a valid backpack, a message indicates that the badge was added.  Clicking on the blue hotlink takes the user from there to their backpack. Users can examine their badges in the backpack and push them out from there if they like.

Pushing Badges to Social Networks
Badges and Groups in Backpack
When users go back to their backpack at http://beta.openbadges.org/ they can see all of the badges in their backpack (but they may need to log back in).  The backpack will contain whatever badges and a single unnamed group.  Dragging a badge into the group allows the user to name the group and create additional groups.  Clicking on the Public box on the lower left means that others can see the badges in that group.


Clicking on the on the familiar sharing symbol on the lower right of group box pushes the badge beyond the backpack; clicking on the badge itself shows what anybody else will see if they click on the badge in your backpack or on the wild. Notice that the criteria and evidence have all been turned to hotlinks that go back the badge holder (which in this case is badges.forallschools.com).


The Information in the a Badge
Clicking on the Share This in the upper right of this window prompts the user to select where to share it (Currently limited to Facebook, Google+ and Twitter.  Users are prompted to add a comment or a tweet to go along with the post; if they are not already logged in to those external sites they are asked to do so. 


Badge Pushed to Facebook



Once the badge is pushed, anybody who gets the tweet or is friended in Facebook or Google+  can simply click on the link and see the same info like the one in in the picture above.  They can in turn click on the links to see more information.  Users can add additional comments and others can comment as well.  While the Facebook post can be deleted, a tweet obviously cannot be taken back.  However, the user can go back to the backpack and “disown” the badge and the link will be killed.




Tweeted Badge

Hopefully we have brought some clarity to the world of badge accepting; now go to the open badges homepage and actually earn a badge yourself by taking the Badges 101 Quiz!