What we have learned running it.
Notes from operating the factory on live products — including the parts that went badly. Written for people responsible for software, not for search engines.
Why the board shows the numbers that make us look worse
A dashboard that only goes up is a marketing asset. We wanted an instrument, and instruments have to be able to read low.
Inheriting a system nobody understands any more
The most common software problem is not building something new. It is being responsible for something old, and the map being gone.
What one item of work actually costs to produce
Most suppliers cannot tell you. We can, because the price of the work and the proof of the work come out of the same record.
Every test was green. The product was broken.
Nine customer journeys, one of them completable, and a fully green test suite. What that taught us about the last check before release.
Start with one piece of work.
Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.
Talk to us