The Tools Instructional Designers Actually Use in 2026

Tool round-ups usually list forty products nobody uses. This is the smaller, duller list of what actually appears in working instructional designers' workflows, organised by the job it does.

Storyboarding and design

Most storyboarding still happens in Word, Google Docs, or a spreadsheet — because clients can read and comment on those without a licence. Purpose-built storyboard tools exist but rarely survive contact with a client who wants to mark up a document.

Miro or FigJam for the messy early phase: mapping content, sequencing modules, running a workshop with SMEs.

Authoring

• Articulate Rise for linear, responsive courses.
• Articulate Storyline for branching, simulations, and precise interactions.
• iSpring if the organisation lives in PowerPoint.
• Document-to-course tools when the source material already exists as policies, procedures or decks — increasingly common in corporate L&D.

Media

• Camtasia — screen recording and straightforward editing. Still the default for software training.
• Canva — graphics, quickly, without a designer.
• Audacity or Descript — audio. Descript's transcript-based editing is a genuine time-saver for narration.
• AI voice tools (ElevenLabs, OpenAI) — increasingly used for draft narration, and sometimes final.

Review and approval

This is where projects die. Review 360 if you're in the Articulate ecosystem. Otherwise a shared document with tracked changes still beats email attachments, which remain the single most common cause of lost feedback.

Delivery

Whatever LMS the client has — you rarely choose. Worth having tested output on Moodle, TalentLMS and SCORM Cloud at minimum. SCORM Cloud is invaluable as a neutral test bed before you hand anything over.

Evaluation

Mostly the LMS's own reporting, supplemented by Microsoft Forms or Google Forms for reaction-level feedback. Dedicated evaluation platforms exist but are rare outside large L&D functions.

The tools that matter more than the tools

A shared naming convention, a folder structure everyone follows, and a version-control habit will save more time than any software on this list. The most common cause of rework isn't a missing feature — it's three people editing three copies of the same file.