https://360.articulate.com/review/content/f6d2ae6c-4ca1-496a-ab41-fc887bd13a3d/review

In the past I have been used to being drip-fed content which often results me constantly changing the plan I had in my head for the development – ultimately ending in a ‘pieced together’ product that essentially ticked a box. Now with a designated Wireframe and better understanding of the Design principles, I can advocate for a more structured approach to product creation from a MUCH earlier stage. I expect this will not only massively improve the product design, but will lead to a better SME relationship as we will both have a clearer understanding of how our roles impact one another.

Screenplan & Storyboard:

Writing the wireframe was fantastic as it gave me a really solid visual to show my SME when we met, however, I admit I really struggled to motivate myself through the creation of the Screenplan and Storyboard.

As a developer, and as someone who ploughs straight into things, I found planning each slide very tedious and several times had to refrain from jumping ahead. I pushed through it though and I was surprised to see how welcomed they were by the rest of my team. I believe it may have actually elevated their opinion of how much consideration goes into development, and while I have previously been used to doing this stage of the planning in my head, I see the value in this approach to sharing the process with the SME as it has made her feel much more connected and included in the overall project.

Videoscribe:

I had not used Videoscribe prior to this assignment, but I enjoyed learning it for this purpose. I could see similarities between it and Articulate Storyline in that you can be developing frame by frame - giving you more control over the design than I had anticipated. I am in the process of putting a software request into my IT team for a Videoscribe subscription, but in the meantime, I have used a trial account (leaving watermarks in this submitted version). These would be removed before launch.

Post-development I felt that I had included too much OST in the middle section of the video. I done further reading on the 'Coherence Principle' (DeBell, 2022) and confirmed these suspicions - and now understand that for my Beta version, this needs to be reduced and simplified to better support the learner.

This has been a good insight into Kolb’s Experiential Learning cycle as I can see how my evaluation of this experience will directly impact how I go on to adapt/ modify the next video I produce. This 'transfer' of learning (Moon, 2004) feels deeper-rooted because I am reflecting on how I need to design for learning, not simply finding ways to share the information participants need.

Padlet:

I am also proud of myself for coming out of my 'Miro comfort zone' and trialling out a new presentation tool for this assignment. This feels like a more succinct way for me to plan my design stages in the future and it has peaked my interest in now experimenting with other tools!

Overall:

As a developer with limited design experience, this has been a new (better!) way of creating learning content. This assignment has encouraged me to put conscious thought into not simply how I am presenting the content - by why. It has forced me to confront my previous ways of working and admit that there is most definitely room for improvement in how I approach the early planning stages of learning design - and that while the user experience is important, I should be taking the lens of producing for the learner experience.

(609 words)

Moon, J. A. (2004). A handbook of reflective and experiential learning: Theory and Practice. Psychology Press.