[{"data":1,"prerenderedAt":5622},["ShallowReactive",2],{"article_list_cperez_":3},[4,1156,1826,2788,4746,5355],{"_path":5,"_dir":6,"_draft":7,"_partial":7,"_locale":8,"title":9,"description":10,"publishDate":6,"image":11,"author":12,"tags":15,"excerpt":10,"body":20,"_type":1150,"_id":1151,"_source":1152,"_file":1153,"_stem":1154,"_extension":1155},"/cperez/2026-07-07/why-ai-projects-fail","2026-07-07",false,"","Why Do Most AI Projects Fail?","AI projects rarely fail because the model was not powerful enough.","/cperez/2026-07-07/img/why-ai-projects-fail.jpg",{"name":13,"user":14},"Carlos Perez","cperez",[16,17,18,19],"ai","ethics","software development","vibe coding",{"type":21,"children":22,"toc":1121},"root",[23,30,35,40,45,50,57,62,67,72,77,83,88,93,109,114,119,124,129,134,139,144,149,154,159,164,169,175,180,194,199,204,209,214,219,224,229,235,240,245,250,255,260,265,320,325,330,336,341,346,351,356,361,373,378,383,388,393,398,403,408,413,418,424,429,434,439,444,456,461,466,471,476,481,486,492,497,502,516,521,526,531,536,541,546,552,557,562,567,572,577,582,587,601,606,611,616,621,626,631,637,642,647,652,665,670,675,680,685,690,696,701,706,711,716,721,726,731,736,741,747,752,757,762,767,772,777,782,787,792,797,802,807,813,818,823,828,833,838,843,848,853,858,863,868,873,878,883,889,894,899,904,909,914,919,924,929,935,940,945,950,955,960,965,970,975,980,986,991,996,1001,1006,1011,1016,1021,1026,1032,1039,1044,1050,1055,1061,1066,1072,1077,1083,1088,1094,1099,1105,1110,1116],{"type":24,"tag":25,"props":26,"children":27},"element","p",{},[28],{"type":29,"value":10},"text",{"type":24,"tag":25,"props":31,"children":32},{},[33],{"type":29,"value":34},"They fail because the team treated AI like a shortcut instead of a system.",{"type":24,"tag":25,"props":36,"children":37},{},[38],{"type":29,"value":39},"That distinction matters. AI can generate code, summarize documents, classify content, detect patterns, automate workflows, and help teams move faster. Art+Logic’s AI software development work is built around that promise: bringing AI into real-world applications that solve complex problems, extract insight, and create software that learns, adapts, and improves.",{"type":24,"tag":25,"props":41,"children":42},{},[43],{"type":29,"value":44},"But a real-world AI product is not a demo. It has users, permissions, messy data, security requirements, integrations, compliance constraints, operational edge cases, support needs, and business rules that do not fit neatly into a prompt.",{"type":24,"tag":25,"props":46,"children":47},{},[48],{"type":29,"value":49},"That is where AI projects tend to break down.",{"type":24,"tag":51,"props":52,"children":54},"h3",{"id":53},"the-short-answer-why-do-ai-projects-fail",[55],{"type":29,"value":56},"The Short Answer: Why Do AI Projects Fail?",{"type":24,"tag":25,"props":58,"children":59},{},[60],{"type":29,"value":61},"Most AI projects fail because teams start with the technology before they define the business problem, validate the data, plan for production, and assign accountability. The model is rarely the only issue. Failure usually comes from unclear goals, poor data readiness, weak integration, unrealistic expectations, missing governance, escalating costs, and treating a prototype like a finished product.",{"type":24,"tag":25,"props":63,"children":64},{},[65],{"type":29,"value":66},"RAND has reported that, by some estimates, more than 80% of AI projects fail, roughly twice the failure rate of IT projects that do not involve AI. Gartner has also found that by the end of 2025, at least 50% of generative AI projects had been abandoned after proof of concept because of poor data quality, inadequate risk controls, escalating costs, or unclear business value.",{"type":24,"tag":25,"props":68,"children":69},{},[70],{"type":29,"value":71},"In other words, AI projects usually fail for the same reason many complex software projects fail: the hard part was never just building the thing.",{"type":24,"tag":25,"props":73,"children":74},{},[75],{"type":29,"value":76},"The hard part is building the right thing, safely, sustainably, and in a way that fits the business.",{"type":24,"tag":51,"props":78,"children":80},{"id":79},"ai-makes-the-easy-part-faster",[81],{"type":29,"value":82},"AI Makes the Easy Part Faster",{"type":24,"tag":25,"props":84,"children":85},{},[86],{"type":29,"value":87},"Generative AI has changed the speed of early software creation. Teams can now produce boilerplate code, interface concepts, documentation, prototypes, test data, and working feature sketches much faster than before.",{"type":24,"tag":25,"props":89,"children":90},{},[91],{"type":29,"value":92},"That speed is real.",{"type":24,"tag":25,"props":94,"children":95},{},[96,98,107],{"type":29,"value":97},"As we mention in \"",{"type":24,"tag":99,"props":100,"children":104},"a",{"href":101,"rel":102},"https://artandlogic.com/videos/ai-can-write-code-but-thats-not-the-hard-part/",[103],"nofollow",[105],{"type":29,"value":106},"AI Can Write Code — But That’s Not the Hard Part,",{"type":29,"value":108},"\" AI coding tools can accelerate development, generate documentation, and produce working prototypes. But generating code is only a fraction of the challenge. We’ve seen cases where AI can deliver the visible 30% of a project: standard workflows, predictable integrations, and common feature patterns. The hidden 70% lives below the surface in compliance constraints, industry regulations, edge cases, failure modes, operational realities, and institutional knowledge.",{"type":24,"tag":25,"props":110,"children":111},{},[112],{"type":29,"value":113},"That is one of the biggest traps in AI development: early progress feels like product progress.",{"type":24,"tag":25,"props":115,"children":116},{},[117],{"type":29,"value":118},"A prototype works. A chatbot responds. A generated app compiles. A workflow automation runs. The demo looks impressive.",{"type":24,"tag":25,"props":120,"children":121},{},[122],{"type":29,"value":123},"Then the real questions begin:",{"type":24,"tag":25,"props":125,"children":126},{},[127],{"type":29,"value":128},"Does it handle exceptions correctly?",{"type":24,"tag":25,"props":130,"children":131},{},[132],{"type":29,"value":133},"Does it know which users can access which data?",{"type":24,"tag":25,"props":135,"children":136},{},[137],{"type":29,"value":138},"Does it integrate with the systems the business actually uses?",{"type":24,"tag":25,"props":140,"children":141},{},[142],{"type":29,"value":143},"Does it fail safely?",{"type":24,"tag":25,"props":145,"children":146},{},[147],{"type":29,"value":148},"Can anyone explain why it made that recommendation?",{"type":24,"tag":25,"props":150,"children":151},{},[152],{"type":29,"value":153},"Will it still work when usage increases?",{"type":24,"tag":25,"props":155,"children":156},{},[157],{"type":29,"value":158},"Does it comply with the rules of the industry?",{"type":24,"tag":25,"props":160,"children":161},{},[162],{"type":29,"value":163},"Can the team maintain it six months from now?",{"type":24,"tag":25,"props":165,"children":166},{},[167],{"type":29,"value":168},"AI can accelerate the first draft. It cannot automatically supply the context that makes software dependable.",{"type":24,"tag":51,"props":170,"children":172},{"id":171},"a-fast-build-is-not-the-same-as-a-finished-product",[173],{"type":29,"value":174},"A Fast Build Is Not the Same as a Finished Product",{"type":24,"tag":25,"props":176,"children":177},{},[178],{"type":29,"value":179},"One of the clearest reasons AI projects fail is the gap between “we built something quickly” and “we built something production-ready.”",{"type":24,"tag":25,"props":181,"children":182},{},[183,185,192],{"type":29,"value":184},"Art+Logic’s \"",{"type":24,"tag":99,"props":186,"children":189},{"href":187,"rel":188},"https://artandlogic.com/newsletters/fast-builds-dont-always-mean-fast-products/",[103],[190],{"type":29,"value":191},"Fast Builds Don’t Always Mean Fast Products",{"type":29,"value":193},"\" describes a pattern many teams are seeing now: organizations use AI-first approaches to modernize legacy systems, generate code faster, reduce costs, and accelerate delivery. The speed is real, but the initial momentum can be misleading because legacy systems carry years of decisions, edge cases, integrations, and constraints that are not always visible in the code itself.",{"type":24,"tag":25,"props":195,"children":196},{},[197],{"type":29,"value":198},"That is where the rework starts.",{"type":24,"tag":25,"props":200,"children":201},{},[202],{"type":29,"value":203},"A feature works in isolation but fails inside the actual workflow. An integration behaves correctly in a test environment but unpredictably in production. Performance looks fine with sample data but breaks under load. Security and compliance concerns show up late because they were never designed into the system.",{"type":24,"tag":25,"props":205,"children":206},{},[207],{"type":29,"value":208},"This is not an argument against AI-assisted development.",{"type":24,"tag":25,"props":210,"children":211},{},[212],{"type":29,"value":213},"It is an argument against confusing speed with completeness.",{"type":24,"tag":25,"props":215,"children":216},{},[217],{"type":29,"value":218},"AI can reduce the cost of exploration. It can make modernization more feasible. It can help teams revisit projects that once looked too expensive or too time-consuming. But feasibility is not the same as simplicity. Architecture, data, security, observability, governance, and long-term maintainability still matter.",{"type":24,"tag":25,"props":220,"children":221},{},[222],{"type":29,"value":223},"The teams that succeed with AI are not the ones that only ask, “How fast can we generate this?”",{"type":24,"tag":25,"props":225,"children":226},{},[227],{"type":29,"value":228},"They ask, “What needs to be true for this to work in production?”",{"type":24,"tag":51,"props":230,"children":232},{"id":231},"why-ai-proofs-of-concept-fail-in-production",[233],{"type":29,"value":234},"Why AI Proofs of Concept Fail in Production",{"type":24,"tag":25,"props":236,"children":237},{},[238],{"type":29,"value":239},"AI proofs of concept often fail because they are built in controlled conditions.",{"type":24,"tag":25,"props":241,"children":242},{},[243],{"type":29,"value":244},"The sample data is cleaner than the real data. The workflow is simpler than the real workflow. The user permissions are less complicated. The edge cases are ignored. The cost model is based on limited usage. The compliance review has not happened yet.",{"type":24,"tag":25,"props":246,"children":247},{},[248],{"type":29,"value":249},"Then the pilot meets the real business.",{"type":24,"tag":25,"props":251,"children":252},{},[253],{"type":29,"value":254},"That is when the gap appears between a promising AI experiment and a production AI system.",{"type":24,"tag":25,"props":256,"children":257},{},[258],{"type":29,"value":259},"For a CTO, product leader, or operations executive, the important question is not “Did the demo work?” It is “Can this system survive the real environment it will operate in?”",{"type":24,"tag":25,"props":261,"children":262},{},[263],{"type":29,"value":264},"Production AI needs:",{"type":24,"tag":266,"props":267,"children":268},"ul",{},[269,275,280,285,290,295,300,305,310,315],{"type":24,"tag":270,"props":271,"children":272},"li",{},[273],{"type":29,"value":274},"Clear success metrics",{"type":24,"tag":270,"props":276,"children":277},{},[278],{"type":29,"value":279},"Reliable data pipelines",{"type":24,"tag":270,"props":281,"children":282},{},[283],{"type":29,"value":284},"Defined ownership",{"type":24,"tag":270,"props":286,"children":287},{},[288],{"type":29,"value":289},"Security controls",{"type":24,"tag":270,"props":291,"children":292},{},[293],{"type":29,"value":294},"Human review where needed",{"type":24,"tag":270,"props":296,"children":297},{},[298],{"type":29,"value":299},"Cost visibility",{"type":24,"tag":270,"props":301,"children":302},{},[303],{"type":29,"value":304},"Monitoring and observability",{"type":24,"tag":270,"props":306,"children":307},{},[308],{"type":29,"value":309},"Integration with real workflows",{"type":24,"tag":270,"props":311,"children":312},{},[313],{"type":29,"value":314},"A plan for failure modes",{"type":24,"tag":270,"props":316,"children":317},{},[318],{"type":29,"value":319},"A path for iteration after launch",{"type":24,"tag":25,"props":321,"children":322},{},[323],{"type":29,"value":324},"Without those pieces, the proof of concept may prove only that the idea can work under ideal conditions.",{"type":24,"tag":25,"props":326,"children":327},{},[328],{"type":29,"value":329},"It does not prove that the product is ready.",{"type":24,"tag":51,"props":331,"children":333},{"id":332},"ai-projects-fail-when-the-problem-is-poorly-defined",[334],{"type":29,"value":335},"AI Projects Fail When the Problem Is Poorly Defined",{"type":24,"tag":25,"props":337,"children":338},{},[339],{"type":29,"value":340},"Many AI initiatives start with a technology mandate instead of a business problem.",{"type":24,"tag":25,"props":342,"children":343},{},[344],{"type":29,"value":345},"Someone says, “We need an AI strategy.”",{"type":24,"tag":25,"props":347,"children":348},{},[349],{"type":29,"value":350},"Someone else says, “We should add a chatbot.”",{"type":24,"tag":25,"props":352,"children":353},{},[354],{"type":29,"value":355},"A competitor launches an AI feature. A board member asks what the company is doing with generative AI. A team starts experimenting because everyone else is experimenting.",{"type":24,"tag":25,"props":357,"children":358},{},[359],{"type":29,"value":360},"The result is often a solution in search of a problem.",{"type":24,"tag":25,"props":362,"children":363},{},[364,371],{"type":24,"tag":99,"props":365,"children":368},{"href":366,"rel":367},"https://www.rand.org/pubs/research_reports/RRA2680-1.html",[103],[369],{"type":29,"value":370},"RAND’s research points to misunderstanding or miscommunication of the problem as one of the root causes of AI project failure.",{"type":29,"value":372}," If the team cannot clearly define the business problem, the system may optimize for the wrong outcome, solve a low-value use case, or fail to fit the workflow where it is supposed to create value.",{"type":24,"tag":25,"props":374,"children":375},{},[376],{"type":29,"value":377},"This is especially risky with generative AI because the technology is so flexible. It can write, summarize, classify, translate, answer, recommend, and generate. That flexibility makes it easy to build something impressive and hard to prove that it matters.",{"type":24,"tag":25,"props":379,"children":380},{},[381],{"type":29,"value":382},"A stronger AI project starts with sharper questions:",{"type":24,"tag":25,"props":384,"children":385},{},[386],{"type":29,"value":387},"What decision are we trying to improve?",{"type":24,"tag":25,"props":389,"children":390},{},[391],{"type":29,"value":392},"What manual workflow are we trying to reduce?",{"type":24,"tag":25,"props":394,"children":395},{},[396],{"type":29,"value":397},"What user pain are we trying to remove?",{"type":24,"tag":25,"props":399,"children":400},{},[401],{"type":29,"value":402},"What business outcome would make this worth maintaining?",{"type":24,"tag":25,"props":404,"children":405},{},[406],{"type":29,"value":407},"What is the cost of being wrong?",{"type":24,"tag":25,"props":409,"children":410},{},[411],{"type":29,"value":412},"What should the system do when confidence is low?",{"type":24,"tag":25,"props":414,"children":415},{},[416],{"type":29,"value":417},"The best AI use cases are not always the flashiest. They are the ones connected to a durable operational problem where better prediction, automation, classification, retrieval, or generation creates measurable value.",{"type":24,"tag":51,"props":419,"children":421},{"id":420},"ai-projects-fail-when-data-is-treated-as-an-afterthought",[422],{"type":29,"value":423},"AI Projects Fail When Data Is Treated as an Afterthought",{"type":24,"tag":25,"props":425,"children":426},{},[427],{"type":29,"value":428},"AI depends on data, but many organizations do not discover how messy their data is until the project is already underway.",{"type":24,"tag":25,"props":430,"children":431},{},[432],{"type":29,"value":433},"The demo used a clean sample set. The real system has missing fields, inconsistent labels, duplicated records, undocumented business logic, unstructured files, siloed databases, outdated permissions, and competing definitions of basic terms.",{"type":24,"tag":25,"props":435,"children":436},{},[437],{"type":29,"value":438},"The model is not the only thing being tested.",{"type":24,"tag":25,"props":440,"children":441},{},[442],{"type":29,"value":443},"The organization’s data maturity is being tested, too.",{"type":24,"tag":25,"props":445,"children":446},{},[447,454],{"type":24,"tag":99,"props":448,"children":451},{"href":449,"rel":450},"https://www.gartner.com/en/articles/genai-project-failure",[103],[452],{"type":29,"value":453},"Gartner identifies data readiness as a major failure point for generative AI projects,",{"type":29,"value":455},"\nnoting that poor-quality data can produce unreliable outputs, failed retrieval-augmented generation implementations, and models that cannot be fine-tuned effectively. Gartner recommends building an AI-ready data foundation with curated, accurate, enriched, and well-governed data.",{"type":24,"tag":25,"props":457,"children":458},{},[459],{"type":29,"value":460},"This is where AI projects often become data projects.",{"type":24,"tag":25,"props":462,"children":463},{},[464],{"type":29,"value":465},"That is not a failure. It is a discovery.",{"type":24,"tag":25,"props":467,"children":468},{},[469],{"type":29,"value":470},"The problem is pretending it will not happen.",{"type":24,"tag":25,"props":472,"children":473},{},[474],{"type":29,"value":475},"If an AI system is expected to make recommendations, summarize records, detect anomalies, automate approvals, or retrieve company knowledge, the team needs to understand where that information lives, how reliable it is, who owns it, who can access it, and how it changes over time.",{"type":24,"tag":25,"props":477,"children":478},{},[479],{"type":29,"value":480},"Without that foundation, AI can produce confident answers from incomplete context.",{"type":24,"tag":25,"props":482,"children":483},{},[484],{"type":29,"value":485},"Confident wrong answers are often worse than no automation at all.",{"type":24,"tag":51,"props":487,"children":489},{"id":488},"ai-projects-fail-when-generated-code-is-mistaken-for-engineered-software",[490],{"type":29,"value":491},"AI Projects Fail When Generated Code Is Mistaken for Engineered Software",{"type":24,"tag":25,"props":493,"children":494},{},[495],{"type":29,"value":496},"AI-generated code can be useful. It can speed up scaffolding, produce working examples, explain unfamiliar APIs, generate tests, and help developers explore alternatives quickly.",{"type":24,"tag":25,"props":498,"children":499},{},[500],{"type":29,"value":501},"But code that runs is not the same as software that is ready for production.",{"type":24,"tag":25,"props":503,"children":504},{},[505,507,514],{"type":29,"value":506},"In Art+Logic’s “",{"type":24,"tag":99,"props":508,"children":511},{"href":509,"rel":510},"https://artandlogic.com/videos/ai-rescue-fixing-what-generative-code-cant-finish/",[103],[512],{"type":29,"value":513},"AI Rescue: Fixing What Generative Code Can’t Finish,",{"type":29,"value":515},"” we describe a common AI-assisted development problem: generated code may build interfaces and functional prototypes quickly, but still miss context, business logic, scalability, security, compliance, real-world edge cases, test coverage, documentation, version control discipline, and architectural quality.",{"type":24,"tag":25,"props":517,"children":518},{},[519],{"type":29,"value":520},"That list is a good summary of why many AI-assisted builds eventually need rescue.",{"type":24,"tag":25,"props":522,"children":523},{},[524],{"type":29,"value":525},"The generated code may look complete from the outside. Under the hood, it may have fragile abstractions, duplicated logic, unhandled errors, hidden security problems, performance bottlenecks, or no clear path for future development.",{"type":24,"tag":25,"props":527,"children":528},{},[529],{"type":29,"value":530},"This is especially common in AI-generated MVPs, where teams use generative tools to create a functioning application quickly without enough architectural oversight. The result may be a promising prototype that cannot be extended safely.",{"type":24,"tag":25,"props":532,"children":533},{},[534],{"type":29,"value":535},"The good news is that these projects do not always need to be scrapped.",{"type":24,"tag":25,"props":537,"children":538},{},[539],{"type":29,"value":540},"They often need an engineering intervention: architecture review, modular refactoring, security assessment, test coverage, integration planning, documentation, DevOps discipline, and a clear plan for turning the prototype into a maintainable product.",{"type":24,"tag":25,"props":542,"children":543},{},[544],{"type":29,"value":545},"In short, yes, AI can write code, but humans still have to build software.",{"type":24,"tag":51,"props":547,"children":549},{"id":548},"ai-projects-fail-when-accountability-is-unclear",[550],{"type":29,"value":551},"AI Projects Fail When Accountability Is Unclear",{"type":24,"tag":25,"props":553,"children":554},{},[555],{"type":29,"value":556},"As AI systems become more autonomous, accountability becomes harder to define.",{"type":24,"tag":25,"props":558,"children":559},{},[560],{"type":29,"value":561},"Who is responsible if an AI recommendation is biased?",{"type":24,"tag":25,"props":563,"children":564},{},[565],{"type":29,"value":566},"Who owns the risk if an automated decision affects a customer, patient, employee, or applicant?",{"type":24,"tag":25,"props":568,"children":569},{},[570],{"type":29,"value":571},"Who signs off on the model’s behavior before deployment?",{"type":24,"tag":25,"props":573,"children":574},{},[575],{"type":29,"value":576},"Who monitors it after release?",{"type":24,"tag":25,"props":578,"children":579},{},[580],{"type":29,"value":581},"Who can override it?",{"type":24,"tag":25,"props":583,"children":584},{},[585],{"type":29,"value":586},"Who explains what happened when something goes wrong?",{"type":24,"tag":25,"props":588,"children":589},{},[590,592,599],{"type":29,"value":591},"Art+Logic’s “",{"type":24,"tag":99,"props":593,"children":596},{"href":594,"rel":595},"https://artandlogic.com/newsletters/the-ethics-of-automation-whos-accountable-when-ai-acts/",[103],[597],{"type":29,"value":598},"The Ethics of Automation: Who’s Accountable When AI Acts?",{"type":29,"value":600},"” frames this as the automation paradox: automation can make work faster and more precise, but it can also make responsibility more complex. When humans make decisions, accountability has a face. When algorithms make them, accountability can disappear into logs, vendors, data pipelines, and unclear ownership.",{"type":24,"tag":25,"props":602,"children":603},{},[604],{"type":29,"value":605},"That is not just an ethical issue.",{"type":24,"tag":25,"props":607,"children":608},{},[609],{"type":29,"value":610},"It is a product risk.",{"type":24,"tag":25,"props":612,"children":613},{},[614],{"type":29,"value":615},"AI projects fail when responsibility is vague. They fail when no one owns validation, when business teams assume the model is “technical,” when technical teams assume policy decisions belong to leadership, and when users are expected to trust outputs without understanding their limits.",{"type":24,"tag":25,"props":617,"children":618},{},[619],{"type":29,"value":620},"Responsible AI needs to be designed into the system. Art+Logic’s guidance emphasizes explainability, bias audits, fairness testing, human-in-the-loop systems, accountability maps, and governance that evolves as models and use cases change.",{"type":24,"tag":25,"props":622,"children":623},{},[624],{"type":29,"value":625},"For many teams, the most important AI feature is not a smarter model.",{"type":24,"tag":25,"props":627,"children":628},{},[629],{"type":29,"value":630},"It is a clearer chain of responsibility.",{"type":24,"tag":51,"props":632,"children":634},{"id":633},"ai-projects-fail-when-they-skip-the-human-in-the-loop",[635],{"type":29,"value":636},"AI Projects Fail When They Skip the Human-in-the-Loop",{"type":24,"tag":25,"props":638,"children":639},{},[640],{"type":29,"value":641},"There is a misconception that the goal of AI is to remove people from the process.",{"type":24,"tag":25,"props":643,"children":644},{},[645],{"type":29,"value":646},"Sometimes automation can fully replace a repetitive task. But in many high-value use cases, AI works best as a collaborator: surfacing patterns, drafting outputs, ranking options, summarizing information, flagging anomalies, or recommending next steps.",{"type":24,"tag":25,"props":648,"children":649},{},[650],{"type":29,"value":651},"Humans still provide judgment, context, ethics, domain knowledge, and accountability.",{"type":24,"tag":25,"props":653,"children":654},{},[655,657,663],{"type":29,"value":656},"That is especially true in complex software projects. Art+Logic’s “",{"type":24,"tag":99,"props":658,"children":660},{"href":101,"rel":659},[103],[661],{"type":29,"value":662},"AI Can Write Code — But That’s Not the Hard Part",{"type":29,"value":664},"” makes the point directly: AI works best when a team is guiding it, refining requirements, checking assumptions, and making sure the system solves the right problem.",{"type":24,"tag":25,"props":666,"children":667},{},[668],{"type":29,"value":669},"This does not make AI less valuable.",{"type":24,"tag":25,"props":671,"children":672},{},[673],{"type":29,"value":674},"It makes it more practical.",{"type":24,"tag":25,"props":676,"children":677},{},[678],{"type":29,"value":679},"A human-in-the-loop approach gives the team a way to manage uncertainty. It creates checkpoints where people can review outputs, correct errors, override recommendations, improve prompts, tune workflows, and identify edge cases before they become production failures.",{"type":24,"tag":25,"props":681,"children":682},{},[683],{"type":29,"value":684},"The question is not only, “Can AI do this task?”",{"type":24,"tag":25,"props":686,"children":687},{},[688],{"type":29,"value":689},"The better question is, “Where should AI assist, and where must a person remain accountable?”",{"type":24,"tag":51,"props":691,"children":693},{"id":692},"ai-projects-fail-when-they-ignore-integration",[694],{"type":29,"value":695},"AI Projects Fail When They Ignore Integration",{"type":24,"tag":25,"props":697,"children":698},{},[699],{"type":29,"value":700},"Many AI demos happen in isolation, while real products do not.",{"type":24,"tag":25,"props":702,"children":703},{},[704],{"type":29,"value":705},"A successful AI system has to fit into authentication, permissions, databases, APIs, legacy workflows, reporting tools, user interfaces, monitoring systems, support processes, and deployment pipelines.",{"type":24,"tag":25,"props":707,"children":708},{},[709],{"type":29,"value":710},"This is one reason AI pilots stall after proof of concept. The model works. The workflow does not.",{"type":24,"tag":25,"props":712,"children":713},{},[714],{"type":29,"value":715},"Art+Logic’s AI capabilities include natural language interfaces, recommendation engines, real-time audio/video/vision processing, anomaly detection, workflow automation, document summarization, predictive modeling, business intelligence, and custom model training or fine-tuning. Each of those capabilities becomes useful only when it is connected to the systems, people, and decisions around it.",{"type":24,"tag":25,"props":717,"children":718},{},[719],{"type":29,"value":720},"A summarization tool that does not connect to the source documents is a novelty.",{"type":24,"tag":25,"props":722,"children":723},{},[724],{"type":29,"value":725},"A prediction engine that does not feed into an operational decision is a dashboard.",{"type":24,"tag":25,"props":727,"children":728},{},[729],{"type":29,"value":730},"A chatbot that cannot access reliable context is a liability.",{"type":24,"tag":25,"props":732,"children":733},{},[734],{"type":29,"value":735},"A code-generation workflow without review, testing, and version control is technical debt with better marketing.",{"type":24,"tag":25,"props":737,"children":738},{},[739],{"type":29,"value":740},"Integration is where AI stops being a feature and starts becoming software.",{"type":24,"tag":51,"props":742,"children":744},{"id":743},"what-ctos-and-product-leaders-should-watch-for",[745],{"type":29,"value":746},"What CTOs and Product Leaders Should Watch For",{"type":24,"tag":25,"props":748,"children":749},{},[750],{"type":29,"value":751},"For technology and product leaders, the warning signs usually appear before the project officially “fails.”",{"type":24,"tag":25,"props":753,"children":754},{},[755],{"type":29,"value":756},"The team is showing progress, but no one can define the business metric the AI system is supposed to improve.",{"type":24,"tag":25,"props":758,"children":759},{},[760],{"type":29,"value":761},"The prototype works, but only with handpicked data.",{"type":24,"tag":25,"props":763,"children":764},{},[765],{"type":29,"value":766},"The AI output looks impressive, but no one knows who approves it.",{"type":24,"tag":25,"props":768,"children":769},{},[770],{"type":29,"value":771},"The system is generating code, but no one has reviewed the architecture.",{"type":24,"tag":25,"props":773,"children":774},{},[775],{"type":29,"value":776},"The workflow depends on human trust, but users cannot understand or challenge the recommendation.",{"type":24,"tag":25,"props":778,"children":779},{},[780],{"type":29,"value":781},"The pilot is getting usage, but the cost model does not work at scale.",{"type":24,"tag":25,"props":783,"children":784},{},[785],{"type":29,"value":786},"The AI feature is technically interesting, but it does not change the user’s job, decision, or outcome in a meaningful way.",{"type":24,"tag":25,"props":788,"children":789},{},[790],{"type":29,"value":791},"These are not reasons to abandon AI. They are reasons to slow down and ask better questions before the project becomes expensive to unwind.",{"type":24,"tag":25,"props":793,"children":794},{},[795],{"type":29,"value":796},"For CTOs, the core question is whether the system can be secured, tested, monitored, integrated, and maintained.",{"type":24,"tag":25,"props":798,"children":799},{},[800],{"type":29,"value":801},"For product leaders, the core question is whether the AI capability solves a real user problem, improves a measurable workflow, and has a clear path from prototype to production.",{"type":24,"tag":25,"props":803,"children":804},{},[805],{"type":29,"value":806},"For executives, the core question is whether the organization is ready to own the outcome.",{"type":24,"tag":51,"props":808,"children":810},{"id":809},"ai-project-failure-checklist",[811],{"type":29,"value":812},"AI Project Failure Checklist",{"type":24,"tag":25,"props":814,"children":815},{},[816],{"type":29,"value":817},"Before investing further in an AI initiative, ask:",{"type":24,"tag":25,"props":819,"children":820},{},[821],{"type":29,"value":822},"Is the business problem clearly defined?",{"type":24,"tag":25,"props":824,"children":825},{},[826],{"type":29,"value":827},"Is AI the right tool for that problem?",{"type":24,"tag":25,"props":829,"children":830},{},[831],{"type":29,"value":832},"Is there a measurable outcome tied to the project?",{"type":24,"tag":25,"props":834,"children":835},{},[836],{"type":29,"value":837},"Is the data reliable, accessible, and governed?",{"type":24,"tag":25,"props":839,"children":840},{},[841],{"type":29,"value":842},"Does the system need human review or approval?",{"type":24,"tag":25,"props":844,"children":845},{},[846],{"type":29,"value":847},"Can the AI output be explained, audited, or overridden?",{"type":24,"tag":25,"props":849,"children":850},{},[851],{"type":29,"value":852},"Have security, privacy, and compliance requirements been identified?",{"type":24,"tag":25,"props":854,"children":855},{},[856],{"type":29,"value":857},"Has the prototype been reviewed for scalability and maintainability?",{"type":24,"tag":25,"props":859,"children":860},{},[861],{"type":29,"value":862},"Does the system integrate with real workflows and existing tools?",{"type":24,"tag":25,"props":864,"children":865},{},[866],{"type":29,"value":867},"Is there a clear owner after launch?",{"type":24,"tag":25,"props":869,"children":870},{},[871],{"type":29,"value":872},"Are costs modeled for production usage, not just proof-of-concept usage?",{"type":24,"tag":25,"props":874,"children":875},{},[876],{"type":29,"value":877},"Is there a monitoring plan for performance, drift, errors, and user feedback?",{"type":24,"tag":25,"props":879,"children":880},{},[881],{"type":29,"value":882},"If the answer to several of these questions is “not yet,” the project may not be failing. It may simply be earlier than the team thinks.",{"type":24,"tag":51,"props":884,"children":886},{"id":885},"how-to-give-an-ai-project-a-better-chance-of-success",[887],{"type":29,"value":888},"How to Give an AI Project a Better Chance of Success",{"type":24,"tag":25,"props":890,"children":891},{},[892],{"type":29,"value":893},"The failure pattern is clear, but it is not inevitable. AI projects have a much better chance of succeeding when teams treat them like serious product and engineering initiatives from the beginning.",{"type":24,"tag":25,"props":895,"children":896},{},[897],{"type":29,"value":898},"Start with the business problem. Define the workflow, decision, user pain, or operational bottleneck before choosing a model or tool.",{"type":24,"tag":25,"props":900,"children":901},{},[902],{"type":29,"value":903},"Validate the data early. Know what data is needed, where it lives, who owns it, how clean it is, how it will be governed, and how it will be monitored over time.",{"type":24,"tag":25,"props":905,"children":906},{},[907],{"type":29,"value":908},"Design for production, not just the demo. Include security, compliance, performance, scalability, observability, support, documentation, and maintainability in the plan from day one.",{"type":24,"tag":25,"props":910,"children":911},{},[912],{"type":29,"value":913},"Keep humans accountable. Decide where human review is required, who can override the system, and who owns outcomes after deployment.",{"type":24,"tag":25,"props":915,"children":916},{},[917],{"type":29,"value":918},"Use AI where it fits. AI is powerful, but it is not always the right solution. Sometimes the better answer is a rules engine, a workflow redesign, a database cleanup, a better user interface, or a simpler automation.",{"type":24,"tag":25,"props":920,"children":921},{},[922],{"type":29,"value":923},"Plan for iteration. AI systems are not “done” when they launch. They need monitoring, evaluation, feedback loops, model updates, prompt refinement, and governance as the business changes.",{"type":24,"tag":25,"props":925,"children":926},{},[927],{"type":29,"value":928},"Bring engineering judgment to AI-generated work. Generated code should be reviewed, tested, refactored, secured, documented, and integrated like any other production software.",{"type":24,"tag":51,"props":930,"children":932},{"id":931},"can-a-failing-ai-project-be-rescued",[933],{"type":29,"value":934},"Can a Failing AI Project Be Rescued?",{"type":24,"tag":25,"props":936,"children":937},{},[938],{"type":29,"value":939},"Often, yes.",{"type":24,"tag":25,"props":941,"children":942},{},[943],{"type":29,"value":944},"A stalled AI project does not always mean the original idea was wrong. It may mean the system needs more context, stronger architecture, cleaner data, better integration, clearer ownership, or a more realistic production plan.",{"type":24,"tag":25,"props":946,"children":947},{},[948],{"type":29,"value":949},"An AI-generated MVP may need refactoring rather than replacement.",{"type":24,"tag":25,"props":951,"children":952},{},[953],{"type":29,"value":954},"A chatbot may need retrieval design, permissions, and source grounding.",{"type":24,"tag":25,"props":956,"children":957},{},[958],{"type":29,"value":959},"A prediction engine may need better data pipelines and clearer decision workflows.",{"type":24,"tag":25,"props":961,"children":962},{},[963],{"type":29,"value":964},"An automation project may need human approval steps and accountability mapping.",{"type":24,"tag":25,"props":966,"children":967},{},[968],{"type":29,"value":969},"A legacy modernization effort may need engineers to identify which parts of the system can be rebuilt safely and which parts need to be preserved.",{"type":24,"tag":25,"props":971,"children":972},{},[973],{"type":29,"value":974},"The goal is not to remove AI from the process. The goal is to use AI inside a disciplined engineering process.",{"type":24,"tag":25,"props":976,"children":977},{},[978],{"type":29,"value":979},"That is the difference between a fast build and a durable product.",{"type":24,"tag":51,"props":981,"children":983},{"id":982},"the-real-reason-ai-projects-fail",[984],{"type":29,"value":985},"The Real Reason AI Projects Fail",{"type":24,"tag":25,"props":987,"children":988},{},[989],{"type":29,"value":990},"Most AI projects do not fail because AI lacks potential.",{"type":24,"tag":25,"props":992,"children":993},{},[994],{"type":29,"value":995},"They fail because potential is not a product.",{"type":24,"tag":25,"props":997,"children":998},{},[999],{"type":29,"value":1000},"A useful AI system needs a real problem, reliable data, thoughtful architecture, secure integration, clear accountability, human oversight, and a path to long-term maintenance. Without those pieces, even the most impressive demo can collapse under real-world conditions.",{"type":24,"tag":25,"props":1002,"children":1003},{},[1004],{"type":29,"value":1005},"The teams that get AI right are not simply moving faster.",{"type":24,"tag":25,"props":1007,"children":1008},{},[1009],{"type":29,"value":1010},"They are moving faster with discipline.",{"type":24,"tag":25,"props":1012,"children":1013},{},[1014],{"type":29,"value":1015},"They understand that AI can accelerate development, expand what is possible, and make previously impractical projects worth revisiting. But they also understand that the work still has to be engineered.",{"type":24,"tag":25,"props":1017,"children":1018},{},[1019],{"type":29,"value":1020},"Because the real challenge is not generating code, producing a prototype, or adding an AI feature.",{"type":24,"tag":25,"props":1022,"children":1023},{},[1024],{"type":29,"value":1025},"The real challenge is getting the whole system right.",{"type":24,"tag":51,"props":1027,"children":1029},{"id":1028},"faqs",[1030],{"type":29,"value":1031},"FAQs",{"type":24,"tag":1033,"props":1034,"children":1036},"h4",{"id":1035},"why-do-most-ai-projects-fail",[1037],{"type":29,"value":1038},"Why do most AI projects fail?",{"type":24,"tag":25,"props":1040,"children":1041},{},[1042],{"type":29,"value":1043},"Most AI projects fail because teams start with AI technology before defining the business problem, validating the data, planning for production, and assigning accountability. Common causes include unclear goals, poor data quality, weak integration, inadequate governance, escalating costs, and unrealistic expectations.",{"type":24,"tag":1033,"props":1045,"children":1047},{"id":1046},"why-do-ai-proofs-of-concept-fail-in-production",[1048],{"type":29,"value":1049},"Why do AI proofs of concept fail in production?",{"type":24,"tag":25,"props":1051,"children":1052},{},[1053],{"type":29,"value":1054},"AI proofs of concept often fail in production because they are built with clean sample data, simplified workflows, and limited constraints. Production systems need security, performance, observability, permissions, integrations, exception handling, support processes, and cost controls.",{"type":24,"tag":1033,"props":1056,"children":1058},{"id":1057},"is-ai-generated-code-production-ready",[1059],{"type":29,"value":1060},"Is AI-generated code production-ready?",{"type":24,"tag":25,"props":1062,"children":1063},{},[1064],{"type":29,"value":1065},"Not by default. AI-generated code can be a useful starting point, but it still needs architecture review, testing, security checks, documentation, version control, performance evaluation, and integration planning before it can be trusted in production.",{"type":24,"tag":1033,"props":1067,"children":1069},{"id":1068},"can-an-ai-generated-app-be-rescued",[1070],{"type":29,"value":1071},"Can an AI-generated app be rescued?",{"type":24,"tag":25,"props":1073,"children":1074},{},[1075],{"type":29,"value":1076},"Often, yes. An AI-generated app may need refactoring, architecture review, test coverage, security hardening, documentation, deployment discipline, and integration work before it can become maintainable production software.",{"type":24,"tag":1033,"props":1078,"children":1080},{"id":1079},"how-do-you-know-whether-ai-is-the-right-solution",[1081],{"type":29,"value":1082},"How do you know whether AI is the right solution?",{"type":24,"tag":25,"props":1084,"children":1085},{},[1086],{"type":29,"value":1087},"AI is a good fit when the problem depends on prediction, classification, summarization, retrieval, generation, anomaly detection, or pattern recognition. It may not be the right fit when the issue is primarily unclear process, poor data, weak UX, missing business rules, or lack of system integration.",{"type":24,"tag":1033,"props":1089,"children":1091},{"id":1090},"what-should-a-cto-check-before-approving-an-ai-project",[1092],{"type":29,"value":1093},"What should a CTO check before approving an AI project?",{"type":24,"tag":25,"props":1095,"children":1096},{},[1097],{"type":29,"value":1098},"A CTO should check whether the project has a defined business outcome, reliable data, clear architecture, security and compliance requirements, human oversight, cost visibility, monitoring, integration plans, and a post-launch owner.",{"type":24,"tag":1033,"props":1100,"children":1102},{"id":1101},"what-is-the-difference-between-an-ai-prototype-and-an-ai-product",[1103],{"type":29,"value":1104},"What is the difference between an AI prototype and an AI product?",{"type":24,"tag":25,"props":1106,"children":1107},{},[1108],{"type":29,"value":1109},"An AI prototype proves that an idea can work in a controlled setting. An AI product must work reliably in real workflows, with real users, real data, permissions, security requirements, compliance needs, monitoring, support, and long-term maintainability.",{"type":24,"tag":1033,"props":1111,"children":1113},{"id":1112},"how-can-companies-improve-ai-project-success-rates",[1114],{"type":29,"value":1115},"How can companies improve AI project success rates?",{"type":24,"tag":25,"props":1117,"children":1118},{},[1119],{"type":29,"value":1120},"Companies can improve success rates by defining the business problem first, validating data readiness early, designing for production, assigning clear accountability, keeping humans in the loop, and using experienced engineers to integrate AI into the broader software system.",{"title":8,"searchDepth":1122,"depth":1122,"links":1123},3,[1124,1125,1126,1127,1128,1129,1130,1131,1132,1133,1134,1135,1136,1137,1138,1139],{"id":53,"depth":1122,"text":56},{"id":79,"depth":1122,"text":82},{"id":171,"depth":1122,"text":174},{"id":231,"depth":1122,"text":234},{"id":332,"depth":1122,"text":335},{"id":420,"depth":1122,"text":423},{"id":488,"depth":1122,"text":491},{"id":548,"depth":1122,"text":551},{"id":633,"depth":1122,"text":636},{"id":692,"depth":1122,"text":695},{"id":743,"depth":1122,"text":746},{"id":809,"depth":1122,"text":812},{"id":885,"depth":1122,"text":888},{"id":931,"depth":1122,"text":934},{"id":982,"depth":1122,"text":985},{"id":1028,"depth":1122,"text":1031,"children":1140},[1141,1143,1144,1145,1146,1147,1148,1149],{"id":1035,"depth":1142,"text":1038},4,{"id":1046,"depth":1142,"text":1049},{"id":1057,"depth":1142,"text":1060},{"id":1068,"depth":1142,"text":1071},{"id":1079,"depth":1142,"text":1082},{"id":1090,"depth":1142,"text":1093},{"id":1101,"depth":1142,"text":1104},{"id":1112,"depth":1142,"text":1115},"markdown","content:cperez:2026-07-07:why-ai-projects-fail.md","content","cperez/2026-07-07/why-ai-projects-fail.md","cperez/2026-07-07/why-ai-projects-fail","md",{"_path":1157,"_dir":1158,"_draft":7,"_partial":7,"_locale":8,"title":1159,"description":1160,"publishDate":1158,"image":1161,"author":1162,"tags":1163,"excerpt":1160,"body":1166,"_type":1150,"_id":1823,"_source":1152,"_file":1824,"_stem":1825,"_extension":1155},"/cperez/2026-07-02/hidden-costs-of-legacy-software","2026-07-02","What Are the Hidden Costs of Legacy Software?","Legacy software is rarely “bad” software.","/cperez/2026-07-02/img/hidden-costs-of-legacy-software.jpg",{"name":13,"user":14},[1164,1165],"legacy modernization","legacy software",{"type":21,"children":1167,"toc":1802},[1168,1172,1186,1191,1196,1201,1207,1212,1217,1222,1234,1239,1245,1250,1262,1267,1272,1278,1283,1288,1293,1305,1310,1316,1321,1326,1331,1336,1347,1352,1358,1363,1368,1379,1384,1389,1395,1400,1412,1417,1422,1427,1433,1438,1443,1454,1459,1465,1470,1475,1480,1485,1496,1501,1507,1512,1523,1528,1539,1544,1550,1555,1560,1565,1577,1582,1616,1621,1627,1632,1637,1680,1685,1690,1696,1701,1712,1723,1728,1733,1738,1743,1747,1753,1758,1764,1769,1775,1780,1786,1791,1797],{"type":24,"tag":25,"props":1169,"children":1170},{},[1171],{"type":29,"value":1160},{"type":24,"tag":25,"props":1173,"children":1174},{},[1175,1177,1184],{"type":29,"value":1176},"In many cases, it is the opposite. It is the system that helped a company grow, supported years of operations, encoded hard-won business rules, and kept critical workflows moving long after newer tools came and went. That is why legacy systems tend to survive: they are doing something important. They contain operational knowledge, customer workflows, integrations, reports, permissions, exceptions, and decisions that may not be documented anywhere else. (",{"type":24,"tag":99,"props":1178,"children":1181},{"href":1179,"rel":1180},"https://artandlogic.com/newsletters/what-modernizing-legacy-systems-actually-means-in-practice/",[103],[1182],{"type":29,"value":1183},"Art+Logic",{"type":29,"value":1185},")",{"type":24,"tag":25,"props":1187,"children":1188},{},[1189],{"type":29,"value":1190},"But that usefulness can make the true cost harder to see.",{"type":24,"tag":25,"props":1192,"children":1193},{},[1194],{"type":29,"value":1195},"The visible costs of legacy software are easy to identify: hosting, licensing, support contracts, maintenance tickets, and the occasional emergency fix. The hidden costs are more dangerous because they compound quietly. They show up as slower releases, fragile integrations, frustrated employees, compliance headaches, customer experience gaps, and opportunities the business cannot pursue because the software cannot support them.",{"type":24,"tag":25,"props":1197,"children":1198},{},[1199],{"type":29,"value":1200},"The real question is not, “Is this system old?” It is: “What is this system preventing us from doing?”",{"type":24,"tag":51,"props":1202,"children":1204},{"id":1203},"legacy-software-creates-a-velocity-tax",[1205],{"type":29,"value":1206},"Legacy Software Creates a Velocity Tax",{"type":24,"tag":25,"props":1208,"children":1209},{},[1210],{"type":29,"value":1211},"One of the most common hidden costs of legacy software is speed.",{"type":24,"tag":25,"props":1213,"children":1214},{},[1215],{"type":29,"value":1216},"A healthy software system lets teams make small, confident changes. A legacy system often does the opposite. A minor update turns into a multi-week effort because no one knows what else it might break. QA takes longer than development. Releases require manual checklists. Engineers avoid touching certain parts of the codebase because those areas are too risky, too tangled, or too poorly understood.",{"type":24,"tag":25,"props":1218,"children":1219},{},[1220],{"type":29,"value":1221},"That is the velocity tax: every feature, fix, and improvement costs more than it should.",{"type":24,"tag":25,"props":1223,"children":1224},{},[1225,1227,1233],{"type":29,"value":1226},"One of the clearest signs that a legacy system is holding a business back is when small code changes take days to deploy, or QA cycles stretch longer than the development work itself; the system is no longer just a technical concern. It is costing the business time and money. (",{"type":24,"tag":99,"props":1228,"children":1231},{"href":1229,"rel":1230},"https://artandlogic.com/newsletters/is-your-legacy-system-holding-you-back/",[103],[1232],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1235,"children":1236},{},[1237],{"type":29,"value":1238},"This tax is easy to normalize. Teams get used to slow releases. Product managers stop asking for certain improvements. Leadership assumes the roadmap is naturally difficult. But underneath that new normal is a software system quietly setting the pace of the business.",{"type":24,"tag":51,"props":1240,"children":1242},{"id":1241},"maintenance-starts-replacing-momentum",[1243],{"type":29,"value":1244},"Maintenance Starts Replacing Momentum",{"type":24,"tag":25,"props":1246,"children":1247},{},[1248],{"type":29,"value":1249},"Legacy software also shifts engineering energy away from value creation.",{"type":24,"tag":25,"props":1251,"children":1252},{},[1253,1255,1261],{"type":29,"value":1254},"Instead of building new capabilities, teams spend more time patching brittle code, resolving regressions, investigating production issues, and maintaining workarounds. Refactoring older code rarely looks exciting on a roadmap, but it can be one of the highest-ROI investments a software-driven organization makes because old code does not only slow engineers down; it taxes the whole business. (",{"type":24,"tag":99,"props":1256,"children":1259},{"href":1257,"rel":1258},"https://artandlogic.com/newsletters/the-true-roi-of-refactoring-old-code/",[103],[1260],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1263,"children":1264},{},[1265],{"type":29,"value":1266},"The hidden cost is not just the maintenance work itself. It is what the team is not doing while maintenance consumes their attention. They are not improving onboarding. They are not building customer-requested features. They are not experimenting with new revenue streams. They are not improving reliability, analytics, accessibility, or automation.",{"type":24,"tag":25,"props":1268,"children":1269},{},[1270],{"type":29,"value":1271},"Over time, the gap between “what the business needs” and “what the system can support” gets wider. Eventually, even reasonable product ideas start to feel expensive.",{"type":24,"tag":51,"props":1273,"children":1275},{"id":1274},"operational-risk-increases-quietly",[1276],{"type":29,"value":1277},"Operational Risk Increases Quietly",{"type":24,"tag":25,"props":1279,"children":1280},{},[1281],{"type":29,"value":1282},"Legacy systems often fail in subtle ways before they fail dramatically.",{"type":24,"tag":25,"props":1284,"children":1285},{},[1286],{"type":29,"value":1287},"Performance slows under load. Nightly jobs require manual babysitting. Integrations break when a vendor updates an API. Reports generate inconsistent results. A process works only because one person knows the workaround. A critical server, library, or framework is no longer actively supported.",{"type":24,"tag":25,"props":1289,"children":1290},{},[1291],{"type":29,"value":1292},"These issues may not stop the business immediately, but they raise the cost of operating it.",{"type":24,"tag":25,"props":1294,"children":1295},{},[1296,1298,1304],{"type":29,"value":1297},"We’ve got a brief video on legacy systems that calls out several of these hidden costs directly: slow performance, constant workarounds, security vulnerabilities from outdated technology, inability to scale or support new features, integration headaches, and employee time lost to systems that no longer fit the business. Sometimes the system breaks; other times it works “just barely,” but at a high cost. (",{"type":24,"tag":99,"props":1299,"children":1302},{"href":1300,"rel":1301},"https://artandlogic.com/videos/legacy-systems-what-to-fix-what-to-keep/",[103],[1303],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1306,"children":1307},{},[1308],{"type":29,"value":1309},"That “just barely” state is risky. It can make teams overly dependent on institutional memory, manual intervention, and luck. The longer that continues, the harder it becomes to predict where the next failure will come from.",{"type":24,"tag":51,"props":1311,"children":1313},{"id":1312},"integration-problems-limit-growth",[1314],{"type":29,"value":1315},"Integration Problems Limit Growth",{"type":24,"tag":25,"props":1317,"children":1318},{},[1319],{"type":29,"value":1320},"Modern businesses rarely run on one system. They depend on a network of tools: CRMs, ERPs, payment platforms, analytics systems, data warehouses, mobile apps, customer portals, AI tools, marketing automation, and third-party APIs.",{"type":24,"tag":25,"props":1322,"children":1323},{},[1324],{"type":29,"value":1325},"Legacy software can become the weak link in that ecosystem.",{"type":24,"tag":25,"props":1327,"children":1328},{},[1329],{"type":29,"value":1330},"Older systems may not expose clean APIs. Data may live in formats that are difficult to access. Authentication patterns may not meet modern expectations. Integrations may rely on fragile scripts, manual exports, or custom bridges that only one or two people understand.",{"type":24,"tag":25,"props":1332,"children":1333},{},[1334],{"type":29,"value":1335},"That creates a hidden cost every time the business wants to adopt a new tool or connect existing systems in a better way.",{"type":24,"tag":25,"props":1337,"children":1338},{},[1339,1341,1346],{"type":29,"value":1340},"Art+Logic identifies integration pain as a major modernization signal: legacy systems often do not play well with newer APIs, tools, or platforms, which makes scaling or even staying current harder than it should be. (",{"type":24,"tag":99,"props":1342,"children":1344},{"href":1229,"rel":1343},[103],[1345],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1348,"children":1349},{},[1350],{"type":29,"value":1351},"The business impact can be significant. A company may want better reporting, self-service customer workflows, AI-assisted operations, or smoother internal automation, but the legacy system keeps every initiative dependent on custom glue code.",{"type":24,"tag":51,"props":1353,"children":1355},{"id":1354},"compliance-and-security-become-harder-to-manage",[1356],{"type":29,"value":1357},"Compliance and Security Become Harder to Manage",{"type":24,"tag":25,"props":1359,"children":1360},{},[1361],{"type":29,"value":1362},"Compliance is not static. Security expectations change. Privacy requirements evolve. Audit standards become more demanding. Vendors stop supporting old dependencies. Attack surfaces expand as systems get connected in new ways.",{"type":24,"tag":25,"props":1364,"children":1365},{},[1366],{"type":29,"value":1367},"A legacy system makes all of that harder.",{"type":24,"tag":25,"props":1369,"children":1370},{},[1371,1373,1378],{"type":29,"value":1372},"In regulated industries, outdated systems can make compliance updates risky and audits expensive. We see that industries such as finance, healthcare, and insurance face evolving compliance rules, and outdated systems make those updates more difficult to manage. (",{"type":24,"tag":99,"props":1374,"children":1376},{"href":1229,"rel":1375},[103],[1377],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1380,"children":1381},{},[1382],{"type":29,"value":1383},"Security risk is similar. A system may still function, but if it depends on unsupported libraries, outdated frameworks, aging infrastructure, or unclear access controls, the business may be carrying risk it cannot easily measure.",{"type":24,"tag":25,"props":1385,"children":1386},{},[1387],{"type":29,"value":1388},"The hidden cost is not just the cost of fixing a vulnerability. It is the cost of uncertainty: not knowing whether the system can pass an audit, withstand scrutiny, or adapt quickly when requirements change.",{"type":24,"tag":51,"props":1390,"children":1392},{"id":1391},"technical-debt-spills-into-product-design-process-and-culture",[1393],{"type":29,"value":1394},"Technical Debt Spills Into Product, Design, Process, and Culture",{"type":24,"tag":25,"props":1396,"children":1397},{},[1398],{"type":29,"value":1399},"Technical debt is often treated as an engineering problem, but it rarely stays confined to the codebase.",{"type":24,"tag":25,"props":1401,"children":1402},{},[1403,1405,1411],{"type":29,"value":1404},"Art+Logic frames debt more broadly: it can accumulate in product decisions, design patterns, development processes, and company culture. Product debt shows up as feature bloat or unvalidated assumptions. Design debt appears in inconsistent workflows and confusing interfaces. Process debt builds when teams skip documentation, testing, or clear specs. Cultural debt emerges when organizations consistently reward speed over sustainability. (",{"type":24,"tag":99,"props":1406,"children":1409},{"href":1407,"rel":1408},"https://artandlogic.com/newsletters/tech-debt-isnt-just-technical/",[103],[1410],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1413,"children":1414},{},[1415],{"type":29,"value":1416},"Legacy software tends to amplify all of these.",{"type":24,"tag":25,"props":1418,"children":1419},{},[1420],{"type":29,"value":1421},"A confusing internal tool leads to more training and support. A fragmented customer experience erodes trust. A weak release process creates firefighting. A culture of “just patch it” trains people to accept instability as normal.",{"type":24,"tag":25,"props":1423,"children":1424},{},[1425],{"type":29,"value":1426},"The hidden cost is not just technical complexity. It is organizational drag.",{"type":24,"tag":51,"props":1428,"children":1430},{"id":1429},"talent-gets-harder-to-hire-keep-and-ramp-up",[1431],{"type":29,"value":1432},"Talent Gets Harder to Hire, Keep, and Ramp Up",{"type":24,"tag":25,"props":1434,"children":1435},{},[1436],{"type":29,"value":1437},"Developers generally understand that every production system has a history, and they do not expect perfection. But there is a difference between a mature system and a hostile one.",{"type":24,"tag":25,"props":1439,"children":1440},{},[1441],{"type":29,"value":1442},"When a codebase is difficult to understand, painful to test, risky to deploy, or built on technologies few people want to work with, hiring becomes harder, and retention can suffer. New team members take longer to become productive. Senior engineers spend more time explaining landmines than improving architecture.",{"type":24,"tag":25,"props":1444,"children":1445},{},[1446,1448,1453],{"type":29,"value":1447},"Art+Logic calls talent friction a modernization warning sign: skilled developers want to work on modern systems, and a dated stack can limit the hiring pool while increasing churn risk. (",{"type":24,"tag":99,"props":1449,"children":1451},{"href":1229,"rel":1450},[103],[1452],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1455,"children":1456},{},[1457],{"type":29,"value":1458},"This is one of the most underestimated legacy costs. It does not always appear as a line item called “legacy software expense.” It appears as longer onboarding, lower morale, slower delivery, and valuable engineers spending their creativity on survival instead of progress.",{"type":24,"tag":51,"props":1460,"children":1462},{"id":1461},"customer-experience-starts-falling-behind",[1463],{"type":29,"value":1464},"Customer Experience Starts Falling Behind",{"type":24,"tag":25,"props":1466,"children":1467},{},[1468],{"type":29,"value":1469},"Legacy systems often expose their age through the customer experience.",{"type":24,"tag":25,"props":1471,"children":1472},{},[1473],{"type":29,"value":1474},"Maybe the interface feels dated. Maybe workflows require unnecessary steps. Maybe performance is inconsistent. Maybe customers cannot self-serve because the system was never designed for that. Maybe competitors are shipping better digital experiences faster because their architecture makes change easier.",{"type":24,"tag":25,"props":1476,"children":1477},{},[1478],{"type":29,"value":1479},"This is where legacy software becomes a strategic constraint.",{"type":24,"tag":25,"props":1481,"children":1482},{},[1483],{"type":29,"value":1484},"The problem is not that the system is old. The problem is that it limits the company’s ability to meet current expectations.",{"type":24,"tag":25,"props":1486,"children":1487},{},[1488,1490,1495],{"type":29,"value":1489},"A system built for one stage of the business may not support the next one. To put it plainly, the systems built when a company was scrappy will not necessarily support the company it is becoming. (",{"type":24,"tag":99,"props":1491,"children":1493},{"href":1229,"rel":1492},[103],[1494],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1497,"children":1498},{},[1499],{"type":29,"value":1500},"That gap can affect retention, sales, support costs, and brand trust. Customers may not know or care what technology powers the experience. They just feel the friction.",{"type":24,"tag":51,"props":1502,"children":1504},{"id":1503},"full-rewrites-can-become-their-own-hidden-cost",[1505],{"type":29,"value":1506},"Full Rewrites Can Become Their Own Hidden Cost",{"type":24,"tag":25,"props":1508,"children":1509},{},[1510],{"type":29,"value":1511},"When legacy pain becomes severe, the instinct is often to start over.",{"type":24,"tag":25,"props":1513,"children":1514},{},[1515,1517,1522],{"type":29,"value":1516},"A full rewrite is appealing because it promises a clean architecture, a modern stack, and freedom from years of accumulated compromises. But rewrites often underestimate how much business knowledge is embedded in the existing system. As teams rebuild, they discover undocumented workflows, edge cases, reporting needs, and integrations that were not included in the original plan. Costs rise, timelines stretch, and confidence erodes. (",{"type":24,"tag":99,"props":1518,"children":1520},{"href":1179,"rel":1519},[103],[1521],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1524,"children":1525},{},[1526],{"type":29,"value":1527},"That does not mean replacement is never the right call. Sometimes it is.",{"type":24,"tag":25,"props":1529,"children":1530},{},[1531,1533,1538],{"type":29,"value":1532},"But modernization should start with understanding, not demolition. The first step is rarely writing new code. It is figuring out what the current system actually does, what business value it preserves, which parts are still useful, and which parts are creating drag. (",{"type":24,"tag":99,"props":1534,"children":1536},{"href":1179,"rel":1535},[103],[1537],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1540,"children":1541},{},[1542],{"type":29,"value":1543},"A legacy system is not one thing. It is a collection of assets, risks, dependencies, and assumptions. Some parts should be refactored. Some should be rebuilt. Some should be retired. Some may be worth keeping exactly as they are.",{"type":24,"tag":51,"props":1545,"children":1547},{"id":1546},"modernization-does-not-have-to-mean-disruption",[1548],{"type":29,"value":1549},"Modernization Does Not Have to Mean Disruption",{"type":24,"tag":25,"props":1551,"children":1552},{},[1553],{"type":29,"value":1554},"One reason companies delay modernization is fear.",{"type":24,"tag":25,"props":1556,"children":1557},{},[1558],{"type":29,"value":1559},"They worry that updating a legacy system will interrupt operations, overwhelm internal teams, frustrate customers, or turn into an open-ended rebuild. That fear is understandable. Many legacy systems support critical workflows, and a careless modernization effort can create real disruption.",{"type":24,"tag":25,"props":1561,"children":1562},{},[1563],{"type":29,"value":1564},"But the alternative is not “do nothing.”",{"type":24,"tag":25,"props":1566,"children":1567},{},[1568,1570,1576],{"type":29,"value":1569},"At Art+Logic, we emphasize incremental modernization: progress can happen one piece at a time, lowering risk, preserving continuity, and giving teams room to adapt as systems evolve. (",{"type":24,"tag":99,"props":1571,"children":1574},{"href":1572,"rel":1573},"https://artandlogic.com/newsletters/legacy-software-modernization-transforming-without-disruption/",[103],[1575],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1578,"children":1579},{},[1580],{"type":29,"value":1581},"Practical approaches include:",{"type":24,"tag":266,"props":1583,"children":1584},{},[1585,1590,1595,1600,1605],{"type":24,"tag":270,"props":1586,"children":1587},{},[1588],{"type":29,"value":1589},"Decoupling high-friction modules instead of demolishing the entire system.",{"type":24,"tag":270,"props":1591,"children":1592},{},[1593],{"type":29,"value":1594},"Running old and new systems in parallel while production workloads shift gradually.",{"type":24,"tag":270,"props":1596,"children":1597},{},[1598],{"type":29,"value":1599},"Using short-term patching alongside long-term planning when immediate fixes are unavoidable.",{"type":24,"tag":270,"props":1601,"children":1602},{},[1603],{"type":29,"value":1604},"Mothballing defunct systems that no longer serve the business.",{"type":24,"tag":270,"props":1606,"children":1607},{},[1608,1610,1615],{"type":29,"value":1609},"Creating shared infrastructure when old and new systems need to coexist for a period of time. (",{"type":24,"tag":99,"props":1611,"children":1613},{"href":1300,"rel":1612},[103],[1614],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1617,"children":1618},{},[1619],{"type":29,"value":1620},"The best modernization work protects what matters while removing what slows the business down.",{"type":24,"tag":51,"props":1622,"children":1624},{"id":1623},"how-to-start-quantifying-the-hidden-costs",[1625],{"type":29,"value":1626},"How to Start Quantifying the Hidden Costs",{"type":24,"tag":25,"props":1628,"children":1629},{},[1630],{"type":29,"value":1631},"You do not need a perfect model to start making better decisions. You need visibility.",{"type":24,"tag":25,"props":1633,"children":1634},{},[1635],{"type":29,"value":1636},"Begin by looking for places where the system is already costing the business more than it should:",{"type":24,"tag":266,"props":1638,"children":1639},{},[1640,1645,1650,1655,1660,1665,1670,1675],{"type":24,"tag":270,"props":1641,"children":1642},{},[1643],{"type":29,"value":1644},"How long does it take to ship a small change?",{"type":24,"tag":270,"props":1646,"children":1647},{},[1648],{"type":29,"value":1649},"How much engineering time goes to maintenance, incidents, and rework?",{"type":24,"tag":270,"props":1651,"children":1652},{},[1653],{"type":29,"value":1654},"Which features have been delayed because the architecture cannot support them?",{"type":24,"tag":270,"props":1656,"children":1657},{},[1658],{"type":29,"value":1659},"Which workflows depend on manual intervention or undocumented knowledge?",{"type":24,"tag":270,"props":1661,"children":1662},{},[1663],{"type":29,"value":1664},"Where do integrations break most often?",{"type":24,"tag":270,"props":1666,"children":1667},{},[1668],{"type":29,"value":1669},"How long does it take new engineers to become productive?",{"type":24,"tag":270,"props":1671,"children":1672},{},[1673],{"type":29,"value":1674},"Which compliance, security, or audit needs are painful to address?",{"type":24,"tag":270,"props":1676,"children":1677},{},[1678],{"type":29,"value":1679},"Where are customers or internal users creating workarounds?",{"type":24,"tag":25,"props":1681,"children":1682},{},[1683],{"type":29,"value":1684},"This exercise often reveals that the cost of legacy software is not a single dramatic failure. It is a pattern of small penalties paid every week.",{"type":24,"tag":25,"props":1686,"children":1687},{},[1688],{"type":29,"value":1689},"Once those costs are visible, the modernization conversation changes. Instead of debating whether the system is “old,” teams can prioritize the areas where change will create the most business value.",{"type":24,"tag":51,"props":1691,"children":1693},{"id":1692},"the-goal-is-not-new-software-it-is-future-optionality",[1694],{"type":29,"value":1695},"The Goal Is Not New Software. It Is Future Optionality.",{"type":24,"tag":25,"props":1697,"children":1698},{},[1699],{"type":29,"value":1700},"Modernization is not about replacing the past for its own sake.",{"type":24,"tag":25,"props":1702,"children":1703},{},[1704,1706,1711],{"type":29,"value":1705},"It is about creating a foundation that can support what comes next. That might mean faster releases, better reliability, improved compliance, stronger integrations, AI readiness, better customer experiences, or new revenue opportunities. We describe successful modernization as controlled evolution: preserving operational stability while removing the constraints that keep the business from adapting. (",{"type":24,"tag":99,"props":1707,"children":1709},{"href":1179,"rel":1708},[103],[1710],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1713,"children":1714},{},[1715,1717,1722],{"type":29,"value":1716},"Refactoring fits the same pattern. Done well, it is not polishing code for aesthetic reasons. It improves modularity, removes brittle dependencies, clarifies intent, makes systems easier to test, and helps teams move with confidence. The ROI shows up in faster time-to-market, lower long-term costs, better scalability, improved reliability and security, and happier, more effective teams. (",{"type":24,"tag":99,"props":1718,"children":1720},{"href":1257,"rel":1719},[103],[1721],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":1724,"children":1725},{},[1726],{"type":29,"value":1727},"Legacy software becomes expensive when it limits choice.",{"type":24,"tag":25,"props":1729,"children":1730},{},[1731],{"type":29,"value":1732},"The sooner you understand where those limits are, the more options you have. You can refactor instead of rewrite. Replace one workflow instead of the whole platform. Stabilize risky areas before they fail. Preserve valuable business logic while modernizing the architecture around it.",{"type":24,"tag":25,"props":1734,"children":1735},{},[1736],{"type":29,"value":1737},"The hidden costs of legacy software are real. But they are not inevitable.",{"type":24,"tag":25,"props":1739,"children":1740},{},[1741],{"type":29,"value":1742},"With the right strategy, modernization becomes less about escaping old code and more about giving the business room to move again.",{"type":24,"tag":51,"props":1744,"children":1745},{"id":1028},[1746],{"type":29,"value":1031},{"type":24,"tag":1033,"props":1748,"children":1750},{"id":1749},"what-are-the-hidden-costs-of-legacy-software",[1751],{"type":29,"value":1752},"What are the hidden costs of legacy software?",{"type":24,"tag":25,"props":1754,"children":1755},{},[1756],{"type":29,"value":1757},"The hidden costs include slower development, higher maintenance effort, operational risk, security and compliance exposure, integration problems, employee frustration, customer experience issues, and missed opportunities for growth.",{"type":24,"tag":1033,"props":1759,"children":1761},{"id":1760},"how-do-you-know-if-a-legacy-system-is-holding-your-business-back",[1762],{"type":29,"value":1763},"How do you know if a legacy system is holding your business back?",{"type":24,"tag":25,"props":1765,"children":1766},{},[1767],{"type":29,"value":1768},"Common signs include slow deployments, long QA cycles, recurring bugs, difficulty hiring developers, fragile integrations, compliance headaches, and features that are delayed because the system cannot support them.",{"type":24,"tag":1033,"props":1770,"children":1772},{"id":1771},"is-refactoring-better-than-replacing-legacy-software",[1773],{"type":29,"value":1774},"Is refactoring better than replacing legacy software?",{"type":24,"tag":25,"props":1776,"children":1777},{},[1778],{"type":29,"value":1779},"Not always, but refactoring is often the smarter first step. It can reduce risk, improve maintainability, and restore development speed without the disruption of a full rewrite.",{"type":24,"tag":1033,"props":1781,"children":1783},{"id":1782},"why-are-full-rewrites-risky",[1784],{"type":29,"value":1785},"Why are full rewrites risky?",{"type":24,"tag":25,"props":1787,"children":1788},{},[1789],{"type":29,"value":1790},"Full rewrites often underestimate the amount of business logic, edge cases, workflows, and integrations embedded in the existing system. That can lead to longer timelines, higher costs, and missed requirements.",{"type":24,"tag":1033,"props":1792,"children":1794},{"id":1793},"how-should-a-company-start-modernizing-legacy-software",[1795],{"type":29,"value":1796},"How should a company start modernizing legacy software?",{"type":24,"tag":25,"props":1798,"children":1799},{},[1800],{"type":29,"value":1801},"Start by understanding what the system actually does, where it creates the most friction, and which parts are valuable versus risky. From there, prioritize incremental improvements that reduce business impact while preserving operational continuity.",{"title":8,"searchDepth":1122,"depth":1122,"links":1803},[1804,1805,1806,1807,1808,1809,1810,1811,1812,1813,1814,1815,1816],{"id":1203,"depth":1122,"text":1206},{"id":1241,"depth":1122,"text":1244},{"id":1274,"depth":1122,"text":1277},{"id":1312,"depth":1122,"text":1315},{"id":1354,"depth":1122,"text":1357},{"id":1391,"depth":1122,"text":1394},{"id":1429,"depth":1122,"text":1432},{"id":1461,"depth":1122,"text":1464},{"id":1503,"depth":1122,"text":1506},{"id":1546,"depth":1122,"text":1549},{"id":1623,"depth":1122,"text":1626},{"id":1692,"depth":1122,"text":1695},{"id":1028,"depth":1122,"text":1031,"children":1817},[1818,1819,1820,1821,1822],{"id":1749,"depth":1142,"text":1752},{"id":1760,"depth":1142,"text":1763},{"id":1771,"depth":1142,"text":1774},{"id":1782,"depth":1142,"text":1785},{"id":1793,"depth":1142,"text":1796},"content:cperez:2026-07-02:hidden-costs-of-legacy-software.md","cperez/2026-07-02/hidden-costs-of-legacy-software.md","cperez/2026-07-02/hidden-costs-of-legacy-software",{"_path":1827,"_dir":1828,"_draft":7,"_partial":7,"_locale":8,"title":1829,"description":1830,"publishDate":1831,"image":1832,"author":1833,"tags":1834,"excerpt":1830,"body":1838,"_type":1150,"_id":2785,"_source":1152,"_file":2786,"_stem":2787,"_extension":1155},"/cperez/2026-07-09/5-rs-application-modernization-legacy-software","2026-07-09","Art+Logic’s 5 Rs of Application Modernization: How to Choose the Right Path for Legacy Software","Legacy software creates a strange kind of tension.","2026-07-01","/cperez/2026-07-09/img/5-rs-application-modernization-legacy-software.jpg",{"name":13,"user":14},[1835,1836,16,1837],"5-rs","legacy","application modernization",{"type":21,"children":1839,"toc":2760},[1840,1844,1849,1854,1859,1864,1878,1884,1889,1894,1899,1904,1909,1915,1920,1949,1954,1959,1965,1970,1975,1980,2008,2013,2018,2023,2029,2034,2039,2044,2077,2082,2087,2093,2098,2103,2108,2113,2141,2146,2151,2156,2162,2167,2172,2177,2182,2225,2230,2235,2240,2245,2250,2255,2261,2266,2271,2276,2281,2319,2324,2329,2334,2339,2345,2350,2356,2361,2366,2371,2377,2382,2387,2392,2398,2403,2408,2413,2419,2424,2429,2434,2440,2445,2450,2455,2460,2465,2503,2508,2513,2518,2524,2529,2650,2655,2660,2666,2671,2676,2681,2686,2691,2696,2701,2705,2711,2716,2722,2727,2733,2738,2744,2749,2755],{"type":24,"tag":25,"props":1841,"children":1842},{},[1843],{"type":29,"value":1830},{"type":24,"tag":25,"props":1845,"children":1846},{},[1847],{"type":29,"value":1848},"On one hand, it may be slow, brittle, expensive to maintain, hard to integrate, difficult to hire for, or increasingly risky from a security and compliance standpoint. On the other hand, it probably exists for a reason. It runs the workflows your business depends on. It contains years of operational knowledge. It encodes decisions, edge cases, user expectations, and business logic that may not be documented anywhere else.",{"type":24,"tag":25,"props":1850,"children":1851},{},[1852],{"type":29,"value":1853},"That’s why application modernization is rarely as simple as “rewrite it” or “move it to the cloud.”",{"type":24,"tag":25,"props":1855,"children":1856},{},[1857],{"type":29,"value":1858},"The common “5 Rs” framework can be useful, but only if you treat it as a decision model, not a menu of buzzwords. The right modernization path depends on what the system does, where the risk lives, how much business value the current software still provides, and what future you need it to support.",{"type":24,"tag":25,"props":1860,"children":1861},{},[1862],{"type":29,"value":1863},"At Art+Logic, we’ve spent more than 30 years designing, building, rescuing, and modernizing custom software. Our view is simple: the best modernization strategy is the one that improves the system without losing what made it valuable in the first place.",{"type":24,"tag":25,"props":1865,"children":1866},{},[1867,1869,1876],{"type":29,"value":1868},"For organizations evaluating ",{"type":24,"tag":99,"props":1870,"children":1873},{"href":1871,"rel":1872},"https://artandlogic.com/modernizing-legacy-software/",[103],[1874],{"type":29,"value":1875},"legacy software modernization",{"type":29,"value":1877},", the 5 Rs are a helpful starting point. But choosing among them requires more than a technical inventory. It requires judgment.",{"type":24,"tag":51,"props":1879,"children":1881},{"id":1880},"first-modernization-starts-with-understanding",[1882],{"type":29,"value":1883},"First: Modernization Starts With Understanding",{"type":24,"tag":25,"props":1885,"children":1886},{},[1887],{"type":29,"value":1888},"Before choosing a path, you need to understand what you actually have.",{"type":24,"tag":25,"props":1890,"children":1891},{},[1892],{"type":29,"value":1893},"That sounds obvious until you’re inside a legacy system that has been evolving for 10, 15, or 25 years. Business rules may be buried in code. Integrations may depend on undocumented behavior. A “weird” workflow may exist because a key customer, regulator, or operational team depends on it. A report no one wants to touch may drive executive decisions every Monday morning.",{"type":24,"tag":25,"props":1895,"children":1896},{},[1897],{"type":29,"value":1898},"This is where many modernization projects go sideways. They start by asking, “What technology should we move to?” when the better first question is, “What value does this system provide, and where is it holding us back?”",{"type":24,"tag":25,"props":1900,"children":1901},{},[1902],{"type":29,"value":1903},"That distinction matters.",{"type":24,"tag":25,"props":1905,"children":1906},{},[1907],{"type":29,"value":1908},"Modernization should not preserve every old technical decision. It should preserve the business value those decisions created while removing the constraints that prevent the organization from moving forward.",{"type":24,"tag":51,"props":1910,"children":1912},{"id":1911},"our-5-rs-of-application-modernization",[1913],{"type":29,"value":1914},"Our 5 Rs of Application Modernization",{"type":24,"tag":25,"props":1916,"children":1917},{},[1918],{"type":29,"value":1919},"Different companies define the Rs differently. Some versions come from cloud migration. Others are adapted for enterprise architecture or application portfolio planning. For legacy software, we find the most practical version is this:",{"type":24,"tag":1921,"props":1922,"children":1923},"ol",{},[1924,1929,1934,1939,1944],{"type":24,"tag":270,"props":1925,"children":1926},{},[1927],{"type":29,"value":1928},"Retain",{"type":24,"tag":270,"props":1930,"children":1931},{},[1932],{"type":29,"value":1933},"Retire",{"type":24,"tag":270,"props":1935,"children":1936},{},[1937],{"type":29,"value":1938},"Rehost or Replatform",{"type":24,"tag":270,"props":1940,"children":1941},{},[1942],{"type":29,"value":1943},"Refactor or Rearchitect",{"type":24,"tag":270,"props":1945,"children":1946},{},[1947],{"type":29,"value":1948},"Rebuild or Replace",{"type":24,"tag":25,"props":1950,"children":1951},{},[1952],{"type":29,"value":1953},"Each path has a place. The mistake is assuming one of them is inherently more modern than the others.",{"type":24,"tag":25,"props":1955,"children":1956},{},[1957],{"type":29,"value":1958},"Sometimes the smartest move is to rebuild. Sometimes it’s to refactor a critical module. Sometimes it’s to leave a stable system alone and focus resources elsewhere. Good modernization is not about changing everything. It’s about changing the right things in the right order.",{"type":24,"tag":51,"props":1960,"children":1962},{"id":1961},"_1-retain-keep-what-still-works",[1963],{"type":29,"value":1964},"1. Retain: Keep What Still Works",{"type":24,"tag":25,"props":1966,"children":1967},{},[1968],{"type":29,"value":1969},"Retaining a legacy application may not sound like modernization, but sometimes it is the right decision.",{"type":24,"tag":25,"props":1971,"children":1972},{},[1973],{"type":29,"value":1974},"Not all legacy software is broken. Some systems are old but stable. They may run a narrow business process, serve a small internal audience, or perform reliably with minimal maintenance. Replacing them too soon can create more risk than value.",{"type":24,"tag":25,"props":1976,"children":1977},{},[1978],{"type":29,"value":1979},"Retain is the right path when:",{"type":24,"tag":266,"props":1981,"children":1982},{},[1983,1988,1993,1998,2003],{"type":24,"tag":270,"props":1984,"children":1985},{},[1986],{"type":29,"value":1987},"The system is stable and low-risk",{"type":24,"tag":270,"props":1989,"children":1990},{},[1991],{"type":29,"value":1992},"Maintenance costs are predictable",{"type":24,"tag":270,"props":1994,"children":1995},{},[1996],{"type":29,"value":1997},"The business process is not changing significantly",{"type":24,"tag":270,"props":1999,"children":2000},{},[2001],{"type":29,"value":2002},"The application has limited integration, security, or compliance exposure",{"type":24,"tag":270,"props":2004,"children":2005},{},[2006],{"type":29,"value":2007},"Modernizing it would distract from higher-priority work",{"type":24,"tag":25,"props":2009,"children":2010},{},[2011],{"type":29,"value":2012},"The key is that “retain” should be an active decision, not neglect in disguise.",{"type":24,"tag":25,"props":2014,"children":2015},{},[2016],{"type":29,"value":2017},"If you choose to keep a system, document why. Identify what would cause you to revisit the decision. Monitor risk factors like unsupported dependencies, aging infrastructure, security exposure, vendor end-of-life timelines, and the availability of people who still understand the system.",{"type":24,"tag":25,"props":2019,"children":2020},{},[2021],{"type":29,"value":2022},"A retained application still needs stewardship. Otherwise, today’s reasonable decision can become tomorrow’s emergency.",{"type":24,"tag":51,"props":2024,"children":2026},{"id":2025},"_2-retire-remove-what-no-longer-creates-value",[2027],{"type":29,"value":2028},"2. Retire: Remove What No Longer Creates Value",{"type":24,"tag":25,"props":2030,"children":2031},{},[2032],{"type":29,"value":2033},"Some legacy systems are not worth modernizing.",{"type":24,"tag":25,"props":2035,"children":2036},{},[2037],{"type":29,"value":2038},"They may support obsolete processes, duplicate newer tools, or exist only because no one has taken the time to shut them down safely. In those cases, retirement can be the highest-ROI modernization move available.",{"type":24,"tag":25,"props":2040,"children":2041},{},[2042],{"type":29,"value":2043},"Retirement is not simply turning something off. It often requires careful discovery:",{"type":24,"tag":266,"props":2045,"children":2046},{},[2047,2052,2057,2062,2067,2072],{"type":24,"tag":270,"props":2048,"children":2049},{},[2050],{"type":29,"value":2051},"Who still uses the system?",{"type":24,"tag":270,"props":2053,"children":2054},{},[2055],{"type":29,"value":2056},"What data needs to be archived?",{"type":24,"tag":270,"props":2058,"children":2059},{},[2060],{"type":29,"value":2061},"Are there downstream dependencies?",{"type":24,"tag":270,"props":2063,"children":2064},{},[2065],{"type":29,"value":2066},"Are there compliance or audit requirements?",{"type":24,"tag":270,"props":2068,"children":2069},{},[2070],{"type":29,"value":2071},"Does another system need to absorb part of the workflow?",{"type":24,"tag":270,"props":2073,"children":2074},{},[2075],{"type":29,"value":2076},"What communication and training will users need?",{"type":24,"tag":25,"props":2078,"children":2079},{},[2080],{"type":29,"value":2081},"This is where a legacy portfolio can surprise you. A system that appears unused may still generate a monthly export for finance. A database that seems obsolete may contain historical records required for compliance. A dusty internal tool may be the only place a support team can look up a specific customer scenario.",{"type":24,"tag":25,"props":2083,"children":2084},{},[2085],{"type":29,"value":2086},"Retirement works best when it is deliberate. The goal is not just to remove old software. It is to reduce complexity without breaking an invisible process the business still depends on.",{"type":24,"tag":51,"props":2088,"children":2090},{"id":2089},"_3-rehost-or-replatform-move-the-system-to-a-better-foundation",[2091],{"type":29,"value":2092},"3. Rehost or Replatform: Move the System to a Better Foundation",{"type":24,"tag":25,"props":2094,"children":2095},{},[2096],{"type":29,"value":2097},"Rehosting and replatforming are often grouped together, but they are not exactly the same.",{"type":24,"tag":25,"props":2099,"children":2100},{},[2101],{"type":29,"value":2102},"Rehosting usually means moving an application to new infrastructure with minimal code changes. Think of moving from on-premises servers to cloud infrastructure. Replatforming goes a step further by making targeted changes so the application can run more efficiently or reliably on a new platform.",{"type":24,"tag":25,"props":2104,"children":2105},{},[2106],{"type":29,"value":2107},"This path can make sense when the application still provides value, but the environment around it is becoming a problem.",{"type":24,"tag":25,"props":2109,"children":2110},{},[2111],{"type":29,"value":2112},"Choose this path when:",{"type":24,"tag":266,"props":2114,"children":2115},{},[2116,2121,2126,2131,2136],{"type":24,"tag":270,"props":2117,"children":2118},{},[2119],{"type":29,"value":2120},"Infrastructure is expensive, fragile, or hard to support",{"type":24,"tag":270,"props":2122,"children":2123},{},[2124],{"type":29,"value":2125},"The application needs better scalability or uptime",{"type":24,"tag":270,"props":2127,"children":2128},{},[2129],{"type":29,"value":2130},"Hardware or hosting environments are nearing end of life",{"type":24,"tag":270,"props":2132,"children":2133},{},[2134],{"type":29,"value":2135},"Cloud migration would reduce operational burden",{"type":24,"tag":270,"props":2137,"children":2138},{},[2139],{"type":29,"value":2140},"You need a safer first step before deeper modernization",{"type":24,"tag":25,"props":2142,"children":2143},{},[2144],{"type":29,"value":2145},"Rehosting or replatforming can reduce risk, improve reliability, and create room for future work. But it is not a cure-all.",{"type":24,"tag":25,"props":2147,"children":2148},{},[2149],{"type":29,"value":2150},"Moving a brittle system to modern infrastructure does not automatically make the codebase healthier. A cloud migration can improve operations while leaving product debt, design debt, process debt, and architectural constraints untouched.",{"type":24,"tag":25,"props":2152,"children":2153},{},[2154],{"type":29,"value":2155},"That is not a reason to avoid it. It is a reason to be honest about what this path solves and what it does not.",{"type":24,"tag":51,"props":2157,"children":2159},{"id":2158},"_4-refactor-or-rearchitect-improve-the-system-without-starting-over",[2160],{"type":29,"value":2161},"4. Refactor or Rearchitect: Improve the System Without Starting Over",{"type":24,"tag":25,"props":2163,"children":2164},{},[2165],{"type":29,"value":2166},"Refactoring is one of the most misunderstood modernization paths.",{"type":24,"tag":25,"props":2168,"children":2169},{},[2170],{"type":29,"value":2171},"It does not mean rewriting the application from scratch. It means improving the internal structure of the system while preserving its essential behavior. Rearchitecting goes deeper, changing how major parts of the system are organized so it can support new scale, features, integrations, or operating models.",{"type":24,"tag":25,"props":2173,"children":2174},{},[2175],{"type":29,"value":2176},"This is often the sweet spot for legacy modernization.",{"type":24,"tag":25,"props":2178,"children":2179},{},[2180],{"type":29,"value":2181},"Refactor or rearchitect when:",{"type":24,"tag":266,"props":2183,"children":2184},{},[2185,2190,2195,2200,2205,2210,2215,2220],{"type":24,"tag":270,"props":2186,"children":2187},{},[2188],{"type":29,"value":2189},"Small changes take too long",{"type":24,"tag":270,"props":2191,"children":2192},{},[2193],{"type":29,"value":2194},"Developers avoid parts of the codebase",{"type":24,"tag":270,"props":2196,"children":2197},{},[2198],{"type":29,"value":2199},"Bugs keep returning after they are “fixed”",{"type":24,"tag":270,"props":2201,"children":2202},{},[2203],{"type":29,"value":2204},"New hires need months to become productive",{"type":24,"tag":270,"props":2206,"children":2207},{},[2208],{"type":29,"value":2209},"Integrations are painful",{"type":24,"tag":270,"props":2211,"children":2212},{},[2213],{"type":29,"value":2214},"Testing is weak or inconsistent",{"type":24,"tag":270,"props":2216,"children":2217},{},[2218],{"type":29,"value":2219},"Security and dependency updates are risky",{"type":24,"tag":270,"props":2221,"children":2222},{},[2223],{"type":29,"value":2224},"The system works, but every improvement feels harder than it should",{"type":24,"tag":25,"props":2226,"children":2227},{},[2228],{"type":29,"value":2229},"This is where the ROI of modernization becomes visible.",{"type":24,"tag":25,"props":2231,"children":2232},{},[2233],{"type":29,"value":2234},"Old code quietly taxes the business. Releases slow down. QA cycles stretch. Engineers spend more time avoiding regressions than shipping value. Customer requests pile up behind architectural limitations. Strong developers become frustrated by a system that fights them at every step.",{"type":24,"tag":25,"props":2236,"children":2237},{},[2238],{"type":29,"value":2239},"Refactoring pays that debt down strategically. It clarifies intent, improves modularity, removes brittle dependencies, strengthens test coverage, and makes the application easier to reason about.",{"type":24,"tag":25,"props":2241,"children":2242},{},[2243],{"type":29,"value":2244},"The goal is not technical perfection. It is momentum.",{"type":24,"tag":25,"props":2246,"children":2247},{},[2248],{"type":29,"value":2249},"For many organizations, the right refactoring strategy is incremental. Isolate the highest-friction areas. Create seams in the architecture. Improve test coverage around critical behavior. Replace risky dependencies. Modernize the parts of the system that directly block business goals.",{"type":24,"tag":25,"props":2251,"children":2252},{},[2253],{"type":29,"value":2254},"That approach reduces risk because the current system can continue operating while the new foundation takes shape.",{"type":24,"tag":51,"props":2256,"children":2258},{"id":2257},"_5-rebuild-or-replace-start-fresh-when-the-current-system-cant-support-the-future",[2259],{"type":29,"value":2260},"5. Rebuild or Replace: Start Fresh When the Current System Can’t Support the Future",{"type":24,"tag":25,"props":2262,"children":2263},{},[2264],{"type":29,"value":2265},"Sometimes the old system has reached the end of its useful life.",{"type":24,"tag":25,"props":2267,"children":2268},{},[2269],{"type":29,"value":2270},"A rebuild or replacement may be the right path when the current application is fundamentally misaligned with where the business needs to go. Maybe the architecture cannot scale. Maybe the user experience is beyond incremental repair. Maybe the core platform is no longer supported. Maybe the application was built for a business model that no longer exists.",{"type":24,"tag":25,"props":2272,"children":2273},{},[2274],{"type":29,"value":2275},"This path can unlock major value, but it also carries the highest risk.",{"type":24,"tag":25,"props":2277,"children":2278},{},[2279],{"type":29,"value":2280},"Rebuild or replace when:",{"type":24,"tag":266,"props":2282,"children":2283},{},[2284,2289,2294,2299,2304,2309,2314],{"type":24,"tag":270,"props":2285,"children":2286},{},[2287],{"type":29,"value":2288},"The current architecture cannot support strategic goals",{"type":24,"tag":270,"props":2290,"children":2291},{},[2292],{"type":29,"value":2293},"Maintenance costs are unsustainable",{"type":24,"tag":270,"props":2295,"children":2296},{},[2297],{"type":29,"value":2298},"Critical dependencies are obsolete or unsupported",{"type":24,"tag":270,"props":2300,"children":2301},{},[2302],{"type":29,"value":2303},"Security or compliance risk is too high",{"type":24,"tag":270,"props":2305,"children":2306},{},[2307],{"type":29,"value":2308},"The UX needs more than cosmetic improvement",{"type":24,"tag":270,"props":2310,"children":2311},{},[2312],{"type":29,"value":2313},"Business workflows have changed dramatically",{"type":24,"tag":270,"props":2315,"children":2316},{},[2317],{"type":29,"value":2318},"Incremental modernization would cost more than a clean build",{"type":24,"tag":25,"props":2320,"children":2321},{},[2322],{"type":29,"value":2323},"The danger is assuming “new” automatically means “better.”",{"type":24,"tag":25,"props":2325,"children":2326},{},[2327],{"type":29,"value":2328},"Full rewrites often underestimate how much institutional knowledge lives in the current system. Teams discover edge cases late. Reports turn out to be more complex than expected. Integrations have hidden dependencies. Users rely on behaviors that were never documented.",{"type":24,"tag":25,"props":2330,"children":2331},{},[2332],{"type":29,"value":2333},"A successful rebuild needs more than a modern tech stack. It needs a migration strategy, stakeholder alignment, parallel operation where appropriate, data planning, testing discipline, and a clear understanding of what must be preserved.",{"type":24,"tag":25,"props":2335,"children":2336},{},[2337],{"type":29,"value":2338},"In many cases, the safest rebuild is not a big-bang replacement. It is a staged transition where old and new systems operate side by side while workloads move gradually.",{"type":24,"tag":51,"props":2340,"children":2342},{"id":2341},"how-to-choose-the-right-r",[2343],{"type":29,"value":2344},"How to Choose the Right R",{"type":24,"tag":25,"props":2346,"children":2347},{},[2348],{"type":29,"value":2349},"The right modernization path usually becomes clearer when you evaluate the system across four dimensions: business value, technical risk, operational disruption, and future fit.",{"type":24,"tag":1033,"props":2351,"children":2353},{"id":2352},"business-value",[2354],{"type":29,"value":2355},"Business value",{"type":24,"tag":25,"props":2357,"children":2358},{},[2359],{"type":29,"value":2360},"Start by asking what the system makes possible.",{"type":24,"tag":25,"props":2362,"children":2363},{},[2364],{"type":29,"value":2365},"Does it support revenue? Customer experience? Internal operations? Compliance? Reporting? Specialized workflows? Institutional knowledge?",{"type":24,"tag":25,"props":2367,"children":2368},{},[2369],{"type":29,"value":2370},"A high-value system deserves careful modernization. A low-value system may be a candidate for retirement. A system with hidden value needs discovery before any major decision is made.",{"type":24,"tag":1033,"props":2372,"children":2374},{"id":2373},"technical-risk",[2375],{"type":29,"value":2376},"Technical risk",{"type":24,"tag":25,"props":2378,"children":2379},{},[2380],{"type":29,"value":2381},"Look for the risks that are already accumulating.",{"type":24,"tag":25,"props":2383,"children":2384},{},[2385],{"type":29,"value":2386},"Outdated frameworks. Unsupported libraries. Security vulnerabilities. Aging infrastructure. Fragile deployments. Poor test coverage. Performance bottlenecks. Lack of documentation. A shrinking talent pool.",{"type":24,"tag":25,"props":2388,"children":2389},{},[2390],{"type":29,"value":2391},"Technical risk is not just an engineering concern. When it slows delivery, raises costs, or threatens reliability, it becomes a business issue.",{"type":24,"tag":1033,"props":2393,"children":2395},{"id":2394},"operational-disruption",[2396],{"type":29,"value":2397},"Operational disruption",{"type":24,"tag":25,"props":2399,"children":2400},{},[2401],{"type":29,"value":2402},"Modernization should not require the business to stop moving.",{"type":24,"tag":25,"props":2404,"children":2405},{},[2406],{"type":29,"value":2407},"Internal teams still need to support users. Customers still need service. Operations still need continuity. A technically elegant plan that creates unacceptable disruption is not a good plan.",{"type":24,"tag":25,"props":2409,"children":2410},{},[2411],{"type":29,"value":2412},"This is why incremental modernization is often more effective than rip-and-replace. It lets teams make progress while reducing the chance of a major operational shock.",{"type":24,"tag":1033,"props":2414,"children":2416},{"id":2415},"future-fit",[2417],{"type":29,"value":2418},"Future fit",{"type":24,"tag":25,"props":2420,"children":2421},{},[2422],{"type":29,"value":2423},"Finally, ask what the software needs to support next.",{"type":24,"tag":25,"props":2425,"children":2426},{},[2427],{"type":29,"value":2428},"Do you need AI readiness? Better data access? Cloud scalability? Modern APIs? Mobile capabilities? Faster feature delivery? More reliable compliance updates? A better user experience?",{"type":24,"tag":25,"props":2430,"children":2431},{},[2432],{"type":29,"value":2433},"The modernization path should be judged by what becomes possible afterward.",{"type":24,"tag":51,"props":2435,"children":2437},{"id":2436},"the-artlogic-difference-the-5-rs-are-not-a-shortcut-around-judgment",[2438],{"type":29,"value":2439},"The Art+Logic Difference: The 5 Rs Are Not a Shortcut Around Judgment",{"type":24,"tag":25,"props":2441,"children":2442},{},[2443],{"type":29,"value":2444},"The 5 Rs are useful, but they do not make the decision for you.",{"type":24,"tag":25,"props":2446,"children":2447},{},[2448],{"type":29,"value":2449},"That is where experience matters.",{"type":24,"tag":25,"props":2451,"children":2452},{},[2453],{"type":29,"value":2454},"After more than 30 years of custom software development, we have learned that legacy systems are rarely just old code. They are business systems. They carry history, constraints, workflows, and trade-offs. They also carry opportunity.",{"type":24,"tag":25,"props":2456,"children":2457},{},[2458],{"type":29,"value":2459},"Our approach is not to force every client into a full rewrite, a cloud migration, or a tool-driven transformation. We help determine what to keep, what to fix, what to modernize, and what to replace.",{"type":24,"tag":25,"props":2461,"children":2462},{},[2463],{"type":29,"value":2464},"That work often involves:",{"type":24,"tag":266,"props":2466,"children":2467},{},[2468,2473,2478,2483,2488,2493,2498],{"type":24,"tag":270,"props":2469,"children":2470},{},[2471],{"type":29,"value":2472},"Understanding the current system before changing it",{"type":24,"tag":270,"props":2474,"children":2475},{},[2476],{"type":29,"value":2477},"Preserving critical business logic",{"type":24,"tag":270,"props":2479,"children":2480},{},[2481],{"type":29,"value":2482},"Collaborating with internal IT teams instead of bypassing them",{"type":24,"tag":270,"props":2484,"children":2485},{},[2486],{"type":29,"value":2487},"Reducing disruption through phased delivery",{"type":24,"tag":270,"props":2489,"children":2490},{},[2491],{"type":29,"value":2492},"Aligning modernization decisions with business outcomes",{"type":24,"tag":270,"props":2494,"children":2495},{},[2496],{"type":29,"value":2497},"Using AI-assisted development where it accelerates safe, repeatable work",{"type":24,"tag":270,"props":2499,"children":2500},{},[2501],{"type":29,"value":2502},"Keeping experienced engineers in the loop for architecture, validation, testing, and quality",{"type":24,"tag":25,"props":2504,"children":2505},{},[2506],{"type":29,"value":2507},"AI has changed what is possible in modernization, especially for analysis, repetitive migration tasks, boilerplate conversion, and pattern-based refactoring. But AI is not a replacement for engineering judgment.",{"type":24,"tag":25,"props":2509,"children":2510},{},[2511],{"type":29,"value":2512},"Used carelessly, AI can produce code that compiles while removing important functionality. Used well, it becomes a force multiplier for experienced teams that know how to validate behavior, preserve logic, and maintain architectural consistency.",{"type":24,"tag":25,"props":2514,"children":2515},{},[2516],{"type":29,"value":2517},"That balance matters. Speed is valuable only when it does not create a new layer of risk.",{"type":24,"tag":51,"props":2519,"children":2521},{"id":2520},"a-practical-decision-guide",[2522],{"type":29,"value":2523},"A Practical Decision Guide",{"type":24,"tag":25,"props":2525,"children":2526},{},[2527],{"type":29,"value":2528},"Here is a simple way to think about the 5 Rs:",{"type":24,"tag":2530,"props":2531,"children":2532},"table",{},[2533,2557],{"type":24,"tag":2534,"props":2535,"children":2536},"thead",{},[2537],{"type":24,"tag":2538,"props":2539,"children":2540},"tr",{},[2541,2547,2552],{"type":24,"tag":2542,"props":2543,"children":2544},"th",{},[2545],{"type":29,"value":2546},"Modernization path",{"type":24,"tag":2542,"props":2548,"children":2549},{},[2550],{"type":29,"value":2551},"Best fit",{"type":24,"tag":2542,"props":2553,"children":2554},{},[2555],{"type":29,"value":2556},"Watch out for",{"type":24,"tag":2558,"props":2559,"children":2560},"tbody",{},[2561,2579,2596,2614,2632],{"type":24,"tag":2538,"props":2562,"children":2563},{},[2564,2569,2574],{"type":24,"tag":2565,"props":2566,"children":2567},"td",{},[2568],{"type":29,"value":1928},{"type":24,"tag":2565,"props":2570,"children":2571},{},[2572],{"type":29,"value":2573},"Stable systems with low risk and clear ongoing value",{"type":24,"tag":2565,"props":2575,"children":2576},{},[2577],{"type":29,"value":2578},"Passive neglect disguised as strategy",{"type":24,"tag":2538,"props":2580,"children":2581},{},[2582,2586,2591],{"type":24,"tag":2565,"props":2583,"children":2584},{},[2585],{"type":29,"value":1933},{"type":24,"tag":2565,"props":2587,"children":2588},{},[2589],{"type":29,"value":2590},"Obsolete, duplicative, or low-value systems",{"type":24,"tag":2565,"props":2592,"children":2593},{},[2594],{"type":29,"value":2595},"Hidden users, data, reports, or dependencies",{"type":24,"tag":2538,"props":2597,"children":2598},{},[2599,2604,2609],{"type":24,"tag":2565,"props":2600,"children":2601},{},[2602],{"type":29,"value":2603},"Rehost/Replatform",{"type":24,"tag":2565,"props":2605,"children":2606},{},[2607],{"type":29,"value":2608},"Valuable systems held back by infrastructure",{"type":24,"tag":2565,"props":2610,"children":2611},{},[2612],{"type":29,"value":2613},"Moving technical debt without reducing it",{"type":24,"tag":2538,"props":2615,"children":2616},{},[2617,2622,2627],{"type":24,"tag":2565,"props":2618,"children":2619},{},[2620],{"type":29,"value":2621},"Refactor/Rearchitect",{"type":24,"tag":2565,"props":2623,"children":2624},{},[2625],{"type":29,"value":2626},"Systems that work but slow delivery, scale, or reliability",{"type":24,"tag":2565,"props":2628,"children":2629},{},[2630],{"type":29,"value":2631},"Endless cleanup without business prioritization",{"type":24,"tag":2538,"props":2633,"children":2634},{},[2635,2640,2645],{"type":24,"tag":2565,"props":2636,"children":2637},{},[2638],{"type":29,"value":2639},"Rebuild/Replace",{"type":24,"tag":2565,"props":2641,"children":2642},{},[2643],{"type":29,"value":2644},"Systems that cannot support the future",{"type":24,"tag":2565,"props":2646,"children":2647},{},[2648],{"type":29,"value":2649},"Underestimating embedded business logic",{"type":24,"tag":25,"props":2651,"children":2652},{},[2653],{"type":29,"value":2654},"No single path is always right. Most organizations need a mix.",{"type":24,"tag":25,"props":2656,"children":2657},{},[2658],{"type":29,"value":2659},"A legacy portfolio might include one application to retire, one to rehost, one to refactor, and one to rebuild over time. The strategic work is sequencing those decisions so the business gains value without absorbing unnecessary risk.",{"type":24,"tag":51,"props":2661,"children":2663},{"id":2662},"modernization-is-controlled-evolution",[2664],{"type":29,"value":2665},"Modernization Is Controlled Evolution",{"type":24,"tag":25,"props":2667,"children":2668},{},[2669],{"type":29,"value":2670},"The best modernization efforts do not begin with a dramatic declaration that everything must change.",{"type":24,"tag":25,"props":2672,"children":2673},{},[2674],{"type":29,"value":2675},"They begin with a clear-eyed assessment.",{"type":24,"tag":25,"props":2677,"children":2678},{},[2679],{"type":29,"value":2680},"What still works? What is costing too much? What creates risk? What blocks growth? What needs to be preserved? What future should this system support?",{"type":24,"tag":25,"props":2682,"children":2683},{},[2684],{"type":29,"value":2685},"From there, the path becomes more practical.",{"type":24,"tag":25,"props":2687,"children":2688},{},[2689],{"type":29,"value":2690},"Retain what is stable. Retire what no longer serves the business. Rehost or replatform where infrastructure is the bottleneck. Refactor or rearchitect where the system needs to evolve. Rebuild or replace when the old foundation can no longer carry the future.",{"type":24,"tag":25,"props":2692,"children":2693},{},[2694],{"type":29,"value":2695},"Modernization is not about replacing the past. It is about creating a stronger foundation for what comes next.",{"type":24,"tag":25,"props":2697,"children":2698},{},[2699],{"type":29,"value":2700},"And done well, it does not have to disrupt the business to transform it.",{"type":24,"tag":51,"props":2702,"children":2703},{"id":1028},[2704],{"type":29,"value":1031},{"type":24,"tag":1033,"props":2706,"children":2708},{"id":2707},"what-are-the-5-rs-of-application-modernization",[2709],{"type":29,"value":2710},"What are the 5 Rs of application modernization?",{"type":24,"tag":25,"props":2712,"children":2713},{},[2714],{"type":29,"value":2715},"The 5 Rs of application modernization are commonly used paths for deciding what to do with legacy software: retain, retire, rehost or replatform, refactor or rearchitect, and rebuild or replace. The right choice depends on the system’s business value, technical risk, operational impact, and future requirements.",{"type":24,"tag":1033,"props":2717,"children":2719},{"id":2718},"is-refactoring-the-same-as-rewriting",[2720],{"type":29,"value":2721},"Is refactoring the same as rewriting?",{"type":24,"tag":25,"props":2723,"children":2724},{},[2725],{"type":29,"value":2726},"No. Refactoring improves the internal structure of existing software while preserving its behavior. Rewriting means rebuilding the application from scratch or replacing it with a new system. Refactoring is often a lower-risk modernization path when the current system still provides value but has become difficult to maintain or extend.",{"type":24,"tag":1033,"props":2728,"children":2730},{"id":2729},"when-should-a-company-rebuild-legacy-software",[2731],{"type":29,"value":2732},"When should a company rebuild legacy software?",{"type":24,"tag":25,"props":2734,"children":2735},{},[2736],{"type":29,"value":2737},"A rebuild may make sense when the existing system cannot support future business goals, has unsustainable maintenance costs, depends on obsolete technology, creates serious security or compliance risk, or requires user experience and architecture changes that cannot be solved incrementally.",{"type":24,"tag":1033,"props":2739,"children":2741},{"id":2740},"why-is-incremental-modernization-often-better-than-rip-and-replace",[2742],{"type":29,"value":2743},"Why is incremental modernization often better than rip-and-replace?",{"type":24,"tag":25,"props":2745,"children":2746},{},[2747],{"type":29,"value":2748},"Incremental modernization reduces disruption by allowing the current system to keep operating while targeted improvements are made. This approach helps preserve business continuity, validate decisions along the way, and reduce the risk of losing critical workflows or embedded business logic.",{"type":24,"tag":1033,"props":2750,"children":2752},{"id":2751},"how-can-ai-help-with-legacy-software-modernization",[2753],{"type":29,"value":2754},"How can AI help with legacy software modernization?",{"type":24,"tag":25,"props":2756,"children":2757},{},[2758],{"type":29,"value":2759},"AI can accelerate modernization by assisting with code analysis, repetitive migration work, boilerplate generation, and pattern-based refactoring. However, AI works best when experienced engineers guide the architecture, validate generated code, test behavior, and ensure critical business logic is preserved.",{"title":8,"searchDepth":1122,"depth":1122,"links":2761},[2762,2763,2764,2765,2766,2767,2768,2769,2775,2776,2777,2778],{"id":1880,"depth":1122,"text":1883},{"id":1911,"depth":1122,"text":1914},{"id":1961,"depth":1122,"text":1964},{"id":2025,"depth":1122,"text":2028},{"id":2089,"depth":1122,"text":2092},{"id":2158,"depth":1122,"text":2161},{"id":2257,"depth":1122,"text":2260},{"id":2341,"depth":1122,"text":2344,"children":2770},[2771,2772,2773,2774],{"id":2352,"depth":1142,"text":2355},{"id":2373,"depth":1142,"text":2376},{"id":2394,"depth":1142,"text":2397},{"id":2415,"depth":1142,"text":2418},{"id":2436,"depth":1122,"text":2439},{"id":2520,"depth":1122,"text":2523},{"id":2662,"depth":1122,"text":2665},{"id":1028,"depth":1122,"text":1031,"children":2779},[2780,2781,2782,2783,2784],{"id":2707,"depth":1142,"text":2710},{"id":2718,"depth":1142,"text":2721},{"id":2729,"depth":1142,"text":2732},{"id":2740,"depth":1142,"text":2743},{"id":2751,"depth":1142,"text":2754},"content:cperez:2026-07-09:5-rs-application-modernization-legacy-software.md","cperez/2026-07-09/5-rs-application-modernization-legacy-software.md","cperez/2026-07-09/5-rs-application-modernization-legacy-software",{"_path":2789,"_dir":2790,"_draft":7,"_partial":7,"_locale":8,"title":2791,"description":2792,"publishDate":2790,"image":2793,"author":2794,"tags":2795,"excerpt":2792,"body":2799,"_type":1150,"_id":4743,"_source":1152,"_file":4744,"_stem":4745,"_extension":1155},"/cperez/2026-06-30/how-ceos-should-evaluate-ai-investments","2026-06-30","How Should CEOs Evaluate AI Investments?","CEOs should evaluate AI investments by asking whether the investment improves a measurable business outcome, changes a real workflow, keeps humans appropriately involved, has a realistic path to production, and creates value that outweighs cost and risk.","/cperez/2026-06-30/img/how-ceos-should-evaluate-ai-investments.jpg",{"name":13,"user":14},[2796,2797,2798,16,18],"agentic ai","ai investment","humans in the loop",{"type":21,"children":2800,"toc":4709},[2801,2805,2818,2822,2827,2832,2838,2843,2977,2982,2988,2993,2998,3010,3022,3027,3032,3038,3043,3048,3053,3096,3101,3106,3111,3116,3121,3127,3132,3137,3260,3265,3270,3276,3281,3286,3291,3296,3301,3354,3359,3364,3374,3379,3385,3390,3395,3400,3405,3448,3453,3466,3472,3477,3482,3495,3500,3505,3558,3570,3575,3580,3586,3591,3596,3606,3611,3616,3621,3626,3632,3637,3642,3647,3656,3661,3666,3672,3677,3682,3687,3696,3701,3706,3711,3716,3722,3727,3740,3745,3750,3759,3764,3769,3775,3780,3785,3790,3883,3893,3898,3904,3909,3914,3927,3932,3937,3942,3947,3952,3962,3967,3973,3978,3983,3988,3993,4006,4011,4016,4069,4074,4079,4085,4090,4095,4100,4239,4244,4254,4264,4270,4275,4285,4295,4305,4315,4320,4325,4331,4336,4409,4414,4419,4425,4430,4498,4503,4509,4514,4519,4529,4539,4549,4554,4559,4564,4569,4575,4580,4585,4590,4595,4599,4605,4610,4616,4621,4627,4632,4638,4643,4649,4654,4660,4665,4671,4676,4682,4687,4693,4698,4704],{"type":24,"tag":25,"props":2802,"children":2803},{},[2804],{"type":29,"value":2792},{"type":24,"tag":25,"props":2806,"children":2807},{},[2808,2810,2816],{"type":29,"value":2809},"The best AI investments are not simply tool purchases; they are ",{"type":24,"tag":2811,"props":2812,"children":2813},"strong",{},[2814],{"type":29,"value":2815},"business capability investments",{"type":29,"value":2817},". That means the question is not just “Can AI do this?” It is: “Can we build, integrate, govern, and maintain an AI-enabled system that makes the business meaningfully better?”",{"type":24,"tag":25,"props":2819,"children":2820},{},[2821],{"type":29,"value":1903},{"type":24,"tag":25,"props":2823,"children":2824},{},[2825],{"type":29,"value":2826},"AI can summarize documents, draft content, analyze data, generate code, classify requests, and recommend next steps. But those capabilities do not become business value on their own. They become valuable when they are designed into real software systems, connected to real workflows, monitored by real people, and supported by engineers who understand what the system is doing and why.",{"type":24,"tag":25,"props":2828,"children":2829},{},[2830],{"type":29,"value":2831},"At Art+Logic, we think that distinction is critical. AI can accelerate parts of the software process, but it does not replace software engineering. Code generated with AI still needs architecture, review, testing, security, maintainability, documentation, and ownership. A model can suggest code, but it cannot be responsible for the code; that responsibility still belongs to people.",{"type":24,"tag":51,"props":2833,"children":2835},{"id":2834},"the-ceo-ai-investment-framework",[2836],{"type":29,"value":2837},"The CEO AI Investment Framework",{"type":24,"tag":25,"props":2839,"children":2840},{},[2841],{"type":29,"value":2842},"A practical AI investment review should cover six areas:",{"type":24,"tag":2530,"props":2844,"children":2845},{},[2846,2867],{"type":24,"tag":2534,"props":2847,"children":2848},{},[2849],{"type":24,"tag":2538,"props":2850,"children":2851},{},[2852,2857,2862],{"type":24,"tag":2542,"props":2853,"children":2854},{},[2855],{"type":29,"value":2856},"Evaluation Area",{"type":24,"tag":2542,"props":2858,"children":2859},{},[2860],{"type":29,"value":2861},"CEO Question",{"type":24,"tag":2542,"props":2863,"children":2864},{},[2865],{"type":29,"value":2866},"Why It Matters",{"type":24,"tag":2558,"props":2868,"children":2869},{},[2870,2887,2905,2923,2941,2959],{"type":24,"tag":2538,"props":2871,"children":2872},{},[2873,2877,2882],{"type":24,"tag":2565,"props":2874,"children":2875},{},[2876],{"type":29,"value":2355},{"type":24,"tag":2565,"props":2878,"children":2879},{},[2880],{"type":29,"value":2881},"What measurable outcome will improve?",{"type":24,"tag":2565,"props":2883,"children":2884},{},[2885],{"type":29,"value":2886},"AI should connect to revenue, cost, speed, quality, risk, or customer value.",{"type":24,"tag":2538,"props":2888,"children":2889},{},[2890,2895,2900],{"type":24,"tag":2565,"props":2891,"children":2892},{},[2893],{"type":29,"value":2894},"Workflow fit",{"type":24,"tag":2565,"props":2896,"children":2897},{},[2898],{"type":29,"value":2899},"What process changes if this succeeds?",{"type":24,"tag":2565,"props":2901,"children":2902},{},[2903],{"type":29,"value":2904},"AI creates value when it changes how work gets done, not when it sits beside existing work.",{"type":24,"tag":2538,"props":2906,"children":2907},{},[2908,2913,2918],{"type":24,"tag":2565,"props":2909,"children":2910},{},[2911],{"type":29,"value":2912},"Data readiness",{"type":24,"tag":2565,"props":2914,"children":2915},{},[2916],{"type":29,"value":2917},"Is the data accurate, accessible, secure, and usable?",{"type":24,"tag":2565,"props":2919,"children":2920},{},[2921],{"type":29,"value":2922},"Poor data quality can stop AI projects from scaling.",{"type":24,"tag":2538,"props":2924,"children":2925},{},[2926,2931,2936],{"type":24,"tag":2565,"props":2927,"children":2928},{},[2929],{"type":29,"value":2930},"Human oversight",{"type":24,"tag":2565,"props":2932,"children":2933},{},[2934],{"type":29,"value":2935},"Where do people need to review, approve, override, or understand AI output?",{"type":24,"tag":2565,"props":2937,"children":2938},{},[2939],{"type":29,"value":2940},"Humans need to stay accountable for high-impact decisions and production software.",{"type":24,"tag":2538,"props":2942,"children":2943},{},[2944,2949,2954],{"type":24,"tag":2565,"props":2945,"children":2946},{},[2947],{"type":29,"value":2948},"Governance and risk",{"type":24,"tag":2565,"props":2950,"children":2951},{},[2952],{"type":29,"value":2953},"What could go wrong, and who owns it?",{"type":24,"tag":2565,"props":2955,"children":2956},{},[2957],{"type":29,"value":2958},"AI needs clear boundaries, especially when it affects customers, decisions, or regulated processes.",{"type":24,"tag":2538,"props":2960,"children":2961},{},[2962,2967,2972],{"type":24,"tag":2565,"props":2963,"children":2964},{},[2965],{"type":29,"value":2966},"Scale economics",{"type":24,"tag":2565,"props":2968,"children":2969},{},[2970],{"type":29,"value":2971},"What will this cost to operate in production?",{"type":24,"tag":2565,"props":2973,"children":2974},{},[2975],{"type":29,"value":2976},"Pilot costs rarely reflect the full cost of a reliable AI capability.",{"type":24,"tag":25,"props":2978,"children":2979},{},[2980],{"type":29,"value":2981},"This framework helps CEOs separate promising AI investments from expensive distractions.",{"type":24,"tag":51,"props":2983,"children":2985},{"id":2984},"why-should-ceos-treat-ai-as-a-software-investment",[2986],{"type":29,"value":2987},"Why Should CEOs Treat AI as a Software Investment?",{"type":24,"tag":25,"props":2989,"children":2990},{},[2991],{"type":29,"value":2992},"CEOs should treat AI as a software investment because AI only creates durable value when it is embedded into systems people can trust, use, and maintain.",{"type":24,"tag":25,"props":2994,"children":2995},{},[2996],{"type":29,"value":2997},"A standalone AI tool may help an individual employee work faster. A custom AI-enabled system can reshape a workflow, connect to existing business data, support governance, and create a repeatable capability.",{"type":24,"tag":25,"props":2999,"children":3000},{},[3001,3003,3009],{"type":29,"value":3002},"That is where an experienced software development firm can add value. At Art+Logic, we see AI work as part of custom AI-driven software that can automate workflows, surface key trends, translate natural language into system actions, parse and summarize documents, and accelerate asset generation, including code, copy, and media. (",{"type":24,"tag":99,"props":3004,"children":3007},{"href":3005,"rel":3006},"https://artandlogic.com/ai/",[103],[3008],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":3011,"children":3012},{},[3013,3015,3020],{"type":29,"value":3014},"The important word there is ",{"type":24,"tag":2811,"props":3016,"children":3017},{},[3018],{"type":29,"value":3019},"software",{"type":29,"value":3021},".",{"type":24,"tag":25,"props":3023,"children":3024},{},[3025],{"type":29,"value":3026},"AI is not useful because it is impressive in isolation. It is useful when it is designed into the right product, interface, workflow, database, integration, permission model, testing process, and operating environment.",{"type":24,"tag":25,"props":3028,"children":3029},{},[3030],{"type":29,"value":3031},"That is the difference between a demo and a system the business can depend on.",{"type":24,"tag":51,"props":3033,"children":3035},{"id":3034},"why-should-ai-investments-start-with-business-outcomes",[3036],{"type":29,"value":3037},"Why Should AI Investments Start With Business Outcomes?",{"type":24,"tag":25,"props":3039,"children":3040},{},[3041],{"type":29,"value":3042},"AI investments should start with business outcomes because the tool itself is not the strategy.",{"type":24,"tag":25,"props":3044,"children":3045},{},[3046],{"type":29,"value":3047},"A vendor demo, a boardroom trend, or an internal push to “use AI” is not enough reason to invest. The investment should be tied to a business result the company already cares about.",{"type":24,"tag":25,"props":3049,"children":3050},{},[3051],{"type":29,"value":3052},"Strong AI investment goals include:",{"type":24,"tag":266,"props":3054,"children":3055},{},[3056,3061,3066,3071,3076,3081,3086,3091],{"type":24,"tag":270,"props":3057,"children":3058},{},[3059],{"type":29,"value":3060},"Increasing revenue",{"type":24,"tag":270,"props":3062,"children":3063},{},[3064],{"type":29,"value":3065},"Reducing operating cost",{"type":24,"tag":270,"props":3067,"children":3068},{},[3069],{"type":29,"value":3070},"Improving customer experience",{"type":24,"tag":270,"props":3072,"children":3073},{},[3074],{"type":29,"value":3075},"Accelerating software or product delivery",{"type":24,"tag":270,"props":3077,"children":3078},{},[3079],{"type":29,"value":3080},"Improving decision quality",{"type":24,"tag":270,"props":3082,"children":3083},{},[3084],{"type":29,"value":3085},"Reducing risk",{"type":24,"tag":270,"props":3087,"children":3088},{},[3089],{"type":29,"value":3090},"Creating a new product capability",{"type":24,"tag":270,"props":3092,"children":3093},{},[3094],{"type":29,"value":3095},"Strengthening competitive advantage",{"type":24,"tag":25,"props":3097,"children":3098},{},[3099],{"type":29,"value":3100},"For example, “We want an AI chatbot” is not a complete business case.",{"type":24,"tag":25,"props":3102,"children":3103},{},[3104],{"type":29,"value":3105},"A better version is: “We want to reduce support resolution time while maintaining or improving customer satisfaction.”",{"type":24,"tag":25,"props":3107,"children":3108},{},[3109],{"type":29,"value":3110},"“We want AI for engineering” is also too broad.",{"type":24,"tag":25,"props":3112,"children":3113},{},[3114],{"type":29,"value":3115},"A stronger version is: “We want to shorten software delivery cycles while maintaining code quality, security, transparency, and maintainability.”",{"type":24,"tag":25,"props":3117,"children":3118},{},[3119],{"type":29,"value":3120},"The CEO’s role is not to choose the model. It is to make sure the investment is pointed at a business problem worth solving.",{"type":24,"tag":51,"props":3122,"children":3124},{"id":3123},"what-types-of-ai-investments-should-ceos-compare",[3125],{"type":29,"value":3126},"What Types of AI Investments Should CEOs Compare?",{"type":24,"tag":25,"props":3128,"children":3129},{},[3130],{"type":29,"value":3131},"Not all AI investments should be judged by the same standard. A productivity tool, an internal decision-support system, a customer-facing AI feature, and an autonomous workflow agent have different costs, timelines, risks, and payoff profiles.",{"type":24,"tag":25,"props":3133,"children":3134},{},[3135],{"type":29,"value":3136},"CEOs should usually compare AI investments across four categories.",{"type":24,"tag":2530,"props":3138,"children":3139},{},[3140,3165],{"type":24,"tag":2534,"props":3141,"children":3142},{},[3143],{"type":24,"tag":2538,"props":3144,"children":3145},{},[3146,3151,3156,3160],{"type":24,"tag":2542,"props":3147,"children":3148},{},[3149],{"type":29,"value":3150},"AI Investment Type",{"type":24,"tag":2542,"props":3152,"children":3153},{},[3154],{"type":29,"value":3155},"Best Use",{"type":24,"tag":2542,"props":3157,"children":3158},{},[3159],{"type":29,"value":2861},{"type":24,"tag":2542,"props":3161,"children":3162},{},[3163],{"type":29,"value":3164},"Main Risk",{"type":24,"tag":2558,"props":3166,"children":3167},{},[3168,3191,3214,3237],{"type":24,"tag":2538,"props":3169,"children":3170},{},[3171,3176,3181,3186],{"type":24,"tag":2565,"props":3172,"children":3173},{},[3174],{"type":29,"value":3175},"Productivity AI",{"type":24,"tag":2565,"props":3177,"children":3178},{},[3179],{"type":29,"value":3180},"Speeding up knowledge work",{"type":24,"tag":2565,"props":3182,"children":3183},{},[3184],{"type":29,"value":3185},"What will we do with the time saved?",{"type":24,"tag":2565,"props":3187,"children":3188},{},[3189],{"type":29,"value":3190},"The value stays theoretical.",{"type":24,"tag":2538,"props":3192,"children":3193},{},[3194,3199,3204,3209],{"type":24,"tag":2565,"props":3195,"children":3196},{},[3197],{"type":29,"value":3198},"Decision support",{"type":24,"tag":2565,"props":3200,"children":3201},{},[3202],{"type":29,"value":3203},"Improving business decisions",{"type":24,"tag":2565,"props":3205,"children":3206},{},[3207],{"type":29,"value":3208},"What decision gets better?",{"type":24,"tag":2565,"props":3210,"children":3211},{},[3212],{"type":29,"value":3213},"Poor data or unclear accountability.",{"type":24,"tag":2538,"props":3215,"children":3216},{},[3217,3222,3227,3232],{"type":24,"tag":2565,"props":3218,"children":3219},{},[3220],{"type":29,"value":3221},"Customer-facing AI",{"type":24,"tag":2565,"props":3223,"children":3224},{},[3225],{"type":29,"value":3226},"Improving product or service experience",{"type":24,"tag":2565,"props":3228,"children":3229},{},[3230],{"type":29,"value":3231},"Does this improve trust and usability?",{"type":24,"tag":2565,"props":3233,"children":3234},{},[3235],{"type":29,"value":3236},"Brand, legal, or customer harm.",{"type":24,"tag":2538,"props":3238,"children":3239},{},[3240,3245,3250,3255],{"type":24,"tag":2565,"props":3241,"children":3242},{},[3243],{"type":29,"value":3244},"Agentic AI",{"type":24,"tag":2565,"props":3246,"children":3247},{},[3248],{"type":29,"value":3249},"Automating bounded workflows",{"type":24,"tag":2565,"props":3251,"children":3252},{},[3253],{"type":29,"value":3254},"Is the process well understood?",{"type":24,"tag":2565,"props":3256,"children":3257},{},[3258],{"type":29,"value":3259},"Uncontrolled action or escalating cost.",{"type":24,"tag":25,"props":3261,"children":3262},{},[3263],{"type":29,"value":3264},"The more deeply AI is connected to business operations, the more important software engineering becomes.",{"type":24,"tag":25,"props":3266,"children":3267},{},[3268],{"type":29,"value":3269},"A simple writing assistant may require light governance. An AI feature inside a customer product requires much more: interface design, testing, integration, security, monitoring, auditability, escalation paths, and a clear answer to the question, “Who is responsible when this system is wrong?”",{"type":24,"tag":51,"props":3271,"children":3273},{"id":3272},"how-should-ceos-evaluate-ai-assisted-software-development",[3274],{"type":29,"value":3275},"How Should CEOs Evaluate AI-Assisted Software Development?",{"type":24,"tag":25,"props":3277,"children":3278},{},[3279],{"type":29,"value":3280},"CEOs should evaluate AI-assisted software development carefully. AI can help engineers move faster, but it does not remove the need for engineering judgment.",{"type":24,"tag":25,"props":3282,"children":3283},{},[3284],{"type":29,"value":3285},"This is one of the easiest places to misunderstand AI.",{"type":24,"tag":25,"props":3287,"children":3288},{},[3289],{"type":29,"value":3290},"AI can generate code. That does not mean AI has designed a system. It does not mean the code is secure. It does not mean the architecture is appropriate. It does not mean the implementation is maintainable. It does not mean the business logic is correct. It does not mean the code will still make sense six months from now.",{"type":24,"tag":25,"props":3292,"children":3293},{},[3294],{"type":29,"value":3295},"A responsible software team uses AI as an accelerator, not as an unquestioned authority.",{"type":24,"tag":25,"props":3297,"children":3298},{},[3299],{"type":29,"value":3300},"Human software engineers still need to:",{"type":24,"tag":266,"props":3302,"children":3303},{},[3304,3309,3314,3319,3324,3329,3334,3339,3344,3349],{"type":24,"tag":270,"props":3305,"children":3306},{},[3307],{"type":29,"value":3308},"Understand the business requirements",{"type":24,"tag":270,"props":3310,"children":3311},{},[3312],{"type":29,"value":3313},"Choose the right architecture",{"type":24,"tag":270,"props":3315,"children":3316},{},[3317],{"type":29,"value":3318},"Review AI-generated code",{"type":24,"tag":270,"props":3320,"children":3321},{},[3322],{"type":29,"value":3323},"Test edge cases",{"type":24,"tag":270,"props":3325,"children":3326},{},[3327],{"type":29,"value":3328},"Identify security risks",{"type":24,"tag":270,"props":3330,"children":3331},{},[3332],{"type":29,"value":3333},"Preserve maintainability",{"type":24,"tag":270,"props":3335,"children":3336},{},[3337],{"type":29,"value":3338},"Document important decisions",{"type":24,"tag":270,"props":3340,"children":3341},{},[3342],{"type":29,"value":3343},"Monitor system behavior",{"type":24,"tag":270,"props":3345,"children":3346},{},[3347],{"type":29,"value":3348},"Refactor when requirements change",{"type":24,"tag":270,"props":3350,"children":3351},{},[3352],{"type":29,"value":3353},"Take responsibility for the final product",{"type":24,"tag":25,"props":3355,"children":3356},{},[3357],{"type":29,"value":3358},"This is especially important for CEOs because software is not only an asset at launch. It is an asset over time.",{"type":24,"tag":25,"props":3360,"children":3361},{},[3362],{"type":29,"value":3363},"A system that no one understands is a liability, even if it works today. A codebase that cannot be explained, maintained, secured, or extended will slow the business down later.",{"type":24,"tag":25,"props":3365,"children":3366},{},[3367,3369],{"type":29,"value":3368},"The CEO question is: ",{"type":24,"tag":2811,"props":3370,"children":3371},{},[3372],{"type":29,"value":3373},"Can our engineers explain, own, and maintain the code behind this AI-enabled system?",{"type":24,"tag":25,"props":3375,"children":3376},{},[3377],{"type":29,"value":3378},"If the answer is no, the investment is not ready to scale.",{"type":24,"tag":51,"props":3380,"children":3382},{"id":3381},"why-is-human-in-the-loop-ai-important",[3383],{"type":29,"value":3384},"Why Is Human-in-the-Loop AI Important?",{"type":24,"tag":25,"props":3386,"children":3387},{},[3388],{"type":29,"value":3389},"Human-in-the-loop AI is important because AI systems can be useful without being fully autonomous.",{"type":24,"tag":25,"props":3391,"children":3392},{},[3393],{"type":29,"value":3394},"In many business settings, the right goal is not to remove people from the process. The right goal is to help people make better decisions, move faster, reduce repetitive work, and focus on higher-value judgment.",{"type":24,"tag":25,"props":3396,"children":3397},{},[3398],{"type":29,"value":3399},"That is especially true when AI affects customers, financial decisions, compliance, security, hiring, healthcare, legal review, product quality, or production software.",{"type":24,"tag":25,"props":3401,"children":3402},{},[3403],{"type":29,"value":3404},"A human-in-the-loop design can include:",{"type":24,"tag":266,"props":3406,"children":3407},{},[3408,3413,3418,3423,3428,3433,3438,3443],{"type":24,"tag":270,"props":3409,"children":3410},{},[3411],{"type":29,"value":3412},"Human review before an AI recommendation is acted on",{"type":24,"tag":270,"props":3414,"children":3415},{},[3416],{"type":29,"value":3417},"Approval steps for high-risk outputs",{"type":24,"tag":270,"props":3419,"children":3420},{},[3421],{"type":29,"value":3422},"Escalation paths when confidence is low",{"type":24,"tag":270,"props":3424,"children":3425},{},[3426],{"type":29,"value":3427},"Clear visibility into source data or reasoning context",{"type":24,"tag":270,"props":3429,"children":3430},{},[3431],{"type":29,"value":3432},"Logging and audit trails",{"type":24,"tag":270,"props":3434,"children":3435},{},[3436],{"type":29,"value":3437},"Feedback loops that improve future performance",{"type":24,"tag":270,"props":3439,"children":3440},{},[3441],{"type":29,"value":3442},"Override controls",{"type":24,"tag":270,"props":3444,"children":3445},{},[3446],{"type":29,"value":3447},"Limits on what the AI system is allowed to do automatically",{"type":24,"tag":25,"props":3449,"children":3450},{},[3451],{"type":29,"value":3452},"This does not make AI less valuable. It makes AI more usable.",{"type":24,"tag":25,"props":3454,"children":3455},{},[3456,3458,3464],{"type":29,"value":3457},"We emphasize embedding AI into real operational workflows while keeping humans firmly in the loop. (",{"type":24,"tag":99,"props":3459,"children":3462},{"href":3460,"rel":3461},"https://artandlogic.com/two-minutes-on-tech/",[103],[3463],{"type":29,"value":1183},{"type":29,"value":3465},") That is a practical way to think about enterprise AI: not as a black box that replaces judgment, but as software that supports better human and organizational performance.",{"type":24,"tag":51,"props":3467,"children":3469},{"id":3468},"what-value-does-a-software-development-partner-add-to-ai-investments",[3470],{"type":29,"value":3471},"What Value Does a Software Development Partner Add to AI Investments?",{"type":24,"tag":25,"props":3473,"children":3474},{},[3475],{"type":29,"value":3476},"A software development partner adds value by turning an AI idea into a working, maintainable, secure system.",{"type":24,"tag":25,"props":3478,"children":3479},{},[3480],{"type":29,"value":3481},"That value matters because most AI failures do not happen because the model cannot produce an impressive answer. They happen because the business cannot integrate that capability into real operations.",{"type":24,"tag":25,"props":3483,"children":3484},{},[3485,3487,3494],{"type":29,"value":3486},"Gartner predicted that at least 30% of generative AI projects would be abandoned after proof of concept by the end of 2025 because of poor data quality, inadequate risk controls, escalating costs, or unclear business value. (",{"type":24,"tag":99,"props":3488,"children":3491},{"href":3489,"rel":3490},"https://www.gartner.com/en/newsroom/press-releases/2024-07-29-gartner-predicts-30-percent-of-generative-ai-projects-will-be-abandoned-after-proof-of-concept-by-end-of-2025",[103],[3492],{"type":29,"value":3493},"Gartner",{"type":29,"value":1185},{"type":24,"tag":25,"props":3496,"children":3497},{},[3498],{"type":29,"value":3499},"Those are not purely AI problems. They are software, data, product, and operating model problems.",{"type":24,"tag":25,"props":3501,"children":3502},{},[3503],{"type":29,"value":3504},"An experienced development partner can help CEOs and leadership teams answer questions like:",{"type":24,"tag":266,"props":3506,"children":3507},{},[3508,3513,3518,3523,3528,3533,3538,3543,3548,3553],{"type":24,"tag":270,"props":3509,"children":3510},{},[3511],{"type":29,"value":3512},"What should we build, buy, or integrate?",{"type":24,"tag":270,"props":3514,"children":3515},{},[3516],{"type":29,"value":3517},"Which workflow is worth improving first?",{"type":24,"tag":270,"props":3519,"children":3520},{},[3521],{"type":29,"value":3522},"What data does the system need?",{"type":24,"tag":270,"props":3524,"children":3525},{},[3526],{"type":29,"value":3527},"How should humans review or approve outputs?",{"type":24,"tag":270,"props":3529,"children":3530},{},[3531],{"type":29,"value":3532},"What parts of the workflow should remain deterministic?",{"type":24,"tag":270,"props":3534,"children":3535},{},[3536],{"type":29,"value":3537},"How should the AI connect to existing systems?",{"type":24,"tag":270,"props":3539,"children":3540},{},[3541],{"type":29,"value":3542},"What should be logged, monitored, or audited?",{"type":24,"tag":270,"props":3544,"children":3545},{},[3546],{"type":29,"value":3547},"How do we test quality before launch?",{"type":24,"tag":270,"props":3549,"children":3550},{},[3551],{"type":29,"value":3552},"How do we keep the system maintainable?",{"type":24,"tag":270,"props":3554,"children":3555},{},[3556],{"type":29,"value":3557},"How do we avoid creating a black box no one owns?",{"type":24,"tag":25,"props":3559,"children":3560},{},[3561,3563,3569],{"type":29,"value":3562},"Art+Logic works on custom software, AI development, web apps, legacy upgrades, automation, secure software development, and technically difficult projects. The company has been designing and developing custom software since 1991 and has built software for more than 900 clients across industries. (",{"type":24,"tag":99,"props":3564,"children":3567},{"href":3565,"rel":3566},"https://artandlogic.com/",[103],[3568],{"type":29,"value":1183},{"type":29,"value":1185},{"type":24,"tag":25,"props":3571,"children":3572},{},[3573],{"type":29,"value":3574},"That kind of experience matters because AI projects still have all the hard parts of software projects: requirements, architecture, integration, user experience, security, deployment, testing, change management, and long-term maintenance.",{"type":24,"tag":25,"props":3576,"children":3577},{},[3578],{"type":29,"value":3579},"AI does not remove those needs. It raises the stakes.",{"type":24,"tag":51,"props":3581,"children":3583},{"id":3582},"how-should-ceos-evaluate-productivity-ai",[3584],{"type":29,"value":3585},"How Should CEOs Evaluate Productivity AI?",{"type":24,"tag":25,"props":3587,"children":3588},{},[3589],{"type":29,"value":3590},"Productivity AI helps employees write, research, summarize, analyze, code, search internal knowledge, or automate repetitive tasks.",{"type":24,"tag":25,"props":3592,"children":3593},{},[3594],{"type":29,"value":3595},"These tools can produce fast wins, but their ROI is often harder to measure than it first appears. Time saved does not automatically become money saved. If employees save three hours a week but the company does not increase throughput, improve quality, reduce cost, or reallocate capacity, the value may remain theoretical.",{"type":24,"tag":25,"props":3597,"children":3598},{},[3599,3601],{"type":29,"value":3600},"The key CEO question is: ",{"type":24,"tag":2811,"props":3602,"children":3603},{},[3604],{"type":29,"value":3605},"What will we do with the time we save?",{"type":24,"tag":25,"props":3607,"children":3608},{},[3609],{"type":29,"value":3610},"Will teams handle more customer volume? Ship software faster? Reduce vendor spend? Improve proposal quality? Shorten sales cycles? Reallocate people to higher-value work?",{"type":24,"tag":25,"props":3612,"children":3613},{},[3614],{"type":29,"value":3615},"Without that second-order benefit, productivity AI becomes a convenience rather than a strategic investment.",{"type":24,"tag":25,"props":3617,"children":3618},{},[3619],{"type":29,"value":3620},"For software teams specifically, AI-assisted development should be evaluated by more than speed. CEOs should also ask whether quality, security, documentation, testing, and maintainability are improving or declining.",{"type":24,"tag":25,"props":3622,"children":3623},{},[3624],{"type":29,"value":3625},"Fast code is not automatically good software.",{"type":24,"tag":51,"props":3627,"children":3629},{"id":3628},"how-should-ceos-evaluate-ai-for-decision-support",[3630],{"type":29,"value":3631},"How Should CEOs Evaluate AI for Decision Support?",{"type":24,"tag":25,"props":3633,"children":3634},{},[3635],{"type":29,"value":3636},"AI decision-support systems help leaders and teams analyze data, identify patterns, forecast outcomes, or recommend actions.",{"type":24,"tag":25,"props":3638,"children":3639},{},[3640],{"type":29,"value":3641},"Examples include demand forecasting, churn prediction, pricing support, fraud detection, operational planning, and financial scenario modeling.",{"type":24,"tag":25,"props":3643,"children":3644},{},[3645],{"type":29,"value":3646},"The value is not just automation. It is better judgment at scale.",{"type":24,"tag":25,"props":3648,"children":3649},{},[3650,3651],{"type":29,"value":3600},{"type":24,"tag":2811,"props":3652,"children":3653},{},[3654],{"type":29,"value":3655},"What decision improves, who makes it, and how will we know the decision got better?",{"type":24,"tag":25,"props":3657,"children":3658},{},[3659],{"type":29,"value":3660},"A decision-support investment should have a clear link to a recurring business decision. It should also define how recommendations will be reviewed, when humans remain accountable, and how the company will measure whether decisions improve over time.",{"type":24,"tag":25,"props":3662,"children":3663},{},[3664],{"type":29,"value":3665},"AI can support a decision. It should not obscure responsibility for that decision.",{"type":24,"tag":51,"props":3667,"children":3669},{"id":3668},"how-should-ceos-evaluate-customer-facing-ai",[3670],{"type":29,"value":3671},"How Should CEOs Evaluate Customer-Facing AI?",{"type":24,"tag":25,"props":3673,"children":3674},{},[3675],{"type":29,"value":3676},"Customer-facing AI includes capabilities embedded into products, platforms, services, or support experiences.",{"type":24,"tag":25,"props":3678,"children":3679},{},[3680],{"type":29,"value":3681},"Examples include personalization, recommendations, natural language interfaces, intelligent onboarding, automated support, AI-assisted design tools, and domain-specific copilots.",{"type":24,"tag":25,"props":3683,"children":3684},{},[3685],{"type":29,"value":3686},"These investments can create differentiation, but they also carry higher brand and trust risk. A bad internal AI answer may waste time. A bad customer-facing AI answer may damage credibility, expose sensitive information, or create legal risk.",{"type":24,"tag":25,"props":3688,"children":3689},{},[3690,3691],{"type":29,"value":3600},{"type":24,"tag":2811,"props":3692,"children":3693},{},[3694],{"type":29,"value":3695},"Does this improve the customer experience enough to justify the operational and reputational risk?",{"type":24,"tag":25,"props":3697,"children":3698},{},[3699],{"type":29,"value":3700},"Customer-facing AI should be evaluated not only for accuracy but also for usability, transparency, escalation paths, privacy, security, and failure handling.",{"type":24,"tag":25,"props":3702,"children":3703},{},[3704],{"type":29,"value":3705},"This is another place where software engineering is essential. The user experience around the model often matters as much as the model itself.",{"type":24,"tag":25,"props":3707,"children":3708},{},[3709],{"type":29,"value":3710},"Can the user tell when they are interacting with AI? Can they correct it? Can they escalate to a person? Can the system explain where an answer came from? Can the business trace what happened if something goes wrong?",{"type":24,"tag":25,"props":3712,"children":3713},{},[3714],{"type":29,"value":3715},"Those are product and engineering questions, not just AI questions.",{"type":24,"tag":51,"props":3717,"children":3719},{"id":3718},"how-should-ceos-evaluate-agentic-ai",[3720],{"type":29,"value":3721},"How Should CEOs Evaluate Agentic AI?",{"type":24,"tag":25,"props":3723,"children":3724},{},[3725],{"type":29,"value":3726},"Agentic AI refers to systems that can take actions across tools, workflows, or systems with some degree of autonomy.",{"type":24,"tag":25,"props":3728,"children":3729},{},[3730,3732,3739],{"type":29,"value":3731},"This area is attracting heavy executive interest, but it requires extra discipline. Gartner predicted that over 40% of agentic AI projects would be canceled by the end of 2027 because of escalating costs, unclear business value, or inadequate risk controls. (",{"type":24,"tag":99,"props":3733,"children":3736},{"href":3734,"rel":3735},"https://www.reuters.com/business/over-40-agentic-ai-projects-will-be-scrapped-by-2027-gartner-says-2025-06-25/",[103],[3737],{"type":29,"value":3738},"Reuters",{"type":29,"value":1185},{"type":24,"tag":25,"props":3741,"children":3742},{},[3743],{"type":29,"value":3744},"That does not mean CEOs should ignore agentic AI. It means they should apply a higher bar.",{"type":24,"tag":25,"props":3746,"children":3747},{},[3748],{"type":29,"value":3749},"Agentic systems are most promising when the workflow is valuable, repeatable, well-bounded, observable, and connected to clear business metrics. They are risky when the workflow is ambiguous, exception-heavy, poorly documented, or dependent on judgment the organization cannot clearly define.",{"type":24,"tag":25,"props":3751,"children":3752},{},[3753,3754],{"type":29,"value":3600},{"type":24,"tag":2811,"props":3755,"children":3756},{},[3757],{"type":29,"value":3758},"Are we automating a well-understood business process, or are we asking AI to compensate for a process we do not understand?",{"type":24,"tag":25,"props":3760,"children":3761},{},[3762],{"type":29,"value":3763},"For agentic AI, human-in-the-loop design becomes even more important. The system should have clear limits on what it can do, when it must ask for approval, what actions are logged, and how a human can intervene.",{"type":24,"tag":25,"props":3765,"children":3766},{},[3767],{"type":29,"value":3768},"Autonomy without accountability is not a business capability. It is a risk.",{"type":24,"tag":51,"props":3770,"children":3772},{"id":3771},"what-is-the-real-cost-of-an-ai-investment",[3773],{"type":29,"value":3774},"What Is the Real Cost of an AI Investment?",{"type":24,"tag":25,"props":3776,"children":3777},{},[3778],{"type":29,"value":3779},"The real cost of an AI investment includes much more than software licenses or model usage.",{"type":24,"tag":25,"props":3781,"children":3782},{},[3783],{"type":29,"value":3784},"A pilot may only require a few users, a small technical team, and limited API spend. A production AI system usually requires a broader operating model.",{"type":24,"tag":25,"props":3786,"children":3787},{},[3788],{"type":29,"value":3789},"CEOs should expect serious AI investments to include some combination of:",{"type":24,"tag":266,"props":3791,"children":3792},{},[3793,3798,3803,3808,3813,3818,3823,3828,3833,3838,3843,3848,3853,3858,3863,3868,3873,3878],{"type":24,"tag":270,"props":3794,"children":3795},{},[3796],{"type":29,"value":3797},"Data preparation and cleanup",{"type":24,"tag":270,"props":3799,"children":3800},{},[3801],{"type":29,"value":3802},"System integration",{"type":24,"tag":270,"props":3804,"children":3805},{},[3806],{"type":29,"value":3807},"Security review",{"type":24,"tag":270,"props":3809,"children":3810},{},[3811],{"type":29,"value":3812},"Cloud infrastructure and model usage",{"type":24,"tag":270,"props":3814,"children":3815},{},[3816],{"type":29,"value":3817},"Vendor evaluation and procurement",{"type":24,"tag":270,"props":3819,"children":3820},{},[3821],{"type":29,"value":3822},"Legal and compliance review",{"type":24,"tag":270,"props":3824,"children":3825},{},[3826],{"type":29,"value":3827},"User experience design",{"type":24,"tag":270,"props":3829,"children":3830},{},[3831],{"type":29,"value":3832},"Workflow redesign",{"type":24,"tag":270,"props":3834,"children":3835},{},[3836],{"type":29,"value":3837},"Training and change management",{"type":24,"tag":270,"props":3839,"children":3840},{},[3841],{"type":29,"value":3842},"Human review processes",{"type":24,"tag":270,"props":3844,"children":3845},{},[3846],{"type":29,"value":3847},"Testing and evaluation",{"type":24,"tag":270,"props":3849,"children":3850},{},[3851],{"type":29,"value":3852},"Monitoring and maintenance",{"type":24,"tag":270,"props":3854,"children":3855},{},[3856],{"type":29,"value":3857},"Incident response planning",{"type":24,"tag":270,"props":3859,"children":3860},{},[3861],{"type":29,"value":3862},"Ongoing model, prompt, and data updates",{"type":24,"tag":270,"props":3864,"children":3865},{},[3866],{"type":29,"value":3867},"Software documentation",{"type":24,"tag":270,"props":3869,"children":3870},{},[3871],{"type":29,"value":3872},"Code review and refactoring",{"type":24,"tag":270,"props":3874,"children":3875},{},[3876],{"type":29,"value":3877},"Observability and logging",{"type":24,"tag":270,"props":3879,"children":3880},{},[3881],{"type":29,"value":3882},"Long-term ownership",{"type":24,"tag":25,"props":3884,"children":3885},{},[3886,3888],{"type":29,"value":3887},"A useful rule for CEOs: ",{"type":24,"tag":2811,"props":3889,"children":3890},{},[3891],{"type":29,"value":3892},"If the estimate only includes the AI tool, it is not a complete estimate.",{"type":24,"tag":25,"props":3894,"children":3895},{},[3896],{"type":29,"value":3897},"The model may work, but the business environment around it may not be ready. That is where many AI business cases break down.",{"type":24,"tag":51,"props":3899,"children":3901},{"id":3900},"why-does-workflow-redesign-matter-for-ai-roi",[3902],{"type":29,"value":3903},"Why Does Workflow Redesign Matter for AI ROI?",{"type":24,"tag":25,"props":3905,"children":3906},{},[3907],{"type":29,"value":3908},"Workflow redesign matters because AI creates value when it changes how work gets done.",{"type":24,"tag":25,"props":3910,"children":3911},{},[3912],{"type":29,"value":3913},"Giving employees access to AI tools may improve individual productivity. But larger gains usually come from redesigning workflows around AI-enabled capabilities.",{"type":24,"tag":25,"props":3915,"children":3916},{},[3917,3919,3926],{"type":29,"value":3918},"McKinsey’s 2025 global AI survey found that workflow redesign had the biggest effect on an organization’s ability to see EBIT impact from generative AI. The same survey reported that 21% of respondents whose organizations use generative AI said their organizations had fundamentally redesigned at least some workflows. (",{"type":24,"tag":99,"props":3920,"children":3923},{"href":3921,"rel":3922},"https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai-how-organizations-are-rewiring-to-capture-value",[103],[3924],{"type":29,"value":3925},"McKinsey & Company",{"type":29,"value":1185},{"type":24,"tag":25,"props":3928,"children":3929},{},[3930],{"type":29,"value":3931},"That distinction is important.",{"type":24,"tag":25,"props":3933,"children":3934},{},[3935],{"type":29,"value":3936},"AI adoption means people have access to tools.",{"type":24,"tag":25,"props":3938,"children":3939},{},[3940],{"type":29,"value":3941},"AI value means the business has changed a workflow in a measurable way.",{"type":24,"tag":25,"props":3943,"children":3944},{},[3945],{"type":29,"value":3946},"For example, giving a sales team an AI writing assistant may help individual sellers move faster. Redesigning the sales proposal process with AI-assisted research, reusable knowledge, pricing guidance, legal review support, and CRM integration may change the economics of the whole function.",{"type":24,"tag":25,"props":3948,"children":3949},{},[3950],{"type":29,"value":3951},"The same applies to software development. AI coding tools can improve individual productivity, but larger gains require disciplined engineering workflows: clearer requirements, better testing, stronger code review, improved documentation, deployment automation, and maintainable architecture.",{"type":24,"tag":25,"props":3953,"children":3954},{},[3955,3957],{"type":29,"value":3956},"The CEO question is simple: ",{"type":24,"tag":2811,"props":3958,"children":3959},{},[3960],{"type":29,"value":3961},"What workflow changes if this succeeds?",{"type":24,"tag":25,"props":3963,"children":3964},{},[3965],{"type":29,"value":3966},"If the answer is “nothing,” the investment is probably too shallow.",{"type":24,"tag":51,"props":3968,"children":3970},{"id":3969},"how-should-ceos-think-about-ai-governance",[3971],{"type":29,"value":3972},"How Should CEOs Think About AI Governance?",{"type":24,"tag":25,"props":3974,"children":3975},{},[3976],{"type":29,"value":3977},"CEOs should treat AI governance as part of the investment case, not as an afterthought.",{"type":24,"tag":25,"props":3979,"children":3980},{},[3981],{"type":29,"value":3982},"Governance is often framed as a brake on innovation. In reality, good governance is what allows AI to scale.",{"type":24,"tag":25,"props":3984,"children":3985},{},[3986],{"type":29,"value":3987},"Without governance, companies risk shadow AI, inconsistent data handling, unclear accountability, duplicated tools, uncontrolled costs, unmanaged security exposure, unreliable outputs, and code no one fully understands.",{"type":24,"tag":25,"props":3989,"children":3990},{},[3991],{"type":29,"value":3992},"With governance, teams have clearer rules for where AI can be used, what data is allowed, who approves high-risk use cases, how outputs are reviewed, how code is tested, and how systems are monitored.",{"type":24,"tag":25,"props":3994,"children":3995},{},[3996,3998,4005],{"type":29,"value":3997},"Regulation is also becoming more concrete. The EU AI Act entered into force on August 1, 2024, and is scheduled to become fully applicable on August 2, 2026, with some exceptions. (",{"type":24,"tag":99,"props":3999,"children":4002},{"href":4000,"rel":4001},"https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai",[103],[4003],{"type":29,"value":4004},"Digital Strategy",{"type":29,"value":1185},{"type":24,"tag":25,"props":4007,"children":4008},{},[4009],{"type":29,"value":4010},"Even companies outside the EU should pay attention to this direction. Customers, regulators, insurers, partners, and enterprise buyers are increasingly likely to ask how AI systems are governed.",{"type":24,"tag":25,"props":4012,"children":4013},{},[4014],{"type":29,"value":4015},"A practical AI governance review should answer:",{"type":24,"tag":266,"props":4017,"children":4018},{},[4019,4024,4029,4034,4039,4044,4049,4054,4059,4064],{"type":24,"tag":270,"props":4020,"children":4021},{},[4022],{"type":29,"value":4023},"Who owns the AI system?",{"type":24,"tag":270,"props":4025,"children":4026},{},[4027],{"type":29,"value":4028},"What data can and cannot be used?",{"type":24,"tag":270,"props":4030,"children":4031},{},[4032],{"type":29,"value":4033},"What security and privacy controls are required?",{"type":24,"tag":270,"props":4035,"children":4036},{},[4037],{"type":29,"value":4038},"When is human review required?",{"type":24,"tag":270,"props":4040,"children":4041},{},[4042],{"type":29,"value":4043},"How will outputs be tested?",{"type":24,"tag":270,"props":4045,"children":4046},{},[4047],{"type":29,"value":4048},"How will AI-generated code be reviewed?",{"type":24,"tag":270,"props":4050,"children":4051},{},[4052],{"type":29,"value":4053},"What happens when the system is wrong?",{"type":24,"tag":270,"props":4055,"children":4056},{},[4057],{"type":29,"value":4058},"How will performance be monitored after launch?",{"type":24,"tag":270,"props":4060,"children":4061},{},[4062],{"type":29,"value":4063},"How will the company respond to incidents?",{"type":24,"tag":270,"props":4065,"children":4066},{},[4067],{"type":29,"value":4068},"Who is responsible for maintaining the system over time?",{"type":24,"tag":25,"props":4070,"children":4071},{},[4072],{"type":29,"value":4073},"The governance should match the risk. An internal brainstorming assistant does not need the same oversight as an AI system that affects hiring, lending, medical guidance, legal review, financial decisions, customer eligibility, or production infrastructure.",{"type":24,"tag":25,"props":4075,"children":4076},{},[4077],{"type":29,"value":4078},"But every AI investment needs boundaries.",{"type":24,"tag":51,"props":4080,"children":4082},{"id":4081},"what-metrics-should-ceos-use-to-measure-ai-roi",[4083],{"type":29,"value":4084},"What Metrics Should CEOs Use to Measure AI ROI?",{"type":24,"tag":25,"props":4086,"children":4087},{},[4088],{"type":29,"value":4089},"CEOs should measure AI ROI using business metrics, not just usage metrics.",{"type":24,"tag":25,"props":4091,"children":4092},{},[4093],{"type":29,"value":4094},"Usage can show adoption, but it does not prove value. A tool can be widely used and still fail to improve business performance.",{"type":24,"tag":25,"props":4096,"children":4097},{},[4098],{"type":29,"value":4099},"Better AI ROI metrics include:",{"type":24,"tag":2530,"props":4101,"children":4102},{},[4103,4119],{"type":24,"tag":2534,"props":4104,"children":4105},{},[4106],{"type":24,"tag":2538,"props":4107,"children":4108},{},[4109,4114],{"type":24,"tag":2542,"props":4110,"children":4111},{},[4112],{"type":29,"value":4113},"Business Goal",{"type":24,"tag":2542,"props":4115,"children":4116},{},[4117],{"type":29,"value":4118},"Possible AI ROI Metric",{"type":24,"tag":2558,"props":4120,"children":4121},{},[4122,4135,4148,4161,4174,4187,4200,4213,4226],{"type":24,"tag":2538,"props":4123,"children":4124},{},[4125,4130],{"type":24,"tag":2565,"props":4126,"children":4127},{},[4128],{"type":29,"value":4129},"Reduce cost",{"type":24,"tag":2565,"props":4131,"children":4132},{},[4133],{"type":29,"value":4134},"Lower cost per ticket, transaction, claim, report, or workflow",{"type":24,"tag":2538,"props":4136,"children":4137},{},[4138,4143],{"type":24,"tag":2565,"props":4139,"children":4140},{},[4141],{"type":29,"value":4142},"Improve speed",{"type":24,"tag":2565,"props":4144,"children":4145},{},[4146],{"type":29,"value":4147},"Shorter cycle time, faster response time, reduced backlog",{"type":24,"tag":2538,"props":4149,"children":4150},{},[4151,4156],{"type":24,"tag":2565,"props":4152,"children":4153},{},[4154],{"type":29,"value":4155},"Increase revenue",{"type":24,"tag":2565,"props":4157,"children":4158},{},[4159],{"type":29,"value":4160},"Higher conversion, larger deal velocity, better retention",{"type":24,"tag":2538,"props":4162,"children":4163},{},[4164,4169],{"type":24,"tag":2565,"props":4165,"children":4166},{},[4167],{"type":29,"value":4168},"Improve quality",{"type":24,"tag":2565,"props":4170,"children":4171},{},[4172],{"type":29,"value":4173},"Fewer errors, fewer rework cycles, better customer satisfaction",{"type":24,"tag":2538,"props":4175,"children":4176},{},[4177,4182],{"type":24,"tag":2565,"props":4178,"children":4179},{},[4180],{"type":29,"value":4181},"Increase capacity",{"type":24,"tag":2565,"props":4183,"children":4184},{},[4185],{"type":29,"value":4186},"More throughput without proportional headcount growth",{"type":24,"tag":2538,"props":4188,"children":4189},{},[4190,4195],{"type":24,"tag":2565,"props":4191,"children":4192},{},[4193],{"type":29,"value":4194},"Reduce risk",{"type":24,"tag":2565,"props":4196,"children":4197},{},[4198],{"type":29,"value":4199},"Fewer compliance issues, better anomaly detection, improved auditability",{"type":24,"tag":2538,"props":4201,"children":4202},{},[4203,4208],{"type":24,"tag":2565,"props":4204,"children":4205},{},[4206],{"type":29,"value":4207},"Improve delivery",{"type":24,"tag":2565,"props":4209,"children":4210},{},[4211],{"type":29,"value":4212},"Faster software releases, fewer defects, shorter review cycles",{"type":24,"tag":2538,"props":4214,"children":4215},{},[4216,4221],{"type":24,"tag":2565,"props":4217,"children":4218},{},[4219],{"type":29,"value":4220},"Improve maintainability",{"type":24,"tag":2565,"props":4222,"children":4223},{},[4224],{"type":29,"value":4225},"Lower technical debt, clearer documentation, easier onboarding",{"type":24,"tag":2538,"props":4227,"children":4228},{},[4229,4234],{"type":24,"tag":2565,"props":4230,"children":4231},{},[4232],{"type":29,"value":4233},"Improve transparency",{"type":24,"tag":2565,"props":4235,"children":4236},{},[4237],{"type":29,"value":4238},"Better traceability, explainability, logs, and review workflows",{"type":24,"tag":25,"props":4240,"children":4241},{},[4242],{"type":29,"value":4243},"A strong AI business case should explain the baseline, the expected improvement, and the method for measurement.",{"type":24,"tag":25,"props":4245,"children":4246},{},[4247,4249],{"type":29,"value":4248},"For example, “save 10,000 hours” is not enough. The better question is: ",{"type":24,"tag":2811,"props":4250,"children":4251},{},[4252],{"type":29,"value":4253},"Which hours, whose hours, what happens next, and what business result changes?",{"type":24,"tag":25,"props":4255,"children":4256},{},[4257,4259],{"type":29,"value":4258},"For AI-assisted software development, “more code shipped” is not enough either. The better question is: ",{"type":24,"tag":2811,"props":4260,"children":4261},{},[4262],{"type":29,"value":4263},"Are we shipping better software faster, with clear ownership and less long-term risk?",{"type":24,"tag":51,"props":4265,"children":4267},{"id":4266},"should-ceos-build-buy-or-partner-on-ai",[4268],{"type":29,"value":4269},"Should CEOs Build, Buy, or Partner on AI?",{"type":24,"tag":25,"props":4271,"children":4272},{},[4273],{"type":29,"value":4274},"CEOs should choose build, buy, or partner based on strategic importance, differentiation, control, cost, and speed.",{"type":24,"tag":25,"props":4276,"children":4277},{},[4278,4283],{"type":24,"tag":2811,"props":4279,"children":4280},{},[4281],{"type":29,"value":4282},"Buy",{"type":29,"value":4284}," when the capability is common, non-differentiating, and well-served by mature tools. Examples may include meeting summaries, basic document drafting, internal productivity assistants, or commodity support features.",{"type":24,"tag":25,"props":4286,"children":4287},{},[4288,4293],{"type":24,"tag":2811,"props":4289,"children":4290},{},[4291],{"type":29,"value":4292},"Build",{"type":29,"value":4294}," when the capability is central to differentiation, depends on proprietary workflows or data, or must be deeply embedded into the product or operating model.",{"type":24,"tag":25,"props":4296,"children":4297},{},[4298,4303],{"type":24,"tag":2811,"props":4299,"children":4300},{},[4301],{"type":29,"value":4302},"Partner",{"type":29,"value":4304}," when the opportunity is strategically important but the company needs outside software, AI, product, data, or architecture expertise to execute safely and effectively.",{"type":24,"tag":25,"props":4306,"children":4307},{},[4308,4310],{"type":29,"value":4309},"The CEO-level question is: ",{"type":24,"tag":2811,"props":4311,"children":4312},{},[4313],{"type":29,"value":4314},"Where do we need ownership, and where do we simply need utility?",{"type":24,"tag":25,"props":4316,"children":4317},{},[4318],{"type":29,"value":4319},"A software development partner like Art+Logic can be especially valuable when the AI investment touches custom workflows, proprietary systems, legacy software, complex integrations, regulated environments, or product differentiation.",{"type":24,"tag":25,"props":4321,"children":4322},{},[4323],{"type":29,"value":4324},"In those cases, the challenge is rarely “Can we call an AI API?” The challenge is building a system that works reliably inside the business.",{"type":24,"tag":51,"props":4326,"children":4328},{"id":4327},"what-should-an-ai-investment-proposal-include",[4329],{"type":29,"value":4330},"What Should an AI Investment Proposal Include?",{"type":24,"tag":25,"props":4332,"children":4333},{},[4334],{"type":29,"value":4335},"A CEO-ready AI investment proposal should include:",{"type":24,"tag":1921,"props":4337,"children":4338},{},[4339,4344,4349,4354,4359,4364,4369,4374,4379,4384,4389,4394,4399,4404],{"type":24,"tag":270,"props":4340,"children":4341},{},[4342],{"type":29,"value":4343},"The business problem",{"type":24,"tag":270,"props":4345,"children":4346},{},[4347],{"type":29,"value":4348},"The proposed AI-enabled capability",{"type":24,"tag":270,"props":4350,"children":4351},{},[4352],{"type":29,"value":4353},"The workflow change required",{"type":24,"tag":270,"props":4355,"children":4356},{},[4357],{"type":29,"value":4358},"The expected value",{"type":24,"tag":270,"props":4360,"children":4361},{},[4362],{"type":29,"value":4363},"The full cost",{"type":24,"tag":270,"props":4365,"children":4366},{},[4367],{"type":29,"value":4368},"The data requirements",{"type":24,"tag":270,"props":4370,"children":4371},{},[4372],{"type":29,"value":4373},"The human-in-the-loop design",{"type":24,"tag":270,"props":4375,"children":4376},{},[4377],{"type":29,"value":4378},"The software architecture",{"type":24,"tag":270,"props":4380,"children":4381},{},[4382],{"type":29,"value":4383},"The risks and controls",{"type":24,"tag":270,"props":4385,"children":4386},{},[4387],{"type":29,"value":4388},"The owner",{"type":24,"tag":270,"props":4390,"children":4391},{},[4392],{"type":29,"value":4393},"The implementation path",{"type":24,"tag":270,"props":4395,"children":4396},{},[4397],{"type":29,"value":4398},"The success metrics",{"type":24,"tag":270,"props":4400,"children":4401},{},[4402],{"type":29,"value":4403},"The plan for testing, monitoring, and maintenance",{"type":24,"tag":270,"props":4405,"children":4406},{},[4407],{"type":29,"value":4408},"The decision point for scaling, changing, or stopping",{"type":24,"tag":25,"props":4410,"children":4411},{},[4412],{"type":29,"value":4413},"That level of clarity makes AI less mysterious. It also makes it more useful.",{"type":24,"tag":25,"props":4415,"children":4416},{},[4417],{"type":29,"value":4418},"A good AI investment case should not simply say, “This technology is powerful.” It should explain how the business will use that power responsibly to improve a measurable outcome.",{"type":24,"tag":51,"props":4420,"children":4422},{"id":4421},"what-are-the-biggest-red-flags-in-ai-investment-proposals",[4423],{"type":29,"value":4424},"What Are the Biggest Red Flags in AI Investment Proposals?",{"type":24,"tag":25,"props":4426,"children":4427},{},[4428],{"type":29,"value":4429},"CEOs should watch for these warning signs:",{"type":24,"tag":266,"props":4431,"children":4432},{},[4433,4438,4443,4448,4453,4458,4463,4468,4473,4478,4483,4488,4493],{"type":24,"tag":270,"props":4434,"children":4435},{},[4436],{"type":29,"value":4437},"The business case is based only on generic productivity assumptions.",{"type":24,"tag":270,"props":4439,"children":4440},{},[4441],{"type":29,"value":4442},"The team cannot explain the workflow impact.",{"type":24,"tag":270,"props":4444,"children":4445},{},[4446],{"type":29,"value":4447},"The proposal depends on clean data the company does not have.",{"type":24,"tag":270,"props":4449,"children":4450},{},[4451],{"type":29,"value":4452},"The demo uses examples that are much simpler than real-world work.",{"type":24,"tag":270,"props":4454,"children":4455},{},[4456],{"type":29,"value":4457},"No one has budgeted for integration or change management.",{"type":24,"tag":270,"props":4459,"children":4460},{},[4461],{"type":29,"value":4462},"Legal, security, or compliance teams are brought in only at the end.",{"type":24,"tag":270,"props":4464,"children":4465},{},[4466],{"type":29,"value":4467},"The system has no clear owner after launch.",{"type":24,"tag":270,"props":4469,"children":4470},{},[4471],{"type":29,"value":4472},"Success is measured by usage instead of business impact.",{"type":24,"tag":270,"props":4474,"children":4475},{},[4476],{"type":29,"value":4477},"The project requires high trust in outputs but has weak testing.",{"type":24,"tag":270,"props":4479,"children":4480},{},[4481],{"type":29,"value":4482},"AI-generated code is accepted without engineering review.",{"type":24,"tag":270,"props":4484,"children":4485},{},[4486],{"type":29,"value":4487},"The team cannot explain how the system works.",{"type":24,"tag":270,"props":4489,"children":4490},{},[4491],{"type":29,"value":4492},"The system has no human override path.",{"type":24,"tag":270,"props":4494,"children":4495},{},[4496],{"type":29,"value":4497},"The investment is justified mainly by fear of falling behind.",{"type":24,"tag":25,"props":4499,"children":4500},{},[4501],{"type":29,"value":4502},"Fear is not a strategy. Neither is experimentation without a path to value.",{"type":24,"tag":51,"props":4504,"children":4506},{"id":4505},"what-is-the-best-ai-investment-strategy-for-ceos",[4507],{"type":29,"value":4508},"What Is the Best AI Investment Strategy for CEOs?",{"type":24,"tag":25,"props":4510,"children":4511},{},[4512],{"type":29,"value":4513},"The best AI investment strategy is a portfolio strategy.",{"type":24,"tag":25,"props":4515,"children":4516},{},[4517],{"type":29,"value":4518},"A healthy AI portfolio includes a mix of near-term productivity gains, operational improvements, and strategic bets.",{"type":24,"tag":25,"props":4520,"children":4521},{},[4522,4527],{"type":24,"tag":2811,"props":4523,"children":4524},{},[4525],{"type":29,"value":4526},"Near-term productivity gains",{"type":29,"value":4528}," help teams build AI fluency and identify practical use cases.",{"type":24,"tag":25,"props":4530,"children":4531},{},[4532,4537],{"type":24,"tag":2811,"props":4533,"children":4534},{},[4535],{"type":29,"value":4536},"Operational improvements",{"type":29,"value":4538}," target measurable workflows where better automation, analysis, or decision support can improve business performance.",{"type":24,"tag":25,"props":4540,"children":4541},{},[4542,4547],{"type":24,"tag":2811,"props":4543,"children":4544},{},[4545],{"type":29,"value":4546},"Strategic bets",{"type":29,"value":4548}," explore new products, services, business models, or defensible capabilities that may take longer to mature.",{"type":24,"tag":25,"props":4550,"children":4551},{},[4552],{"type":29,"value":4553},"The portfolio should be reviewed regularly. Some experiments should be stopped. Some should be merged. Some should receive more funding. Some should move from innovation budgets into operating budgets.",{"type":24,"tag":25,"props":4555,"children":4556},{},[4557],{"type":29,"value":4558},"That last point matters.",{"type":24,"tag":25,"props":4560,"children":4561},{},[4562],{"type":29,"value":4563},"Once an AI system becomes part of how the business runs, it is no longer an experiment. It is infrastructure.",{"type":24,"tag":25,"props":4565,"children":4566},{},[4567],{"type":29,"value":4568},"And infrastructure needs engineering discipline.",{"type":24,"tag":51,"props":4570,"children":4572},{"id":4571},"final-takeaway-ceos-should-evaluate-ai-as-responsible-software",[4573],{"type":29,"value":4574},"Final Takeaway: CEOs Should Evaluate AI as Responsible Software",{"type":24,"tag":25,"props":4576,"children":4577},{},[4578],{"type":29,"value":4579},"AI can be transformative, but only when it is evaluated as more than technology.",{"type":24,"tag":25,"props":4581,"children":4582},{},[4583],{"type":29,"value":4584},"For CEOs, the mandate is clear: do not evaluate AI by the quality of the demo. Evaluate it by the quality of the business case, the workflow design, the human oversight model, and the engineering discipline behind it.",{"type":24,"tag":25,"props":4586,"children":4587},{},[4588],{"type":29,"value":4589},"The companies that create lasting value with AI will not necessarily be the ones that spend the most or automate the fastest. They will be the ones that connect AI investments to measurable business outcomes, redesign workflows around those capabilities, keep humans responsible where it matters, and build software that can be trusted, explained, maintained, and improved.",{"type":24,"tag":25,"props":4591,"children":4592},{},[4593],{"type":29,"value":4594},"AI investment is a strategy decision. It is an operating model decision. It is a governance decision. It is a software engineering decision. And increasingly, it is a leadership decision.",{"type":24,"tag":51,"props":4596,"children":4597},{"id":1028},[4598],{"type":29,"value":1031},{"type":24,"tag":1033,"props":4600,"children":4602},{"id":4601},"how-should-ceos-evaluate-ai-investments",[4603],{"type":29,"value":4604},"How should CEOs evaluate AI investments?",{"type":24,"tag":25,"props":4606,"children":4607},{},[4608],{"type":29,"value":4609},"CEOs should evaluate AI investments by asking whether they improve a measurable business outcome, change a real workflow, include appropriate human oversight, have a realistic path to production, and create value that outweighs cost and risk.",{"type":24,"tag":1033,"props":4611,"children":4613},{"id":4612},"why-should-ceos-treat-ai-as-a-software-investment-1",[4614],{"type":29,"value":4615},"Why should CEOs treat AI as a software investment?",{"type":24,"tag":25,"props":4617,"children":4618},{},[4619],{"type":29,"value":4620},"CEOs should treat AI as a software investment because AI only creates durable value when it is integrated into reliable systems, workflows, data sources, interfaces, security controls, and maintenance processes. A demo is not the same thing as production software.",{"type":24,"tag":1033,"props":4622,"children":4624},{"id":4623},"why-is-human-in-the-loop-ai-important-1",[4625],{"type":29,"value":4626},"Why is human-in-the-loop AI important?",{"type":24,"tag":25,"props":4628,"children":4629},{},[4630],{"type":29,"value":4631},"Human-in-the-loop AI is important because people need to remain accountable for high-impact decisions, customer-facing actions, regulated workflows, and production software. Human oversight helps improve accuracy, trust, transparency, and risk management.",{"type":24,"tag":1033,"props":4633,"children":4635},{"id":4634},"can-ai-write-production-code-without-software-engineers",[4636],{"type":29,"value":4637},"Can AI write production code without software engineers?",{"type":24,"tag":25,"props":4639,"children":4640},{},[4641],{"type":29,"value":4642},"AI can generate code, but software engineers still need to review, test, secure, document, maintain, and take responsibility for that code. AI-generated code should be treated as a starting point, not as a finished software product.",{"type":24,"tag":1033,"props":4644,"children":4646},{"id":4645},"what-value-does-a-software-development-firm-add-to-an-ai-project",[4647],{"type":29,"value":4648},"What value does a software development firm add to an AI project?",{"type":24,"tag":25,"props":4650,"children":4651},{},[4652],{"type":29,"value":4653},"A software development firm can help turn an AI idea into a working system by designing the architecture, integrating data and tools, building user workflows, testing outputs, managing risk, reviewing code, and ensuring the software remains maintainable over time.",{"type":24,"tag":1033,"props":4655,"children":4657},{"id":4656},"what-is-the-most-important-question-ceos-should-ask-about-ai-roi",[4658],{"type":29,"value":4659},"What is the most important question CEOs should ask about AI ROI?",{"type":24,"tag":25,"props":4661,"children":4662},{},[4663],{"type":29,"value":4664},"The most important question is: what business result will improve? AI ROI should be measured through outcomes such as lower cost, faster cycle time, higher revenue, better customer experience, improved quality, increased capacity, reduced risk, or better maintainability.",{"type":24,"tag":1033,"props":4666,"children":4668},{"id":4667},"why-do-ai-projects-fail-after-proof-of-concept",[4669],{"type":29,"value":4670},"Why do AI projects fail after proof of concept?",{"type":24,"tag":25,"props":4672,"children":4673},{},[4674],{"type":29,"value":4675},"AI projects often fail after proof of concept because the demo works, but the business environment is not ready. Common causes include poor data quality, unclear business value, escalating costs, weak governance, integration challenges, and lack of workflow redesign.",{"type":24,"tag":1033,"props":4677,"children":4679},{"id":4678},"should-ceos-focus-on-ai-tools-or-ai-capabilities",[4680],{"type":29,"value":4681},"Should CEOs focus on AI tools or AI capabilities?",{"type":24,"tag":25,"props":4683,"children":4684},{},[4685],{"type":29,"value":4686},"CEOs should focus on AI capabilities. A tool is only valuable if it helps the business do something meaningfully better, such as make faster decisions, automate a high-value workflow, improve a customer experience, or create a differentiated product feature.",{"type":24,"tag":1033,"props":4688,"children":4690},{"id":4689},"what-should-every-ai-investment-proposal-include",[4691],{"type":29,"value":4692},"What should every AI investment proposal include?",{"type":24,"tag":25,"props":4694,"children":4695},{},[4696],{"type":29,"value":4697},"Every AI investment proposal should include the business problem, proposed capability, expected value, workflow impact, data requirements, human oversight model, software architecture, full cost, risks, governance controls, owner, implementation path, success metrics, and maintenance plan.",{"type":24,"tag":1033,"props":4699,"children":4701},{"id":4700},"how-should-ceos-decide-whether-to-build-buy-or-partner-on-ai",[4702],{"type":29,"value":4703},"How should CEOs decide whether to build, buy, or partner on AI?",{"type":24,"tag":25,"props":4705,"children":4706},{},[4707],{"type":29,"value":4708},"CEOs should buy AI when the capability is common, build when it is strategically differentiating, and partner when the opportunity is important but the company needs outside software, AI, product, data, or architecture expertise to execute safely and effectively.",{"title":8,"searchDepth":1122,"depth":1122,"links":4710},[4711,4712,4713,4714,4715,4716,4717,4718,4719,4720,4721,4722,4723,4724,4725,4726,4727,4728,4729,4730,4731],{"id":2834,"depth":1122,"text":2837},{"id":2984,"depth":1122,"text":2987},{"id":3034,"depth":1122,"text":3037},{"id":3123,"depth":1122,"text":3126},{"id":3272,"depth":1122,"text":3275},{"id":3381,"depth":1122,"text":3384},{"id":3468,"depth":1122,"text":3471},{"id":3582,"depth":1122,"text":3585},{"id":3628,"depth":1122,"text":3631},{"id":3668,"depth":1122,"text":3671},{"id":3718,"depth":1122,"text":3721},{"id":3771,"depth":1122,"text":3774},{"id":3900,"depth":1122,"text":3903},{"id":3969,"depth":1122,"text":3972},{"id":4081,"depth":1122,"text":4084},{"id":4266,"depth":1122,"text":4269},{"id":4327,"depth":1122,"text":4330},{"id":4421,"depth":1122,"text":4424},{"id":4505,"depth":1122,"text":4508},{"id":4571,"depth":1122,"text":4574},{"id":1028,"depth":1122,"text":1031,"children":4732},[4733,4734,4735,4736,4737,4738,4739,4740,4741,4742],{"id":4601,"depth":1142,"text":4604},{"id":4612,"depth":1142,"text":4615},{"id":4623,"depth":1142,"text":4626},{"id":4634,"depth":1142,"text":4637},{"id":4645,"depth":1142,"text":4648},{"id":4656,"depth":1142,"text":4659},{"id":4667,"depth":1142,"text":4670},{"id":4678,"depth":1142,"text":4681},{"id":4689,"depth":1142,"text":4692},{"id":4700,"depth":1142,"text":4703},"content:cperez:2026-06-30:how-ceos-should-evaluate-ai-investments.md","cperez/2026-06-30/how-ceos-should-evaluate-ai-investments.md","cperez/2026-06-30/how-ceos-should-evaluate-ai-investments",{"_path":4747,"_dir":4748,"_draft":7,"_partial":7,"_locale":8,"title":4749,"description":4750,"publishDate":4748,"image":4751,"author":4752,"tags":4753,"excerpt":4750,"body":4756,"_type":1150,"_id":5352,"_source":1152,"_file":5353,"_stem":5354,"_extension":1155},"/cperez/2026-06-25/ai_makes_modernization_feasible","2026-06-25","How AI-Assisted Legacy Modernization Reduces Cost, Risk, and Project Timelines","Many organizations know they need to modernize their legacy applications. They also know why they haven't.","/cperez/2026-06-25/img/ai_makes_modernization_feasible.png",{"name":13,"user":14},[1164,4754,16,4755],"tech debt","legacy migration",{"type":21,"children":4757,"toc":5329},[4758,4764,4768,4773,4778,4783,4788,4793,4798,4804,4809,4814,4819,4857,4862,4867,4872,4878,4883,4888,4893,4898,4903,4908,4956,4961,4966,4971,4976,4981,4986,4992,4997,5002,5008,5013,5018,5023,5028,5034,5039,5044,5049,5055,5060,5065,5070,5076,5081,5086,5092,5097,5102,5107,5112,5155,5160,5165,5171,5176,5181,5186,5191,5200,5206,5211,5216,5221,5226,5232,5237,5242,5247,5252,5257,5263,5269,5274,5280,5285,5291,5296,5302,5307,5313,5318,5324],{"type":24,"tag":51,"props":4759,"children":4761},{"id":4760},"why-human-led-ai-assisted-development-makes-legacy-system-modernization-feasible-again",[4762],{"type":29,"value":4763},"Why Human-Led, AI-Assisted Development Makes Legacy System Modernization Feasible Again",{"type":24,"tag":25,"props":4765,"children":4766},{},[4767],{"type":29,"value":4750},{"type":24,"tag":25,"props":4769,"children":4770},{},[4771],{"type":29,"value":4772},"For years, legacy modernization projects have traditionally been expensive, time-consuming, and difficult to justify. Before a single line of code could be updated, teams often had to spend months analyzing existing systems, uncovering business rules, documenting dependencies, and determining how everything worked.",{"type":24,"tag":25,"props":4774,"children":4775},{},[4776],{"type":29,"value":4777},"For many organizations, the effort required just to understand a legacy application made modernization feel out of reach, if not impossible.",{"type":24,"tag":25,"props":4779,"children":4780},{},[4781],{"type":29,"value":4782},"Today, AI-assisted development is changing that equation.",{"type":24,"tag":25,"props":4784,"children":4785},{},[4786],{"type":29,"value":4787},"By helping development teams analyze, document, and understand legacy systems more efficiently, AI can reduce some of the biggest barriers to modernization. Projects that once seemed too risky, too costly, or too complex are becoming increasingly feasible.",{"type":24,"tag":25,"props":4789,"children":4790},{},[4791],{"type":29,"value":4792},"The keyword, however, is \"assisted.\"",{"type":24,"tag":25,"props":4794,"children":4795},{},[4796],{"type":29,"value":4797},"What we’ve seen is that the most successful modernization initiatives are not replacing experienced engineers with AI. They're combining AI-powered tools with human expertise to create better outcomes, reduce risk, and accelerate delivery, all while maintaining transparency and accountability, which is essential to building trust in your development team.",{"type":24,"tag":51,"props":4799,"children":4801},{"id":4800},"why-legacy-modernization-has-been-so-challenging",[4802],{"type":29,"value":4803},"Why Legacy Modernization Has Been So Challenging",{"type":24,"tag":25,"props":4805,"children":4806},{},[4807],{"type":29,"value":4808},"It may seem like a truism, but most legacy systems weren't created to become legacy systems.",{"type":24,"tag":25,"props":4810,"children":4811},{},[4812],{"type":29,"value":4813},"They were developed to solve business problems, often over many years, with countless updates, integrations, and customizations layered on top of one another, often without enough notes or documentation.",{"type":24,"tag":25,"props":4815,"children":4816},{},[4817],{"type":29,"value":4818},"As a result, organizations frequently face challenges such as:",{"type":24,"tag":266,"props":4820,"children":4821},{},[4822,4827,4832,4837,4842,4847,4852],{"type":24,"tag":270,"props":4823,"children":4824},{},[4825],{"type":29,"value":4826},"Limited or outdated documentation",{"type":24,"tag":270,"props":4828,"children":4829},{},[4830],{"type":29,"value":4831},"Business-critical logic buried in code",{"type":24,"tag":270,"props":4833,"children":4834},{},[4835],{"type":29,"value":4836},"Aging technology stacks",{"type":24,"tag":270,"props":4838,"children":4839},{},[4840],{"type":29,"value":4841},"Complex integrations",{"type":24,"tag":270,"props":4843,"children":4844},{},[4845],{"type":29,"value":4846},"Security vulnerabilities",{"type":24,"tag":270,"props":4848,"children":4849},{},[4850],{"type":29,"value":4851},"Institutional knowledge concentrated among a few employees",{"type":24,"tag":270,"props":4853,"children":4854},{},[4855],{"type":29,"value":4856},"Difficulty finding developers with expertise in older technologies",{"type":24,"tag":25,"props":4858,"children":4859},{},[4860],{"type":29,"value":4861},"Before modernization can begin, teams must first understand what they have.",{"type":24,"tag":25,"props":4863,"children":4864},{},[4865],{"type":29,"value":4866},"Historically, that process has required hundreds or even thousands of hours of manual investigation.",{"type":24,"tag":25,"props":4868,"children":4869},{},[4870],{"type":29,"value":4871},"Developers review source code, trace dependencies, interview stakeholders, and create documentation from scratch. The uncertainty associated with this phase often causes organizations to delay modernization efforts altogether.",{"type":24,"tag":51,"props":4873,"children":4875},{"id":4874},"how-ai-assisted-modernization-changes-the-economics",[4876],{"type":29,"value":4877},"How AI-Assisted Modernization Changes the Economics",{"type":24,"tag":25,"props":4879,"children":4880},{},[4881],{"type":29,"value":4882},"We’ve noticed that when a lot of business leaders hear the term AI, they think of a black box.",{"type":24,"tag":25,"props":4884,"children":4885},{},[4886],{"type":29,"value":4887},"Data goes in. An answer comes out. AI does it all.",{"type":24,"tag":25,"props":4889,"children":4890},{},[4891],{"type":29,"value":4892},"That perception makes sense. Most discussions about AI focus on the outputs rather than the process behind them.",{"type":24,"tag":25,"props":4894,"children":4895},{},[4896],{"type":29,"value":4897},"In software modernization, however, AI delivers value in a different way.",{"type":24,"tag":25,"props":4899,"children":4900},{},[4901],{"type":29,"value":4902},"Rather than replacing human decision-making, AI functions as an intelligent development tool that helps teams process information faster and uncover insights more efficiently.",{"type":24,"tag":25,"props":4904,"children":4905},{},[4906],{"type":29,"value":4907},"In our legacy modernization projects, we’ve used AI to help teams:",{"type":24,"tag":266,"props":4909,"children":4910},{},[4911,4916,4921,4926,4931,4936,4941,4946,4951],{"type":24,"tag":270,"props":4912,"children":4913},{},[4914],{"type":29,"value":4915},"Analyze large codebases",{"type":24,"tag":270,"props":4917,"children":4918},{},[4919],{"type":29,"value":4920},"Generate technical documentation",{"type":24,"tag":270,"props":4922,"children":4923},{},[4924],{"type":29,"value":4925},"Identify dependencies and integrations",{"type":24,"tag":270,"props":4927,"children":4928},{},[4929],{"type":29,"value":4930},"Explain unfamiliar programming languages",{"type":24,"tag":270,"props":4932,"children":4933},{},[4934],{"type":29,"value":4935},"Surface hidden business logic",{"type":24,"tag":270,"props":4937,"children":4938},{},[4939],{"type":29,"value":4940},"Accelerate testing efforts",{"type":24,"tag":270,"props":4942,"children":4943},{},[4944],{"type":29,"value":4945},"Recommend modernization pathways",{"type":24,"tag":270,"props":4947,"children":4948},{},[4949],{"type":29,"value":4950},"Create migration roadmaps",{"type":24,"tag":270,"props":4952,"children":4953},{},[4954],{"type":29,"value":4955},"Highlight potential risks and bottlenecks",{"type":24,"tag":25,"props":4957,"children":4958},{},[4959],{"type":29,"value":4960},"While those capabilities are valuable individually, the real advantage comes from how they work together.",{"type":24,"tag":25,"props":4962,"children":4963},{},[4964],{"type":29,"value":4965},"In practice, AI-assisted modernization isn't a collection of separate tasks. It's a connected workflow where each output helps accelerate the next stage of the project.",{"type":24,"tag":25,"props":4967,"children":4968},{},[4969],{"type":29,"value":4970},"For example, we often use AI to help write behavioral tests that exercise parts of a legacy system that may have little or no documentation. Those tests don't just improve quality. They help surface business rules that have been buried in code for years.",{"type":24,"tag":25,"props":4972,"children":4973},{},[4974],{"type":29,"value":4975},"Because those tests are written in business-friendly language, they can also serve as documentation. AI can then help summarize those behaviors for stakeholders, making it easier for subject matter experts to confirm whether the system is working as intended or identify areas where the documented behavior no longer reflects current business needs.",{"type":24,"tag":25,"props":4977,"children":4978},{},[4979],{"type":29,"value":4980},"The same pattern appears throughout modernization efforts. AI can help developers analyze existing code, generate documentation, create tests, identify dependencies, and produce a significant amount of modernized code. Each step produces knowledge that informs the next one, creating a feedback loop that helps teams understand legacy systems more quickly and make better modernization decisions.",{"type":24,"tag":25,"props":4982,"children":4983},{},[4984],{"type":29,"value":4985},"This is why the greatest value of AI isn't automation for its own sake. It's the ability to help experienced engineers uncover, validate, document, and modernize complex systems more efficiently while keeping human expertise at the center of the process.",{"type":24,"tag":51,"props":4987,"children":4989},{"id":4988},"what-business-leaders-get-wrong-about-ai",[4990],{"type":29,"value":4991},"What Business Leaders Get Wrong About AI",{"type":24,"tag":25,"props":4993,"children":4994},{},[4995],{"type":29,"value":4996},"Many executives are interested in AI but remain skeptical about adopting it for mission-critical initiatives, which is entirely reasonable.",{"type":24,"tag":25,"props":4998,"children":4999},{},[5000],{"type":29,"value":5001},"The problem is that public conversations about AI often frame it as either a miracle solution or an existential threat. The reality, however, is much more practical.",{"type":24,"tag":1033,"props":5003,"children":5005},{"id":5004},"concern-1-can-we-trust-ai",[5006],{"type":29,"value":5007},"Concern #1: Can We Trust AI?",{"type":24,"tag":25,"props":5009,"children":5010},{},[5011],{"type":29,"value":5012},"Business leaders know that AI can hallucinate and make mistakes.",{"type":24,"tag":25,"props":5014,"children":5015},{},[5016],{"type":29,"value":5017},"When decisions involve critical systems, customer data, regulatory requirements, or core business operations, accuracy matters.",{"type":24,"tag":25,"props":5019,"children":5020},{},[5021],{"type":29,"value":5022},"We encourage organizations not to blindly trust AI-generated outputs. They should validate them.",{"type":24,"tag":25,"props":5024,"children":5025},{},[5026],{"type":29,"value":5027},"That is why successful AI-assisted modernization initiatives keep experienced engineers involved throughout the process.",{"type":24,"tag":1033,"props":5029,"children":5031},{"id":5030},"concern-2-will-ai-understand-our-business",[5032],{"type":29,"value":5033},"Concern #2: Will AI Understand Our Business?",{"type":24,"tag":25,"props":5035,"children":5036},{},[5037],{"type":29,"value":5038},"Every company has unique processes, workflows, and institutional knowledge.",{"type":24,"tag":25,"props":5040,"children":5041},{},[5042],{"type":29,"value":5043},"A legacy application often contains years of business decisions that are not documented anywhere else.",{"type":24,"tag":25,"props":5045,"children":5046},{},[5047],{"type":29,"value":5048},"AI can help identify and explain patterns within a codebase, but understanding why those decisions were made requires human expertise and stakeholder collaboration.",{"type":24,"tag":1033,"props":5050,"children":5052},{"id":5051},"concern-3-what-about-security-and-compliance",[5053],{"type":29,"value":5054},"Concern #3: What About Security and Compliance?",{"type":24,"tag":25,"props":5056,"children":5057},{},[5058],{"type":29,"value":5059},"Security, governance, and compliance concerns are among the most common questions executives raise about AI adoption.",{"type":24,"tag":25,"props":5061,"children":5062},{},[5063],{"type":29,"value":5064},"These concerns become especially important in industries such as healthcare, finance, manufacturing, and government.",{"type":24,"tag":25,"props":5066,"children":5067},{},[5068],{"type":29,"value":5069},"Organizations need confidence that AI-assisted processes align with their security requirements, compliance obligations, and risk management frameworks.",{"type":24,"tag":1033,"props":5071,"children":5073},{"id":5072},"concern-4-are-we-replacing-human-expertise",[5074],{"type":29,"value":5075},"Concern #4: Are We Replacing Human Expertise?",{"type":24,"tag":25,"props":5077,"children":5078},{},[5079],{"type":29,"value":5080},"Perhaps the biggest misconception is that AI exists to replace developers, architects, and technical leaders.",{"type":24,"tag":25,"props":5082,"children":5083},{},[5084],{"type":29,"value":5085},"The most successful organizations are not removing people from the process. Instead, they’re using AI to help their teams work more effectively.",{"type":24,"tag":51,"props":5087,"children":5089},{"id":5088},"why-human-centered-ai-creates-better-modernization-outcomes",[5090],{"type":29,"value":5091},"Why Human-Centered AI Creates Better Modernization Outcomes",{"type":24,"tag":25,"props":5093,"children":5094},{},[5095],{"type":29,"value":5096},"At Art+Logic, we view AI as a tool, not a substitute for expertise.",{"type":24,"tag":25,"props":5098,"children":5099},{},[5100],{"type":29,"value":5101},"AI can help accelerate analysis, generate documentation, identify patterns, and reduce repetitive work.",{"type":24,"tag":25,"props":5103,"children":5104},{},[5105],{"type":29,"value":5106},"But AI cannot replace the judgment required to make strategic modernization decisions.",{"type":24,"tag":25,"props":5108,"children":5109},{},[5110],{"type":29,"value":5111},"Human experts remain responsible for:",{"type":24,"tag":266,"props":5113,"children":5114},{},[5115,5120,5125,5130,5135,5140,5145,5150],{"type":24,"tag":270,"props":5116,"children":5117},{},[5118],{"type":29,"value":5119},"Technology strategy",{"type":24,"tag":270,"props":5121,"children":5122},{},[5123],{"type":29,"value":5124},"Architecture decisions",{"type":24,"tag":270,"props":5126,"children":5127},{},[5128],{"type":29,"value":5129},"Security reviews",{"type":24,"tag":270,"props":5131,"children":5132},{},[5133],{"type":29,"value":5134},"Risk assessment",{"type":24,"tag":270,"props":5136,"children":5137},{},[5138],{"type":29,"value":5139},"Business alignment",{"type":24,"tag":270,"props":5141,"children":5142},{},[5143],{"type":29,"value":5144},"Quality assurance",{"type":24,"tag":270,"props":5146,"children":5147},{},[5148],{"type":29,"value":5149},"Stakeholder communication",{"type":24,"tag":270,"props":5151,"children":5152},{},[5153],{"type":29,"value":5154},"Long-term maintainability",{"type":24,"tag":25,"props":5156,"children":5157},{},[5158],{"type":29,"value":5159},"This human-in-the-loop approach combines the speed and efficiency of AI with the experience and accountability of seasoned software professionals. Organizations benefit from faster discovery and analysis without sacrificing quality, governance, or business context.",{"type":24,"tag":25,"props":5161,"children":5162},{},[5163],{"type":29,"value":5164},"That balance is where AI creates the greatest value.",{"type":24,"tag":51,"props":5166,"children":5168},{"id":5167},"real-world-results-from-ai-assisted-modernization",[5169],{"type":29,"value":5170},"Real-World Results from AI-Assisted Modernization",{"type":24,"tag":25,"props":5172,"children":5173},{},[5174],{"type":29,"value":5175},"The benefits of AI-assisted modernization are already being realized in real-world projects.",{"type":24,"tag":25,"props":5177,"children":5178},{},[5179],{"type":29,"value":5180},"In a recent engagement, Art+Logic used AI-assisted development techniques to help analyze and modernize a complex legacy application. Our engineers used AI to accelerate code analysis, enhance documentation efforts, and write code, enabling our developers to spend more time validating assumptions, understanding business requirements, and making informed technical decisions.",{"type":24,"tag":25,"props":5182,"children":5183},{},[5184],{"type":29,"value":5185},"The result was a more efficient modernization process while maintaining the human oversight required for long-term success.",{"type":24,"tag":25,"props":5187,"children":5188},{},[5189],{"type":29,"value":5190},"Learn more about our approach in our AI-Assisted Modernization Case Study:",{"type":24,"tag":25,"props":5192,"children":5193},{},[5194],{"type":24,"tag":99,"props":5195,"children":5198},{"href":5196,"rel":5197},"https://artandlogic.com/ai-assisted-modernization/",[103],[5199],{"type":29,"value":5196},{"type":24,"tag":51,"props":5201,"children":5203},{"id":5202},"ai-is-making-previously-delayed-projects-possible",[5204],{"type":29,"value":5205},"AI Is Making Previously Delayed Projects Possible",{"type":24,"tag":25,"props":5207,"children":5208},{},[5209],{"type":29,"value":5210},"Many organizations have postponed modernization because the economics simply didn't work.",{"type":24,"tag":25,"props":5212,"children":5213},{},[5214],{"type":29,"value":5215},"The required investment felt too large, or the timeline felt too long, or the risks felt too difficult to predict. AI-assisted development is helping change those realities.",{"type":24,"tag":25,"props":5217,"children":5218},{},[5219],{"type":29,"value":5220},"By reducing the time required to understand legacy systems, organizations can create modernization plans more quickly, make better-informed decisions, and allocate resources more effectively.",{"type":24,"tag":25,"props":5222,"children":5223},{},[5224],{"type":29,"value":5225},"The complexity of modernization hasn't disappeared, but it has become more manageable. For many organizations, that shift is enough to move modernization from the \"someday\" category into an actionable strategic initiative.",{"type":24,"tag":51,"props":5227,"children":5229},{"id":5228},"the-future-of-legacy-modernization-is-human-led-and-ai-assisted",[5230],{"type":29,"value":5231},"The Future of Legacy Modernization Is Human-Led and AI-Assisted",{"type":24,"tag":25,"props":5233,"children":5234},{},[5235],{"type":29,"value":5236},"The organizations seeing the greatest value from AI are not handing over decision-making to algorithms.",{"type":24,"tag":25,"props":5238,"children":5239},{},[5240],{"type":29,"value":5241},"They are combining AI-powered tools with experienced professionals who understand technology, business objectives, and organizational realities.",{"type":24,"tag":25,"props":5243,"children":5244},{},[5245],{"type":29,"value":5246},"AI helps teams move faster, while human expertise ensures they move in the right direction.",{"type":24,"tag":25,"props":5248,"children":5249},{},[5250],{"type":29,"value":5251},"As legacy systems continue to age and technology expectations continue to evolve, this combination of human insight and AI-assisted efficiency is making modernization projects more achievable than ever before.",{"type":24,"tag":25,"props":5253,"children":5254},{},[5255],{"type":29,"value":5256},"For organizations that have delayed modernization because of cost, complexity, or uncertainty, the opportunity has changed. The tools are better, and the process is faster. And with the right human expertise guiding the effort, modernization is becoming a far more practical path forward.",{"type":24,"tag":51,"props":5258,"children":5260},{"id":5259},"frequently-asked-questions",[5261],{"type":29,"value":5262},"Frequently Asked Questions",{"type":24,"tag":1033,"props":5264,"children":5266},{"id":5265},"what-is-ai-assisted-legacy-modernization",[5267],{"type":29,"value":5268},"What is AI-assisted legacy modernization?",{"type":24,"tag":25,"props":5270,"children":5271},{},[5272],{"type":29,"value":5273},"AI-assisted legacy modernization uses AI tools to help development teams analyze code, generate documentation, identify dependencies, and accelerate planning activities while keeping human experts responsible for decision-making and implementation.",{"type":24,"tag":1033,"props":5275,"children":5277},{"id":5276},"can-ai-modernize-a-legacy-application-without-human-involvement",[5278],{"type":29,"value":5279},"Can AI modernize a legacy application without human involvement?",{"type":24,"tag":25,"props":5281,"children":5282},{},[5283],{"type":29,"value":5284},"No. AI can accelerate analysis and discovery, but successful modernization still requires human expertise to evaluate business requirements, design architectures, manage risk, and ensure quality.",{"type":24,"tag":1033,"props":5286,"children":5288},{"id":5287},"how-does-ai-reduce-legacy-modernization-costs",[5289],{"type":29,"value":5290},"How does AI reduce legacy modernization costs?",{"type":24,"tag":25,"props":5292,"children":5293},{},[5294],{"type":29,"value":5295},"AI reduces the manual effort associated with code analysis, documentation, testing, and discovery activities, allowing organizations to spend less time understanding existing systems and more time creating modernization solutions.",{"type":24,"tag":1033,"props":5297,"children":5299},{"id":5298},"is-ai-assisted-modernization-secure",[5300],{"type":29,"value":5301},"Is AI-assisted modernization secure?",{"type":24,"tag":25,"props":5303,"children":5304},{},[5305],{"type":29,"value":5306},"When implemented with appropriate governance, security controls, and human oversight, AI-assisted modernization can support enterprise security and compliance requirements.",{"type":24,"tag":1033,"props":5308,"children":5310},{"id":5309},"why-are-organizations-investing-in-ai-assisted-modernization-now",[5311],{"type":29,"value":5312},"Why are organizations investing in AI-assisted modernization now?",{"type":24,"tag":25,"props":5314,"children":5315},{},[5316],{"type":29,"value":5317},"Advances in AI-powered development tools have made it easier and faster to understand legacy systems, reducing many of the barriers that previously made modernization projects difficult to justify.",{"type":24,"tag":1033,"props":5319,"children":5321},{"id":5320},"can-you-use-ai-to-write-code-too",[5322],{"type":29,"value":5323},"Can you use AI to write code, too?",{"type":24,"tag":25,"props":5325,"children":5326},{},[5327],{"type":29,"value":5328},"Yes, AI can be used to write code more efficiently. An engineer must still review that code, however, since sometimes AI writes code like an eager intern.",{"title":8,"searchDepth":1122,"depth":1122,"links":5330},[5331,5332,5333,5334,5340,5341,5342,5343,5344],{"id":4760,"depth":1122,"text":4763},{"id":4800,"depth":1122,"text":4803},{"id":4874,"depth":1122,"text":4877},{"id":4988,"depth":1122,"text":4991,"children":5335},[5336,5337,5338,5339],{"id":5004,"depth":1142,"text":5007},{"id":5030,"depth":1142,"text":5033},{"id":5051,"depth":1142,"text":5054},{"id":5072,"depth":1142,"text":5075},{"id":5088,"depth":1122,"text":5091},{"id":5167,"depth":1122,"text":5170},{"id":5202,"depth":1122,"text":5205},{"id":5228,"depth":1122,"text":5231},{"id":5259,"depth":1122,"text":5262,"children":5345},[5346,5347,5348,5349,5350,5351],{"id":5265,"depth":1142,"text":5268},{"id":5276,"depth":1142,"text":5279},{"id":5287,"depth":1142,"text":5290},{"id":5298,"depth":1142,"text":5301},{"id":5309,"depth":1142,"text":5312},{"id":5320,"depth":1142,"text":5323},"content:cperez:2026-06-25:ai_makes_modernization_feasible.md","cperez/2026-06-25/ai_makes_modernization_feasible.md","cperez/2026-06-25/ai_makes_modernization_feasible",{"_path":5356,"_dir":5357,"_draft":7,"_partial":7,"_locale":8,"title":5358,"description":5359,"publishDate":5360,"image":5361,"author":5362,"tags":5363,"excerpt":5359,"body":5369,"_type":1150,"_id":5619,"_source":1152,"_file":5620,"_stem":5621,"_extension":1155},"/cperez/2026-06-17/xamarin-to-maui","2026-06-17","Migrating a Xamarin Medical Application to .NET MAUI","A widely used medical reference application built with Xamarin had become increasingly difficult to maintain as platform support deadlines approached. The client needed to modernize the application before operating system changes and framework deprecations created larger compatibility risks.","2026-06-22","/cperez/2026-06-17/img/xamarin-to-maui.png",{"name":13,"user":14},[1164,5364,5365,5366,5367,5368],"xamarin",".net","maui","app migration","mobile",{"type":21,"children":5370,"toc":5612},[5371,5375,5380,5386,5391,5396,5424,5429,5435,5440,5445,5473,5479,5484,5489,5517,5522,5527,5533,5538,5543,5548,5553,5559,5564,5569,5607],{"type":24,"tag":25,"props":5372,"children":5373},{},[5374],{"type":29,"value":5359},{"type":24,"tag":25,"props":5376,"children":5377},{},[5378],{"type":29,"value":5379},"Art+Logic led the successful migration of the application to .NET MAUI, preserving the existing C# ecosystem while modernizing architecture, improving usability, and reducing future maintenance risk.",{"type":24,"tag":51,"props":5381,"children":5383},{"id":5382},"the-challenge",[5384],{"type":29,"value":5385},"The Challenge",{"type":24,"tag":25,"props":5387,"children":5388},{},[5389],{"type":29,"value":5390},"The original Xamarin application served medical residents and healthcare professionals who relied on quick access to treatment guides, splinting references, and antibiotic data while working in fast-paced clinical environments.",{"type":24,"tag":25,"props":5392,"children":5393},{},[5394],{"type":29,"value":5395},"Migrating the application presented several major obstacles:",{"type":24,"tag":266,"props":5397,"children":5398},{},[5399,5404,5409,5414,5419],{"type":24,"tag":270,"props":5400,"children":5401},{},[5402],{"type":29,"value":5403},"Xamarin support was aging toward eventual deprecation",{"type":24,"tag":270,"props":5405,"children":5406},{},[5407],{"type":29,"value":5408},"Platform APIs and libraries had changed substantially",{"type":24,"tag":270,"props":5410,"children":5411},{},[5412],{"type":29,"value":5413},"The application contained years of accumulated technical debt",{"type":24,"tag":270,"props":5415,"children":5416},{},[5417],{"type":29,"value":5418},"A complete rewrite would have been cost-prohibitive",{"type":24,"tag":270,"props":5420,"children":5421},{},[5422],{"type":29,"value":5423},"Reliability requirements were extremely high due to medical usage contexts",{"type":24,"tag":25,"props":5425,"children":5426},{},[5427],{"type":29,"value":5428},"The client needed a migration path that balanced cost, stability, and long-term maintainability.",{"type":24,"tag":51,"props":5430,"children":5432},{"id":5431},"why-net-maui",[5433],{"type":29,"value":5434},"Why .NET MAUI",{"type":24,"tag":25,"props":5436,"children":5437},{},[5438],{"type":29,"value":5439},"After evaluating alternatives, including native mobile development and Flutter, the team selected .NET MAUI because it allowed the client to retain its existing C# investment and many familiar architectural patterns.",{"type":24,"tag":25,"props":5441,"children":5442},{},[5443],{"type":29,"value":5444},"Choosing MAUI enabled:",{"type":24,"tag":266,"props":5446,"children":5447},{},[5448,5453,5458,5463,5468],{"type":24,"tag":270,"props":5449,"children":5450},{},[5451],{"type":29,"value":5452},"Greater code continuity",{"type":24,"tag":270,"props":5454,"children":5455},{},[5456],{"type":29,"value":5457},"Reduced retraining costs",{"type":24,"tag":270,"props":5459,"children":5460},{},[5461],{"type":29,"value":5462},"Faster migration timelines",{"type":24,"tag":270,"props":5464,"children":5465},{},[5466],{"type":29,"value":5467},"Easier long-term maintenance",{"type":24,"tag":270,"props":5469,"children":5470},{},[5471],{"type":29,"value":5472},"Lower overall implementation risk",{"type":24,"tag":51,"props":5474,"children":5476},{"id":5475},"the-migration-strategy",[5477],{"type":29,"value":5478},"The Migration Strategy",{"type":24,"tag":25,"props":5480,"children":5481},{},[5482],{"type":29,"value":5483},"Rather than rebuilding the entire application at once, Art+Logic approached the migration incrementally.",{"type":24,"tag":25,"props":5485,"children":5486},{},[5487],{"type":29,"value":5488},"The team:",{"type":24,"tag":266,"props":5490,"children":5491},{},[5492,5497,5502,5507,5512],{"type":24,"tag":270,"props":5493,"children":5494},{},[5495],{"type":29,"value":5496},"Reworked application layers piece by piece",{"type":24,"tag":270,"props":5498,"children":5499},{},[5500],{"type":29,"value":5501},"Updated framework dependencies",{"type":24,"tag":270,"props":5503,"children":5504},{},[5505],{"type":29,"value":5506},"Modernized UI components",{"type":24,"tag":270,"props":5508,"children":5509},{},[5510],{"type":29,"value":5511},"Refactored platform-specific functionality",{"type":24,"tag":270,"props":5513,"children":5514},{},[5515],{"type":29,"value":5516},"Continuously tested each migrated module",{"type":24,"tag":25,"props":5518,"children":5519},{},[5520],{"type":29,"value":5521},"AI-assisted tooling helped accelerate repetitive migration tasks, but engineers maintained direct oversight throughout the process to validate generated code and ensure functional accuracy.",{"type":24,"tag":25,"props":5523,"children":5524},{},[5525],{"type":29,"value":5526},"This careful balance between automation and engineering review allowed the team to move quickly without sacrificing reliability.",{"type":24,"tag":51,"props":5528,"children":5530},{"id":5529},"improving-the-user-experience",[5531],{"type":29,"value":5532},"Improving the User Experience",{"type":24,"tag":25,"props":5534,"children":5535},{},[5536],{"type":29,"value":5537},"The migration effort became an opportunity to rethink several critical workflows.",{"type":24,"tag":25,"props":5539,"children":5540},{},[5541],{"type":29,"value":5542},"One major enhancement involved redesigning a complex antibiogram table used by physicians to cross-reference bacteria and antibiotics. The previous interface relied heavily on manual scrolling, making navigation cumbersome on mobile devices.",{"type":24,"tag":25,"props":5544,"children":5545},{},[5546],{"type":29,"value":5547},"The updated experience introduced filtering and guided selection workflows that dramatically improved speed and usability for clinicians.",{"type":24,"tag":25,"props":5549,"children":5550},{},[5551],{"type":29,"value":5552},"The team also developed a new licensing and account-management system that enabled users to purchase and manage digital content licenses directly.",{"type":24,"tag":51,"props":5554,"children":5556},{"id":5555},"the-results",[5557],{"type":29,"value":5558},"The Results",{"type":24,"tag":25,"props":5560,"children":5561},{},[5562],{"type":29,"value":5563},"The migration to .NET MAUI was fully successful.",{"type":24,"tag":25,"props":5565,"children":5566},{},[5567],{"type":29,"value":5568},"Outcomes included:",{"type":24,"tag":266,"props":5570,"children":5571},{},[5572,5577,5582,5587,5592,5597,5602],{"type":24,"tag":270,"props":5573,"children":5574},{},[5575],{"type":29,"value":5576},"100% resolution of known Xamarin-version bugs",{"type":24,"tag":270,"props":5578,"children":5579},{},[5580],{"type":29,"value":5581},"Successful transition to a modern supported framework",{"type":24,"tag":270,"props":5583,"children":5584},{},[5585],{"type":29,"value":5586},"Improved mobile UX and navigation",{"type":24,"tag":270,"props":5588,"children":5589},{},[5590],{"type":29,"value":5591},"Expanded licensing functionality",{"type":24,"tag":270,"props":5593,"children":5594},{},[5595],{"type":29,"value":5596},"Delivery several hundred hours under budget",{"type":24,"tag":270,"props":5598,"children":5599},{},[5600],{"type":29,"value":5601},"Reduced long-term platform risk",{"type":24,"tag":270,"props":5603,"children":5604},{},[5605],{"type":29,"value":5606},"Streamlined development and maintenance workflows",{"type":24,"tag":25,"props":5608,"children":5609},{},[5610],{"type":29,"value":5611},"The project demonstrated that Xamarin-to-MAUI migrations can be both technically successful and financially viable when approached with the right modernization strategy, tooling, and engineering oversight.",{"title":8,"searchDepth":1122,"depth":1122,"links":5613},[5614,5615,5616,5617,5618],{"id":5382,"depth":1122,"text":5385},{"id":5431,"depth":1122,"text":5434},{"id":5475,"depth":1122,"text":5478},{"id":5529,"depth":1122,"text":5532},{"id":5555,"depth":1122,"text":5558},"content:cperez:2026-06-17:xamarin-to-maui.md","cperez/2026-06-17/xamarin-to-maui.md","cperez/2026-06-17/xamarin-to-maui",1783408212218]