EXELON · SERVICE DESIGN · ENTERPRISE UX

Modernizing how electric-distribution work gets done

Exelon had tried to create greater consistency across six operating companies through shared technology. I led the electric-distribution workstream to understand how the work actually happened across roles, systems, and field environments—and translate that research into a more coherent future operating model.

Senior Designer — Electric Distribution Workstream Owner

  • 6 operating companies
  • 50+ interviews
  • 10 personas
  • 30+ tools & systems analyzed

The pivotal finding: Employees had become the integration layer.

The engagement, in order:

  1. Research across six operating companies

    • 50+ interviews
    • Ride-alongs and contextual inquiry
    • 10 personas
  2. Shared current-state synthesis

    • What was common
    • What legitimately varied

RESEARCH-DERIVED FUTURE STATE — NOT IMPLEMENTED OUTCOME

  1. Five research-derived future-state capabilities

  2. Roadmap priorities and application requirements

Illustrative

Summary of the engagement's stages — not a measured outcome.

01 /

Shared technology had not created a shared way of working.

Exelon wanted greater consistency across six operating companies, but those organizations differed in role structures, local practices, labor constraints, technology environments, geography, field conditions, and organizational histories.

A shared software platform had been introduced as part of the standardization effort, but the rollout struggled to fit how work actually happened. The design problem became larger than improving an application.

Standardizing technology is not the same thing as standardizing work.

The question

What should be standardized, what variation was legitimate, and what did the future service need to support across people, process, information, and technology?

02 /

I owned the electric-distribution workstream across all six operating companies.

I worked under a principal designer as part of the broader Deloitte engagement.

Within electric distribution, I owned the research and synthesis from planning through future-state recommendations.

The six operating companies

  • ComEd
  • BGE
  • Pepco
  • DPL
  • PECO
  • ACE

Workstream I owned

Electric distribution · all six operating companies

  • Research

    • Planning
    • Participant coordination
    • 50+ interviews
    • Field observation
  • Synthesis

    • 10 personas
    • Workflows
    • Service blueprints
    • Cross-company comparison
  • Facilitation

    • ~12 workshops
    • Stakeholder validation
    • Future-state discussion
  • Strategy

    • Future-state concepts
    • Recommendations
    • Roadmap input
    • Application requirements

Context

Scope
This workstream—not the whole Deloitte program.
Oversight
Under a principal designer, within the broader Deloitte engagement.
Handoff
A separate team was responsible for building the future application.

I followed the work beyond the interface.

I investigated how software, asset data, physical infrastructure, safety, organizational rules, materials, and downstream teams combined to create the employee experience, through six research lenses.

Research lenses

  • People
  • Process
  • Technology
  • Information
  • Policy / Organization
  • Physical Environment

An end-to-end service investigation, not a screen-level usability study.

03 /

The pivotal discovery

Employees had become the integration layer.

A single physical job could be represented across operational events, enterprise work orders, field systems, spreadsheets, material requests, crew assignments, financial codes, and the work happening in the field.

When those states stopped matching, employees made them match.

They searched for missing information, re-entered data, maintained spreadsheets, called other teams, recreated work, checked handoffs, and reconciled whether the systems still reflected what had actually happened.

Key statementPeople weren’t simply using fragmented tools. They were maintaining the relationships between the tools, teams, and business states.

One job, many states

One representative job

  1. Operational event
  2. Field response
  3. Work order
  4. Readiness & planning
  5. Materials
  6. Crew assignment
  7. Execution
  8. Closeout

Employees as the integration layer

Repeated human reconciliation

  • Search
  • Re-enter
  • Check
  • Call
  • Recreate
  • Reconcile

Reconstructed for portfolio presentation based on original project research and surviving notes.

From a distance the process looked connected. Underneath it, people were manually maintaining many of the connections.

What this looked like in the work

  • Work identity

    The same work could appear differently across systems.

  • Portfolio visibility

    Employees used spreadsheets to see and manage multiple jobs.

  • Materials

    Physical inventory state and work-completion state could diverge.

  • Handoffs

    Employees sometimes had to verify that downstream systems actually received or reflected an action.

  • Exceptions

    Phone, email, and manual follow-up filled gaps where ownership or state was unclear.

