Tag: systems-accountability
-
Field Note 095: The Next Person at the Terminal
A welcome screen is not proof that a shared terminal has forgotten its last visitor. Mara follows a session across a handover, with an exercise for reviewing the boundary safely.
-
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.
-
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.
-
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.
-
Intel Report 089: Coverage Before Confidence
A current report can omit the places it cannot reach. Define the expected scope, distinguish missing from zero, and keep partial results visibly partial.
-
Field Note 091: The Missing Platform
The station board finally carries fresh information. Then Mara notices that the platform where people are waiting has disappeared from the count.
-
Intel Report 088: A Refresh Is Not Freshness
A responsive interface can display old evidence. Distinguish page rendering, update attempts, successful receipt and the time represented by the source data.