Why a generic product tour does not stick
Most people forget a feature demo within days, because it answered questions they had not yet asked. A warehouse picker does not need to see the whole Supply Chain Management menu; they need to confirm a pick, report a short and print a label, and to know what to do when the scanner complains.
So we start from job roles. For each role we list the ten or so tasks that fill a normal week and the few exceptions that cause calls to the help desk. Those tasks become the lesson plan, taught in a sandbox loaded with your customers, items, and open orders, so every screen looks like the one people will see on the first live morning.
People learn faster when the example is their own customer and the lesson ends with a task they finish themselves.
Separate lessons for separate jobs
Sellers and sales managers
Working the pipeline from phone and Outlook, keeping forecasts honest, and letting managers coach from the same data.
- βQualifying leads
- βUpdating opportunities
- βBuilding quotes
- βReading the forecast
Agents and team leads
Handling cases from queues, using the knowledge base, and escalating without losing history.
- βPicking up routed work
- βLinking cases to assets
- βUsing knowledge articles
- βResolving and closing
Dispatchers and technicians
Scheduling on the board, then completing work orders on the mobile app, including offline.
- βBooking resources
- βUpdating work order status
- βRecording parts and time
- βCapturing signatures
Accounting staff
Daily entries, payables, receivables and the close, practiced on your chart of accounts and dimensions.
- βJournals and approvals
- βVendor invoices
- βCustomer payments
- βPeriod close tasks
Growing your own trainers
- 1
Choose the champions
Pick one or two people per department who are respected by colleagues and curious about the system. Seniority matters less than patience.
- 2
Train them deeper
Champions get extra sessions covering the why behind each process, the exceptions, and how to find answers themselves.
- 3
Co-deliver
They teach their colleagues alongside us, then on their own with us in the room, then without us.
- 4
Hand over the kit
Lesson plans, practice exercises, sandbox data and recorded guides stay with your champions for onboarding new hires.

Help that stays after the classroom
Short recorded guides
Screen recordings of a few minutes each, one task per video, named the way users search: how to reverse a payment, how to reassign a case.
Quick reference sheets
One page per role with the daily steps and the fields that must never be left blank, printed or pinned in Teams.
In-app help
Model-driven apps can point a custom help link at your own pages, and Finance and SCM can show task guides built with task recorder.
Office hours after go-live
Drop-in calls in the first weeks where users bring real questions. The questions feed updates to the guides.
Training questions from project leads
Is Microsoft Learn enough on its own?
Microsoft Learn is free and good for understanding the standard product, and we point users to relevant modules. It cannot teach your own processes, your approval rules or the custom fields your team added. That gap is what role-based training fills. The two work well together.
Can you train users on a system someone else implemented?
Yes. We spend time in your environment first to learn how it is set up, then build lessons around it. Where we find configuration that confuses users, we point it out, since sometimes a small change removes the need for training altogether. The training plan is scoped in writing before sessions are booked.
Remote or on site?
Most of our training runs remotely over Teams, with users practicing in a sandbox during the session. That suits distributed teams and lets sessions be recorded for people who miss them. Where hands-on work matters, such as a warehouse with scanners, on-site sessions can be arranged. We discuss what suits your locations during scoping.
When should training happen during an implementation?
Champions should be involved from design, so they understand the choices behind the system. End user sessions work best close to go-live, while the system is stable enough and the memory stays fresh by the first live day. Too early and people forget; too late and they panic. Refresher sessions after launch catch what did not stick.
What about new hires in a year's time?
That is the point of train-the-trainer and the recorded guides. Your champions keep the lesson plans and practice data, and the guides stay searchable in SharePoint or Teams. When a release wave changes a screen, the affected guide gets updated. New hires then learn from your own people, using your own materials.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.
