WM Blog
Daily columns from Clara, studio essays, and an archive of earlier work — operating models, delivery and the gap between strategy theatre and systems that hold.
Showing 10–18 of 141 · Page 2 of 16
The scanner at the gate flashes green on the second pass even though the trailer plate already sits in the system under a prior division code. The new record lands in a separate bucket because the batch prefix rule changed after the last vendor patch.
Read ↗
A tablet screen flickers black then returns with a blank ticket form while the technician waits at the gate. The voice notes captured seconds earlier never make the handoff to the repair queue.
Read ↗
Federated identity providers push session tokens across jurisdictions faster than residency clauses can be enforced. Delivery teams accept the resulting access paths because uptime metrics outweigh boundary violations in every release checklist.
Read ↗
You approved the SaaS licence after the vendor's sandbox delivered clean results on your sample files. That environment never contained the duplicate keys, legacy timestamps and partial records your actual feeds carry every day.
Read ↗
Override rates on model outputs track whether recommendations alter choices or simply sit beside unchanged behaviour. Boards receive coverage percentages that ignore the interventions that actually determine results.
Read ↗
You signed off on the PMO workflow that treats every contractor's handover bundle as final once the PDF checklist clears the gate. The result is assets entering operations with untested interlocks and missing control logic that only surface during first real load.
Read ↗
Exception routing rules that default every unmatched field to a shared inbox mean the finance team never sees the 14 percent of invoices the bot rejected for format drift. Vendors count a run as successful once the script finishes, regardless of whether the downstream system acce
Read ↗
Contract variation fees that escalate after month three turn every integration discovery into a budget fight instead of a design fix. Procurement teams learn to lock scope early and ignore what surfaces once data actually moves.
Read ↗
Your ops lead at a 160-person Melbourne software reseller watches the founder reject a senior solutions architect offer while signing off three new analytics platforms that duplicate existing dashboards.
Read ↗Navigate with ↑ ↓ · Enter to open · Esc to close
