Start with a question staff actually ask
A record lands on the wrong work list. The obvious place to investigate is the list itself, but the cause may sit upstream in a rule, a field update or an inherited territory decision. A useful audit begins with that visible problem and follows the decisions behind it.
In The Hidden Operating System, David brings five conference sessions into a cross-session interpretation of Slate stewardship. His connecting argument is that rules, workflows, assignment lists, permissions and legacy decisions function together as an institutional operating system. The Hidden Automation Audit turns that interpretation into a manageable piece of work.
Choose one process that matters: inquiry assignment, application review or event follow-up. Write the question the team cannot currently answer. Keep the scope small enough to trace what happened, who encountered the result and what should have happened instead.
In the recording · 15:38 ↗Recover the reason before judging the object
An old rule may encode a perfectly reasonable decision. A temporary fix may also have survived several cycles without anyone revisiting its assumptions. Age does not distinguish those cases. Recover the purpose, trigger, affected population and downstream effects before choosing a future for it.
A useful inventory explains the operational decision in ordinary language. Record who owns that decision, who understands the configuration, when it was reviewed and what could break if it stopped running. If the original reason remains unknown, mark that gap rather than supplying a plausible story.
The legacy decision log provides a place for the recovered context. Some objects will need rebuilding or retirement; others will need a clearer name, an owner and a review date. The first deliverable is an explanation the team can inspect.
In the recording · 05:19 ↗Check the work the system puts in front of people
Assignment lists influence where staff spend their attention. For each list, explain how records enter and exit, how often it refreshes and which action staff should take. A list based on territory needs an owner for territory logic. A list based on priority needs a shared definition of priority.
Cadences carry those decisions into a sequence of actions. Review whether the timing matches the follow-up the team actually wants. A technically functioning cadence can still repeat work that is no longer useful.
Workflow review needs the same attention to lived practice. Ask staff what waiting, done and stuck mean today, including the steps they bypass. Bring the builder and process owner together before planning modernization. Their descriptions of the configuration and the intended process should agree.
In the recording · 07:45 ↗Make access part of the process review
Permissions determine who can see the work, act on it and change its configuration. Permission drift develops when people retain earlier access after a role change or a temporary exception becomes routine. The audit should identify those cases for the responsible access owner.
Document the work a role needs to perform and the access that supports it. Record exceptions with a reason, scope, owner and review date. Review role changes, departures, export capabilities and sensitive access as part of normal operations.
A missing view is not, by itself, a reason to broaden permissions. First establish whether the person should perform the task and whether the population, workflow and access design match that responsibility.
In the recording · 12:12 ↗Build an operating brief someone can use
Trace the chain: a rule changes a field, the field affects a list, the list creates a staff expectation, a workflow responds and a report counts the outcome. The map should show dependencies across object types rather than stopping at an inventory of names.
Then write a short operating brief. Capture the object, trigger, population, business owner, technical contact, dependencies, risk, test approach and last review. The companion workbook adds change approval, notifications and expected versus failure results, making the brief useful when a proposed change is considered.
Give consequential objects more attention. Incorrect routing, missed work, exposed data and distorted reporting warrant stronger ownership and a regular review. A low-impact object may need basic documentation and review when its process changes. Set the cadence according to the consequence, not the length of the inventory.
In the recording · 17:30 ↗Choose the next step without creating a new blind spot
Retirement belongs in the plan, but identifying an apparently redundant object does not establish that it is safe to remove. The reviewed chapter asks what uses it, which historical records need preserving, who needs notice and what evidence would confirm a safe retirement. A replacement may need to exist first.
Finish with one proposed action, an owner and a review date. Before an approved change, agree on dependency checks, test results and how the team would recover if the outcome differs from expectations. Keeping a working object with better documentation is a valid result. The goal is to leave the next person a decision they can understand.
In the recording · 21:38 ↗