If it’s not designed, built, and actively managed, it is being held together by effort, context, or chance.
This system pattern shows how work gets delivered depending on what is built into the system and what is actively monitored.
Four common ways work gets delivered:
- By design
- On demand (effort)
- In context (variation)
- By chance
When delivery is not by design:
- people step in to get important work done, often at the expense of other priorities
- delivery varies depending on team, leadership, and pressure
- outcomes are inconsistent and difficult to assess
- hidden effort creates cost and fragility
Over time, this becomes normalised.
Why this is hard to shift
Over time, patterns become embedded and shape how work actually gets done.
People build their identity around the role they play and are often rewarded for the extra effort.
Important work has been pushed ‘down the road’ so many times, that it becomes default practice.
No one is explicitly accountable for the things being left to chance.
Effort, workarounds, and gaps in accountability become part of how the system sustains itself.
What helps shift the pattern
Reliable delivery requires deliberate design and reinforcement:
- building work into operating models, processes, and workflows
- clearly defining ownership and accountability
- actively monitoring and managing delivery
- aligning resources and priorities to what matters most
Both systemisation and monitoring are required.
As these strengthen, delivery becomes consistent, even under pressure.
Questions to reflect on
- Where are we over-relying on effort to get important work done?
- Where does delivery vary depending on team or context?
- What are we leaving to chance?
- What needs to be built in and actively managed?