If the job comes out different depending on who does it, fix the process first; software will only copy the mess. If everyone does it the same way and it is still slow, it is a tool problem.
Work it out in a minute
Six questions on one task, scored on volume, rules, stability and judgment. Returns a straight verdict.
What you get
The test
Give the same job to three people who all do it, separately, and compare what comes back. Different shapes means the process is not settled. Same shapes and still slow means the tool is the problem.
Why the order matters
Software makes a process faster and permanent in the same move. Run it against a process three people disagree about and the disagreement is now in the system, with a login and a renewal date.
What a process fix looks like
One written sequence, one owner, one place the work lives. It has no launch date and no invoice, which is exactly why it keeps losing to a purchase.
When buying first is right
When the sequence is already the same every time and the cost is waiting, carrying or retyping. That is a tool problem and no amount of documentation touches it.
The expensive middle
Buying software to impose a process on people who never agreed it. The tool gets blamed, gets replaced, and the second one fails in the same place.
What nobody prices
The month a new tool takes to become the place work happens. It is real whichever way you go and it belongs in the decision.
How to decide, in order
Somebody proposes software when the work is slow. The proposal is usually right about the symptom and silent about the cause, because both a broken process and a missing tool look identical from outside. Work takes too long and nobody can say exactly where it went.
The test takes an afternoon. Give the same job to three people who all do it, separately, and compare what comes back. If the outputs differ in shape, order or completeness, the process is not settled, and there is nothing yet for software to encode except the disagreement.
If the three match and the work is still slow, find where the time goes. It will be waiting for somebody, carrying a record from one place to another, or typing something that already exists somewhere else. Those are tool problems and documentation does not touch them.
The order is not a preference. A tool makes the current way of working faster and harder to change at once. Buy against an unsettled process and the company now defends a workflow nobody chose, because changing it means changing the tool.
A process fix is unglamorous. One written sequence, one owner, one place the work lives. It has no launch and no invoice, which is why it loses to a purchase in most rooms, and why the same company buys a second tool eighteen months later.
And where it is a tool problem, buy quickly. A settled sequence with the time going into carrying and waiting is exactly the case software was built for. Delaying that to write more documentation wastes the one answer that was going to work.
Whatever you buy, contract negotiation decides the terms.
Questions we get
What if it is both?
It usually is, and the split is rarely even. Run the three person test and one side will dominate.
Settle the part people disagree about, then buy against the settled version. The requirements list comes out shorter and far more accurate.
Can we buy now and fix it later?
You can, and the fix gets harder. Once a tool is in place the process becomes whatever the tool allows, so changing it later means changing the tool.
That is how a company ends up defending a workflow nobody chose.
How do we know the process is settled?
Three people produce the same thing in the same order without checking with each other first. That is the bar, and it is lower than it sounds.
If they have to ask you, it is not settled yet.
Does writing it down count as fixing it?
Only if somebody follows it. A written sequence nobody reads is a record of a decision rather than a working process.
Document it or automate it splits that question further.
What about buying something small to try?
Good instinct, with one condition: pick a tool you can leave. A trial that quietly becomes the place the work lives is not a trial.
Decide in advance what would make you stop.
How long does a process fix take?
Days rather than quarters, for one sequence. The long part is agreement, not writing.
If it is taking months, the disagreement is about something larger than the process.
More in the guides and every answer in one place.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built