Design implicationOne coherent work state — not necessarily one monolithic application.

04 /

Three proof points

The fragmentation appeared across many workflows, but three examples made the operating-model problem especially clear.

Proof point 01 — Supervisor capacity

Administrative reconciliation was pulling supervisors away from the field.

Field supervisors were expected to lead crews, monitor readiness, support safe execution, and respond to changing conditions.

Research showed significant attention being consumed by administrative coordination around the work. Not every administrative task was unnecessary.

Administrative coordination around the work

  • Finding information across systems
  • Preparing and enriching work
  • Maintaining operational spreadsheets
  • Resolving material issues
  • Correcting state and accounting problems
  • Checking downstream status
  • Handling exceptions

Work that needs supervisory judgment

  • Leading crews
  • Monitoring readiness
  • Supporting safe execution
  • Responding to changing conditions

Reconstructed for portfolio presentation based on original project research and surviving notes.

~56%

potential recovery of one field supervisor’s workday

MODELED — NOT REALIZED

Modeled future-state opportunity · not a realized post-launch result

PrincipleThe opportunity was not simply to make administration faster. It was to separate work that needs supervisory judgment from deterministic reconciliation that could be handled earlier, by another role, or by the system.

Explore Recovering Supervisor Field Time

Proof point 02 — Material ownership

What looked like a Stores problem was actually an ownership problem.

Operations could see physically completed work while a material request remained unresolved.

At first that could appear to mean Stores simply needed to close the request. Research with Stores changed the problem definition.

Stores knew

  • What was received
  • What was staged
  • What physically moved or was issued
The complete decision stateNot consistently held

Operations knew

  • Whether the job was complete
  • Whether remaining material was still needed

Reconstructed for portfolio presentation based on original project research and surviving notes.

Neither side consistently possessed the complete decision state.

PrincipleStores owns physical inventory truth. Operations owns job-completion and remaining-need truth. The service needs to connect them.

The design problem was ownership and shared state, not just the material-request screen.

Explore The Material-Request Black Hole

Proof point 03 — Operating model

The same enterprise needed more than one execution model.

The same enterprise ran planned work and emergent work, and the two did not follow the same logic.

Planned work

  • Engineering upstream
  • Dependencies prepared
  • Materials prepared
  • Crews scheduled
  • Predictable readiness sequence

Emergent work

  • Work can arrive immediately
  • Outages and storms change priorities
  • Crews can be reassigned
  • Material needs can change dynamically
  • Operational-control dependencies can affect execution

Held in common

  • Shared work identity
  • Governance

Reconstructed for portfolio presentation based on original project research and surviving notes.

PrincipleStandardize shared work identity and governance—not every execution path.

The research did not conclude that every operating company and every workflow should become identical. Some variation was legitimate because the work itself was different.

See the operating-mode capability

05 /

Design lesson — learn from the workarounds

The workarounds were telling us what the system was missing.

Employees relied on Excel, paper, email, phone calls, and local digital practices. Instead of treating them as legacy habits, I asked what capability each artifact was providing that the official workflow was not.

  • Excel

    Many jobs at once

    What users were preserving

    • Portfolio visibility
    • Flexible filtering
    • Priorities
    • Barriers
    • Operational coordination

    Insight

    Operational roles needed configurable multi-job visibility.

  • Paper

    One coherent job package

    What users were preserving

    • Persistent context
    • Annotations
    • Portability
    • Handoff
    • Access without repeated navigation or login
    • Resilience when digital access was poor

    Insight

    A future digital experience needed to preserve the successful function of the artifact, not simply remove paper.

  • Email + phone

    Exception ownership

    What users were preserving

    • Negotiating ownership
    • Resolving exceptions
    • Documenting commitments
    • Filling workflow-state gaps

    Insight

    Some communication problems were actually missing workflow state.

PrincipleDon’t digitize the artifact. Digitize the function the artifact successfully performs.

06 /

