“If most of your courses rely on the same basic interactions every time, your course developers are probably sticking to what they know.” Rob Mynett, Omniplex Learning’s Product Enablement Specialist, told us in our recent expert Q&A on authoring tool enablement.
It’s easy to see how it happens. A team gets a new authoring tool, but little time or budget goes into helping people learn it, so they work it out as they go. Or the tool has been around for years, and people settle into using the same handful of features they learned first. Either way, before long they’re sticking to the same basic builds and producing courses that make little impact beyond completion rates.
Getting more from your tool depends on the skills around it, from instructional design and visual design to accessibility and building confidently, and, luckily, all of those can be developed.
Our free authoring skills gap matrix shows you where your team sits across five key areas, and which ones to tackle first. Once you’ve filled it in, come back to this blog for practical next steps, whichever areas you choose to prioritise.
How do you use the authoring skills gap matrix?
Once you’ve downloaded the matrix, set aside 10 minutes, ideally with your team, and work through it in three steps:
- Rate. For each skill area, circle the level most of your team reaches (Foundation, Practitioner, or Advanced – F, P, or A). Base it on recent builds rather than intentions. If levels vary a lot, rate each person.
- Prioritise. Mark each area high, medium, or low (H, M, or L), depending on how much it would improve your learners’ experience or support your business goals.
- Act. Choose your top two areas and then use the next section in this blog to decide what to do first.
What to do next: area by area
Start with the areas you marked as priorities. Trying to tackle everything at once usually means nothing moves, so give your top two proper attention. Each area below sets out practical steps to help your team reach the next level, plus training options if you’d like expert support.
Instructional design
Moving to Practitioner
- Ask your team to write one learning objective per build before they open the tool, starting with “After this, learners will be able to…”
- Introduce a one-page brief covering the objective, the audience, what learners need to do differently, and one practice moment.
- In the next build, encourage your team to swap one knowledge check for a scenario or decision-based activity.
- Agree on a design process that suits your projects, such as ADDIE or SAM, so everyone works from the same playbook.
- Pair people up to review each other’s briefs, or run a short workshop on writing objectives.
- Bring in an expert-led instructional design course to upskill the team.
Moving to Advanced
- Start with a learning needs analysis, so each build addresses a confirmed performance gap.
- Agree with stakeholders how you’ll measure behaviour change on the job, and set a date to check.
- After launch, review the results and make at least one change to the module based on them.
- Build learning science into your designs, drawing on research into approaches such as spaced and retrieval practice.
👉 Learn from the experts on our ITOL-accredited Instructional Design Diploma
Visual design
Moving to Practitioner
- Put your last three builds side by side, along with work from the rest of the team, and note where fonts, colours, spacing, and image styles differ.
- Turn what you find into a one-page style guide that reflects your brand guidelines.
- Create a handful of flexible layouts (title, content, scenario, summary) as starting points for new builds. They keep branding consistent while leaving room for the design to fit the learning.
- Consider arranging training so your team can learn from visual design experts
Moving to Advanced
- Grow the style guide mentioned above into a shared library of approved components.
- Cover key design principles as a team, such as hierarchy, contrast, alignment, and white space.
- Run refresher sessions on good visual design principles, using real examples from your own library.
👉 Sharpen your skills with our Visual Design Diploma
Accessibility
Moving to Practitioner
- Add a short checklist to your storyboard stage: alt text, colour contrast, keyboard navigation, and captions or transcripts for audio and video.
- Ask your team to run text and background colours through a free contrast checker as they build.
- Test one module using only a keyboard.
- Have your team explore the accessibility features built into your authoring tool and use them on their next build if they aren’t already.
- Learn the principles behind the guidelines. WCAG (the Web Content Accessibility Guidelines) are built around four: content should be perceivable, operable, understandable, and robust.
- Put your team through an expert-led course that covers the WCAG principles in practice.
Moving to Advanced
- Test with a screen reader and, where you can, with learners who use assistive technology.
- Build accessibility checks into every stage of your process, from storyboard through to final review, and make it a sign-off requirement for every build.
- Nominate an accessibility champion who keeps up with requirements and answers everyday questions.
👉 Build better courses for everyone: Articulate 360 AI Accessibility training
Tool proficiency
Moving to Practitioner
- Ask your team to list the features they use regularly, then compare that with your tool’s help documents or vendor training to see what’s missing and relevant.
- Pick one new feature and rebuild an existing module with it. Time-box it to half a day, so it stays realistic. Then share what you found in a 15-minute team session.
- Enrol your team on an expert-led course that covers the essentials.
- Keep a shared tips document or playbook, so discoveries don’t stay with one person.
- Block out regular time for experimenting, even half an hour a fortnight. It rarely happens unless someone protects it.
Moving to Advanced
- Encourage your team to take on a more complex interaction, such as branching or conditional logic, and document how they built it so others can learn from it.
- Set up a test project where your team can experiment without a live deadline.
- Review each new product release for features worth adopting and share a short summary with the team.
- Hold a regular feature enablement session and name a champion for questions.
- Book your team onto an advanced course once they’ve mastered the basics.
👉 Whether you’re just starting out or want to learn more advanced features, we have Articulate 360 AI training for every level
Workflow and efficiency
Moving to Practitioner
- Review your last five builds and list the structural elements that repeat, such as navigation, intro screens, and layouts.
- Turn those into templates and agree a naming convention and one shared place to store them. This gives everyone a consistent place to start, while still allowing room for creativity.
- Test each template on a phone and tablet before you share it.
- Add a peer review before publishing, so quality doesn’t depend on one person’s eye. Build in time for any edits it raises.
Moving to Advanced
- Give your template library an owner and review it every six months.
- Retire or refresh any template that’s either unused or nudges your team towards the same basic style of course every time.
- Write a standards and process playbook for new starters.
Where does your team stand?
Get your free authoring skills gap matrix, then use the steps above to close your gaps.



