---
title: "CEOs and boards are now fighting over AI implementation speed. Here's how to pick a pace that doesn't fail."
description: "Business Insider reported on 4 May 2026 that CEOs and boards across the United Kingdom and the United States are openly disagreeing on how fast to push AI inside their companies. Some boards want urgency, some CEOs want caution, and the disagreement is forcing pace decisions that often go wrong in both directions. This piece walks through three honest pace options for SMBs (slow-and-stable, fast-and-fix, parallel-track), shows which org each one fits, lists the three signs you've picked the wrong one, and gives a short decision matrix you can run in a board meeting before the temperature in the room rises any further."
canonical: https://richardbatt.com/blog/ceo-board-ai-speed-disagreement-pace
date: 2026-05-05
author: Richard Batt
tags: [AI Strategy, Implementation, Leadership]
type: blog_post
---

# CEOs and boards are now fighting over AI implementation speed. Here's how to pick a pace that doesn't fail.

_Business Insider reported on 4 May 2026 that CEOs and boards across the United Kingdom and the United States are openly disagreeing on how fast to push AI inside their companies. Some boards want urgency, some CEOs want caution, and the disagreement is forcing pace decisions that often go wrong in both directions. This piece walks through three honest pace options for SMBs (slow-and-stable, fast-and-fix, parallel-track), shows which org each one fits, lists the three signs you've picked the wrong one, and gives a short decision matrix you can run in a board meeting before the temperature in the room rises any further._

**Richard Batt** — AI implementation specialist. 120+ projects across 15+ industries, serving SMBs (5-200 employees) worldwide from Middlesbrough, UK (working globally). Contact: richard@richardbatt.com · https://richardbatt.com

Business Insider reported on 4 May 2026 that CEOs and boards across the United Kingdom and United States are now openly disagreeing on how fast to push AI inside their companies. Some boards are demanding urgency. Some CEOs are pushing back with caution. The arguments are landing in board minutes that, three years from now, will be read as either prescient or quaint, and you don't know which yet. But you can pick a pace that survives both readings.

I've sat in 14 of these conversations over the past nine months, mostly with UK SMBs in the 30 to 200 staff range. The pattern is recognisable inside two minutes of the meeting opening. Speed without redesign produces burnout and rework, while caution without action produces quiet decline. The right answer is one of three pace options, and the disagreement most boards are having is because nobody has named which one they're trying to pick.

## The three honest pace options

There are three shapes of AI rollout I've watched work for UK SMBs in 2025 and 2026. Each one fits a different org. The mistake is treating them as a hierarchy from worst to best, when they're really a fit question.

### Slow-and-stable: 18 months, two pilots a quarter

The slow-and-stable pace runs about two pilots a quarter, with each one running 8 to 12 weeks before a decision to keep, kill, or scale. Year one delivers two productionised workflows, modest cost savings, and a learning organisation that knows how to run AI projects. Year two compounds that.

This pace fits UK SMBs that are mid-cycle on a different transformation (an ERP migration, a major hire, a market expansion). It fits firms whose client base values reliability over novelty (legal practices, accounting firms, or anything in healthcare). And it fits owners who are themselves cautious about AI and need to see two or three wins before they commit to wider investment.

The risk of slow-and-stable is that it loses to faster competitors in markets where the pace is already accelerating. So check first whether your competitive context allows for it. If two of your top five competitors are rolling out AI faster, slow-and-stable is the wrong pick.

### Fast-and-fix: 6 months, four to six pilots in parallel

The fast-and-fix pace runs four to six AI pilots in parallel, with a deliberate tolerance for some of them failing. The objective is to get to four or five productionised workflows inside six months, then spend the next six months consolidating. Year one delivers more change but also more breakage.

This pace fits UK SMBs in markets where competitors are already moving on AI (marketing agencies, ecommerce operators, consumer-facing services). It fits firms with strong operational management who can absorb a 40% pilot failure rate without it destabilising the team. And it fits owners with deep pockets who can afford to spend £40k to £80k on what becomes wasted effort, in exchange for the two or three workflows that produce real margin.

The risk of fast-and-fix is the burnout it can cause if the operational manager isn't strong. I've seen one 80-person services firm in Birmingham try this pace with a thin management layer and produce four months of operational chaos before reverting to slow-and-stable. The pace itself wasn't wrong. The fit was.

### Parallel-track: dedicated team, ring-fenced budget, 12-month horizon

The parallel-track pace creates a small dedicated AI team (one full-time hire plus 30% of two existing senior staff) with a ring-fenced budget. The rest of the firm runs as normal. The dedicated team produces three to five productionised workflows a year and hands them to operational owners.

This pace fits UK SMBs over 100 staff with a stable core business that can't afford operational disruption. It fits firms with the headcount to absorb one full-time AI hire without it being a strategic gamble. And it fits boards that want a visible AI commitment without forcing it through every department at once.

The risk of parallel-track is that the dedicated team becomes an island. The work doesn't transfer to operational owners and the productionised workflows go unused. The fix is the handover discipline. Every workflow shipped by the team has an operational owner named on day one, and the team's success metric is operational adoption, not pilot delivery.

## How to pick (a 4-question decision matrix)

Run this in your next board conversation. It takes 20 minutes and changes the temperature of the room.

