Everyone uses the same Manabu2, but what people need to learn, how deeply, and in what order varies a lot with their position and the role they're expected to play. This guide walks through what kind of learning path to design for each role, with concrete examples.
- Give everyone the same path and it will be too shallow for some and too hard for others
- Design paths by role and you deliver only the learning each person actually needs
- Whatever the role, the thinking behind a good learning flow is the same
Why role-based paths matter
Giving every user the same learning path causes problems like these:
Too shallow for some people
Too hard for others
Designing paths by role lets you deliver just the learning people need, to the people who need it.
Role ①: Paths for learners (general staff)
The goal of a learner path is to give people the minimum knowledge and behaviors they need to do their job.
Learner path ├ Manabu2 basics ├ Core knowledge for the job ├ Cautions and things not to do └ Comprehension check quiz
- Keep jargon to a minimum
- Can be finished in a short time
- Clearly separate required from optional
Role ②: Paths for HR
For HR paths, the operations and administration perspective is what matters.
HR path ├ How Manabu2 fits together ├ Managing users and departments ├ Reading progress and reports └ Common operational pitfalls
- Covers the "why," not just the clicks
- Includes how to handle problems
- Keeps collaboration with other departments in mind
Role ③: Paths for executives and managers
The goal of an executive path is not to understand every detail.
Executive path ├ Why we adopted Manabu2, and the big picture ├ How to read learning status ├ Where we are with AI / DX └ What you need to make decisions
- Gives the big picture quickly
- Leaves out specialist operations
- Focuses on numbers and metrics
Role ④: Paths for curriculum managers
Curriculum manager paths are for the people who design the learning itself.
Curriculum manager path ├ The overall learning structure ├ Designing courses and lessons ├ Designing quizzes and tests ├ Designing and improving paths └ Real-world design examples
- Covers both principles and practice
- Doesn't impose a single right answer
- Assumes ongoing improvement and operation
Role ⑤: Paths for RAG managers and AI leads
RAG manager paths are for specialist roles that drive advanced use.
RAG manager path ├ RAG / AI fundamentals ├ Organizing and managing internal data ├ Choosing the right agent for the job ├ Security and access control └ Use cases and how to improve them
- Assumes some technical background
- Expects trial and error
- Emphasizes how it ties into operating rules
What every role-based path has in common
Whatever the role, the thinking behind a good learning flow is the same.
- State the goal up front
- Leave out what isn't needed
- Make it easy to pick up again after stopping partway
What to read next
The next guides cover more advanced automation and how to keep improving.
