Organizations & Technology
How software, data, automation, and AI change the way organizations operate.
Capability, not category
Software, data, automation, and AI are inputs, and they only become organizational capability once they’re placed inside a workflow with clear ownership, clear information, and a decision or outcome they improve.
Technology multiplies whatever the arrangement already does, and that’s the whole of its contribution, a large one, though it’s directional in a way that’s easy to forget. Give a well designed flow good tooling and it moves faster. Give the same tooling to a badly designed flow and it produces its errors faster, at higher volume, with better records of having produced them. A bigger engine only gets a car that’s pointed the wrong way lost sooner.
Organizations work against this all the time, and carelessness has little to do with it. The tool is the part of the system that can be requisitioned, with a vendor, a price, a timeline, and an owner. A change to who decides has none of those, can’t be put in a capital request, and has no milestone anyone can be held to. So when a problem meets a budget cycle, the problem gets reshaped into the one form the budget cycle accepts, which is a purchase.
Automation exposes design
Automation compresses a process. Squeezing it removes the slack that used to absorb ambiguity, and unclear ownership and undefined exceptions surface quickly, the way rocks appear when the tide goes out, which makes automation a surprisingly useful audit of the operating model.
The audit is worth taking seriously, and routing around what it finds wastes it. When an automated flow stalls on a case nobody can categorize, the automation has located a decision that was never actually defined, one that had been carried, silently and for years, by whichever person the work happened to reach.
The same compression removes things that were doing work nobody recorded. The person receiving a handoff was performing their assigned task and also glancing at whether the thing in front of them made sense, and only the first of those was in the job description. Automate the handoff and both go, and the loss turns up months later in a failure whose connection to the automation is several people and two quarters away.
AI belongs in the operating model
What a model can do in isolation is interesting and mostly beside the point. The useful question is which decision or unit of work becomes faster, more reliable, or less costly, and how the organization will measure that change.
Operations are full of the kind of work AI is unusually good at: reading unstructured input, drafting, classifying, summarizing, and answering questions that used to need someone who knew where to look. AI is also the least directional technology yet, because it’ll do whatever it’s pointed at with equal fluency. Point it at a broken intake process and it produces well written summaries of badly specified requests, quickly and at scale.
Fluency cuts both ways. A badly specified request used to look badly specified, and that rough appearance was doing quality control nobody had written down, the way a wobbly chair warns you before you put your full weight on it. Summarized well, the same request looks clear and travels further into the operation before anyone catches it.
Where an agent genuinely belongs, the questions left are operational ones: where in the flow it acts, what context it needs and whether that context exists anywhere it can be retrieved, what it’s permitted to decide, and what happens when it can’t decide, including whether the path it hands off to has an owner. Those four answers decide whether it becomes part of the operating system or just another component sitting beside it.
The test worth applying
Ask what changes in the operation if the deployment succeeds completely. If the answer comes back in the technology’s own terms (more automated, better integrated, more visibility), the technology has quietly become the objective and the operation has become incidental to it.
If the answer is that a specific wait disappears, a specific decision gets made with information it didn’t have before, or a specific category of rework stops occurring, the technology is a component and somebody has done the thinking. An answer of that kind also tells you when to stop building.
How software, data, automation, and AI change the way organizations operate.
If this describes an operation you’re responsible for, the diagnostic is where that conversation starts.
How engagements begin
