Skip to content
digital | visual | cultural digital | visual | cultural
A research series at Oxford 2018 to 2019 / Dossier archive

Program design / Workday consulting

Workday Consulting Skills Development Program

A practical program design for building consultants who can configure with judgment, work with data, hold a client conversation and lead a delivery workstream.

Workday consulting is learned in the overlap between product knowledge and client work. A consultant can know the configuration screen and still struggle to run a design session, challenge a weak requirement or explain a data defect to a payroll lead. A development program should build those capabilities together, not as separate courses.

This program design is for consulting leaders, practice managers, learning leads and experienced consultants who are building the next group of practitioners. It assumes access to a Workday tenant, a set of real or realistic processes and a group of people who can coach.

It is deliberately practical. The aim is not to complete a curriculum. The aim is to produce consultants who can be trusted with a client problem.

Abstract grid of light and code suggesting a structured learning path
A program works when practice, feedback and client judgment are designed together.

Why a program, not a course

Product training gives knowledge. Consulting skills need practice with consequences. A course can explain how a business process works. A program puts a learner in a room where a client disagrees, a data set does not reconcile and a deadline is real. The difference is not more content. It is more responsibility, with support.

Design the program as a sequence of experiences. Each experience should ask the learner to make a decision, defend it and observe the result. The sequence matters more than the syllabus.

For product instruction, Workday training is one external starting point. It supplies knowledge; the program supplies the practice.

The four transitions

  • Learn the platform. Understand the core objects, security model, reporting approach and the limits of standard capability.
  • Apply it to a process. Turn a business process into a configuration choice, a test and a support model.
  • Defend a design decision. Explain the trade offs to a client, record the decision and manage the consequence.
  • Lead a delivery workstream. Plan the work, coach others, manage risk and hold the line on quality.

The competency model

A useful competency model describes what a consultant does, not what a consultant knows. Keep it small enough to observe and specific enough to assess.

  • Functional depth. Understands the process end to end, including the roles, controls and exceptions that sit around the screen.
  • Configuration judgment. Knows when standard capability is enough and when a change needs a named business case.
  • Data fluency. Can profile, reconcile and explain data without hiding behind a technical team.
  • Client communication. Can run a session, challenge a requirement and write a decision that people can act on.
  • Delivery discipline. Can plan, test, complete cutover and support the first live cycle.
  • Commercial and change awareness. Understands scope, risk, adoption and the cost of delay.

The program test

If a learner can describe the right answer but cannot make a decision under pressure, the program has taught knowledge, not consulting.

Program architecture

Build the program in four layers. Each layer should produce evidence that the learner is ready for the next one.

Foundation

Short modules on Workday concepts, security, data, reporting and the consulting method. Keep them short and test recall with applied questions, not trivia. A learner should leave each module with one thing they can do in the tenant.

Guided practice

Case labs in the tenant. Each lab has a scenario, a decision to make, a build, a test and a short write up. The output is evidence, not completion. Review the write up with a coach and ask what the learner would do differently.

Client simulation

A full day simulation with a client lead, a payroll lead, a data lead and at least one difficult requirement. Participants run the session, make a decision, record it and present the trade offs. The simulation should include a moment where the client is wrong and the consultant has to say so with evidence.

Live apprenticeship

Shadow a real workstream, then reverse shadow. In reverse shadowing, the learner leads while a senior consultant observes. Use a weekly review to turn experience into judgment. The learner should present the decision, the evidence and the risk, not just the task list.

Curriculum and practice

The curriculum should follow the work, not the product menu. Use a small number of modules and connect each one to a real deliverable.

  • Workday foundations and the consulting method. Core objects, security, reporting and the way a consultant frames a problem.
  • Process design and requirements. How to run a session, separate a need from a preference and write a testable requirement.
  • Configuration standards and decision logs. How to configure consistently and record the reason for every exception.
  • Data profiling and reconciliation. How to measure quality, agree a tolerance and prove that data arrived intact.
  • Testing and defect triage. How to design end to end scenarios, judge severity and decide what is ready.
  • Client communication and challenge. How to present a trade off, hold a boundary and keep the relationship intact.
  • Cutover and hypercare. How to plan a runbook, staff a command structure and exit support on evidence.
  • Commercial awareness and change. How scope, cost, adoption and benefits connect to the design.

The weekly rhythm

One short learning session, one case lab, one client conversation and one feedback review. The rhythm matters more than the volume. Protect the time in the resourcing plan and make it visible to delivery leads.

