Observation No. 06
The work is always ahead of the software.
The software was chosen a few years ago, to fit the business as it was then. Since then the business changed, the way businesses do: a new service, a different kind of client, a workaround someone invented on a Tuesday that quietly became the process. The software did not change with it. So now the work happens partly inside the software and partly around it, in the spreadsheet that patches what the software cannot do, in the text messages where the real decisions get made.
This is the normal condition, and nothing to be ashamed of. The work is always ahead of the software, because the work is alive and the software is a snapshot. The moment a tool is installed it begins to fall behind the thing it was meant to serve. The gap is where the workarounds grow, and the workarounds, over time, become the actual system, undocumented and lodged in a few people’s habits.
An assembly starts from the work itself, precisely because of this. It asks how the business actually operates now, workarounds included, and treats the software as one material among several, chosen to fit the current shape rather than to impose an old one.
The tell is the workaround. Every one is a place where the work moved and the software stayed. Follow them, and they will draw you a map of the assembly the business already needs.