Writing on Systems.
4 pieces across the Systems cluster. Field notes, not thought leadership. back to all insights.
What this cluster covers
Operator software fails in predictable ways, and the dashboard is usually the last place it shows. These articles are about where it starts: a CRM the field team works around within ninety days, a dashboard full of numbers nobody traces back to source, an automation business case built on hours that were never being spent. What they share is that the system and the operation drift apart quietly. Nothing breaks. The reports keep arriving, the fields keep getting filled in, and the people doing the work keep a second version in their heads. By the time it surfaces in a number, it has been true for months. Written for anyone choosing or replacing internal tooling, and for anyone being handed a dashboard they are expected to trust.
The field team is the product — not the dashboard
Executives buy software for reporting. Field teams use it to close deals. When the two are in tension, the field team wins by default — they just stop using it. Design for them first.
Read →Why most operator CRMs fail within 90 days
A CRM the team avoids is worse than a spreadsheet. The pattern that kills adoption in energy, real estate and hospitality shops — and five decisions that fix it before rollout.
Read →Why most operator dashboards quietly lie to their CEOs
The numbers on the dashboard are never wrong — but the frame is. Three patterns that turn clean data into misleading narratives, and how to audit your own dashboard in under an hour.
Read →The automation ROI myth, and what actually pays back
Most automation projects save hours nobody was going to spend anyway. Three rules for picking the ones that actually move the P&L — and one test to apply before you buy another tool.
Read →