Kelly

# How Kelly Built a Scalable Enterprise Work Management System

Global IT at Kelly was good at its work and still spent too much energy chasing requests, untangling tools, and building reports by hand. Together we built one shared way of working, proved it with a live team, and gave leaders a clear view of the work before it reached their people.

Global IT Professional Services

**Get your copy of the case studies today.** The Implementation Story for the people who will build it, or the Executive Overview for the short read.

[Implementation Story](https://www.agileon.com/pdf/case/kelly-enterprise-work-management?v=mwflecqe-pakch1clhp)
[Executive Overview](https://www.agileon.com/pdf/case/kelly-executive-overview?v=mwflecqe-pakch1clhp)

The starting point

## A capable team, held back by the system around it.

Global IT supports nearly everything Kelly does, and by most measures it was performing well. But requests arrived through six different doors, each group set its own priorities, and leaders were steering from reports that trailed reality by days.

- 01 Work came in through six doors
- 02 Priorities were set wherever the pressure was
- 03 One tool behaved like many different systems
- 04 Releases were tracked three different ways
- 05 Reports were always looking backward

Results

## What changed in the pilot.

**6 to 2** ways for work to come in, now two clear paths Front Office pilot

**5 to 3** five hand-built reports became three dashboards that update themselves Front Office pilot

**3 to 1** ways of tracking releases, now one release path

**81.1% to 83.1%** organizational health score Same survey, re-run with the pilot group

What Agileon designed

## Five connected moves.

### Bring every request through the front door

Six ways in became two, and leaders see demand before it lands on their teams.

### Decide priorities together, in one place

Business partners built shared criteria for weighing requests and decide together in one recurring forum.

### Make one tool work like one system

Delivery teams share a common language and see all of their work in one place.

### Connect every release to its approval

Three ways of tracking releases became one, and every deployment traces back to its approved change.

### Let the work produce the reports

Three dashboards that update themselves replaced five reports built by hand.

How each move was designed, tested in live work, and handed over is in the Implementation Story.

Read the full story

## Two versions of the full case study.

For the leader deciding

### Executive Overview

The short read for leaders: where Kelly started, the approach, and what changed.

- Where Kelly started and what it set out to achieve
- The approach: two phases and four steps
- One way to work: the five-component operating model
- What changed, and what made the pilot hold

[Read the Executive Overview](https://www.agileon.com/pdf/case/kelly-executive-overview?v=mwflecqe-pakch1clhp)
PDF, 16 pages. Opens in a new tab, no form.

For the team building it

### Implementation Story

How the work was designed, built, and piloted, step by step.

- Where Global IT started
- How the response was designed
- How the work was done, step by step
- What changed, in numbers and in people's own words
- What we learned, and what comes next

[Read the Implementation Story](https://www.agileon.com/pdf/case/kelly-enterprise-work-management?v=mwflecqe-pakch1clhp)
PDF, 48 pages. Opens in a new tab, no form.

Prefer to talk it through? [Walk Through It With the People Who Built It](https://calendly.com/d/45d-t98-3pm/connect-with-agileon)

The work behind this story

[Work Management Systems Build one way for work to come in, get ranked, and get delivered, inside the tools you already run. Reporting comes out of the system itself, so nobody rebuilds status by hand.](https://www.agileon.com/professional-services/work-management-systems)[Portfolio Governance Build the forum, criteria, and capacity view that make portfolio tradeoffs visible and make them hold. A decision made this month is still the decision next month.](https://www.agileon.com/professional-services/portfolio-governance)[Change Enablement Keep a new operating model running after launch, with clear owners, playbooks, and early warning when it starts to drift. Outside support steps back on a plan, not on a calendar.](https://www.agileon.com/professional-services/change-enablement)

More proof

[Preserving Speed While Increasing Strategic Clarity Simbex](https://www.agileon.com/case-studies/preserving-speed)[Unifying Strategy Across Six Regions Global Consumer Goods Enterprise](https://www.agileon.com/case-studies/fortune-500-six-regions)

The same pattern, in short form

[Six Front Doors Is the Same as None Field story](https://www.agileon.com/insights/field-note-002-six-front-doors)[The Number That Looks Healthy Hides the Rot Field story](https://www.agileon.com/insights/field-note-095-healthy-number-hides-rot)