Every learner keeps a decision journal. The journal records the situation, the options, the decision, the evidence and the result. It becomes the portfolio for assessment and the raw material for coaching.

Assessment and progression

Assess evidence, not attendance. A learner who has completed every module may still be unable to lead a design session. A learner who has led one difficult session with a clear record may be ready for more responsibility.

Use four gates: a knowledge check, a case lab review, a simulation observation and a live workstream review. Each gate should have an observable rubric. A simple rubric works well: context, options, decision, evidence and communication.

Progression is a responsibility ladder. The learner observes, supports, leads with support, leads and then teaches. Do not promote on confidence alone. Promote on evidence that the learner can repeat the behaviour in a different situation.

Certification should be a portfolio review, not a quiz. Ask the learner to present three decisions, the evidence behind them and what changed as a result.

Coaching and feedback

Every learner needs a named coach and a named practice lead. The coach develops capability. The practice lead provides the work. Without both, the program becomes a series of workshops with no route into responsibility.

Feedback should be specific, observed and timely. Use three questions: what did you decide, what evidence did you use and what would you do differently? Avoid feedback that evaluates personality. Describe the behaviour and its effect.

Run a monthly calibration session for coaches. Compare evidence, challenge generous assessments and keep the standard consistent. A program is only as strong as the judgment of the people who assess it.

Protect time for reflection. A program that only adds work will lose to delivery pressure. The weekly review is not a luxury. It is where experience becomes capability.

Running the program

Treat the program as a delivery workstream with an owner, a calendar, a budget and a risk log. It needs the same discipline as client work.

Capacity is the main constraint. Protect a weekly learning block and make it visible in the resourcing plan. If the program depends on people who are already fully booked, it will fail quietly.

Use real client material with permission. Sanitise data and respect confidentiality. A realistic case is more useful than a perfect fictional one, provided the program protects the client.

Keep a faculty of practising consultants. External trainers can teach method. Your own consultants must teach judgment, because judgment is contextual and earned.

Measure the program by the quality of work it produces, not by the number of sessions delivered. Completion is an input. Capability is the outcome.

A 12 week roadmap

Use the first 12 weeks to establish the rhythm and produce evidence. Extend the program after that with live workstreams and specialisms.

  • Weeks 1 to 2: baseline assessment, personal development plan and coach matching.
  • Weeks 3 to 4: Workday foundations, security, data and reporting.
  • Weeks 5 to 6: process design, requirements and configuration labs.
  • Weeks 7 to 8: data profiling, reconciliation and testing labs.
  • Weeks 9 to 10: client simulation and decision review.
  • Weeks 11 to 12: live apprenticeship plan and portfolio review.

Metrics and common pitfalls

Use a small set of measures that show whether the program is producing capable consultants. Track time to independent workstream, the quality of decision journals, defect escape rate, client feedback, portfolio pass rate and retention. Review the measures quarterly and change the program when the evidence says it is not working.

Curriculum without practice. The program covers content but never asks for a decision. Countermeasure: every module ends with a lab, a review and a recorded decision.

Too much content. The program tries to teach everything and finishes nothing. Countermeasure: a small number of modules tied to real deliverables.

No coaching capacity. Learners are assigned to busy seniors who have no time to observe. Countermeasure: named coaches, protected time and a calibration rhythm.

Assessment by quiz. The program measures recall and calls it capability. Countermeasure: portfolios, simulations and live workstream reviews.

No route into live work. The program ends and the learner returns to the same tasks. Countermeasure: a planned apprenticeship with a named practice lead and a first responsibility.

Program checklist

  • A named program owner and a faculty of practising consultants.
  • A competency model with observable behaviours.
  • A tenant and a case library for safe practice.
  • A weekly rhythm protected in the resourcing plan.
  • A decision journal and a portfolio for every learner.
  • Assessment gates with evidence and coach calibration.
  • A live apprenticeship route into client work.
  • A review cycle that changes the program based on outcomes.

A strong program does not produce consultants who know more. It produces consultants who can be trusted with a problem, a client and a decision. That is the standard the program should be designed to meet.

External reading

These external sources cover the wider capabilities around the program: change, leadership, operating models, workforce research and consulting practice. They are not Workday product documentation or course catalogues.

Use this guide with the archiveThis program design is an independent resource. It does not replace your organisation's consulting method, Workday documentation or legal advice. For the earlier legacy note, read Planning and execution for Workday implementations. You can also return to the resource index or contact the project.