Blog

Most AI and automation projects do not fail because the idea was bad. They fail because the system cannot survive real operations. A common story looks like this. A team builds a working pilot in a few weeks. The demo looks great. Leadership is excited. Then the same pilot hits production and everything slows down. Data is missing. Exceptions show up. Security asks hard questions. The business is unsure who owns it after go-live. Adoption is patchy because the workflow is not inside the tools people already use. If you are planning AI or automation, this is the article to read before you spend your budget. This guide explains the most common problems teams run into, why they happen, and what to do instead. It uses simple language and practical steps. No hype. First, a simple definition (so we stay clear) Automation means software follows steps you define. Example: “If the status is Approved, then create a ticket and send an email.” RPA (Robotic Process Automation) is a type of automation. It uses software “bots” to click through screens and move data across systems, like a human would. AI is useful when the task involves language, patterns, or judgment support. Example: reading an email, identifying intent, drafting a response, or summarizing a case. Intelligent automation often combines both. Rules handle what should be predictable. AI helps with what is messy. Controls keep it safe. Challenge 1: Teams automate too early, before the workflow is truly understood Many teams start with tools. They should start with the work. If you do not understand the workflow, automation will amplify confusion. It will move faster, but in the wrong direction. What “not understood” looks like: What to do instead: A quick test: if you cannot explain the workflow in one page, you are not ready to automate it. Challenge 2: Data issues break AI and automation faster than anything else [Image: Data pipeline from multiple systems into a single “clean view” | Alt: Data quality and access for AI ] AI needs data. Automation needs data too. Poor data is the silent killer. This problem usually has three parts. 1) Data quality If records are incomplete or inconsistent, the system will make bad decisions. “Bad in, bad out” is real. 2) Data access Even if the data exists, your system may not be allowed to access it. This is common in regulated environments. 3) Data meaning Two systems may use the same field name but mean different things. That creates logic errors and wrong outcomes. What to do instead: If your AI cannot explain what it used and where it came from, you will struggle with trust later. Challenge 3: The solution is built outside real workflows, so adoption stays low A separate portal is a common mistake. People do not want “one more tool.” They want less work inside the tools they already use. When AI and automation live outside daily workflows, three things happen: What to do instead: This is also why platform work matters. Many teams want automation that works inside major platforms, not next to them. Challenge 4: People and change management get ignored, then everything stalls Teams often treat implementation as a technical project. It is also a people project. Even strong automation fails if: What to do instead: A helpful mindset: adoption is part of the system design, not a separate rollout task. Challenge 5: Governance and compliance are treated as paperwork, not as product design If your system touches customer operations, governance is not optional. Good governance answers simple questions: Frameworks like the NIST AI Risk Management Framework focus on building “trustworthy AI” through structured risk management. This includes governance practices and ongoing measurement, not just model building. (NIST) Also, regulation is moving toward risk-based expectations. The EU’s AI Act is built around risk levels, with stricter rules for higher-risk uses. (Digital Strategy) What to do instead: If you are using generative AI, treat it with extra care. NIST has a dedicated companion profile for generative AI risk management, which highlights why testing and controls matter. (NIST Publications) Challenge 6: Security and privacy get handled late, and delays pile up [Image: Security checklist with access controls, encryption, logging | Alt: Security and privacy for automation ] Security teams do not block projects because they dislike innovation. They block projects because unclear systems create risk. This is where many projects get stuck: Standards like ISO/IEC 27001 exist because security needs a management system, not just tools. (ISO) And modern privacy laws, including GDPR principles, emphasize integrity and confidentiality of personal data. (GDPR) What to do instead (simple version): This is not “extra work.” It prevents months of delay. Challenge 7: Scaling breaks because there is no “run” plan after go-live [Image: Monitoring dashboard with alerts and error rates | Alt: Operating model for AI systems ] A pilot is not a production system. Production needs an operating model. That means: Without this, small issues turn into bigger failures: What to do instead: A good rule: go-live is the start of ownership, not the end of delivery. Challenge 8: ROI is measured poorly, so leadership loses confidence [Image: Simple ROI model with time saved, error reduction, and cost | Alt: Outcome metrics for automation ROI ] Many teams use vanity metrics because they are easy: These do not prove business value. Better outcome metrics (pick 3 to start): A simple ROI model (easy and honest): This keeps the conversation grounded. A practical “ready for implementation” checklist [Image: Checklist page with boxes ticked | Alt: AI and automation readiness checklist ] Before you scale beyond a pilot, you should be able to answer yes to most of these: Workflow clarity Data readiness Controls Operations If you cannot answer these, the project may still succeed, but it will be slower and riskier. A simple implementation plan you can follow (30 to 90 days) [Image: Timeline with Discover -> Build -> Run -> Improve | Alt: 30-60-90 day plan for

A vendor put a number in front of a finance director last spring: 82 percent of invoices would go straight through, untouched. Sixty thousand invoices a year, eleven minutes each by hand. The arithmetic on the slide came out at four hundred and sixteen thousand dollars of freed labour against a hundred and fifty-two thousand of annual cost. A hundred and seventy-four percent return. The number was not dishonest. It was incomplete in three specific places, and each of the three maps onto one of the trends everybody is writing about this year. That is the useful way into intelligent automation: not as a list of capabilities, but as a list of things that each generate work someone has to absorb after go-live. What intelligent automation actually is Intelligent automation is the combination of rule-based automation, robotic process automation (RPA), machine learning models, and workflow orchestration, applied to a single business process end to end. RPA is software that drives existing applications the way a person would, through their screens and interfaces. Orchestration is the layer that decides what happens next and who gets involved. The definition needs no citation because it is a description, not a claim. What needs a citation is the origin of the word everyone reaches for next. Trend one: hyperautomation, and the discipline it was defined with Gartner introduced hyperautomation as its first of ten strategic technology trends for 2020, in research published on 21 October 2019 by David Cearley, Nick Jones, David Smith, Brian Burke, Arun Chandrasekaran and CK Lu. The definition is more demanding than the way the word gets used now. Gartner described hyperautomation hyperautomation as the combination of multiple machine learning, packaged software and automation tools to deliver work, and specified that it refers “not only to the breadth of the pallet of tools, but also to all the steps of automation itself (discover, analyze, design, automate, measure, monitor and reassess).” Read that list of steps again. Three of the eight are things you do after the automation is running: measure, monitor, reassess. Gartner also said plainly that “RPA alone is not hyperautomation.” So the term that gets used to mean more automation was defined to mean automation plus a measurement and reassessment loop. Most programmes buy the first half. The reason this matters for the invoice model is that the vendor’s 82 percent touchless rate assumed the remaining 18 percent would still take eleven minutes each, the same as before. Exceptions do not work that way. When the clean cases leave the queue, what remains is the hard residue, and it takes longer per item than the blended average ever did. Trend two: AI-assisted workflow, where the exception rate is the whole story Rule-based automation fails loudly. A rule either matches or it does not. AI-assisted workflow fails quietly: it produces an output that is well-formed, plausible, and wrong, and nothing in the pipeline objects. That is why the observed exception rate, not the touchless rate, is the number the business case turns on. In the invoice case the real figure after four months of production was 26 percent, not 18, and those exceptions averaged fourteen minutes each rather than eleven, because the residue was the awkward supplier formats and the partial deliveries. Here is the whole model, and it is illustrative. Substitute your own figures; what is being shown is the shape of the calculation, not a price list. Sixty thousand invoices a year. Eleven minutes each by hand. Labour rate derived from a fully loaded cost of $71,000 for a processor, divided by productive hours rather than paid hours: 2,080 paid hours less 26 percent shrinkage for leave, training, sickness and non-productive time gives 1,539.2 productive hours, so $46.13 an hour. Baseline: 11,000 hours, or $507,406 a year. After go-live, at a 26 percent exception rate and fourteen minutes per exception, exception handling consumes 3,640 hours. Freed hours: 7,360, worth $339,501 at the processor rate. Annual cost: build of $210,000 amortised over a three-year life is $70,000, plus $58,000 of licence share and $24,000 of support and maintenance. Total $152,000. Those are plausible market rates for a programme of this size rather than quotes from a specific price list, and should be treated as such. Then the part the vendor slide did not have, which is the subject of the next two trends. Trend three: low-code and no-code, and the inventory nobody is keeping Low-code and no-code platforms let people who are not developers build working applications. Gartner’s 2019 research called this democratisation of expertise and predicted it would accelerate through 2023, including “democratization of design (expanding on the low-code, no-code phenomena with automation of additional application development functions to empower the citizen-developer).” That happened. What it produces is an asset class with no owner. The Open Web Application Security Project, a vendor-neutral non-profit, maintains a Top 10 for exactly this, and its ninth entry, asset management failures, describes the mechanism better than any vendor page will: citizen-developed applications “are prone to being forgotten or abandoned while remaining active and functional,” and useful internal applications “become widely shared within the organization, scaling rapidly in usage and dependency without the necessary business continuity measure expected of more standardized and essential systems such as having designated owners, IT monitoring, or a Service Level Agreement (SLA).” Note what that is not. It is not a security-scare argument. It is an operations argument with a cost attached: something that is running, that people depend on, that nobody is named against. In the invoice programme there were 34 such assets by month four, and keeping an inventory current, with an owner name and a last-reviewed date against each one, took about nine hours per asset per year. 306 hours, at a reviewer rate of $67.57 an hour derived the same way from a $104,000 fully loaded cost. The counter-metric here pairs naturally: count assets built alongside assets with a named owner and a review date inside the last quarter. The first number

A statement of work crossed our desk last year with a line in the scope section that read, in full: “Automate the contract intake process.” No volumes, no definition of intake, no statement of where the process started or stopped. It had been signed by both parties. That line is not unusual, and it is not really about contracts. It is about a category error that runs through most legal automation projects. “Intake” in that firm turned out to be seven separate waits: a business unit emailing a shared mailbox, someone opening the mailbox, someone deciding which reviewer it belonged to, the reviewer opening it, the reviewer asking for the missing counterparty details, the business unit answering, and the reviewer picking it up again. Almost none of the elapsed time was work. Nearly all of it was waiting for the next person to look. That distinction decides which legal workflows are worth automating first, and it is the organising idea of everything below. What intelligent automation means in legal work Intelligent automation is the combination of three things that used to be bought separately. Rule-based automation, usually called RPA (robotic process automation), moves data between systems and performs deterministic steps. Document intelligence reads a file and extracts structured fields from it. A model, increasingly a generative one, drafts or classifies or summarises. Orchestration decides which of these runs, in what order, and when a human is required. In legal work the useful framing is narrower than the vendor framing. Intelligent automation does not replace legal judgement, and any description of it that implies otherwise should be treated as a sales artefact. What it does is remove the steps between judgements: the routing, the chasing, the copying of the same eight fields into a third system, the assembling of the pack that a reviewer needs before the reviewer can think. Two acronyms recur below and are worth fixing now. ESI means electronically stored information, the term the discovery process uses for anything that lives in a system rather than on paper. GAI means generative artificial intelligence, which is the term the American Bar Association uses in its ethics guidance, so it is the term used here when discussing that guidance. Sort your use cases before you cost them The six workflows legal teams usually shortlist are not one category. They divide cleanly by what is actually holding them up, and the division changes both the business case and the risk posture. 1 Queue-bound work. The elapsed time is dominated by waiting for the next person to look at it. The work itself is short and largely uncontested. Automation here removes handoffs, and removing a handoff removes a wait, which is why the gain is large and shows up in days rather than minutes. Intake and triage, compliance evidence assembly, status communication to requesters and stakeholders, and matter reporting and billing preparation all sit here. 2 Judgement-bound work. The elapsed time is dominated by someone reading carefully. Automation here does not remove the reading; it changes what the reader is given. That can be a real gain, but it arrives with a verification obligation attached, and the verification is new work that did not exist before. Substantive contract review and discovery review sit here. The practical consequence is uncomfortable for pilot selection. Judgement-bound work is more interesting, demos better, and is what most vendors lead with. Queue-bound work is where the first measurable win lives. A programme that starts with contract review because it is impressive, rather than with intake because it is slow, tends to produce a well-received demonstration and no defensible number. The four queue-bound candidates Intake and triage. A request arrives, and something decides what it is, whether the mandatory information is present, which reviewer or queue it belongs to, and what the counterparty and value bands are. Where information is missing, the requester is asked automatically rather than after a reviewer notices. This is the single highest-yield legal automation in most organisations and it involves no legal judgement at all. Compliance tracking and evidence assembly. Obligations with dates attached, and the evidence that each was met, collected as the work happens rather than reconstructed before an audit. GDPR is explicit that this is the controller’s job rather than a nice-to-have: Article 5(2) states that the controller “shall be responsible for, and be able to demonstrate compliance with” the processing principles, and Article 30 sets out what the record of processing activities must contain and requires it to be made available to the supervisory authority on request. Stakeholder communication. The requester is told where their agreement is without anyone being asked. Most of the chase traffic in a legal inbox is not a request for work; it is a request for status, and status is a field, not a judgement. Matter reporting and billing preparation. Time, stage and volume data assembled into the shape the finance function and the client actually need, rather than reassembled by hand at month end. The two judgement-bound candidates 1 Contract review support. The system extracts the terms that matter (term length, renewal mechanics, liability cap, indemnity, governing law, termination triggers, data-protection clauses) and compares them against a playbook position. It does not approve anything. Its output is a reviewer’s starting position, which the reviewer then has to check, and the checking is real work. This distinction matters enough that it reappears in the model below. 2 Discovery support and legal holds. Custodian identification, hold notices, acknowledgement tracking and volume reduction before review. It is worth being accurate about what the reference model here actually says, because the sequence is often described as a pipeline and it is not one. EDRM (EDRM.NET) states plainly that its diagram “represents a conceptual view of the e-discovery process, not a literal, linear or waterfall model”, that “one may elect to carry out the steps in a different order than shown here”, and that the process is iterative: “one might repeat the same step numerous times, honing

One and a half minutes. That is what generated summaries take off the after-call work on a single voice contact in the model further down this page. It sounds too small to chase. Across a sixty-seat operation handling 358,800 contacts a year it comes to 8,970 hours, which is just under six full-time equivalents. Six people’s worth of time, and none of it is money yet. It becomes money only if somebody decides in advance what those six people will do instead, and then makes sure it happens. That decision is usually nobody’s job. It is the reason contact centre automation programmes report savings finance cannot find, and it is the thread running through everything below. So this is not a tour of features. It is the work ordered by where the money actually is, the four places it gets stuck, and the three numbers that decide whether any of it pays. Start where the time goes, not where the demo starts Vendor demonstrations open with the conversational interface, because that is the part that looks like the future. Cost sits somewhere less impressive: in the minutes after the customer has hung up, and in the manual steps between systems that nobody designed and everybody works around. That mismatch is the first decision, and getting it backwards is expensive. Front-end automation touches every contact and carries reputational risk on each one. Back-end automation touches the same volume with almost none, because the customer has already gone. If you are going to be wrong somewhere, be wrong where the customer cannot see it. One caution before picking a target, and it is the reason to map the work before shortlisting tools. Occasionally the workflow that scores highest on automatability is holding up something that is not operational at all: a compliance record, an audit trail, a judgment call that someone downstream depends on being made by a person. Automating it improves every figure on the dashboard and quietly removes the thing the business was relying on. No dashboard can show you that trade, which is why somebody has to go looking for it while the build is still cheap to cancel Map one high-volume workflow end to end before anything else: the trigger, the systems it crosses, the decisions a human makes and why, the exception paths, and the steps where being wrong causes harm. Teams that do this honestly all report the same finding. The pain is concentrated in the glue between systems, not in the systems themselves. The four seams where contact centre work gets stuck Work does not get lost inside systems. It gets lost passing between them, and between the people and software either side of a handoff. There are four such seams in a contact centre. Each one has automation worth doing, a way that automation flatters itself, and something specific you can sample to find out which is happening. Seam one: intake, and the handoff out of it Customers like self-service when it resolves the thing. They hate it when it holds them. Virtual agents handle status checks, policy questions and basic troubleshooting well; knowledge search works when it matches the customer’s own words rather than the taxonomy your content team built. The stakes at this seam are rising on a documented timeline. Gartner’s published guidance on customer service artificial intelligence (AI) states that by 2028, at least 70% of customers will use a conversational AI interface to start their customer service journey. Read that as a claim about the front door, not about resolution. If most journeys will begin in a conversational interface, the quality of the exit from that interface becomes the thing that determines customer experience. Which means the escalation rules are the design, not an afterthought. Define the triggers explicitly: the customer asks for a person, confidence is low, the same step fails twice, or the intent carries risk such as a billing dispute, a legal request, or anything medical. When escalation fires, the agent should receive what the customer already tried, what the bot already told them, and what data was already captured. Most failures blamed on the bot are failures of what did not survive the handoff How this seam flatters itself: containment. A contact that resolves nothing but produces a callback tomorrow is not contained, it is postponed, and postponement and resolution look identical on a containment dashboard. Read containment only ever alongside repeat contact rate inside 72 hours. What to sample: fifty escalated contacts, checking whether the agent could see the bot transcript without asking the customer to start again. Seam two: the routing decision Routing is not only which agent answers. It is a sequence of decisions about channel, queue, priority, skill match and what happens next. Automation earns its place in intent detection, where even coarse classification stops “I want to change my delivery address” landing in general support; in skill matching; in priority rules for regulated complaints, account security and time-critical delivery problems; and in load balancing, so a queue spike does not need a supervisor watching it. How this seam flatters itself: routing accuracy. Aggressive skill-based routing raises first contact resolution on the contacts it classifies correctly while generating transfers on everything it does not, and the two effects can cancel out while both dashboards look busy. Pair routing accuracy with transfer rate and read them as one number. What to sample: every transferred contact for one week, sorted by the intent the classifier assigned. The misroutes cluster, and the clusters are fixable. Seam three: the agent’s desktop Most leaders talk about deflection. Several of the largest wins come from supporting the person instead: customer context, recent history, the relevant policy line, the next best action, a draft reply. Less searching, fewer mistakes, more consistency between agents. One rule outranks the feature list. Assistance has to appear inside the application the agent already has open. A second window is a tax, and agents will route around a tax. How this seam flatters itself: average handle time (AHT). Time falls