Skip to main content
School of Information Sciences · University of Pittsburgh
iSchool Inclusion Institute Imagine. Immerse. Inspire.
Professional Development

Workday Business Process Design Workshop

A structured, hands on workshop for teams who need to translate how work really happens into reliable Workday business processes.

Workday business processes are the rules that decide how work moves through an organization: who starts a task, who reviews it, which conditions change its path, and who receives the final result. A well designed process removes guesswork. A poorly designed one creates queues, duplicate effort and frustrated users.

This workshop treats process design as a design discipline rather than a configuration task. Participants map the real process first, agree on the decisions and exceptions, and only then build and test the Workday definition.

Why process design comes before configuration

It is tempting to open the system and start building. Teams that do usually discover the gaps later: an approval that no one owns, a step that runs twice, or a security group that reaches more records than it should. The workshop begins with a simple principle: describe the process in plain language, confirm it with the people who do the work, and then translate it into Workday.

That order matters because a Workday process definition is only as good as the agreement behind it. When the design is clear, configuration becomes a short, mechanical translation of decisions that everyone already understands.

Teams that are new to the platform often pair the design sessions with Workday training so that owners and administrators share the same vocabulary before configuration begins.

Curriculum

What the workshop covers

Each module pairs a short explanation with an exercise that participants complete for a process from their own organization.

Module One

Process discovery and mapping

Capture the current state in plain language, identify the trigger and the outcome, and separate the real exceptions from the habits that grew around old tools.

Module Two

Structuring the definition

Translate the map into a sequence of steps with clear owners, decision points and exit conditions that match how the process actually ends.

Module Three

Conditions and routing

Use conditions to route work to the right people, avoid needless approvals, and keep a single source of truth for each decision.

Module Four

Security and assignees

Decide who must act, who may view, and who should only be notified, then align security groups with those responsibilities rather than legacy roles.

Module Five

Notifications and timing

Design alerts that inform without overwhelming, and set sensible deadlines and reminders so work does not stall silently in a queue.

Module Six

Testing and validation

Walk the process end to end with realistic data, confirm each branch and approval, and document the result before anything goes live.

Audience

Who should attend

The workshop is written for the people who own a process and the people who build it, working side by side.

  • Process owners and operations leads who know how the work really happens
  • Business analysts who document requirements and decisions
  • Workday administrators and functional leads who configure and maintain the definition
  • Security administrators who manage roles, groups and access
  • Project managers coordinating a rollout or a redesign

No prior configuration experience is required for the design sessions. Teams that bring both a process owner and an administrator to the same table get the most from the exercises.

Agenda

A one day outline

  1. Morning: discovery

    Map a real process, agree on the trigger, the outcome and the exceptions, and write the plain language description the rest of the day will build on.

  2. Late morning: decisions

    Turn the map into steps, identify decision points, and sketch the conditions that route work to the right person.

  3. Afternoon: build

    Configure the definition in a sandbox, align security groups and assignees, and set notifications and deadlines.

  4. Close: validation

    Test every branch with realistic data, review the audit trail, and agree on what must be documented before go live.

What participants leave with

  • A current state process map agreed by the people who do the work
  • A documented list of decisions, exceptions and owners
  • A configured process definition that has been tested end to end
  • A short validation checklist for future changes
  • A clearer picture of which security groups and roles are involved

These artefacts are deliberately lightweight. The aim is a process that a new team member can read and understand, not a document that is written once and never opened again.

Common design pitfalls

  • Building the system before agreeing on the process
  • Adding an approval step to compensate for an unclear owner
  • Copying a legacy form into Workday without reviewing its fields
  • Granting broad security access because role design feels slow
  • Testing only the happy path and discovering the exceptions in production

The workshop spends time on these pitfalls because most rework comes from decisions made early and quietly, long before anyone touches configuration.

From the workshop to the profession

Process design is one of the clearest examples of the work that information professionals do: understanding how people use systems, translating that understanding into rules, and protecting the integrity of the data those rules touch. It rewards the same habits that i3 cultivates, including careful listening, clear documentation, and a willingness to ask why before asking how.

If you are exploring the field, the workshop connects naturally to careers in the information sciences, where business analysis, information architecture and systems management are everyday work. You can also read more about the i3 program or contact the i3 office with questions.

Further reading. Independent resources on process design, usability and the information sciences:

Bring a process you want to fix

The best workshops start with a real problem. Come with a process that is slow, unclear or heavily reworked, and leave with a design the team agrees on.