Workflow Intelligence · Method
You can't fix a process until you know what "working correctly" looks like.
Theory of Operation is a troubleshooting method from industrial maintenance. Before a technician touches a machine, they know exactly what correct operation looks like. The gap between that and what's actually happening is the diagnosis. The same discipline works on a business workflow.
Direct answer
The seven steps, in order
Observe
Watch how the work actually happens: who does it, when, in which tools, and what they do when something goes wrong.
Document
Write down every step, handoff, and workaround, along with how often it happens and how long it takes.
Compare
Define the fewest steps, right tools, and reasonable time the workflow should take, then hold today's process against it.
Identify
Name each gap between the two. Where they match, say so and leave it alone.
Determine
Pick the fix that actually serves the business, not automatically the most technical one.
Implement
Build the fix with the team in the room, with approval steps wherever the work touches a customer or money.
Measure
Check the time saved and error rate against the baseline, honestly, and adjust.
Why it comes from maintenance
A machine doesn't lie about its symptoms. A process description sometimes does.
Ask someone to describe how a process works and you'll usually get the ideal version, not the version that runs when things get busy. A maintenance technician doesn't trust a description either; they watch the machine run. The same applies here: step one is observation, not an interview, because the gap between how a process is described and how it actually runs is usually where the real problem lives.
Where it fits
The method behind every recommendation we make
This isn't a framework we mention once and set aside. Every engagement, whether it ends in a Claude skill, an automation, or a recommendation to simplify a process by hand, starts with these seven steps. See the full method, including the five possible fixes step 5 chooses between.
Questions
FAQ
Do you skip steps for a small, simple process?
The depth changes, not the order. A simple process still gets watched before it gets fixed, even if that takes twenty minutes instead of a week.
What if the "compare" step shows the process is already right?
Then step four says so, and nothing gets built. Finding no gap is a legitimate outcome, not a wasted diagnosis.
Can we run this ourselves without hiring anyone?
Yes, and the steps above are enough to start. Where it helps to have an outside pair of eyes is usually the honesty of step one: watching what actually happens, not what you assume happens.
Next step
Let's watch how one of your workflows actually runs
A short call to start the same seven-step process on something specific in your business.