The role conflict
The operating model expected supervisors in the field. The service kept pulling them back to the desk.
That reframed what efficiency meant here. The value was not finishing the same paperwork faster. It was protecting time for the work supervisors were already expected to do: field leadership, safety oversight, and readiness decisions.
A field supervisor described being expected to work the street while still tied down by desk work, and said the time returned would go toward keeping crews working safely.
One workaround at the center
The proposed design did not optimize the workaround. It eliminated the need for it.
Field-created work could arrive with a default, placeholder project code. Correcting that project coding by hand, the dummy-code workflow, was described as a daily task: Finance shared cleanup information, and supervisors replaced each placeholder with the correct project and accounting destination.
Participants argued that the type of work and the asset involved often provided enough information to derive or validate that destination. The manual step was reconstruction, not judgment. The proposed future-state design eliminated the need for dummy codes. Known cases derive or validate the correct destination, and cases the system could not resolve were routed as explicit exceptions rather than carried under a placeholder.
- The workaroundPlaceholder project codes on field-created work were corrected by hand.
- Design factThe proposed future-state design eliminated the need for dummy codes.
- Modeled outcomeRemoving that workflow represented modeled potential supervisor-day recovery, not a measured result.
Illustrative. A simplified link between the design and the modeled outcome, not a measurement.
~56%
Modeled potential supervisor-day recovery
MODELED — NOT REALIZED
The dummy-code workflow accounted for roughly 56% of the modeled supervisor day. The proposed future-state design eliminated the need for that workaround.
Based on interview-derived time allocations modeled against an eight-hour day. The application was not implemented during this engagement; this is not a post-launch result.
The burden ran wider
The same reconstruction pattern showed up across the workflow, not in one place.
The supervisor was often functioning as a human work-preparation engine: knowing where to look, which state to trust, and which workaround to use. Nine kinds of administrative burden recurred.
Evidence-supported categories from across the research. Not sized or weighted.
Observed burden categories — not a causal breakdown of the ~56% modeled figure.
A participant described looking across three separate platforms just to assemble the information needed for a single job.
Who should own the work
Not every repeated check was waste. The design question was who is best placed to own each piece of work.
A planner, a supervisor, and a crew leader could each review the same work, and research showed extra supervisor involvement could be explicitly valued for safety. So the goal was not to delete repeated steps. It was to separate independent checks that create safety and readiness value from repetition that existed only because earlier information could not be trusted or carried forward.
Responsibility and decision model
Question 1 of 3
Does this require supervisory judgment?
Yes
Keep with supervisor
Judgment and safety-relevant checks stay with the supervisor.
- Deciding whether work is executable
- Assessing crew readiness and fit
- Responding to changing field conditions and reprioritizing emergent work
- Independent safety checks where safety or governance requires them
If no, continue to question 2
Question 2 of 3
Can rules resolve it deterministically?
Yes
System logic
Repetitive, rule-based work moves out of the supervisor's day.
- Prefill known event, asset, and location data
- Derive or validate the correct work/accounting destination from known work attributes — no placeholder required
- Maintain one authoritative priority value
- Save progress across pages and show publish and sync state
If no, continue to question 3
Question 3 of 3
Does another role hold the authoritative information?
Yes
Route to that role
The role that knows the answer makes the decision.
- Stores for physical inventory decisions
- Finance for accounting exceptions
- Back Office for completion controls
If no, continue to the last outcome
Otherwise
No to all three
Explicit exception
Rules cannot resolve it and no other role clearly holds the answer. Route it to the person with the knowledge and authority to decide.
Illustrative. Synthesized from research findings; not an original project artifact.
Research-derived future-state model — not an implemented workflow.
PrinciplePreserve independent judgment. Remove repeated reconstruction.
Prepare for Crew
Design around getting work ready for a crew, not around individual systems.
The research supported a guided readiness experience that brings together what a supervisor needs to move work from enterprise record to executable field job. The normal path stays easy, the exception path stays visible, and the supervisor stays in the decisions that require a supervisor.
Prepare for Crew requirement groups
- Work identity
- Job
- Asset
- Location
- Circuit
- Readiness
- Priority
- Barriers
- Material
- Crew fit
- Schedule
- Dependencies
- Control state
- Network and outage permission
- Required approvals
- Unresolved exceptions
- Field handoff
- Publish status
- Field availability
- Assignment
- Crew package
- Exception management
- Coding
- Materials
- Duplicate work
- Failed sync
- Blocked permission
- State mismatch
Illustrative. Research-derived requirement groups, not a screen design.
RESEARCH-DERIVED FUTURE STATE — NOT IMPLEMENTED OUTCOME
A clue already in the field
A shared huddle board gave supervisors crew assignments, day-of changes, barriers, and completion notes in one place, so they could get into the field instead of spending the afternoon creating work or attending meetings.
Functions the future state should absorb
- Portfolio visibility
- Shared day-of coordination
- Barrier visibility
- Assignment context
- Rapid reprioritization
PrincipleDo not digitize the artifact. Digitize the function it performs.
The intended outcome is more capacity for higher-value work
These are design intent, not measured, post-launch results. The engagement ended before implementation.
Intended future-state outcomes
- More field leadership
- Greater safety-oversight capacity
- Faster crew readiness
- Lower administrative and cognitive load
- Fewer avoidable office handoffs
- Fewer correction cycles
- Clearer exception ownership
Efficiency matters more when you know what the time is for
Participants connected administrative burden directly to the time available for field leadership and safety oversight. Reducing steps is not automatically valuable. The question is what those steps are displacing, and whether the step should exist at all.
The goal was not to make supervisors process work faster. It was to let them spend more of their time supervising.