When a spreadsheet becomes an operational risk
How to tell when a useful spreadsheet has quietly become critical business infrastructure — and what to do next.
Read article →Insights
Short, useful guidance on deciding what to automate, when to integrate, when to build, and how to recognize operational problems before they become expensive.
How to tell when a useful spreadsheet has quietly become critical business infrastructure — and what to do next.
Read article →Why the missing piece in many businesses is the operating layer between software products, not another subscription.
Read article →A practical way to prioritize automation opportunities without starting with the flashiest technology.
Read article →A decision framework for choosing between process changes, off-the-shelf software, integration, and a custom build.
Read article →Manual re-entry looks inexpensive because it is distributed across the day. In aggregate, it can become a major source of waste and operational risk.
Read article →A practical comparison of buying software, integrating existing tools, and building a custom operational system.
Read article →Why maintenance, onboarding, training, documentation, and roadmap ownership matter after custom software goes live.
Read article →A practical way to divide a larger systems roadmap into useful releases that create value before the entire platform is finished.
Read article →Start with the problem
Languages, frameworks, databases, cloud platforms, and development tools I use to design and build business systems.