An Operational View on Top of the System the Floor Already Trusts

An established Nordic industrial manufacturer was running operations on a system everyone trusted but nobody actually liked. The scheduling view did not show resource load the way the floor needed to read it. Manual workarounds were proliferating in spreadsheets. The risk was the obvious one: build a parallel tool that fragments the source of truth.

• Built a new load-view UI on top of the existing system's data, not as a replacement under it.

• Two-way sync so the system of record stays authoritative; the new view is a read-and-act surface, not a second database.

• Weekly iteration driven by the operations team itself, not by a remote design process.

• Mobile read-only for floor checks; desktop for scheduling authority. Different roles, different surfaces.

The operations team gets a view that reads the schedule the way they actually use it. The system of record remains the source of truth. Decisions made in the morning meeting reflect in the underlying system without manual reconciliation. The pattern (a view on top, not a replacement under) is reusable across the rest of the operations stack.