How it shows up
A request starts in email. The checklist is a spreadsheet. The latest file is in someone's downloads. The next action is in a chat that two people saw.
Why it happens
The tools were adopted one at a time. None of them was designed to own the whole path from request to done. People filled the gaps because they are conscientious. The process now depends on them.
If nothing changes
People chase the latest version and the next owner. That chasing is the cost.
Money
Duplicate work, missed extras, and rework that nobody priced.
Time
Every file waits on someone to notice it, find the latest version, and push it forward.
People
A few employees become the memory of the company. Their vacation is an operational risk.
Process
There is no single owner of status. Ownership is reconstructed in meetings.
Customers
They wait, then they call. Each call creates more administrative work.
Risk
Decisions are made on stale information because the live picture is scattered.
Growth
Volume does not add capacity. It adds follow-up.
Questions worth asking
Who has to intervene when a file stalls?
What waits while that person hunts for the latest version?
How many tools does one request pass through before it is done?
What happens if the person who 'just knows' is away for two weeks?
Does this get worse as volume grows?
When it is working
A request enters once. It has an owner. Missing information is visible. Next action does not depend on someone remembering to send a reminder. Managers look at exceptions.
What we might actually do
Workflow software
A path with states, owners and required information.
Operational application
A system designed around this process.
Integration
If a competent system already holds part of the work, connect it. Do not re-type it.
Automation
Useful after the path is stable. Automating a scattered process just scatters faster.
When software is the wrong first move
- The process changes every week and no one owns it.
- People will not use a shared system, and that will not be addressed.
- A mature product already covers the path and is simply not adopted.
Where we see it
Roles this hits
Related problems
Selected work
Comparable files are walked through in a working session. We do not invent percentages for the website.
Describe the process as it runs. A specification is optional.