Writing for decisions, not algorithms.
Short essays on patterns I keep seeing across process, operating model, CRM, data, automation and AI: the assumptions I disagree with, and what follows from them. Perspectives, not universal laws.
01Essays06 perspectives
- Perspective / 01CRM adoption is usually an operating-model problemWhen people avoid a CRM, the cause usually sits in the operating model around it: who benefits from the data, which routines run on it, and what managers keep asking for.CRM · Operating Model · 5 min
- Perspective / 02AI agents cannot fix fragmented commercial dataAgency turns ambiguity into action. An agent working on unresolved identity and authority does not clean the data; it repeats the confusion faster and further.AI · Data · 4 min
- Perspective / 03The hidden cost of unclear system ownershipDuplicate data is the cost people see. The larger cost is the reconciliation, the shadow copies and the decisions nobody can make with confidence.Governance · Integration · 4 min
- Perspective / 04Automation makes a broken sales process worseAutomation removes time and friction. In a sales process that was never fully designed, some of that friction is where unresolved judgement lives.Automation · RevOps · 4 min
- Perspective / 05An approval step is not a decision modelAdding an approval is easy. Defining the decision behind it, its owner, its evidence and what “no” means is the actual design work.Process · Governance · 4 min
- Perspective / 06Better adoption, more architecture: the trade-off behind reliable dataReducing what users must capture can improve adoption and even data quality, but the complexity does not disappear. It moves into the architecture needed to retrieve, derive, validate and govern the information elsewhere.Adoption · Data · 6 min