TEMPLATESJIRA · TRN
Training Artefact
A training deliverable with purpose, audience, content, format and delivery method.
01Summary
Name the artefact and what it teaches. Someone browsing a content library should know what it is.
[Format] for [system / process / topic]
Example
User guide for the new expense management system
02Purpose
Say what people should be able to do after using it. Write it as an ability, not a topic.
After using this, [audience] can [ability] without [help or workaround].
Example
After using this, employees can submit and track an expense claim without asking Finance.
03Intended Audience
Describe who they are, what they already know and what tools they have. This decides the length, tone and format.
- Who: [roles / groups, number] - Existing knowledge: [what they know] - Context: [where / when they'll use it]
Example
- Who: all employees (about 1,800), plus line managers who approve
- Existing knowledge: used the old spreadsheet form, no experience with the new system
- Context: on a laptop or phone, usually at month end
04Content Description
List the topics in the order a learner needs them. Start with the task they do most. Say what's left out.
1. [Topic] 2. [Topic] 3. [Topic] Not covered: [excluded topics]
Example
- Sign in and set up your profile
- Submit a claim with receipts
- Track and amend a claim
- Approving claims (managers)
Not covered: finance reconciliation, policy detail
05Format & Delivery
Choose the format that fits how people will use it, then say how it reaches them and who maintains it.
- Format: [PDF / video / slide deck / quick reference card] - Delivery: [LMS / intranet / email] - Owner and update date: [name, date]
Example
- Format: 12-page PDF guide and a one-page quick reference card
- Delivery: intranet finance page, linked from the system sign-in screen
- Owner and update date: Finance Systems, reviewed each release
06Acceptance Criteria
Check coverage, accuracy and accessibility. Say who reviews.
- [ ] Training artefact covers all agreed topics and meets audience needs. - [ ] Artefact is reviewed and approved by SMEs or relevant stakeholders. - [ ] Artefact is in the correct format and accessible to the intended audience.
Example
- All four topics covered, tested with five staff who completed a claim using only the guide.
- Approved by Finance Systems and Internal Comms.
- Meets accessibility standards; screenshots have alt text.
07Definition of Done (DoD)
Done means published, linked and announced, with a way to collect feedback and keep it current.
- [ ] Artefact is stored in the agreed repository or platform. - [ ] Linked to relevant change, process, or system tickets. - [ ] Communication plan for release is completed. - [ ] Feedback loop is established for future updates.
Example
- Published on the intranet.
- Linked to EPIC-58 and the go-live checklist.
- Announcement in the all-staff newsletter on 2 Dec.
- Feedback form linked; reviewed monthly for six months.