Delivering the highest quality of training is what sets Savv-e apart. It involves an ongoing, iterative process of improvement to deliver a product. So what does that look like in day-to-day business functions? Savv-e's Quality Assurance Manager, Kylie, walks us through her process, the importance of her role and the functionality of all things QA.
Quality Assurance takes place at every level of business
While the final and most dramatic part of my work is during the testing of a built module, I lend a hand to other stages of Savv-e’s operations. During my day I may be asked to carry out an editorial review of a proposal that we are submitting, write a draft storyboard (the blueprint for creating a training solution), integrate client feedback, or review existing storyboards before final client approval for our digital designers to build the module.
Quality Assurance is holistic
Punctuation is incredibly important in my role. Whether to capitalise a bullet point, to end it with a comma, a full stop, or nothing at all varies with each client. It can cause agonies. However, editorial review is not the sole focus of QA. I also need to ensure that what we are preparing fits seamlessly within its intended context:
- The overall learning outcomes (including technical specifications and module functionality)
- The style and voice of the client organisation
- The target audience
- Accessibility requirements
After all, it doesn’t matter if we’ve created the most intuitive, inspiring learning module in the world if it doesn’t actually teach learners what our client needs them to learn.
Quality Assurance is all about teamwork and communication
I like to say that at its most basic level, as a Quality Manager I look for ways to break things. If the things which are broken are words, then I can provide a solution (or obtain one from a learning designer / project lead). If the repair involves the actual functionality of a training module, then I can point out the context in which it is malfunctioning.
By myself though, my ability to actually fix the issues I find is limited. I can’t go in and change text in the built module itself; nor can I code. Part of the quality assurance process is knowing when and who to ask for bug fixes – and with an amazing team of skilled colleagues, we’re all likely working on different projects at any given time. I can’t expect them to be able to immediately switch gears to focus on my priorities. In keeping up communication, we can address one another’s needs and contribute to the best product possible.
Why Quality Assurance?
Because I genuinely love language, attention to detail, and knowing that I’m helping to improve a training solution. Module by module, at Savv-e we’re contributing to companies helping their people. It’s extremely rewarding to consider! And honestly, again, I love words. When I go home from work at the end of the day, I sit down at a different computer…and keep writing.