{"version":"1.0","type":"agent_native_article","locale":"en","slug":"automating-without-redesigning-most-expensive-way-preserve-past-mqtigt5n","title":"Automating Without Redesigning Is the Most Expensive Way to Preserve the Past","primary_category":"innovation","author":{"name":"Ignacio Silva","slug":"ignacio-silva"},"published_at":"2026-06-25T12:03:33.598Z","total_votes":89,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/automating-without-redesigning-most-expensive-way-preserve-past-mqtigt5n","agent":"https://sustainabl.net/agent-native/en/articulo/automating-without-redesigning-most-expensive-way-preserve-past-mqtigt5n"},"summary":{"one_line":"Organizations that automate broken processes don't accelerate transformation—they accelerate their distance from the point where they'll eventually have to start over.","core_question":"Why does automation so frequently fail to deliver operating impact, and what must organizations do before deploying automation to avoid encoding their own inefficiencies at scale?","main_thesis":"The gap between AI adoption rates and measurable operating impact is not a technology problem—it is an organizational design problem. Automation deployed on top of poorly designed processes amplifies existing defects at greater speed and volume, making them harder and more expensive to correct. The prerequisite for effective automation is process redesign, not better tooling."},"content_markdown":"## Automating Without Redesigning Is the Most Expensive Way to Preserve the Past\n\nThere is a sequence of decisions that repeats itself with surprising consistency across large companies with substantial digital transformation budgets: they identify a process that generates friction, they contract automation technology, they deploy the tool on top of the existing workflow, and they report progress. Executive dashboards show speed. Committee presentations talk about efficiency. And six months later, the same problems reappear, now packaged inside a system that is much harder to dismantle.\n\nThis is not an anecdotal phenomenon. McKinsey reports that 88% of organizations use artificial intelligence in at least one business function, but only 39% attribute impact to their operating margin. The difference between both groups does not lie in the vendor chosen or the budget allocated. It lies, almost invariably, in whether the organization redesigned its workflows before introducing automation or simply covered them with a layer of technology.\n\nThe magnitude of that gap deserves to be read carefully. We are not facing a problem of technological adoption. We are facing a problem of organizational design that technology is making visible at greater scale and at greater cost.\n\n## When Automation Turns Error Into Speed\n\nTraditional automation, based on defined rules and narrow flows, already had this fragility. If a process contained undocumented exceptions, steps that depended on the tacit judgment of certain employees, or incomplete data that someone corrected manually before the system ever saw it, automating that process produced inconsistent results. But volumes were limited and the damage was manageable.\n\nAgentic AI operates differently. It interprets objectives, generates recommendations, activates workflows, and makes decisions across multiple systems simultaneously. That makes it more powerful in well-designed contexts and significantly more damaging in poorly designed ones. An agent deployed on a process with ambiguous decision logic does not detect the ambiguity: it executes it with consistency and volume. What a senior analyst previously resolved with judgment, escalation, and institutional intuition now becomes an automated pattern of error that circulates through the system before anyone notices.\n\nThe documented case of a Fortune 500 insurance company illustrates the mechanism with precision. The company had documented operating procedures and a mature automation foundation. However, straight-through processing of cases had dropped sharply. The diagnosis revealed that automation had been deployed on top of workflows loaded with exceptions. The result was a fragile and costly system. The solution was not more technology: it was business experts who redesigned the flow, eliminated bottlenecks, and assigned clear responsibilities to specific leaders. After that, performance improved in a sustained manner.\n\nThe pattern revealed by that case is not technical. It is one of organizational design. Automation amplified the existing structure, defects included. What was missing was not a better AI model, but a process that actually deserved to be automated.\n\n## The Trap That Never Appears in Progress Reports\n\nThere is a dynamic that rarely makes it into executive progress reports on transformation projects: **organizations tend to confuse activity with foundation**. When automation is deployed, certain metrics improve immediately, at least superficially: processing speed, reduction of visible manual interventions, apparent cycle time. Those indicators feed quarterly presentations and reinforce the perception of progress.\n\nWhat does not appear in those reports is the cost of the undocumented work that disappeared with automation. Not the manual work that the system replaced, but the invisible work of correction, informal validation, and situational judgment that employees performed to compensate for the deficiencies of the process. When automation eliminates that human work without first having resolved the deficiencies that made it necessary, those deficiencies remain present in the system, only now without any cushioning.\n\nBCG names this error clearly: the frequent temptation is to automate what already exists. The value comes from starting from the desired outcome and reinventing how to deliver it. That distinction is not semantic. It has structural consequences. An organization that starts from the outcome must ask itself what flow of decisions, data, and responsibilities is needed to produce it in a sustained way. An organization that starts from the existing process is merely converting what was already happening into code, with its inefficiencies built in.\n\nThe cost of that difference scales. Dismantling poorly designed automation requires systems reengineering, model retraining, governance review, and in many cases, management of the damage the system produced during the time it operated. The expenditure is not only financial: it includes trust lost among the teams that depended on the process and among the customers who experienced it.\n\n## The Five Moves That Separate Correction From Escalating the Damage\n\nFor organizations that have already deployed automation on top of processes with weak foundations, pausing is not enough. Stopping the deployment limits incremental damage, but it does not correct the source. The five actions that mark the difference between real correction and a temporary patch all point to the same core: making the process visible before attempting to govern it with technology.\n\n**The first move is to identify the highest-risk workflows** and halt their expansion. Not all poorly designed processes carry the same damage profile. Those that combine high frequency, decisions that are difficult to reverse, and regulatory or financial exposure are where the cost of delay is greatest. Those require priority attention, not additional analysis.\n\n**The second move is to map the process that actually exists**, not the one that is documented. In most organizations, the documented process and the operated process diverge in ways that IT or automation teams cannot see from their positions. The exceptions, the workarounds, and the informal interventions that kept the flow running are not in the diagrams. They live in the daily practice of the people who execute them. Making them visible is not an audit exercise: it is a prerequisite for any redesign that is actually going to work.\n\n**The third move is to assign responsibility over the process, not over the tool.** When accountability is fragmented among the technology team, the operations team, and the business area, the process has no owner. It has partial custodians who each optimize their portion without taking responsibility for the total outcome. Agentic AI cuts horizontally across multiple functions, decisions, and data sets. Without a leader accountable for that end-to-end outcome, automation improves isolated tasks while the business indicator remains stagnant or deteriorates further.\n\n**The fourth move is to rebuild human validation at the points where error is costly.** This does not mean halting automation indefinitely or recovering manual steps that add no value. It means identifying the decision nodes where an incorrect output carries material consequences that are difficult to reverse, and maintaining active oversight at those points while the process stabilizes. The autonomy of agents must be earned progressively, not assumed from the outset.\n\n**The fifth move is to change the success metrics.** Cycle speed and reduction of manual interventions are indicators of activity, not of outcome. Organizations that achieve sustained corrections monitor decision quality, the cost of error recovery, the robustness of regulatory compliance, and the impact on the customer experience. Those indicators do not improve with more automation layered on top of weak processes. They improve when the underlying process is sound.\n\n## The Moment of Crisis Already Occurred Before AI Arrived\n\nThere is a reading of this problem that deserves not to be lost from view: when AI automation produces deficient results, the crisis that manifests in that moment was not created by the AI. It was created earlier, at the moment the organization chose not to invest in the design of its processes. AI only made visible, at greater scale and with greater urgency, a structural fragility that already existed.\n\nThat changes the nature of the diagnosis. We are not facing a problem of technological adoption that is resolved with more investment in tools, better change management, or more technical training. We are facing organizations that used the promise of automation to defer a design decision that at some point became uncomfortable or costly to make.\n\nThe case of the technology company with erroneous revenue projections is revealing in that sense. The projection workflows involved multiple handoffs of responsibility and asynchronous updates that produced incorrect forecasts. Those projections distorted hiring, planning, and margin decisions. The solution was not a more sophisticated forecasting model. It was a redesigned process with clear checkpoints and responsibility assigned to cross-functional leaders. Once the foundation was corrected, the automation that had amplified the problem began to close the gap.\n\nThe lesson is not that AI does not work. The lesson is that AI works exactly as well as the process surrounding it is designed to work. The organizations that scale with confidence are those that treat process clarity as a strategic asset before treating it as a destination for technology.\n\nAn organization that automates something it has already poorly designed is not accelerating its transformation. It is accelerating its distance from the point from which it will eventually have to start again.","article_map":{"title":"Automating Without Redesigning Is the Most Expensive Way to Preserve the Past","entities":[{"name":"McKinsey","type":"institution","role_in_article":"Source of the 88%/39% adoption-vs-impact statistic that anchors the article's central argument."},{"name":"BCG","type":"institution","role_in_article":"Source of the framing that the temptation is to automate what exists, with value coming from starting from the desired outcome."},{"name":"Fortune 500 insurance company","type":"company","role_in_article":"Documented case study illustrating how automation deployed on exception-laden workflows produces fragile, costly systems that require process redesign to fix."},{"name":"Agentic AI","type":"technology","role_in_article":"The specific automation paradigm that raises the stakes of poor process design by executing ambiguous logic consistently and at volume across multiple systems."},{"name":"Ignacio Silva","type":"person","role_in_article":"Author; frames the argument from organizational design rather than technology adoption perspective."}],"tradeoffs":["Speed of automation deployment vs. quality of process foundation: deploying fast on existing workflows shows quick metric improvements but encodes deficiencies that are expensive to correct later","Eliminating manual work vs. eliminating the informal correction buffer: automation removes both documented steps and the invisible judgment that compensated for process deficiencies","Agent autonomy vs. oversight at high-cost decision nodes: granting full autonomy from the outset vs. earning it progressively as the process stabilizes","Reporting activity metrics vs. outcome metrics: activity metrics improve superficially and feed executive presentations, while outcome metrics reveal whether the underlying process is sound","Deferring process design investment vs. paying the cost of reengineering after automation has amplified defects"],"key_claims":[{"claim":"88% of organizations use AI in at least one business function, but only 39% attribute impact to their operating margin (McKinsey).","confidence":"high","support_type":"reported_fact"},{"claim":"The differentiator between high-impact and low-impact AI adopters is whether workflows were redesigned before automation was introduced.","confidence":"medium","support_type":"inference"},{"claim":"Agentic AI executes ambiguous decision logic consistently and at volume, making poorly designed processes significantly more damaging than with traditional automation.","confidence":"high","support_type":"editorial_judgment"},{"claim":"A Fortune 500 insurance company saw straight-through processing drop sharply after deploying automation on exception-laden workflows; the fix was process redesign, not more technology.","confidence":"high","support_type":"reported_fact"},{"claim":"Dismantling poorly designed automation requires systems reengineering, model retraining, governance review, and management of damage produced during operation.","confidence":"high","support_type":"editorial_judgment"},{"claim":"Organizations confuse activity metrics (speed, reduced manual interventions) with outcome metrics, creating false signals of transformation progress.","confidence":"high","support_type":"editorial_judgment"},{"claim":"BCG identifies the frequent temptation as automating what already exists, with value coming from starting from the desired outcome instead.","confidence":"high","support_type":"reported_fact"},{"claim":"A technology company with erroneous revenue projections fixed the problem through process redesign with clear checkpoints, not a more sophisticated forecasting model.","confidence":"high","support_type":"reported_fact"}],"main_thesis":"The gap between AI adoption rates and measurable operating impact is not a technology problem—it is an organizational design problem. Automation deployed on top of poorly designed processes amplifies existing defects at greater speed and volume, making them harder and more expensive to correct. The prerequisite for effective automation is process redesign, not better tooling.","core_question":"Why does automation so frequently fail to deliver operating impact, and what must organizations do before deploying automation to avoid encoding their own inefficiencies at scale?","core_tensions":["Organizational pressure to show transformation progress (activity metrics) vs. the need to invest in process redesign before automation (outcome foundation)","The power of agentic AI in well-designed contexts vs. its destructiveness in poorly designed ones","The visibility of automation costs (vendor, deployment, training) vs. the invisibility of process design costs (deferred, diffuse, organizational)","Speed of deployment vs. reversibility of errors in automated decision flows","Assigning tool ownership vs. assigning process ownership across cross-functional workflows"],"open_questions":["How should organizations measure process design readiness before approving automation deployment budgets?","What governance structures effectively assign end-to-end ownership of agentic workflows that span multiple business functions?","At what point does the cost of correcting poorly designed automation exceed the cost of starting over with process redesign?","How can organizations make the invisible correction work performed by employees visible before it is eliminated by automation?","What criteria should determine when an agent has earned progressive autonomy at high-cost decision nodes?","Does the 39% impact attribution figure vary significantly by industry, company size, or type of AI application?"],"training_value":{"recommended_for":["Chief Operating Officers evaluating automation ROI","Digital transformation leads assessing why AI deployments are not moving operating margins","Business process owners preparing workflows for automation","CIOs and CTOs designing governance for agentic AI deployments","Strategy consultants advising on AI transformation programs","SME leaders considering automation investments with limited budgets for error recovery"],"when_this_article_is_useful":["When evaluating whether to automate an existing workflow or redesign it first","When diagnosing why an automation deployment is not producing expected operating impact","When building a business case for process redesign investment before AI deployment","When designing governance structures for agentic AI systems that span multiple functions","When selecting success metrics for digital transformation initiatives","When an organization needs to triage which poorly automated processes to address first"],"what_a_business_agent_can_learn":["How to distinguish between activity metrics and outcome metrics in transformation projects","The specific mechanism by which agentic AI amplifies process defects rather than correcting them","A five-step framework for correcting automation deployed on weak process foundations","Why informal human correction work is a leading indicator of process fragility that must be mapped before automation","How to frame process design as a strategic asset rather than a destination for technology","The difference between starting from existing processes vs. starting from desired outcomes when designing automation strategy","How accountability fragmentation across functions creates processes with no end-to-end owner"]},"argument_outline":[{"label":"1. The adoption-impact gap","point":"88% of organizations use AI in at least one function, but only 39% attribute impact to operating margin. The differentiator is whether workflows were redesigned before automation was introduced.","why_it_matters":"Establishes that the problem is systemic and structural, not anecdotal or vendor-specific."},{"label":"2. Agentic AI raises the stakes","point":"Unlike rule-based automation, agentic AI executes ambiguous decision logic consistently and at volume. Errors that a senior analyst previously caught with judgment now propagate automatically before anyone notices.","why_it_matters":"The risk profile of automating broken processes has increased qualitatively with agentic systems, not just quantitatively."},{"label":"3. The invisible work problem","point":"Automation eliminates not only documented manual steps but also the informal correction, validation, and judgment employees used to compensate for process deficiencies. When that buffer disappears, deficiencies surface unmitigated.","why_it_matters":"Progress metrics (speed, reduced manual interventions) improve superficially while the underlying structural fragility worsens—creating a false signal of success."},{"label":"4. Starting from outcome vs. starting from existing process","point":"BCG's framing: the temptation is to automate what already exists. Value comes from starting with the desired outcome and reinventing how to deliver it. Automating existing processes encodes inefficiencies into code.","why_it_matters":"This is the core design decision that separates organizations that scale with confidence from those that accumulate technical and organizational debt."},{"label":"5. Five corrective moves","point":"Halt high-risk workflow expansion; map the process that actually operates (not the documented one); assign end-to-end ownership; rebuild human validation at high-cost decision nodes; change success metrics from activity to outcome quality.","why_it_matters":"Provides an actionable framework for organizations that have already deployed automation on weak foundations."},{"label":"6. The crisis predates AI","point":"When AI automation produces deficient results, the crisis was created earlier—when the organization chose not to invest in process design. AI only makes the pre-existing fragility visible at greater scale.","why_it_matters":"Reframes the diagnosis: the solution is not more AI investment or better change management, but a deferred design decision that must now be made."}],"one_line_summary":"Organizations that automate broken processes don't accelerate transformation—they accelerate their distance from the point where they'll eventually have to start over.","related_articles":[{"reason":"Directly complementary: if 97% of companies have AI projects but only 5% have data ready, the data readiness gap mirrors the process design gap this article diagnoses—both point to infrastructure prerequisites being skipped in the rush to deploy AI.","article_id":14241},{"reason":"Explores the tension between autonomous AI agent promises and the need for human oversight, which maps directly to the article's argument that agent autonomy must be earned progressively, not assumed from the outset.","article_id":14001},{"reason":"Addresses the pattern of users double-checking AI outputs when trust erodes—a downstream symptom of the same problem: automation deployed without sufficient process or quality foundation.","article_id":14121}],"business_patterns":["Automating broken processes encodes inefficiencies into code and makes them harder to dismantle","Progress reports on transformation projects systematically omit the cost of invisible correction work that automation eliminates","Accountability fragmentation across technology, operations, and business teams leaves automated processes without an end-to-end owner","Organizations use the promise of automation to defer uncomfortable or costly process design decisions","Agentic AI amplifies whatever structure it is deployed on—defects included—at greater speed and volume than traditional automation","The documented process and the operated process diverge in ways that IT and automation teams cannot see from their positions"],"business_decisions":["Whether to automate an existing process or redesign it before automation","How to assign end-to-end ownership of automated workflows that cut across multiple functions","When to halt expansion of automation deployments that are producing inconsistent results","How to rebuild human validation checkpoints in agentic systems without eliminating automation value","Which success metrics to use for transformation projects (activity vs. outcome quality)","How to prioritize which poorly designed automated processes to address first based on damage profile"]}}