Wednesday, October 24, 2012

Dan experienced 'creating a Tin Can API statement'

I've just read up on Tin Can API. I've been meaning to do it for ages and I'm kinda pleased that, as it turns out, Tin Can does pretty much what I had assumed it would do - but it does it better than I could have imagined and way more besides.

I'm also excited because I've also just generated my first Tin Can statement:
"id": "09888f33-2285-4c84-8ffa-18db65173171",
"actor": {
"name": "Dan",
"mbox": "",
"objectType": "Agent"
"verb": {
"id": "",
"display": {
"en-UK": "experienced"
"timestamp": "2012-10-24T14:46:34.354Z",
"stored": "2012-10-24T14:46:35.219Z",
"object": {
"id": "",
"definition": {
"name": {
"en-UK": "creating an Experience API statement"
"description": {
"en-UK": "Completing the Tin Can Api test generator on the Rustici website"
"objectType": "Activity"
This genuinely changes everything, it really does.

Something for everyone

All the LMS loving tracky types can love it because it does everything they need it to. Social learning types should be delighted as this reaches out and allows individuals to say what they learnt rather than only rewarding pre-ordained learning experiences. ILT luddites can feel good about themselves and come in from the cold and report on all the little parts of their courses. And ROI hounds should be cock-a-hoop at the notion of being able to track learning back in to the workplace in the form of results.

The main benefits as I would summarising them if I was making the case would be:

  • Freedom from the tyranny of the walled garden LMS
  • ability to account for non-online activity
  • able to take control of your own learning via personal learning repositories
  • builds tracking in to tools we recognise
I really am struggling to get a handle on how different things could be, and I'll tell you why I think this is so important. Buried away at the end of the description is the fact that the Tin Can API, or Experience API as it is also known, is based on common designed approach to the feeds you get on the social networking sites, but open and independent. That's it - this ties in to one of the most basic, and influential elements of the modern web and doesn't subvert it or lock it away - it sets it free. Brilliant.

Crucially however, it can't be a bolt on. I don't think that is going to work. Trying to retro fit this to an old school LMS isn't going to work. It would be like fitting four-wheel-drive to a Honda Fireblade* - sure it would work, but all the time you're going to be thinking "it was never designed for this". I really think that it will require a root and branch rethink of how we go about tracking and storing the results of our learning.

But do we want to track it?

My answer to this trope is simple - if we can, why don't we? The difference with this system is that we can build that tracking in to familiar feeling tools that we are comfortable with. Okay, so for now it's early adopters that use bookmarklets and phone apps to seamlessly join up our online and offline selves, but this has the usecase, this has the capacity to be the killer app for self tracking. Oh gosh, I am soooooo excited by this.

What can we do with it?

Question is, where does this go in the normal run of things? It's an obvious tool for CPD and some enterprising professional bodies should be all over this as a way of tracking it (doubt somehow that the CIPD will be early adopters, but maybe the LPI could get up on it?). Will we see it being co-opted by LinkedIn as yet another feature they draw in? Would we get this to work with Mozilla's badges? I can see all sorts of ways this could go.

Please let me know if you have spotted this going in any interesting ways. I'm off to comb the Learning 2012 and DevLearn conversation streams for bits now...

UPDATE: here's a great article by Gary Wise that does a more thorough job of explaining what Experience API can do.

* Okay - two things wrong with this statement. One, I doubt four wheel drive would work with this class defining road-going race bike and, two, most LMSs are not that well made or thought out. They are like 80s era Skodas (shoddy) or 90s American sports cars (great at one thing).


Sam Burrough said...

I still don't get why we need to track all this stuff. I know I should take the time to read all about Tin Can and I can see that it is better than plain old SCORM, but why track anything other than the stuff you need for legal compliance?

Dan said...

Tracking was what SCORM was all about - pre-ordained learning objects that you were told you had to do. The difference with TIn Can is that it can behave more akin to your beloved (as you pointed out in the pub last night) and you can track serendipitous learning anyway on the web or otherwise!

And it can be cleverer than that still - imagine building it in to a bespoke company system such that when you complete your 10th edit of the Intranet, or your first credit note on the sales system it records this such that you can relate it back to the training you did on these, see how you start to get a realistic chance of proving ROI! Gimme ROI or gimme death, Sam! ROI. Death. It's your call.

Doc Havis said...

Why track this? To demonstrate its value and open people's eyes to the power of this kind of learning. And that helps drive adoption = more and better learning. Increasingly, if "L&D" is to continue to exist in the 21st century then this is the kind of thing we need to support (I know you're on side with that) and, for better or worse if a company's spending money on L&D then it wants to know what value it's getting. Whilst measurement doesn't help the learning process from the learner's perspective it does mean that one of the last logical barriers to L&D evolving is being broken down. It gives an alternative/addition to the courses completed/training hours metric which for so long has been the only tangible that's really convinced the business.

Doc Havis said...

um, so this has used my Blogger profile not my Google account, interesting. Anyway,it's me, Doc Havis!

Dan said...

Hey Dave, yeah, I agree. There is definite value to be made from the kind of information Experience API (the term I'm gonna stick with from now on) will generate.

And you're right that this will redress the balance away from "managed learning" toward simply recorded learning - something that individuals will be better able to make use of in their careers. Win and win.

Dan said...

Of course, what would be a better title would be "Dan created an Experience LPI statement"...