Why we love prototyping for elearning (and you should, too!)

In the second part of our interview with Simon Greany of Make Sense Design (Part 1 here!), he talks about how e-learning prototyping allows his high performance e-learning team to actually create a script within Elucidat and how it is a much fairer process for stakeholders.

Read the transcription here:

Has it been quick for you to learn how to best implement the new tool?

We see these changes as exciting ones, and ones as technology professionals we have to constantly look at and keep up-to-date with, it’s a process. It’s ongoing. It’s always in change.

We even see that in the authoring tool Elucidat that we’re working with at the moment. It’s very quickly changing to respond to advances.

How do you keep everyone on track with the vision of the course?

If the question is regarding how do we make sure everyone’s on track and following the same kind of vision for what the project will be, it would be partly a process thing.

So, we’re looking at an initial scoping phase and an analysis of what we’re trying to do to really lay out in a kind of a very high-level, just to say how the structure will pan out. And then take a sample of that to do a sample treatment that we can build, look at and evaluate to check it works before we roll out the whole module.

Of course when we’re working in Elucidat, we can see how that will all come into life as it’s being built out.

So, for example, at the moment we’re creating three hours of content for a client, the scriptwriter can go ahead and start building screens with kind of ready-made, pre-formatted ones that the graphic designers have been working on already to roll-out a whole approach across the module.

So, we can see it coming to life at its various stages while everyone’s still working on the same project. That’s quite an exciting, organic way of working.

How closely can you work with your client in terms of visuals?

For some reason, I’ve seen it a lot in the e-learning industry, people have this concept of script-to-screen, meaning you do a Word document which gets sent to the client. They read the words in a Word document and the description of what will happen on the screen.

So in our opinion, that’s a very demanding thing to ask your client to do because you’re expecting them to imagine how this thing will come to life as a product in a very abstract way. It’s something that I’ve always felt uncomfortable about and felt this is perhaps unfair as a thing to ask your client to sign-off. But now we can prototype within tools. We can actually script within the software itself and share that with the client.

Now that does open up the thing for QA. So with Word, we QA things by putting on track changes, so we can see version control by what people have done and when they’ve done it and ask for it.

But there’s a commenting feature in Elucidat, we’re using that to track comments against what we’re putting into the tool. It is interesting. And with another client we’re actually collaborating openly with them to share the content. So, we’re putting in the first draft and then they actually go in themselves to make changes further.

So, that feels quite exciting and that’s certainly a very new way of working.

Did you enjoy this post?

Don’t miss out – click here to get more posts like this delivered straight to your inbox