Open Thinkering

Menu

Tag: Open Badges

Wake me up when you’ve stopped talking about microcredentials for workforce development

What's a badge really worth?
 What’s a badge really worth? by Visual Thinkery is licenced under CC-BY-ND

Note: this post had a previous title: Keeping alive the dream of an open, democratic, web-native way of giving and receiving recognition


This is a response to Justin Mason’s excellent provocation / blog post “Thinking Out Loud” About Why Static, Online, Competency-Based Microcredential Courses Are Boring. I want to use this post to get a bit more radical than Justin as I don’t have to include a disclaimer about my employer’s opinions 😉

Justin makes four points in his post:

  1. Higher education’s primary value isn’t in curating and disseminating instructional content.
  2. Static, competency-based microcredentials in higher education probably won’t solve the “skills gap.”
  3. “If the only tool you have is a hammer, you tend to see every problem as a nail.”
  4. Competency-based micro-credentials focus on workforce development to the exclusion of liberal arts education

Despite having four qualifications from universities, I don’t actually care that much about the continuation of Higher Education in its current form. It’s also been more than a decade since I’ve been employed by a formal education institution. So I want to highlight a point that Justin makes which reminds me that all but the most prestigious universities are about to be eaten alive:

In theory, we could develop practical microcredentials for all the contexts. But who has the resources to do that? You know who has the resources to at least try? LinkedIn, and huge companies like it. For example, you know who has a vast collection of LinkedIn Learning courses and is now promoting skills assessments to compliment them, and is awarding badges? You know who’s partnering with large higher education systems and other companies to develop microcredentials around LinkedIn Learning? Yup. If you’re developing short, online, static, competency-based courses + microcredentials with the idea that you’ll create a large collection of them, ask yourself if your institution has the resources to build microcredential collections that will compete with LinkedIn Learning’s microcredentials in scope and quality. And then allow yourself to have a good cry.

Dividing up existing courses into bite-size pieces will hasten the demise of Higher Education institutions, especially if they partner with organisations such as LinkedIn. Using a third-party provider to give students access to courses that make them more employable is all well and good, but at some point they will cut out the middleman. Why pay tens of thousands to go to university to get a series of microcredentials you can get from the same provider for less (or while working)?

Universities will realise too late that what they’re selling are experiences and signals. What they’ve got the opportunity to move into is recognition of the unique nature of each learner. So instead of making ever smaller generic credentials, they’ve got the chance to provide bespoke recognition.

I really believe that the next step higher education takes toward making itself more accessible, inclusive, and equitable is through the recognition of life-wide learning. I wager that microcredentials, or something very much like them*, will probably be a big part of how recognition of life-wide learning works. But if microcredentials are understood to be 100% about workforce development, then I worry they’ll contribute to the workforce-ification of public higher education, and that’s something I don’t want to see happen. I wish, oh how I wish, that faculty and administrators who advocate for higher education’s public mission would stop simply identifying microcredentials with workforce development. Instead, I would ask them to consider how microcredentials could be one available tool that helps us extend the reach of public higher education to previously unserved people, as well as extend the lens of liberal arts learning to encompass lifelong and life-wide learning! Seriously, our rapidly changing world needs that lens!

People need income to live, which usually means that they need to work. Most work, but not all work, comes in the shape of ‘a job’ which entails an employer. This does not mean that we need to tailor our whole education system to please employers. As Justin mentions, the ‘skills gap’ is a convenient fiction peddled by large organisations who do not want to spend money on training and development. It’s only recently, after all, that graduates were expected to be immediately ‘work ready’ for employers.

But even if we did want to please employers, the way that Higher Education seems to be approaching microcredentialing seems to be backwards. Instead of creating generic content that then needs to be applied to an area, the world of work requires extremely contextual and domain-dependent recognition of knowledge, skills, and understanding.

[K]nowledge and skills tend to be embedded in contexts. People (okay… mostly my relatives) bemoan higher education for being too abstract. Learning should be practical, they say. What my relatives don’t realize is that an amount of “abstractness” is necessary if you’re developing curricula intended for any and all contexts and learners. Take, for example, an introductory microcredential on project management. The trouble is that project management in the construction industry looks significantly different from project management in the health care industry or software development industry. Even within a given industry, project management will differ from one organization to the next. So microcredential designers must consider tradeoffs. They can either build a “practical” microcredential curriculum that is 80% useful to 5% of their potential learner-consumers, or they can build an “abstract” curriculum that is 40% useful to 80% of their potential learner-consumers (those percentages are made up examples).

