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.

Kelly Global IT, One Way to Work: manual reporting became automated visibility.
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.

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.

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

Results

What changed in the pilot.

6 to 2ways for work to come in, now two clear pathsFront Office pilot
5 to 3five hand-built reports became three dashboards that update themselvesFront Office pilot
3 to 1ways of tracking releases, now one release path
81.1% to 83.1%organizational health scoreSame survey, re-run with the pilot group

What Agileon designed

Five connected moves.

01

Bring every request through the front door

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

02

Decide priorities together, in one place

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

03

Make one tool work like one system

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

04

Connect every release to its approval

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

05

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.

We moved from reactive to deliberate. A shared view of priorities and pipeline now shapes how the team plans and executes.
Antony Brahin, Development Manager, Front Office Pilot

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 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 PDF, 48 pages. Opens in a new tab, no form.

Prefer to talk it through? Walk Through It With the People Who Built It

The work behind this story

More proof

The same pattern, in short form

Seeing the same pattern inside your organization?

Bring us the situation that sounds like this story. A practitioner will tell you which part of the system it points to, and whether we are the right people to work on it.