Why do key users repeat the same explanation?
A key user is an employee from the business side who represents a department in the SAP project. Key users join the workshops, test the new processes and then train everyone else. They do this next to their normal job.
Training usually happens once, in a meeting room or on a call, a few weeks before go-live. On the first real day people have forgotten half of it. They call the key user, who shares the screen and shows the same steps again. The same question arrives from the next colleague an hour later, and again when someone new joins three months later.
A written guide with screenshots answers the question without the key user. It also outlives the project: when the consultants leave, the guides stay.
Which SAP tasks should be documented first?
Start with tasks that many people do, and with tasks that are done so rarely that they are forgotten.
| Area | Example tasks | Who needs the guide |
|---|---|---|
| Purchasing | Create a purchase requisition, approve a purchase order | Requesters and approvers in every department |
| Sales | Create a sales order, check a delivery | Sales office |
| Finance | Enter an incoming invoice, look up a payment | Accounting team |
| Warehouse | Post a goods receipt, move stock | Warehouse staff |
| Master data | Create a customer or a supplier record | Master data team |
| Employee tasks | Enter working time, request leave, submit expenses | All employees |
Employee tasks reach the most people, so one guide there saves the most questions. Month-end and year-end tasks are done rarely, so they are forgotten most often.
When in the project should the guides be recorded?
| Phase | What to record | Why then |
|---|---|---|
| Design workshops | Nothing yet | Screens and steps still change |
| User acceptance testing | Each test case you run | You are doing the task anyway, with test data |
| End-user training | The gaps trainees find | Their questions show what is missing |
| Go-live and first weeks | Answers to repeated tickets | One guide closes many tickets |
| After each release | Guides whose screens changed | Old screenshots mislead |
The test phase is the best moment. A test case and a user guide describe the same thing: the steps of one task and the expected result. Recording while you test gives you both with one effort.
How do you prepare the guides?
- List the tasks per role. Write down what each role does in the new system, not what was configured.
- Record in the test or training system. Use made-up records, so no real customer, supplier or employee data ends up in a screenshot.
- Keep one task per guide. “Create a purchase requisition” is a guide. “Purchasing” is a folder.
- Add the reason where it matters. One sentence on why a field must be filled prevents wrong entries.
- Hide what should not be seen. If real data did get into a screenshot, redact it before sharing. See how to redact sensitive data in screenshots.
- Test it with one end user. Ask a colleague who missed the training to do the task with only the guide.
- Publish before go-live and name an owner. Each guide needs a person who updates it when the screen changes.
How to create training documentation covers the planning side, and the training manual template gives you a structure for the whole set.
Guide, video or classroom training?
- Classroom or call: good for the big picture and for questions. Poor as a reference, because nobody can look it up later.
- Video: good for a first look at a new screen. Slow when you only need step seven.
- Step-by-step guide: best during the work itself. The user keeps it open next to the SAP screen and follows along.
Most rollouts need all three. The guides are the part that keeps working after the project ends.
Does this work for every SAP screen?
No, and it is worth checking before you plan. A browser tool records what happens in the browser. Newer SAP products are used through web pages, for example the SAP Fiori launchpad, so those tasks can be recorded like any other web page. The classic SAP GUI for Windows is a desktop program, and a browser tool cannot record it.
Ask your project team which screens your users will open in the browser after go-live. In a move to a newer SAP version many daily tasks move to the browser, and some expert transactions may stay in the desktop program.
Who keeps the guides current after go-live?
SAP screens change with releases and with your own improvements. Give each process area one owner, usually the key user, and review the guides after every release. A guide with an old screenshot is worse than no guide, because people stop trusting the whole set. Keeping training docs up to date has a simple routine for this.
If an implementation partner built the system, agree early who writes the guides. The ERP and CRM implementation handover page lists what the partner should leave behind.
How does Izly help SAP key users?
Izly is a Chrome extension. You do a task once in your browser and Izly turns it into a step-by-step guide with a marked screenshot for each click, and into a narrated video if you want one. You do not write the steps or cut screenshots by hand. You edit the wording, hide what should not be seen and share the guide as a link or a PDF.
The Free plan includes 10 guides with PDF export and 3 trial videos, which is enough to try it on the first tasks of one department. People who only read a guide never pay.
Izly works in Chrome on Windows and Mac, and only inside the browser. It does not record SAP GUI for Windows or other desktop programs. Izly is an independent product and is not affiliated with SAP. Try it on our practice form first, then on one real task in your test system.
Frequently asked questions
What is a key user in an SAP project?
A key user is a business employee who represents a department in the project. Key users help design the processes, test the system, train their colleagues and answer the first questions after go-live.
Can Izly record SAP GUI?
No. SAP GUI for Windows is a desktop program, and Izly records only what happens in Chrome. SAP screens that open in the browser, such as the SAP Fiori launchpad, are web pages and can be recorded.
How many guides does an SAP rollout need?
Count tasks, not modules. List what each role does in a normal week and at month-end. Start with the five tasks that most people do every week and add the rest from the questions you receive.
Can the guides contain real company data?
Avoid it. Record in the test or training system with made-up records. If a screenshot still shows a real name or an amount, redact it before you share the guide.
Should the consultant or the key user write the guides?
The key user, where possible. Consultants know the system, but key users know the words and the cases their colleagues meet. A guide in the department's own terms is followed more often.
Do end users need to install anything to read a guide?
No. A guide is opened as a link in the browser or as a PDF. Only the person who records needs the Chrome extension.
Related pages
- Use caseERP and CRM implementation handover: guides you leave with the client
- GuideHow to Create Training Documentation for Software
- GuideHow to Create a User Guide for Software, with Screenshots
- TemplateFree training manual template: Word, Google Docs and PDF
- TemplateFree user manual template: Word, Google Docs and PDF
Record it once and let the guide write itself
With Izly you do the task once in the browser. Clicks and screenshots become a step-by-step guide that you edit, share, turn into a narrated video or run again for every row of a table.