We came, we saw, we badged: an update on the Insignia project

Now that the official part of the Insignia project has wrapped up, we thought it would be a good time for an update on how our badges pilot project went. Looking back on the past year, it’s been an interesting ride for our project team. Here are some of our results and lessons learned:

The process for implementing badges was more complex than we could have anticipated.

As we mentioned in the paper we presented at the ascilite conference, our greatest challenge was that our institution’s policy for trialling new technologies was too onerous and time-consuming for small, short-term pilot programs. In most cases, small pilots of new technologies are forced to go “underground” and trial things without official support (which doesn’t benefit the larger university community). The need for a robust and stable learning management system is not under dispute, but there needs to be some mechanism to help foster limited trials without having to change the entire enterprise system.

We found significant interest in badges around the ACT, Australia, and the higher education sector more broadly.

Wow! So many institutions and colleagues are genuinely excited about the potential for digital badges in their areas. Most of the fellow badgers we met were investigating badges for co-curricular or supplementary purposes (rather than including badges as part of the core curriculum) or as part of a “gamified” experience of a degree program. We were also contact by students who were keen to set up their own badging system to credentialise participation in student-run programs. And all this within only the limited scope of this project! It would be fantastic to see ongoing discussions of inter-operable and widely sharable badges moving between these institutions in the future.

As a new and still immature technology, the students who received the badges were not quite sure what they represented or how to utilise them.

After receiving badges through the Insignia project, several students commented that they were unsure what the value of the badge was, or how to use it. This was likely amplified by the use of a third-party service. In our survey one student commented: ” I probably won’t sign up for this badge because I’ve no idea what Credly is nor of its formal relationship with the ANU.” This is a fair point! Our analysis of the badge take-up confirms this: only 17% of the students eligible for the badges chose to receive one.

Without the reputation of the university behind it, badges lose a lot of their value (see more on this below). The network economy of badges, as it were, is still too immature. Comprehensive education is needed around the concept of badges in order to ensure that students understand what the badges are for, and also how to display them appropriately for employers and others to view them.

To have a truly effective badging system, you must have an associated portfolio or backpack system to display them.

Being able to display your badges in a coherent, curated way is also key to their usefulness. Without an official portfolio or backpack space, endorsed and supported by the university, the badges were shared on places like Facebook and Twitter. While these social media spaces might be partially used for academic purposes, they are not primarily a portfolio or professional space. An ANU-branded portfolio would legitimise any badges shared within it.

Institutional reputation and credibility are key to badges holding value to students and employers.

Badges are semiotically dense: they need to communicate an extraordinary amount of information in a small, pixelated image. We discused this in the previous post on badge design: it matters a great deal who gave a credential, and this needed to be represented in how it looks as a future employer needs to be able to tell who granted it from a glance. Many of our focus group participants had concerns about the perceived lack of trust in digital credentials, and an “official” looking badge might be one way to address this. For intellectual property reasons the ANU crest could not be included in the badge design, but future badges should likely follow the ANU brand visuals more closely in order to carry the reputational credibility.

Stay posted to the blog for future updates on how badges can be used for libraries, and for our final white paper on implementing digital badges in higher education.

State of the union with ANU badges

As our badge team heads towards the end of the year and to the ascilite conference in Dunedin, New Zealand, we thought it was due time to give an update on our badges project thus far. At the time of writing, we have successfully delivered 37 badges to ANU research students for completing modules on research integrity and library research skills. There’s a new page describing our badges available here. As it turns out, the design and delivery of the badges were the  most straightforward part of the process. But as badges are intended to be moveable and visible externally, they cause a lot of problems for existing university systems and processes. Badges are still in their infancy, and a full institutional implementation is a time-consuming and expensive proposition involving multiple governance groups, committees, legal teams, and so on. Communication with students and stakeholders about the function and role of badges is another key area which will need to be addressed if badges are to be used in larger projects. After all, if you don’t know what it means or what to do with it, the badge loses much of its value.

I’m sure we will have many productive discussions about badges at ascilite next week, but for any readers out there who are working on their own badges projects, we’d love to hear how the implementation side of your project is going. Leave us a note in the comments!




A null result is still a result. Right?

IntegrityQuiz_makebadgesIn the Unjaded Reflections blog post “Why should you create an open badge system”, Jade Forester has three warnings for people designing open badge systems:

1. Don’t try to make your badge system grow too much, too fast;
2. Ensure you have the technical and human resources you need to fully support your badge system;
3. Make sure there’s a need for badges

