Skip to main content
International Conference on Learning and Administration in Higher Education Conference enquiries: [email protected]
ICLAHE Learning and Administration

Practical learning

Practical Learning Approaches for Workday Training

Workday is not a single screen that someone can learn once and then set aside. It is a connected system of records, approvals and reports, where one action quietly changes what another team sees. Training people to use it well is therefore a design problem rather than a content problem.

The aim is not to tour every button. The aim is to help people make sound decisions inside Workday on an ordinary working day, without a trainer at their shoulder. That distinction changes almost everything about how a programme is built.

Begin with the work, not the software

Most Workday curricula are assembled from menus. That is the quickest way to produce material and one of the slowest ways to produce competence. A better starting point is the list of tasks each role performs in a normal week.

A manager approves time, moves a requisition forward and checks a team report. A finance partner corrects a journal and reconciles a cost centre. An employee updates personal details and requests leave. Build the curriculum around those tasks, and the screens become the place where the task happens rather than the subject of the lesson.

Give people somewhere safe to practise

People learn a system by using it, not by watching someone else use it. A practice environment, such as the sandbox tenant used during an implementation, lets learners make mistakes where no real record is affected. Design short exercises with a clear finish line, and watch where people hesitate.

The hesitation is the curriculum. If several learners pause at the same approval step, that step needs a job aid and another round of practice before the next group arrives.

Build role based paths

A single course for everyone wastes time for almost everyone. Managers, human resources partners, finance staff and employees need different subsets of the same system. Share a short foundation on navigation, security and notifications, then branch into role specific modules. Keep each path to the tasks that role actually performs, and remove the rest.

Space the practice and ask for recall

One long session feels efficient and fades quickly. Short sessions spread across several weeks are more durable. Ask learners to recall a step before showing it to them, and use low stakes quizzes to make recall routine. Return to the material just before the moments when it matters, such as a pay period close or a review cycle.

The Learning Scientists publish free summaries of spaced practice and retrieval, and Retrieval Practice offers plain explanations that a trainer can adapt without a background in psychology.

Teach with realistic scenarios

A scenario gives learners a decision to make, which is what the job requires. An employee changes cost centre in the middle of a pay period. A manager needs to backfill a role before a deadline. A finance partner finds a journal that does not balance.

Each case forces the learner to reason about the system rather than follow a script. Debrief every scenario, and ask what would have happened if the choice had gone the other way. That conversation is where judgement forms.

Put coaches close to the work

A knowledgeable colleague in each team answers most questions faster than a central help desk. Choose coaches who are patient and well organised, give them a short guide and a regular office hour, and keep their names visible in the team space. Coaching also gives the central team an early warning about confusing processes.

Talent development bodies such as the Association for Talent Development publish useful guidance on coaching and on learning that happens during real work.

Measure whether behaviour changed

Completion rates record attendance, not learning. Look instead at the measures that show how work is done: the rate of corrections, the time an approval spends waiting, the number of support tickets for a given task, and whether people use the reports they were taught. Ask managers what has changed. These signals are imperfect, but they point at behaviour rather than at clicks.

Keep help short and findable

Long manuals are rarely opened at the moment of need. Provide one page job aids, short recorded clips and a searchable knowledge base, and place them where the work happens. A learner who can find an answer in twenty seconds will use the system more confidently than one who must book a course.

Plan for change

The platform changes on a regular release cycle, and people change roles. Build a light process for reviewing material after each release, and keep a short refresher for anyone who returns to a task after a long gap. Training is a service that continues, not an event that ends.

Summary

Practical approaches at a glance

Learning approaches and what they achieve
Approach In practice Why it helps
Task based design Curriculum built from the tasks a role performs each week Learners practise what they will actually do
Safe practice Short exercises in a sandbox with a clear finish Mistakes cost nothing and confidence grows
Role paths Shared foundation, then modules for each role Less time on screens a person never uses
Spaced review Short sessions across several weeks Recall lasts longer than a single long day
Scenario work Realistic cases with a decision to make Builds judgement rather than memorisation
Local coaches A trained colleague in each team Answers arrive when the question does
Transfer measures Error rates, cycle times and support tickets Shows whether behaviour actually changed

Common pitfalls

  • Covering every feature instead of the tasks that matter.
  • Demonstrating the system while learners only watch.
  • Measuring attendance and calling it success.
  • Leaving managers out of the design.
  • Treating the launch as the end of the work.

A final word

Good Workday training is quiet. It shows up as fewer corrections, faster approvals and colleagues who help one another without waiting for a course. Start from the work, give people room to practise, and keep the help close.

The system will keep changing. A habit of learning around it will last longer than any single set of slides.

Explore our learning resources Read the journals