Structure Before Software
Part of a short series on how operational systems emerge and how they can be formalised. Introducing a simple discipline: understand structure before introducing software.
When operational systems struggle, the usual response is to look for better software.
But often the issue is not the software.
It is that the structure of the work has never been clearly defined.
What structure means
Operational structure describes:
- the entities involved
- the relationships between them
- the workflow states
- how work moves between those states
In many organisations this structure exists, but only implicitly.
What happens when software comes first
If software is introduced too early:
- workflows are forced to fit the system
- reporting becomes awkward
- workarounds appear outside the system
The organisation ends up maintaining two systems:
- the formal system
- the real operational process
The discipline
A more reliable approach is to define the structure first.
Once the structure is clear, the appropriate system becomes obvious.
Focusing on the importance of defining structure first. Next → Workflow State Is the Missing Layer