A microcredential itself is not ‘content’ but rather a signal of having learned or mastered something. While a university might want to control the value of the different kinds of credentials it offers, it’s not quite as simple as that. As the illustration at the top of this post shows, there are many facets to take into account. What Higher Education institutions need to bear in mind that, as part of this great unbundling, there is no actual requirement that they are the ones who issue valuable forms of recognition.

The work that I’m involved with at the moment (alongside Justin!) through Keep Badges Weird and the OSN Open Recognition working group involves thinking about what happens when a Community of Practice takes the place of an institution. I think we could see the return of guilds run as a form of co-operative trade union which would recognise and legitimate workers within a given domain. They could push back against the overbearing power of employers. I think it would be massively preferable to the situation in which we find ourselves right now.

Most of the questions that badges have raised over the last 12 years have been ‘trojan horse’ in nature. What do we mean by ‘quality assurance’? How can we do assessment at scale? What’s the minimum viable qualification? In fact, when I was on the original Mozilla Open Badges team, the main opposition to badges came from exactly those kinds of universities that are now jumping on the ‘static, online, competency-based’ microcredential bandwagon. I suspect they’re, either consciously or unconsciously, looking for ways to embrace, extend, and extinguish an open standard to try and firm up their position within the ecosystem.

Perhaps I’m getting older, but I see a lot of issues that on the surface look like they’re about skills and credentialing that are actually deeper and more structural. There are assumptions about power relations baked into every conversation I have had over more than a decade in this area. At some point we’re going to need to have some real talk about that as well. My view, unsurprisingly, is that we need more democracy and autonomy in the workplace, and that this starts with this being practised within our education systems.

For now, though, I’d encourage those who see the world through the lens of microcredentials to read some work that my colleagues and I have done in this area over the last few years. I’d suggest reading these three posts, focused particularly on Open Recognition in the workplace:

Once you’ve done that, come and introduce yourself to the KBW Community, start earning some badges for recognition, and see if we can keep alive the revolutionary dream of an open, democratic, web-native way of giving and receiving recognition!

Some thoughts on programmatic Open Badge image creation using AI models

Towards the end of yesterday’s meeting of the Open Recognition working group of the Open Skills Network we got on to talking about how it might be possible to programatically create the images for Open Badges when aligning with Rich Skill Descriptors (RSDs).

Creating lots of badges manually is quite the task, and gets in the way of Open Recognition and Keeping Badges Weird. So the first step would be to speed up the process by creating a style guide. Sharing SVG templates that are editable in a wide range of image-editing applications can speed up the process.

For example, for the upcoming Badge Summit, we’re issuing a badge which we want others to be able to issue for their own events. So we asked Bryan Mathers to create an image where the outside would remain the same, but the middle bit could be swapped out easily. Here’s the result:

I Kept Badge Weird at The Badge Summit 2022 badge

The next step would be to have a style guide which makes it faster to create unique badges. That involves a colour palette, font choices, shapes, etc. You can see this in action for our Keep Badges Weird community badges:

Selection of badges available to earn in the Keep Badges Weird community.

Lovely as they are, this is still labour-intensive and time-consuming. So how about we create them programatically? My former Mozilla colleague Andrew Hayward did a great job of this years ago, and the Badge Studio site (code) is still online at the time of posting.

The advantage of programmatically creating badge images is that it (helpfully) constrains what you can do to be in alignment with a style guide. Creating good looking badges can take seconds rather than hours!

An example of a badge image created using Badge Stuudio

However, what if we want to create badge images quickly, and programatically based on certain inputs? There are libraries that can create unique shapes and images based on email address and are used sometimes as the default avatar for platforms. Here, for example, is RoboHash which can be used to create good-looking unique ‘robots’:

Selection of unique robots created using RoboHash

It’s not a huge leap to think about how this could be used to create badge images based on a unique reference from an RSD.

