iorad is a tool that captures software workflows as interactive, step-by-step tutorials.
Instead of screenshots or static documentation, iorad records how a process is actually performed inside a tool and turns it into clear, reusable guidance that’s easy to follow and keep up to date.
Why we’re using it
We’re introducing iorad to make it easier to:
- Document repeatable software processes
- Support onboarding and training
- Reduce repeated “how do I do this?” questions
- Capture subject-matter expertise once and reuse it
- Keep documentation current as tools and processes change
What we’ll use iorad for
iorad will be used for workflows where steps matter, including:
- Software how-to guides
- Internal process documentation
- Onboarding and enablement
- Job aids embedded in the tools we already use
iorad is not intended for strategy, policy explanations, or one-off tasks.
Who iorad is for
Not everyone will use iorad in the same way.
- Most team members will view tutorials as part of their daily work training
- Some team members will create or update tutorials for processes they own
- A smaller group will review and maintain standards
For creators: what to expect
If you’re asked to create a tutorial, iorad is designed to be lightweight.
You’ll typically:
- Perform the process as you normally would
- Let iorad capture the steps
- Make small edits for clarity if needed
Where tutorials will live
iorad tutorials may be:
- Embedded in training platforms
- Linked from internal documentation
- Shared directly when guidance is needed
Example
Here’s a short example of what an iorad tutorial looks like: