When Automation Disappoints: A Practical Review
Trace a failed journey, identify the missing decision or control, and choose a proportionate repair.

The practical answer
Investigate one actual failure using process, data, technology, adoption and ownership evidence. The Efficiency Stack helps organise questions; it does not explain every failure.
Put your workflow questions into a broader roadmap that reflects your business goals and the resources available. Explore Tech Clarity.
When an automation project disappoints, investigate the actual failure before buying another tool. Unclear process, inconsistent data, poor fit, weak adoption and unowned operations can each contribute. No single framework explains every failed project.
Review one failed journey #
Take a real example: a client submitted a form but nobody followed up. Trace the evidence from submission to assignment, notification and the intended response. Ask what happened, what should have happened and who owned each handoff. Avoid assigning blame before the sequence is understood.
Use the Efficiency Stack as a diagnostic aid #
The LD Efficiency Stack is a practical framework for examining foundation, standardisation, automation and visibility. Use the layers to organise questions; do not treat them as a certification or a rule that all work must happen in a rigid sequence.
| Layer | Observed symptom | Evidence to inspect | Possible next step |
|---|---|---|---|
| Foundation | Nobody agrees who owns an enquiry | Actual handoffs and responsibilities | Agree an owner and completion definition before changing the tool |
| Standardisation | Several statuses mean the same thing | Data values, staff instructions and exceptions | Choose clear states and migrate inconsistent records |
| Automation | A failed connection leaves work stranded | Run logs, retries and permission failures | Add monitored failure handling and a manual recovery route |
| Visibility | The owner only discovers delays after a complaint | Queue age, exception ownership and reporting freshness | Show actionable overdue work with a responsible person |
Example: a reminder that never solved the delay #
In this illustrative scenario, a team receives automatic approval reminders but jobs still wait. Investigation finds that the named approver cannot make the decision without a scope attachment, and nobody is responsible for supplying it. Sending more reminders increases noise. A better intervention is to require the attachment before requesting approval and assign missing-information tasks to an owner.
Test that change on a small sample. Measure time awaiting information separately from time awaiting a decision. If the delay continues, revise the explanation rather than declaring the framework proved.
Check adoption and operating responsibility #
Watch staff perform the task. A workflow can be technically correct and still require too many steps, hide important context or lack a sensible fallback. Identify who updates instructions, responds to failures and handles access changes after launch.
Choose repair, replacement or retirement #
Repair a small, understood gap when the underlying system remains suitable. Replace a component when it cannot meet an important requirement at a reasonable total cost. Retire an automation that creates more checking and maintenance than value. Include migration and transition effort in that decision.
Use the worked process-map tutorial to establish the journey and the ROI guide to compare the complete cost of the proposed fix.
A useful companion: Automation ROI Calculator.
Other articles worth reading

Why Map a Process Before Automating It?

How to Choose a Business Automation Consultant in New Zealand

