{"version":"1.0","type":"agent_native_article","locale":"en","slug":"fastest-ai-not-the-smartest-mqo5kjee","title":"The Fastest AI Is Not the Smartest","primary_category":"ai","author":{"name":"Isabel Ríos","slug":"isabel-rios"},"published_at":"2026-06-21T18:03:21.268Z","total_votes":74,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/fastest-ai-not-the-smartest-mqo5kjee","agent":"https://sustainabl.net/agent-native/en/articulo/fastest-ai-not-the-smartest-mqo5kjee"},"summary":{"one_line":"EY's concept of the 'tempo gap' reveals that enterprise AI failures often stem not from technical errors but from systems moving faster than users can comprehend, creating hidden operational costs and regulatory risk.","core_question":"When AI systems outpace human comprehension, who bears the cost—and how should organizations redesign for trust rather than just speed?","main_thesis":"The dominant enterprise AI metric of speed is producing a structural design failure: systems optimized for efficiency without calibration for human comprehension generate trust deficits, silent manual review reintroduction, and regulatory vulnerability. The next competitive advantage belongs to organizations that align machine tempo with human tempo."},"content_markdown":"## The Fastest AI Is Not the Smartest\n\nThere is a pattern that repeats itself in enterprise artificial intelligence projects and that rarely appears in monitoring dashboards: users begin to double-check what they previously accepted without hesitation. Not because the system failed. But because the system moved forward before they could keep up with it.\n\nEY gave a name to that pattern in an article published in Fortune at the end of June 2026. They called it **\"tempo gap\"**: the point at which the speed of the machine exceeds the human capacity for comprehension. Patricia Camden, customer experience leader at EY Studio+, and John Dubois, AI strategy leader for the Americas, documented this phenomenon based on their work with enterprise clients across different industries. Their diagnosis is direct: most organizations believe their biggest problem with AI is adoption. It is not. It is the pace.\n\nWhat makes this argument interesting is not that it is new in technical terms. It is that two executives from one of the largest consulting firms in the world are saying it, in a high-impact business publication, using a language that no longer sounds like a euphemism: the problem is not in the algorithm, it is in the design of the human experience surrounding that algorithm. And that has implications that go well beyond user experience.\n\n## When the System Works Well and Something Still Goes Wrong\n\nThe three cases that Camden and Dubois cite to illustrate the tempo gap are precise in what they reveal. A traveler with a cancelled flight is automatically rerouted to another flight before they can compare options. A customer completes a financial application so quickly that they accept material conditions without having processed them. A patient filling out a medical form sees their sensitive data pre-filled before understanding how it will be used.\n\nIn all three cases, the system functioned exactly as it was designed to. There were no technical errors. There were no security failures. And yet, the experience produced hesitation, distrust, and in some environments, the silent reintroduction of manual review into processes that had been automated precisely to eliminate it.\n\nThat last point deserves attention. When teams begin to verify outputs they previously accepted, they are not being irrational. They are responding to a design signal: the system moved faster than their capacity for understanding, and that generated a trust deficit that they now have to settle by hand. The cost does not appear in the process speed indicators. It appears in the invisible time that operators spend re-validating what the AI already did.\n\nEY calls this **\"manual review seeping back into the process\"**. From an organizational architecture perspective, it is something more specific: it is the symptom of a system that was optimized for efficiency without being calibrated for trust. And that distinction is not semantic. It has direct consequences on operational costs and on the real capacity to scale.\n\nThe argument underlying EY's diagnosis is that most organizations still treat AI adoption as an efficiency initiative. The corporate conversation remains focused on automation, friction reduction, and speed. What is left out of that conversation is that accelerating workflows also changes the cognitive demands placed on the people who navigate them. And when those demands are not well designed, the promised efficiency becomes an operational illusion: the process is formally faster, but people are running behind it without understanding what they are approving.\n\n## The Blind Spot That No One Named in the Design Room\n\nThis is where EY's analysis touches on something that goes beyond user experience and enters the territory of power architecture. The tempo gap is not just an interface design problem. It is, first and foremost, a problem of who was present when the design decisions were made.\n\nThe three examples EY documents — the rerouted traveler, the financial customer who accepts without reading, the patient with pre-filled data — share a common structure: a system that was designed from the perspective of whoever operates it, not from the perspective of whoever experiences it. The efficiency of automatic rerouting is perfectly logical from the airline's or agency's side. The speed of the financial application is an achievement from the bank's point of view. The pre-filling of medical data looks like a usability improvement from the technical team's standpoint.\n\nWhat was missing in those design rooms was not malicious intent. It was **peripheral intelligence**: the perspective of the person at the receiving end of the system, whose experience is not the optimization of the process, but the preservation of their own capacity for agency.\n\nThis is a structural pattern in how enterprise AI systems are built. Design and product teams tend to be composed of people who share a set of assumptions about how decision-making works, what constitutes a good experience, and how much time it reasonably takes someone to process information. When those teams are homogeneous in their relationship with technology, in their tolerance for speed, in their prior access to complex financial or medical information, they produce systems calibrated for people like themselves.\n\nThe tempo gap is, among other things, the cost of that homogeneity. Not in moral terms, but in terms of design quality. A system that systematically generates hesitation in its users is a system that was designed without incorporating the perspectives of those who most need comprehension before acting. And that is a problem of collective intelligence architecture, not declarative ethics.\n\nEY does not frame its analysis in these terms. Its entry point is more operational: organizations must align the tempo of the machine with the human tempo. That is a sensible prescription. But the prior question is more uncomfortable and more relevant to the companies that are designing these systems right now: from what design room did the assumption emerge that faster is always better, and who was in that room?\n\n## Friction as a Design Signal, Not an Obstacle\n\nFor more than a decade, the dominant philosophy in digital design was the elimination of friction. Fewer clicks, fewer steps, less time between intention and action. That philosophy produced measurable results: higher conversion rates, greater retention, faster processes. It also produced, silently, systems where speed began to serve those who operate the system more than those who use it.\n\nEY proposes a precise conceptual shift: **intentional friction** as a design tool. Not arbitrary delays, but deliberate pauses at the moments where a user needs comprehension before acting. A confirmation before executing a financial decision. A brief explanation of how sensitive data will be used. A second of visibility into why the system did what it did.\n\nWhat is remarkable about this argument is that it is not asking for systems to be slower in absolute terms. It is asking for them to be selectively slower at the moments of greatest consequence for the user. That requires the system to know how to distinguish between a moment of low and high cognitive load, between a routine action and a decision with material implications. That capacity for distinction does not emerge from the algorithm. It emerges from design, and design emerges from those who understand what makes a decision material for someone who does not share the same context as the team that built the system.\n\nIn sectors such as financial services, healthcare, or insurance, this argument carries a regulatory dimension that EY mentions in passing but which deserves more weight. Consumer protection regulations, informed consent requirements, and fair disclosure rules are all built on the assumption that people understand what they are agreeing to. An AI system that moves users faster than their capacity for comprehension does not merely produce a poor experience. It produces a legal and regulatory vulnerability that organizations are silently accumulating in every workflow they optimized for speed without considering comprehension.\n\nEY warns that if organizations do not name this problem themselves, a regulator or a customer will. That is a reasonable prediction given the pace at which AI regulatory frameworks are advancing in Europe and, with a lag, in other regions. The question is not whether there will be external scrutiny over how AI systems handle user agency and comprehension. The question is how much accumulated damage there will be before that scrutiny arrives.\n\n## The Next Phase of Adoption Is Not Won With Speed\n\nEY's argument has a strategic core worth extracting with precision: **the next phase of competitive advantage in AI will not belong to whoever automates fastest, but to whoever best calibrates the pace at which their systems relate to the people who use them**.\n\nThis is not a concession to slowness. It is a diagnosis about where technical and organizational debt is accumulating in enterprise AI projects. Organizations that have high override rates, unplanned manual review, and systematic user hesitation are not failing at adoption. They are failing at design. And that failure has a direct cost on the return from AI programs, which promised to eliminate manual work and are, in some cases, generating it again through the back door.\n\nThe solution EY proposes — aligning the tempo of the machine with the human tempo — requires a capability that cannot be built with better algorithms alone. It requires organizations to incorporate, into their AI system design teams, perspectives from people who represent the full range of user experiences: those with less technological familiarity, those who face greater information asymmetry in financial or medical contexts, those who have more at stake in each interaction.\n\nThat is not design philanthropy. It is the structural condition for an AI system to be intelligent enough to know when it should slow down. And a system that does not know when to slow down is not an intelligent system. It is a fast system. The difference between the two is precisely the gap that EY has just given a name to — and that most organizations still do not have on their metrics dashboard.","article_map":{"title":"The Fastest AI Is Not the Smartest","entities":[{"name":"EY","type":"company","role_in_article":"Source of the 'tempo gap' concept; primary research and diagnostic framework cited throughout the article"},{"name":"Patricia Camden","type":"person","role_in_article":"EY Studio+ customer experience leader; co-author of the original Fortune article documenting the tempo gap"},{"name":"John Dubois","type":"person","role_in_article":"EY AI strategy leader for the Americas; co-author of the tempo gap analysis"},{"name":"Fortune","type":"institution","role_in_article":"Publication where EY's original tempo gap article appeared in June 2026"},{"name":"Isabel Ríos","type":"person","role_in_article":"Author of this Sustainabl article analyzing and extending EY's argument"},{"name":"Enterprise AI","type":"technology","role_in_article":"Central subject—the class of AI systems whose design and deployment pace is under scrutiny"},{"name":"Financial services","type":"market","role_in_article":"Cited as a sector with high regulatory exposure to tempo gap failures"},{"name":"Healthcare","type":"market","role_in_article":"Cited as a sector with informed consent and data pre-filling risks from tempo gap"},{"name":"Insurance","type":"market","role_in_article":"Cited alongside financial services and healthcare as high-consequence sector for tempo gap regulatory risk"},{"name":"Europe","type":"country","role_in_article":"Referenced as leading AI regulatory framework development, increasing external scrutiny pressure"}],"tradeoffs":["Speed of automation vs. user comprehension and trust—faster processes can generate slower net throughput when manual review re-enters","Homogeneous design team efficiency vs. design quality—teams that share assumptions move faster but produce systems calibrated for a narrow user range","Friction elimination vs. informed consent—removing all friction increases conversion but accumulates legal and regulatory liability","Short-term efficiency metrics vs. long-term AI program ROI—speed KPIs hide the cost of trust deficits and re-validation labor","Algorithmic optimization vs. human-centered design—better algorithms alone cannot solve a problem rooted in design room composition"],"key_claims":[{"claim":"EY named the 'tempo gap' as the point at which machine speed exceeds human comprehension capacity, based on work with enterprise clients across industries.","confidence":"high","support_type":"reported_fact"},{"claim":"Manual review is silently re-entering automated processes when users lose trust in AI outputs they cannot process fast enough.","confidence":"high","support_type":"reported_fact"},{"claim":"Most organizations treat AI adoption as an efficiency initiative, leaving cognitive demand design out of the conversation.","confidence":"high","support_type":"editorial_judgment"},{"claim":"The tempo gap is partly a consequence of homogeneous design teams who build for users like themselves.","confidence":"medium","support_type":"inference"},{"claim":"Organizations optimizing AI workflows for speed without comprehension design are accumulating regulatory and legal vulnerability.","confidence":"medium","support_type":"inference"},{"claim":"The next phase of AI competitive advantage will belong to organizations that calibrate machine tempo to human tempo, not those that automate fastest.","confidence":"interpretive","support_type":"editorial_judgment"},{"claim":"A system that does not know when to slow down is not intelligent—it is merely fast.","confidence":"interpretive","support_type":"editorial_judgment"}],"main_thesis":"The dominant enterprise AI metric of speed is producing a structural design failure: systems optimized for efficiency without calibration for human comprehension generate trust deficits, silent manual review reintroduction, and regulatory vulnerability. The next competitive advantage belongs to organizations that align machine tempo with human tempo.","core_question":"When AI systems outpace human comprehension, who bears the cost—and how should organizations redesign for trust rather than just speed?","core_tensions":["Machine efficiency vs. human agency: systems designed to maximize throughput can systematically undermine the user's capacity to make informed decisions","Design team homogeneity vs. design quality: the people best positioned to build fast AI systems are often least positioned to understand where it fails users","Speed as competitive advantage vs. speed as liability: the same optimization that wins market position can accumulate regulatory and trust debt","Adoption metrics vs. design metrics: organizations measure what is easy (speed, automation rate) and miss what is costly (override rates, comprehension failures)","Algorithmic intelligence vs. contextual intelligence: a system can be technically correct and experientially wrong simultaneously"],"open_questions":["How should organizations measure the tempo gap operationally—what metrics proxy for comprehension failure and trust deficit?","What design methodologies reliably incorporate the perspectives of users with high information asymmetry into AI system development?","At what point does a tempo gap in financial or medical AI workflows constitute a regulatory violation under existing informed consent frameworks?","How do organizations distinguish between friction that serves user comprehension and friction that merely slows processes without benefit?","Will AI regulatory frameworks in Europe and elsewhere explicitly address machine-to-human tempo calibration, or will enforcement remain reactive?","Can algorithmic systems be trained to detect high-cognitive-load moments and self-regulate pace, or is this inherently a design-layer problem?"],"training_value":{"recommended_for":["Chief AI Officers and AI program leads evaluating enterprise AI deployment quality","Product and design teams building AI-assisted workflows in regulated industries","Strategy consultants advising on AI transformation programs","Risk and compliance officers assessing AI regulatory exposure","Investors evaluating the operational maturity of enterprise AI programs beyond speed and automation metrics"],"when_this_article_is_useful":["When evaluating why an AI automation program is not delivering expected ROI despite high technical performance","When designing AI workflows in financial services, healthcare, or insurance where informed consent is legally required","When building the business case for investing in user research and diverse design team composition for AI projects","When assessing regulatory exposure in AI-assisted customer-facing processes","When reframing an AI adoption problem that has been misdiagnosed as a change management or training issue"],"what_a_business_agent_can_learn":["How to identify the tempo gap as a hidden cost driver in AI programs—look for override rates, unplanned manual review, and user hesitation as proxy metrics","That AI program ROI can be undermined by design failures invisible to speed-based dashboards","How to frame AI design quality as a collective intelligence architecture problem, not a declarative ethics problem","That intentional friction is a legitimate design tool at high-consequence decision points, not a failure of optimization","How regulatory risk accumulates silently in AI workflows that prioritize speed over comprehension in regulated sectors","That design team composition is a structural determinant of AI system quality for diverse user populations"]},"argument_outline":[{"label":"1. The Tempo Gap","point":"EY executives Patricia Camden and John Dubois identified a recurring pattern in enterprise AI: users begin double-checking outputs not because the system failed, but because it moved faster than their capacity to understand.","why_it_matters":"This reframes the AI adoption problem from a technical or change-management issue to a design and pacing issue—one that most dashboards do not measure."},{"label":"2. When Success Produces Failure","point":"Three documented cases (auto-rerouted traveler, fast financial application, pre-filled medical data) show systems functioning as designed yet generating hesitation, distrust, and manual review reintroduction.","why_it_matters":"The cost of the tempo gap is invisible in speed metrics but real in operator time spent re-validating AI outputs—a direct drag on ROI from automation programs."},{"label":"3. Design Room Blind Spot","point":"The tempo gap is a structural consequence of homogeneous design teams who calibrate systems for users like themselves, omitting the perspective of those with less technological familiarity or higher information asymmetry.","why_it_matters":"This is a collective intelligence architecture problem, not a declarative ethics problem—meaning it has measurable design quality consequences, not just moral ones."},{"label":"4. Intentional Friction as a Tool","point":"EY proposes selective, deliberate pauses at high-consequence moments rather than uniform slowdown—requiring systems to distinguish routine actions from decisions with material implications.","why_it_matters":"This redefines friction from an obstacle to a design signal, shifting the optimization target from conversion speed to comprehension-enabled consent."},{"label":"5. Regulatory and Legal Accumulation","point":"AI systems that move users faster than their comprehension capacity silently accumulate legal and regulatory vulnerability in sectors governed by informed consent, fair disclosure, and consumer protection rules.","why_it_matters":"Organizations that do not self-diagnose this problem will face external scrutiny from regulators or customers—with accumulated damage already baked in."},{"label":"6. Strategic Reframe","point":"Competitive advantage in the next phase of AI will belong to organizations that best calibrate machine-to-human tempo, not those that automate fastest.","why_it_matters":"High override rates, unplanned manual review, and user hesitation are design failures with direct cost implications—not adoption failures to be solved with more training."}],"one_line_summary":"EY's concept of the 'tempo gap' reveals that enterprise AI failures often stem not from technical errors but from systems moving faster than users can comprehend, creating hidden operational costs and regulatory risk.","related_articles":[{"reason":"Directly complementary: examines the contradiction between AI autonomy promises and the need for human oversight—the same tension between machine speed and human agency that the tempo gap describes","article_id":14001},{"reason":"Relevant context: Databricks' ontology bet for enterprise AI agents addresses the architecture layer of AI intelligence, relevant to understanding what 'smarter' AI infrastructure looks like beyond speed","article_id":14021},{"reason":"Relevant context: Accenture's market drop linked to questions about AI consulting model credibility—connects to the broader enterprise AI adoption and trust narrative","article_id":14041}],"business_patterns":["Enterprise AI programs promise to eliminate manual work but silently regenerate it through trust deficits—a hidden ROI leak","Design teams optimizing for their own cognitive profile produce systems that fail users with different information contexts","Regulatory vulnerability accumulates invisibly in AI workflows until external scrutiny forces costly remediation","Speed-first AI adoption creates a second wave of investment need: redesign for comprehension and trust calibration","The gap between formal process speed and actual operational throughput is a leading indicator of AI program design failure"],"business_decisions":["Whether to optimize AI workflows for speed or for comprehension-calibrated trust","Whether to include diverse user perspectives in AI design teams before deployment","Whether to introduce intentional friction at high-consequence decision points in AI-assisted workflows","Whether to measure override rates, manual review reintroduction, and user hesitation as AI program KPIs","Whether to conduct regulatory risk audits of AI workflows in financial services, healthcare, and insurance","Whether to reframe AI adoption programs as design quality initiatives rather than change management initiatives"]}}