Tag: information-quality
-
Operator Brief: Test a Moving Estimate
Use a fictional sequence of forecasts, an interruption and a confirmed assignment to test whether the interface tells readers what has actually changed.
-
Intel Report 092: An Estimate Is Not a Commitment
An estimate, an assignment and a service commitment are different claims. Keep their meanings intact as information moves from internal fields to public displays.
-
Field Note 094: The Promise in the Estimate
The station finally acknowledges the unfinished queue. Then a countdown promises a departure that no desk has actually confirmed.
-
Operator Brief: Test an Unfinished Wait
Keep four short completed requests and one long open request in a synthetic report. Check whether the dashboard describes both without inventing a completion.
-
Intel Report 091: Completed Is Not Everyone
A completed-case average can remain low while open cases grow older. Define the measured population and give unresolved work its own visible account.
-
Field Note 093: The Wait Outside the Average
The station reports a three-minute service time. A traveler who arrived before the morning shift is still waiting to enter the statistic.
-
Operator Brief: Test a Counting-Rule Change
Use a fixed synthetic queue to test whether a report confuses fewer tickets with fewer people after a definition change.
-
Intel Report 090: Definition Before Comparison
A trend can change because its counting rule changed. Record the unit, scope and method before treating two numbers as evidence of improvement.
-
Field Note 092: The Number That Changed Its Name
Every platform is reporting again, but the station announces a shorter queue without moving anyone. Mara finds a new counting rule beneath an old heading.
-
Operator Brief: Test a Partial Report
Build a fictional three-desk report to distinguish zero, missing and stale contributions, then check how recovery changes the total without double counting.