.svg)
.svg)
Most organisations I spoke with didn’t have a notification problem.
They already had emails, reports, dashboards and reminders.
Yet overdue work continued to pile up.
As operational portfolios expanded across multiple buildings, contractors and internal teams, accountability became increasingly fragmented. Everyone could see the problem, but nobody was certain who should act next.
Work often remained unresolved because responsibility sat outside the workflow itself. Managers were forced to manually monitor reports, chase teams and intervene when service levels were already at risk.
The challenge wasn’t creating another alerting system.
It was making accountability visible, scalable and consistent across complex operational environments.
Early discovery revealed that escalation wasn’t simply an alerting problem.
The real issue was that ownership often existed outside the operational workflow.
I wanted escalation to become part of the day-to-day experience rather than something managers needed to monitor separately through reports and spreadsheets.
The solution needed to support both administrators configuring escalation policies and operational teams managing work on the ground.
Several design principles guided the approach:
- Reduce manual oversight
- Support different organisational structures
- Automate escalation processes
- Make ownership visible
- Prioritise overdue work
- Improve confidence in SLA compliance
Rather than introducing another layer of administration, the goal was to ensure accountability naturally followed the work itself.
Configuring Escalations At Asset Level
One of the earliest decisions was avoiding a single global escalation framework.
Different buildings, properties and operational environments often have different service expectations and accountability structures.
Associating escalation policies directly with assets allowed organisations to tailor service rules where they mattered most without introducing unnecessary complexity.
Supporting Multiple Escalation Levels
Operational accountability rarely sits with a single individual.
Allowing tasks to progress through multiple escalation levels ensured unresolved work continued moving through the organisation instead of becoming trapped within one team.
Enabling Inheritance And Reuse
Large portfolios create significant configuration overhead.
Allowing assets to inherit escalation policies from parent assets reduced administration effort while maintaining consistency across hundreds of locations.
Maintaining Visibility Within The Workflow
Escalation information remained visible directly inside operational workflows.
Ownership, urgency and escalation status were surfaced in context, helping teams understand responsibility without leaving the task they were working on.
The final solution introduced a configurable escalation framework that continuously monitored unresolved work and automatically routed accountability through the organisation.
Rather than relying on managers to manually track overdue tasks, escalation became a structured and predictable part of the workflow.
Administrators could:
- Define escalation levels
- Assign escalation owners
- Configure escalation timings
- Add notification recipients
- Apply rules across task groups
- Inherit rules from parent assets
Operational teams gained immediate visibility into active escalations directly within their existing workflows, helping them understand ownership, urgency and next actions without relying on separate reporting tools.
The objective wasn’t to generate more notifications.
It was to ensure every piece of work had a clear path forward.
The biggest success wasn’t the automation itself.
It was reducing the effort required to understand who owned a problem.
By making accountability visible and automating escalation processes, organisations could spend less time chasing work and more time resolving it.
The solution delivered:
- Greater operational accountability
- Improved SLA compliance
- Reduced risk of missed tasks
- Faster intervention on overdue work
- Lower administrative overhead
- Consistent escalation processes across large portfolios
This project reinforced something I’ve seen repeatedly throughout enterprise software.
Operational failures rarely happen because people don’t care.
They happen because complexity obscures ownership.
Good systems don’t just track work.
They make responsibility impossible to ignore.
LET’S MAKE CLARITY A HABIT.
Have a product, platform, or operational challenge in mind?
I help organisations simplify complexity, create scalable foundations, and build digital products that deliver lasting value.