Starting INSIGNIA as a small scale system, with available resources, certainly sounded like a sensible approach, especially given this is only a seed project. If the need for the badge is clear, it’s likely to help with acceptance of open badges in the research community. Given these constraints, I seemed to have a perfect starting point: ANU’s compulsory, yet non credit bearing, research integrity course.

This course is a problem I had inherited from my predecessor, who built it in collaboration with the community, but without a good assessment regime or ongoing maintenance strategy. The course attempts to explain, mostly through case studies, how complex research integrity issues, such as authorship, plagiarism, informed consent etc, are in practice. The material was great, but I’ve been working for nearly a year to move the course from his bespoke online platform into our ANU learning management system (on Moodle) and to introduce a quiz as the final assessment activity (yes – this seemingly straightforward task took nearly a year. Committees eh?).

Taking Jade Forester’s advice on board, I thought issuing a badge for the successful completion of the final quiz would be a good first step towards an INSIGNIA series of badges for research education. I needed a way to provide students with evidence that they had completed the course and I had available resources. The research integrity course content was already there in Moodle 2.5, which I know has the capacity to create and issue badges. Red Dog Learning, who had been helping me to build the course, even offered to make the badge for me as the last part of their contract.

The problem, I quickly discovered, was that people and technical resources are not always enough. The barriers are more likely to be hidden and, just like a coral reef just under your bow, you sometimes don’t know they are there until you run aground.

Last week I happened to wander into the lunch room at the same time as the ANU online team, who are the people responsible for looking after ANU’s implementation of Moodle. Over my burrito I asked the team if our Moodle had the badges option turned on because I couldn’t see it anywhere when I was editing my course. The team told me they had not turned it on because no one had asked for it.

I told them I needed it and politely asked if they could turn it on.

They hesitated. “Most people don’t have a good reason for using open badges” said one, cautiously. I suspected this was a gentle way of saying “no” so I pounced on it.

“Well I have a whole pedagogical model” I replied. Then I explained the idea of open badges providing a ‘respectful pedagogy’ for research students, who may be well versed in the material within a course and just needed to demonstrate competency – my research integrity course being a good case in point.

The ANU online team nodded and looked thoughtful.

“We’ve been reluctant to turn it on because anyone could offer a badge for anything” another member of the team said.

I replied that was rather the point of open badges, but I could see the problem with it in a university context. Anything with the ANU brand on it, and no quality control mechanism behind it, was challenging to the credentialing authority of our institution. Poorly designed badges, like poorly designed courses, have the potential to reflect badly on us and might even undermine our credibility as an education provider.

I explained I was happy to have this conversation because my research was designed to elicit just these issues and write about them. But I couldn’t get very far in my project if I couldn’t actually make any badges available. Perhaps they turn on the badge making capacity, but just for me. I cheekily promised to be good.

They told me that turning on the capacity for making badges would have to pass through their stakeholder consultation mechanisms. I’ve been in the university long enough to spot the possibility of slow death by committee when I see it, so I offered to write a memo for the committee and the DVC A – to explain the project and the need for badges.

Still they hesitated. I couldn’t understand why.

As it turned out, the ANU online were worried about the possible privacy implications of open badges. The idea of a badge is that it can be easily moved ‘out’ of the Moodle platform and displayed in other places, like the Mozilla backpack. If the badge ‘carried’ data about the student with it, like an email address, this would be a breach of privacy legislation and the insitution would be subject to up to $300,000 in fines. Apparently this was complicated by the fact that ANU is a federal university (actually the only federal university, since all the others are run by state governments).

I started to get a head ache. “Would an open badge project off the ground actually require an act of Parliament?” I wondered aloud. Then I laughed, you know – in horror. My project was melting around my ears.

ANU online team looked at me sympathetically. They didn’t want to stifle innovation they explained, but they had Responsibilities. I believed them, but had to ask the next obvious question: “can we put in a check box that students can tick so they are giving consent for their private information to be shared in the badge?” Well, that probably contravened the legislation as well they explained. I must have looked despondant at that point because the team did, bless their hearts, tell me they would explore whether Moodle could selectively turn off student information so that the badge could be ‘clean’.

This is, I suspect, where the road gets bumpy… A null result is still a result. Right?

Oh well. At least I managed to use Makebadges to do the graphics for the badge. If you are interested in designing your own badges, I’ve found some good sites which I have started to compile into a ‘make your own badges!” page. I’ll be interested in your comments – has anyone else had a similar experience?