In short
- Definition: The learning effort and materials needed for users, operators and support staff to use the system effectively.
- Goal: Bring people to proficiency quickly and at low cost.
- Example S.M.A.R.T. requirement: New users completing key tasks unaided after a training session of under 2 hours, with 90% passing the post-training quiz.
1. Definition
As a non-functional requirement, training defines the learning effort and the materials needed so that users, operators and support staff can use the system effectively [1], [2], [3], [4].
If a system needs a week of training, the requirement to fix is usually usability.Key takeaway
Training requirements cover the audiences (end users, administrators, support), the formats (classroom, e-learning, in-app guidance, quick reference cards), the maximum acceptable learning time and how proficiency is checked.
Training and usability are linked: the easier a system is to learn, the less formal training it needs.
2. Goal
The goal is to bring people to proficiency quickly and at low cost, so that the expected benefits of the system are reached.
Without explicit training requirements, materials are written at the last minute, adoption stalls and support teams absorb the gap.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Training time per user | Hours | ≤ 2 | Training plan |
| Post-training quiz pass rate | % | ≥ 90% | Learning platform |
| Tasks completed unaided after training | % of key tasks | ≥ 90% | Observation or usability test |
| Training-related tickets | % of tickets in first month | < 10% | Service desk |
The Kirkpatrick model is a common way to evaluate training at four levels: reaction, learning, behavior and results.
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- End users: “New users shall be able to complete the five key tasks unaided after a training session of under 2 hours.”
- Materials: “E-learning modules and quick reference guides shall be available in English and French before go-live.”
- Support staff: “Level 1 support staff shall complete a 1-day training course and pass a certification quiz before go-live.”
5. Questions to Ask Stakeholders
- Who must be trained: users, administrators, support?
- How many people, and where are they?
- How much time can they spend on training?
- Which formats suit the audience?
- Who maintains materials when the system changes?
- How will proficiency be measured?
6. Common Pitfalls
- Training as an afterthought. Plan materials and budget from the start.
- One course for everyone. Administrators and casual users need different content.
- Stale materials. Each release must update guides and screenshots.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Usability — easy systems need less training.
- Documentation — training builds on good documentation.
- Supportability — support staff need training too.
- Internationalization and Localization — materials in the users’ languages.
8. FAQ
Yes. It describes a quality of the delivered solution, how learnable and adoptable it is, rather than a feature.
The time a new user needs before performing key tasks correctly without help.
Often for casual users, rarely for administrators or complex workflows.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [5] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [4] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [7] |
| Usability testing | Observing real users as they try to complete tasks with a product. | [8] |
10. Sources and Further Reading
- [1] “Training.” Wikipedia. https://en.wikipedia.org/wiki/Training (accessed Nov. 18, 2026).
- [2] “Donald Kirkpatrick.” Wikipedia. https://en.wikipedia.org/wiki/Donald_Kirkpatrick (accessed Nov. 18, 2026).
- [3] “Learnability.” Wikipedia. https://en.wikipedia.org/wiki/Learnability (accessed Nov. 18, 2026).
- [4] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [8] “Usability testing.” Wikipedia. https://en.wikipedia.org/wiki/Usability_testing (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @heyquilia; inline photo by @silverkblack, both on Unsplash.








