We do not believe in greenfield.
A short note on why every Anillion engagement begins with a sober, written reading of the environment that is already there — and ends with a refusal to pretend it is not.
The premise
Every engineering firm has a posture. Ours is that the existing environment is the starting point, not the obstacle.
We do not believe in greenfield, because there is no such thing in a real enterprise. Even the most aggressive transformation programs we have seen — the ones with executive air cover and three-letter consulting firms on retainer — end up running on top of, alongside, or quietly through systems that pre-date the program by a decade.
What we do instead
Every Anillion engagement begins with a sober, written reading of the environment that is already there. We call it the inventory. It includes:
- +The systems of record, named and dated, with operational owners.
- +The systems of action, named and dated, with operational owners.
- +The interfaces between them, including the unofficial ones.
- +The reconciliation steps. Including the ones a human still does on Wednesday mornings.
- +The known failure modes. Especially the ones that have not failed in three years.
We share this document with the client before any code is written. It is rarely flattering. It is always useful.
What that buys us
It buys us a shared map. It buys us alignment on what is load-bearing. It buys us the right to say no to scope that does not respect the inventory.
It also buys us speed. Nine of ten platform deployments that fail do so because the team built around the system they wished they had, not the system that is actually running. The inventory makes the actual system unignorable.
We do not believe in greenfield. We believe in the seam, the receipt, and the inventory. They are usually enough.
N° 006.X— Continue reading
Send the next memo to my inbox.
One memo a month, no roundups, no marketing. Unsubscribe in one click.