Controls
Multiplies trust — management doesn't have to verify every transaction manually.
Requires: evidence-based verification.
04 — AI & INTELLIGENT OPERATIONS
Technology rarely fails because of the technology.
Across every transformation I've led, the software, the platform, or the monitoring tool was rarely the constraint. The constraint was that nobody had redesigned the workflow around it, equipped the people who had to use it, or challenged the assumption that made the original limitation feel permanent.
A remote-monitoring platform sat mostly unused for years — not because it didn't work, but because nobody had removed the one dependency creating customer hesitation, or taught the sales team to have the conversation that would resolve it. My focus is understanding where value already exists inside an organization, why it isn't being realized, and only then deciding what role technology should play in unlocking it.
Technology should amplify a well-designed operating model, not compensate for a poorly designed one. Business strategy, objectives, operating model, governance, process, and data all come before the technology decision — not after it.
Every system should have one clear purpose: the ERP manages accounting; it should not be forced to run operations.
And the highest return on a technology investment rarely comes from buying more of it — it comes from enabling people and fully using what the organization already owns.
The Latent Value Model
A practical sequence answering one recurring question: where does value already exist that the organization is failing to realize, and what has to change before technology can unlock it? Technology enters deliberately late.
Look for capability the organization already owns — a monitoring platform, a licensed automation tool, historical data — before assuming something new is required.
Diagnose the actual blocker: a missing workflow, an unaddressed objection, a skills gap, or an assumption nobody has tested recently.
Ask whether the constraint is real or inherited. A rule that made sense once often has a much narrower actual cause than the story built around it.
Change how the work happens before changing what runs it. A workflow redesigned around the real constraint often removes the need for a bigger technology investment altogether.
Build the knowledge, materials, and conversations people need to trust and use the new workflow — sales teams who can explain encryption, service teams who know what a notification means.
Configure, connect, or introduce the technology that executes the redesigned workflow. This is the sixth step, not the first.
Re-measure after go-live, not just at go-live, and feed the result back into the next cycle.
Technology is step six. Not step one.
Each stage of my career added a new form of leverage without discarding the one before it. AI is the fourth — and a genuinely different one, because for the first time the constraint is not execution but thinking.
Multiplies trust — management doesn't have to verify every transaction manually.
Requires: evidence-based verification.
Multiplies consistency — hundreds of people execute the same way.
Requires: process design and standardization.
Multiplies execution — repetitive steps no longer require a person.
Requires: workflow-maturity assessment before automating.
Multiplies thinking — reasoning, communication, and decision support, not just execution.
Requires: capability architecture and knowledge design.
Three cases, each demonstrating a different mechanism: unlocking technology that already existed, redesigning an ecosystem instead of an application, and making adoption itself the business outcome.
A remote-monitoring platform sat underused for years. Removing one dependency and equipping the sales team turned it into the foundation of a proactive service model.
What started as a single-application rollout reaching 20% of the installed base became the redesign of an entire operating ecosystem spanning dealers, inventory, dispatch, and accounting.
An enterprise SaaS portfolio facing cancellation was retained not through relationship management alone, but by proving automation on the customer's own data.
My own use of AI moved through four phases: personal productivity, decision support, knowledge synthesis, and finally capability-building. Each phase increased the complexity of what AI was trusted to help build — not just what it was asked to produce.
The AI Lab is where that fourth phase becomes visible: small, working systems built to test whether the methodology on this page holds when a machine executes it. Projects are named, documented, and published as they are built — including the ones that don't work.
SEE THE AI LABAI & Intelligent Operations does not replace the first three capabilities — it scales them. Governance & Risk establishes how the organization creates, protects, and can lose value. Operational Excellence improves how value is created. Customer Success ensures customers realize it. This capability increases the speed, intelligence, and reach of all three. Which is why weak processes should never be automated simply because automation is available.
The highest return on a technology investment rarely comes from buying more of it.
LET'S JOIN FORCES