Start with the work itself
A company decides that customer follow-up is taking too long. The proposed solution is an automated sequence: a message after the enquiry, another after two days, and a final reminder after a week. Before building it, there is a more useful question to ask: what prevents a good follow-up today?
Perhaps no one owns the request. Perhaps availability has not been checked. Perhaps the salesperson is waiting for an approval that has no time limit. Automation can repeat the message while each of these conditions remains unresolved.
Five checks before an automation decision
Examine the operating logic in a deliberate order. The answer to each question should be specific enough for someone else to use.
- Outcome: define the result the workflow must produce.
- Necessity: identify the steps that contribute to that result.
- Ownership: name the person accountable for the complete outcome.
- Decision rights: make authority, thresholds and exceptions explicit.
- Information flow: identify the source, destination and required quality of each signal.
Classify the steps
A workflow often contains several different kinds of work. A duplicate entry may be eliminated. A necessary approval may be simplified. A handoff may need a standard. A predictable rule may be suitable for automation. Treating every step as a software requirement hides those distinctions.
Consider a hypothetical availability check. If the customer promise depends on current inventory, the check is necessary. The team should first agree which record is authoritative, who resolves a discrepancy and when the promise can be made. An automated check becomes useful once those conditions are clear.
Give the pilot a stop rule
Pilot one defined workflow with a named owner. Record the starting conditions, the exceptions and the result. Decide in advance what would cause the team to pause the automation, review its logic or revert to the previous procedure.
The useful output is a workflow that people understand and can govern. Faster execution is valuable when the work, the rule and the intended result deserve to move faster.
Before automating a step, be able to explain its purpose, owner, decision rule and required information.