No visual differentiation
All data was presented as plain numbers with no color coding, status indicators, or alert signals. Engineers had to manually scan numerical values to identify anomalies — a process highly prone to misreads, especially under time pressure.
Manual formula dependency
To assess whether current dispatch loads were within safe operating ranges, engineers had to manually apply formulas outside the system. There was no built-in calculation or threshold visualization — meaning critical decisions depended on manual arithmetic.
Customized columns obscuring core data
Over time, engineers had added many personalized calculation columns to the report. While useful individually, the accumulation made it difficult to locate the most fundamental machine status information — the baseline data that every dispatch decision depends on.
There was no established communication path between engineers and the report development team. Interface pain points accumulated silently, with no mechanism for engineers to request improvements or flag usability issues.
