AI is not a content layer sitting beside the business. It becomes useful when it becomes an operating layer inside the business.
Most companies are using AI to make broken workflows look busy.
They generate better emails, cleaner notes, sharper summaries, and faster slide decks. None of that is useless. None of it is transformation either. If the operating model underneath is slow, fragmented, political, and dependent on memory, AI does not fix it. It accelerates the mess.
I have seen this movie before. In the 1990s, business process reengineering promised that if you redesigned work, performance would follow. The instinct was right. The workflow mattered more than the org chart. The handoff mattered more than the department. The bottleneck mattered more than the title. But the execution cycle was slow. A serious BPR effort often took 90 to 180 days: interviews, workshops, process maps, redesign sessions, training plans, compliance reviews, rollout decks. By the time the new process reached the business, the business had already changed.
That is why so many reengineering efforts felt heavy and stale. They treated the company like a machine you could stop, open up, rebuild, and start again. Real companies do not work like that. They keep moving. They route around the diagram. They invent side channels. They adapt in private, then surprise the official process later.
AI changes the economics of this completely.
For the first time, a company can watch work as it happens, reconstruct the real workflow from its digital exhaust, encode rules and policies closer to the point of action, and revise the operating model in weeks rather than quarters. The old BPR cycle that took 90 to 180 days can compress into 30.
But only if the company makes its work legible.
That is the dividing line. AI does not create clarity out of thin air. It needs written decisions, structured data, visible handoffs, named owners, accessible system context, and rules that exist somewhere other than a senior operator’s head. If status lives in meetings, if approvals live in DMs, if exceptions live in folklore, and if nobody can tell which system holds truth, AI has nothing durable to work with. It becomes a smart veneer on top of organizational fog.
This is where the old BPR questions come back into focus.
Where does work stall? Where do approvals pile up? Where are the same decisions made twice? Where does the org chart interrupt the flow of the customer outcome? Where are people doing coordination work that the system itself could carry?
Those questions have not changed. The method has.
Old BPR started with interviews and whiteboards. AI-enabled rewiring starts with workflow exhaust: tickets, product specs, support logs, meeting notes, policies, approval chains, API events, backlog movement, and internal documentation. Old BPR produced a future-state diagram once or twice a year. AI-enabled rewiring can keep updating the map as the company actually behaves. Old BPR asked people to comply with a redesigned process. AI-enabled rewiring can embed part of the redesign into the workflow itself.
That is the real shift: from process redesign as an event to workflow rewiring as an operating discipline.
I think this matters because most companies are still framing AI too narrowly. They treat it as a content tool, a productivity add-on, or a layer for answering questions after the real work is done. That misses the bigger opening. AI becomes far more valuable when it helps the company read and rewrite how work moves.
I have seen that more clearly in the work around AI at Blockdaemon. One of the useful lessons behind Konstant.cloud was that the interesting problem was never “can the model answer a question?” The harder and more valuable question was whether the company could expose enough structured context, system hooks, permissions, and policy boundaries for AI to act usefully without creating chaos. In other words: could the workflow itself become machine-readable enough for AI to participate in it?
That is a much more serious ambition than adding a chatbot to the side of the business.
It also leads to a practical 30-day model.
Days 1-5: map the actual workflow.
Not the official version. The real version. Pull from Jira, Slack, product docs, support escalations, approvals, incident notes, and customer handoffs. Let AI surface the hidden bottlenecks, duplicated decisions, missing owners, and recurring stalls. What matters in this phase is not elegance. It is fidelity. You want to know how the work really moves.
Days 6-10: define the constitutional layer.
This is where many companies lose the plot. They rush to agents before deciding what the agents are allowed to do. Every serious AI system inside a company needs a constitutional layer: who can approve what, which data can be touched, which actions need human sign-off, what must be logged, and where the boundary sits between suggestion and execution. If that layer is vague, the AI system becomes politically dangerous long before it becomes operationally useful.
Days 11-20: wire AI into the flow.
Now the company gets leverage. One AI layer drafts requirements from messy input. Another flags stale tickets or broken dependencies. Another translates raw discussion into a decision-ready brief. Another routes issues to the right owner. Another explains policy at the point where work happens. Another turns buried context into usable state. This is the phase where AI stops looking like a demo and starts behaving like infrastructure.
Days 21-30: tighten the loop.
Measure what changed. Look at cycle time, escalation volume, rework, exception rates, and time-to-decision. Keep what reduces friction. Remove what adds noise. Rewrite the routing, prompts, policies, and thresholds. Then repeat the cycle. That repetition is the point. A rewired company is not redesigned once. It learns how to keep redesigning itself.
This, to me, is the real successor to business process reengineering.
The first BPR wave got captured by the worst instinct in management. It became associated less with redesigning work and more with cutting people. “Chainsaw Al” became the symbol: use process language to justify headcount removal, declare victory, and call it modernization. Some companies got leaner on paper. Many got weaker in reality. They reduced cost without building a better operating system.
AI now faces the same trap.
Use AI mainly as a labor-reduction story and people will hide work, protect turf, and move decisions into darker corners of the organization. The result will be faster fear, not better execution. Use AI to make the company clearer, faster, and easier to run, and the result is very different. You get better visibility. Better handoffs. Better written decisions. Better exception handling. Better memory. Better management.
That is why I think the opening question matters so much. Not “which jobs can AI replace?” but “which workflows are too slow, too manual, too fragmented, too opaque, or too dependent on memory?” One question produces a stronger company. The other produces a brittle one with better software.
This also has to come from the top. Workflow rewiring is not a side project. It needs an explicit operating priority, a decision about which systems hold truth, a writing discipline, named ownership, permission boundaries, and real trade-offs on roadmap and resourcing. If AI work lives as a part-time hobby scattered across well-meaning teams, the company gets prototypes and politics, not transformation.
That is why “AI transformation” is often too vague to be useful.
The more precise phrase is AI-enabled business process rewiring.
Same core instinct as BPR. Better instrumentation. Faster cycle times. Higher-resolution visibility. Tighter feedback loops. More room for human judgment where judgment matters, and less tolerance for chaos where chaos used to hide.
The companies that win this next phase will not be the ones with the most AI pilots. They will be the ones that can take one important workflow, make it legible, connect it to policy and machine-readable state, improve it inside 30 days, and then do it again the month after that.
AI will not save companies that cannot explain how work moves.
It will expose them.
And the winners will not be the companies with the best prompts. They will be the ones that can turn management itself into a rewiring discipline.