We translated the research into five future-state capabilities.

Exelon did not need one giant application or one identical workflow for every operating company. It needed a connected service where different roles could use experiences designed for their work while sharing trustworthy work identity, status, ownership, and controls.

That principle shaped the five capabilities.

Future-state operating model

One connected service. Different role-specific experiences.

RESEARCH-DERIVED FUTURE STATE — NOT IMPLEMENTED OUTCOME

Example role-specific experiences

  • Supervisor
  • Planner
  • Crew leader
  • Stores
  • Operations
  • Finance

Role bridge

02

Role-Based Coherent Work Views

Give each role the right view of the same work.

  • Job-centered packages
  • Portfolio views
  • Multi-key search
  • Task-based navigation

Connected service foundation

01

Shared Work Identity & Trustworthy State

Keep the same work connected as it moves across systems.

  • Event-to-work traceability
  • Status propagation
  • Duplicate detection
  • Reconciliation queues

03

Material & Work Reconciliation

Make material state and work state converge deliberately.

  • Physical vs. reserved inventory
  • Partial-request disposition
  • Cross-center transfer
  • Explicit ownership

04

Planned / Emergent Operating Variants

Share governance while allowing different execution rhythms.

  • Planned readiness
  • Rapid reprioritization
  • Different execution logic over shared governance

Field-fit frame

05

Field-Fit Digital Experience

Design the digital service for the environment where the work happens.

  • Persistent context
  • Mobile usability
  • Offline / queued behavior where needed
  • Clear asset identity
  • Visible save / publish / sync state

Illustrative

Tiering is a portfolio interpretation — not an architecture or screen design.

07 /

The future state was developed with the people doing the work.

I brought current-state maps and proposed future-state concepts back to stakeholders, facilitated workshops, captured corrections and constraints, compared alternative flows, and used discussion and prioritization to narrow the future-state direction.

This happened across approximately 12 cross-organizational workshops. Senior and leadership stakeholders took part in voting and prioritization, and the team used that discussion to decide which direction to carry forward.

From current state to future-state direction

  1. Current state
  2. Opportunities
  3. Stakeholder feedback
  4. Alternatives
  5. Prioritization
  6. Future-state direction

Reconstructed for portfolio presentation based on original workshop process and surviving notes.

08 /

The engagement created a shared view of the work—and a roadmap for changing it.

A separate team was responsible for building the future application. Because the project ended before that future state was implemented, the strongest outcomes were strategic, organizational, and design-delivery outcomes rather than post-launch performance metrics.

Strategic

  • Built a cross-company view of electric-distribution work
  • Distinguished shared needs from legitimate local variation
  • Identified internal better practices worth scaling
  • Created alignment around future-state directions

Design & delivery

  • Future-state workflows
  • Service-design recommendations
  • Prioritized opportunities
  • Roadmap input
  • Requirements for future application and vendor work

~56%

Potential recovery of one field supervisor’s workday

MODELED — NOT REALIZED

Not a post-launch result.

Based on interview-derived time allocations modeled against an eight-hour day. The application was not implemented during this engagement.

The engagement ended before implementation of the new future-state application.

09 /

Explore how the research changed the problem definition.

The main case study shows the system-level story. These deeper views expose the evidence, root causes, and design reasoning behind it.

Proof point 01 · Supervisor capacity

Recovering Supervisor Field Time

How could the future state reduce administrative reconciliation and return supervisory capacity to field leadership?

~56%modeled opportunity

Explore deep dive

Proof point 02 · Material ownership

The Material-Request Black Hole

What happens when physical inventory, job completion, and system state disagree—and no single role has the full decision context?

Explore deep dive

Additional findings included planned vs. emergent work, field-fit digital workflows, work-order lifecycle integrity, and cross-company standardization.

10 /

The project changed the question.

This engagement started with a technology-standardization problem. The research showed that the deeper challenge was the service around the technology: how work was identified, prepared, assigned, executed, reconciled, and governed across people, systems, organizations, and the physical grid.

From

“How should this software work?”

To

“How should the service work—and what should technology do inside it?”