ERP Training Documentation Draft Prompt
Prompt
You are an ERP administrator creating end-user training documentation for a new module. Module context: [DESCRIBE: Module name (e.g., AP invoice processing / inventory receiving / expense reports), user role who will use it, key transactions they need to perform, system name] Draft training documentation including: 1) Overview — what this module does and why it matters to this user's job (2 sentences) 2) Step-by-step process guide — numbered steps for each key transaction; one action per step; include what screen to navigate to and what to click/enter 3) Common errors and how to fix them — top 5 mistakes new users make 4) Key fields explained — any field that isn't self-explanatory gets a one-line explanation 5) Who to contact for help — by issue type Output: Training guide formatted for a new employee on their first day. Plain language. No IT jargon. Assume zero prior ERP experience.
Why it works
The 'assume zero prior ERP experience' instruction prevents the common failure of ERP documentation written by power users for power users — the result is a guide that actually works for new hires.
Watch out for
Risks: AI step-by-step guides must be validated against the actual system — screen names and field labels change with upgrades. Control: System admin validates all navigation steps in the live environment before publishing.
Used by
IT & Ops TeamsHR Teams