But, if we’re getting a computer to generate something, why not something crazy and unique? Lately, there’s been a lot of noise about different AI models that can be used to generate images based on text input. One of the best-known of these, the images from which have been circulating my corner of social media quite frequently is Craiyon (formerly DALL-E mini). Here’s a really basic attempt:

Nine images created via the Craiyon AI model showing recognition badges

They’re quite… uninspiring and generic? However, they didn’t take any thought or effort on my part.

There are more advanced models than Craiyon, such as Midjourney. This can create stunning images, such as the one featured in Albert Wenger’s post about machine creativity. In fact, it was that post that got me thinking about all this!

You can create up to 25 images using the Midjourney Discord account before paying, so I created this one as quickly as possible using the same prompt as above. You can create variations and upscales, so I asked it to create variations of one of four images created, and the upscaled it to the max. I ended up with the following:

Round patch-style badge (black/yellow with orange shapes)

This is also quite boring, to be fair, but the awesome and weird thing about doing this in Discord is that you see the prompts that other people are entering to create image — e.g. ‘huge potato chip eating a bag of humans’ or ‘rainbow slushy trippy wallpaper’. I noticed that there were certain prompts that led to amazing outputs, so I tried ‘rainbow waterfall in a hexagon,bright,trippy’ and got these options:

rainbows and hexagons, AI created art

The bottom-left image looked potentially interesting, so I asked for variations and then upscaled one of them. I then just cropped it into a 12-sided shape and ended up with the following. I guarantee it’s one of the most unique badge images you’ll have seen recently!

12-sided rainbow hexagon images

The point is that there’s almost infinite variations here. And, as I found, getting the words right, and then doing variations and upscaling is actually quite a creative process!

As ever, I don’t have the technical skills to stitch all of this together, but I guess my job is to encourage those who do in particularly fruitful directions. The workflow would go something like:

  1. Community decides new RSDs
  2. Organisation or individual creates badge metadata aligning with one or more RSD
  3. AI model generates badge image

I should imagine a lot of this could be automated so that badges that align with a particular RSD could have visual similarity.

This could be amazing. Anyone want to give it a try? 🤩

Wanted: a simple 3-step Open Badges platform to generate claim codes and issue badges

Today I’ve been frustrated by Open Badges issuing platforms. Instead of getting philosophical about it, or bemoaning the state of the world (as I usually would!) I’ve decided to be more practical. If you’re a developer, I’m hoping this might tempt you into a side project…

That’s because, while I haven’t got the skills to create a badge issuing platform myself, I do know what it is that I and other people want. I’ve been in and around badges for the past 11 years, and I know Open Recognition can only flourish if it’s easy to issue and earn badges by claiming them.

Today, in my case, it was related to people completing activities as part of the email-based courses that WAO offer. But there are many other use cases.

I’m sure there’s other things that need to be in the mix, such as CAPTCHA codes, to prevent spam, and a simple admin interface. However, at its core, this is a really simple process.

Step 1: enter claim code

Mockup of screen showing text-entry box with a 'Go!' button. The prompt is "Got a claim code? Great! Enter it below"

Below the box is a link: "What's a claim code?"

As badge claimant, I want to be presented with an extremely simple box in which to paste a claim code I’ve copied from an email, chat message, or somewhere on the web.

(if I’ve come to this page by accident, or don’t recognise the term ‘claim code’ I want a link/tooltip to show me what this means)

Step 2: fill in essential details

A form asking for the applicants name, email address and evidence in support of their submission for the 'Innovator' badge

On the next screen, all I want to do is to fill in a form to tell the platform my name and email address. I then want the ability to enter words in a text box and/or upload a file providing evidence in support of my application.

Note that I’m not creating an account here. The badge issuing platform literally issues badges to the email address I’ve entered, if my submission is approved.

(if I don’t know what is meant by ‘evidence’ or what is required then I want to be able to click on a question mark icon for a link/tooltip to explain this )

Step 3: confirmation of submission

A confirmation screen confirming tha the submission has been received.

Once I’ve submitted my name, email address, and evidence, I want confirmation that the platform has received my application, and what will happen next. That’s it. Done.


There we go! This would require some kind of admin interface on the backend, but for an MVP this could literally be a spreadsheet. Who’s going to give this a try as a side project and make the world a better place? Here’s the Open Badges v2.1 specification if I can tempt anyone…

css.php