**Question 1. What's our competitive context?** If two of your top five competitors are visibly running AI faster than you, the answer skews to fast-and-fix or parallel-track. If none of them are, slow-and-stable is fine. Most UK SMBs over-estimate how fast their competitors are moving. So ask for evidence, not opinion.

**Question 2. How strong is our operational management?** If your senior operational managers are stretched thin, fast-and-fix will break them. Slow-and-stable or parallel-track is the right answer. The single best predictor I've seen of AI rollout success isn't budget, tools, or strategy. It's whether the manager who owns the workflow wants the change.

**Question 3. What's our risk tolerance for visible failure?** If a 40% pilot failure rate would destabilise the firm (because the team is small, the brand is conservative, or the cash position is tight), don't pick fast-and-fix. The pace assumes failures are absorbed, not escalated. Slow-and-stable spreads the failure surface across longer pilots and fewer of them.

**Question 4. How committed is the CEO personally?** If the CEO is sceptical or distracted, parallel-track is the only pace that works. The dedicated team gives the CEO an arms-length structure to support without owning. Forcing a sceptical CEO to drive fast-and-fix produces bad theatre and worse outcomes.

The decision falls out of the four answers, not out of one. So if your board is fighting over speed without first running these four questions, the disagreement isn't about pace. It's about uncertainty masquerading as strategy.

## The three signs you've picked the wrong pace

I've watched a handful of UK SMBs realise mid-year that their pace is wrong. The signs are recognisable.

**Sign one: pilot fatigue.** Three months in, the team is talking about AI in a tired voice. Pilots are blurring into each other. Nobody can name what shipped last quarter. That's fast-and-fix without enough management strength. The fix is to consolidate to two pilots and finish them properly before opening any more.

**Sign two: visible competitor moves you didn't see coming.** A competitor publicly launches an AI service or compresses a delivery window in a way that gets named in your sales calls. That signals slow-and-stable in a market that's accelerating. The fix is to add one or two faster pilots without abandoning the slower ones.

**Sign three: the dedicated team has shipped, and nothing is being used.** The parallel-track team is producing workflows but operational owners aren't adopting them. This is parallel-track without handover discipline. The fix is to slow the team's pilot intake and force the next two workflows to have operational sign-off before development starts.

In all three cases, the response is to recalibrate, not to switch pace entirely. So if your firm is on slow-and-stable and the signs say it's wrong, you don't need to leap to fast-and-fix. You need to add one parallel pilot. If you're on fast-and-fix and you're seeing burnout, you don't go to slow-and-stable. You go to fast-and-fix-with-fewer-pilots, which is the same shape with less load.

## What I'd do tomorrow if my board was fighting over AI pace

Three actions, in priority order.

First, run the four-question matrix above before the next board conversation. Get written answers from the CEO, the chair, and the senior ops manager. The disagreement usually disappears once those three perspectives are visible side by side, because the answers are usually closer than the conversation makes them feel.

Second, name the pace explicitly in the next set of board minutes. "We are running slow-and-stable for the next six months, two pilots per quarter, with a check at month nine on whether to add a parallel-track team." That sentence does more for board alignment than three more meetings.

Third, set the recalibration check now, not later. Slow-and-stable boards tend to skip the check because everything feels fine until it isn't. Fast-and-fix boards skip the check because they're too busy. So both fail at the same point, which is month four, when the original pace decision needs adjustment and nobody's set the agenda for that adjustment.

## FAQ

**My board says we're behind on AI. How do I tell if they're right?**

Ask three questions. First, are two of your top five competitors visibly running AI faster than you? Second, are you losing pitches or RFPs because the buyer expects an AI-augmented offer? Third, are your own staff using AI tools at home that you're not deploying at work? If two of those answers are yes, the board is right. If only one is yes, you have time. If none are, the board is reading the news, not the market.

**Can a small UK SMB really run a parallel-track AI team?**

Below 100 staff, probably not, unless the dedicated person is part-time. The economics don't work. The right shape for a 30 to 80 person firm is slow-and-stable with one motivated senior who has 20% of their week ring-fenced for AI projects. That's a lighter version of parallel-track that fits the headcount.

**How do I tell my CEO they're moving too slow without it becoming a fight?**

Don't tell them. Ask them. Ask the four questions in the matrix above and listen to the answers. The CEO who answers honestly will usually adjust their own pace once they see the gap between their answers and the competitive context. The CEO who can't answer the four questions is the harder problem, and that's a different conversation.

## Where to take this next

If you want a structured way to answer the four-question matrix and pick the pace your board can actually agree on, the AI Roadmap audit is the fastest path. We map your competitive context, your operational management strength, and your CEO commitment, and tell you which of the three paces fits your firm right now. https://richardbatt.co.uk/roadmap

Most board fights about AI speed aren't about speed. They're about uncertainty in disguise. So name the pace, set the check date, and the temperature in the room drops by ten degrees inside one meeting.

---

## More about Richard Batt

Richard Batt is an AI implementation specialist who helps businesses deploy working AI automation in days, not months. 120+ projects across 15+ industries.

### Key pages

- [Home](https://richardbatt.com/)
- [About Richard](https://richardbatt.com/about)
- [Blog](https://richardbatt.com/blog)
- [Contact](https://richardbatt.com/contact)
- [Subscribe](https://richardbatt.com/subscribe)

### Contact

- Email: richard@richardbatt.com
- Location: Middlesbrough, UK (working globally)
- Website: https://richardbatt.com