Automating a close you have not simplified buys you the same close, faster, and makes it permanent.
This field guide sets the sequence: count the manual touches, delete steps before standardizing, standardize toward the more rigorous version, automate only the high-volume rule-based steps, and measure time-to-answer rather than days-to-close. Skip the sequence and you buy an expensive, fast, permanent version of the process you had.
What this guide is for
You want a shorter close. This guide is about the order of operations, and about the specific ways skipping a step makes the problem permanent rather than solved.
The failure it addresses
The sequence is simplify, standardize, automate, measure. It only works forwards.
Automation applied to a process nobody simplified encodes every workaround into a system, and a workaround in a spreadsheet can be argued with while a workaround in a platform has an owner, a budget line and a support contract. Standardization skipped means you have automated one entity’s way of doing something and created an exception for every other entity. And measurement placed first produces a scoreboard for a process nobody has fixed, which reliably makes people faster at the wrong thing.
The order is not a preference. Each step is only possible because the one before it ran.
The use cases you can run
Count the touches
Before anything else, map one close end to end and count every human handoff, every manual journal, every reconciliation done outside the system, and every file that moves by email. Do not design anything yet.
Delete before you standardize
For each touch, ask what would break if it stopped. A surprising share exists because it once mattered, because one person once asked for it, or because nobody has questioned it since an ERP migration.
Standardize on the harder version
Where two entities do something differently, converge them before automating, and converge toward the more rigorous of the two rather than the more common. Converging downward is faster and buys a system that cannot support the entity with the real requirement.
Automate the boring middle
Automate the steps that are high volume, rule-based and low judgment. Leave judgment where a person can be accountable for it. A close is not slow because judgment is slow. It is slow because judgment is waiting behind data movement.
Measure the right thing last
Not days to close on its own. Measure how long after period end a specific question can be answered reliably, because that is what the rest of the business experiences.
What good looks like
The process was smaller before it was automated. One version exists across entities and it is the rigorous one. Judgment steps still have people attached. And the measure is answer-time, not close-days.
What it costs to skip it
An expensive, fast, permanent version of the process you had. Automation makes a process durable, which is exactly why it should be the third step and never the first.
Where this connects
This sequence is the spine of one of the case files, Simplify, Standardize, Automate, Measure. Where it sits among the pathways is Transform. The patient-side view of the same ten exits is at Where did your treatment stop?
Former employers and products referenced are matters of professional history. The views expressed are my own and are not made on behalf of any current or former employer, and no commercial outcome for any named product is attributed to me personally. All trademarks belong to their respective owners.