T.J. BUMGARDNER

Internal service transformation

One Service Front Door for HR, Payroll, and IT

One employee experience had to conceal several very different kinds of work—without sacrificing ownership, coordination, or trust.

Business systems leadership · Internal service transformation · Confidential workflow architecture

The reality behind the request

What the room needed to understand.

Employee need
HR privacy
Payroll action
One experience
Controlled ownership↗

The visible request sounded straightforward: give employees one place to ask for help. But an employee does not experience the organization as a collection of queues, and a confidential payroll or HR concern cannot safely inherit the same assumptions as a broken laptop. The experience needed to feel unified without making the work operationally identical.

The decisive move was to separate experience design from work design. Employees could receive one coherent front door while the architecture beneath it preserved departmental ownership, restricted visibility, different approval paths, and coordinated obligations across teams.

The critical decision

Design one employee experience without pretending every department performs the same work.

The pressure

The organization wanted to extend an established IT service environment into HR and payroll. The simplicity desired at the front door created risk behind it: payroll corrections, employee concerns, onboarding, offboarding, equipment, accounts, and manager actions carried different owners and visibility requirements.

Why the obvious approach fails

A conventional ‘add another queue’ implementation would have made intake easier while leaving confidentiality, ownership, and cross-department coordination unresolved.

What I owned

  • Led cross-functional discovery and requirements translation
  • Defined departmental roles, routing, ownership, and restricted visibility
  • Designed employee and manager intake around recognizable needs
  • Structured onboarding and offboarding as coordinated service journeys
  • Preserved expansion capacity without overbuilding the first phase

The system response

The design separated the employee experience from the controls beneath it. Shared intake could gather context and direct work correctly while permissions protected sensitive information and downstream responsibilities could be coordinated without exposing the original confidential request.

How the work moved

Discovery → stakeholder translation → service model → permissions and routing → validation → phased expansion

Delivered state

An implementation-ready employee-service architecture involving 33 identified users, IT, HR, and payroll scope, restricted-ticket requirements, employee and manager intake, onboarding and offboarding, and cross-department coordination.

What this proves

The judgment to make an experience simpler without making the underlying operating model less safe.

Business systems leadership · Internal service transformation · Confidential workflow architecture

← Return to selected work