Notes from inside
other people’s operations.
What we learned building the systems in Work — written for the person who has to run the operation, not the person who has to buy the software. No frameworks, no maturity models. Specific failures and what they cost.
One essay for each thing we do.
The four practices on Services, each argued from a system we actually shipped.
The spreadsheet did not fail. It succeeded for too long.
How to tell when an operation has outgrown Excel, and what the first six weeks of replacing it actually look like.
ReadThe dashboard nobody opens
Most analytics projects fail before a single chart is drawn — in the definition of the number, not the visualisation of it.
ReadConfidence scoring, or why 95% accurate is a useless number
Document extraction in production is not an accuracy problem. It is a question of which fields a human still has to look at.
ReadThe integration that fails at 2am
Every system you connect to will send you the same message twice, or none at all. Idempotency, reconciliation, and what to build before you need them.
ReadThe same failure, wearing different clothes.
Every operation we have worked in loses money somewhere between two systems that do not talk. What changes by industry is which gap it falls through, and what the regulator does about it.
Where freight brokers lose money
A leak taxonomy from an operation that lost ₹85 lakhs in twelve months without anyone noticing. Six gaps, in the order they usually appear.
ReadCompliance you cannot bolt on
When a statute says a thing must not happen, a warning dialog is not a control. The difference between a system that is compliant and one that is auditable.
ReadMoney is an integer
Floats, rounding, and the reconciliation that finds out nine months later. How to build a ledger that a finance team will actually trust.
ReadTraceability before automation
A plant that cannot say which batch went to which customer cannot automate anything safely. Start with the record, not the robot.
ReadPublishing on a deadline, every day, forever
Editorial operations is a supply chain with opinions. What breaks first when a daily publication scales, and what to build for it.
ReadBefore you hire an MIS Executive, read this
That job posting is a specification for software you have decided not to build. Here is how to work out which of the two is cheaper.
ReadRecognise your operation in any of these?
Then the next step is not a proposal. It is a two-week operations leak audit — we map where money, time and proof go missing between your systems and come back with numbers. Applies against the build if you continue.