Work/Ernst & Young

Ernst & Young · Case study

Workforce tools, compliance made coherent.

  • Enterprise UX
  • Workflow Design
  • Data-dense Interfaces
  • Internal Tooling
  • Design Systems
  • Case Management
01 / 04

IOWP hours-mix demand modal: scope staffing changes by month, SMU, city, and competency before save.

Overview

Two tools, one engagement.

Compliance-sensitive, multi-role, and used at global scale: EY’s internal workforce tooling required design that could carry policy logic without putting the burden on individual users. The engagement covered two products: IOWP for workforce planning, used by partners and engagement leads to forecast and reconcile staffing, and IML for international mobility, used to coordinate cross-border talent and visa programs.

The mandate was to help teams get through complex staffing and mobility work faster, with cases that still held up when compliance asked what had changed.

Strategy

Consistent patterns, distinct surfaces.

  1. 01

    Aligned patterns, distinct surfaces

    Tables, modals, filters, and form patterns appeared in both tools. Interaction conventions were aligned where it reduced switching cost, without treating the products as one system. Visual identity stayed distinct enough to signal context.

  2. 02

    Modal-driven data editing

    Modal editing kept the dashboard visible while a partner reviewed and changed staffing data.

  3. 03

    Template-first workflows

    Templates let compliance configure once and coordinators run cases without needing to know policy by memory. Repeatable task templates carried the operational logic so individual users worked from configured defaults rather than from scratch.

  4. 04

    Checked against enterprise patterns

    Contained edits, change previews and role-based approvals made each action clear before a case moved forward. These patterns fit the review and coordination work in the staffing and mobility flows.

Design

Rigid structures that can adapt.

Staffing scenarios, edited in context

Engagement leads model supply and demand for each staffing scenario. The modal pattern brought edits inside the dashboard, so reconciliation happened next to the data rather than away from it. Inline editing was considered but unreliable at this data density; the modal kept dashboard state intact while isolating the edit target.

01 / 04
01 / 07

Start from a template, not scratch

New assignments did not need a custom workflow built step by step. Coordinators applied a pre-configured template to a live case so tasks, defaults, and compliance steps arrived together instead of being reassembled for every engagement. A preview-before-commit screen showed what would change before apply, saving setup time while keeping the action auditable.

Structured case archive

Coordinators closed cases through a structured archive flow: explicit states, clear handoff points, and a record suitable for downstream review.

01 / 09
01 / 06

Role-separated approval chain

Review steps stayed role-separated: submitters, approvers, and coordinators each had a distinct surface, matching how enterprise HR and compliance tools keep sign-off explicit before a case advances.

Assign, tag, approve, and track

The task center gave coordinators a linear path through each mobility case: assign work from a template, tag steps for review, route them for approval, and track status in one queue. Each task showed an owner and its place in the sequence, so handoffs stayed visible. The process stayed auditable without rebuilding policy from scratch on every assignment.

01 / 10

Outcome

Workflows, auditable by design.

2

IOWP and IML redesigned for consistent, auditable internal workflows

5

Flows for in-context edits, template apply, archive, approvals, and task tracking

3

Systematic controls: preview-before-commit, templates, role-separated sign-off

Reflection

Operational value in planning and mobility

In IOWP, engagement leads adjusted hours-mix and staffing scenarios inside the dashboard. In IML, mobility coordinators applied configured templates, routed approvals, and tracked tasks with change previews. Both workflows kept owners, status, and the record of change visible in the product.