The "do more with the team you have" week

By Jason Sibley

The problem

Every small team has the same quiet frustration: there's more work than hours, adding people isn't an option right now, and "just be more efficient" is advice with no actual steps attached. Meanwhile, AI adoption is visibly happening around you — Office for National Statistics data shows self-reported AI use among UK businesses with 10 or more employees has grown from around 12% to around 35% since late 2023 — but "use AI" as an instruction is about as useful as "be more efficient." Neither tells your team what to actually do on Monday morning.

This piece is a structure for one specific week: a way to find the handful of tasks where AI genuinely helps your existing team do more, without pretending it's a company-wide overhaul.

What people get wrong

They announce "we're adopting AI" without naming a single task. Enterprise Nation's Tech Hub research found that only 6% of small businesses have AI embedded into daily work, even though a much larger share have tried it at some point. The gap between trying and embedding is almost always this: nobody named the specific, recurring task the tool was meant to solve.

They pick the task based on excitement, not frequency. The most satisfying AI use case to demo is rarely the most valuable one to embed. A task done once a month that AI makes flashy is worth far less than a boring task done five times a week that AI makes ten minutes shorter.

They run the experiment with no one accountable for checking it worked. Without someone specifically responsible for saying "yes, this saved time" or "no, this created more work than it solved," a trial AI habit quietly fades rather than getting a clear verdict.

They let the whole team try different tools for different things simultaneously. This produces a scattered set of one-person habits rather than a shared team capability. A single week focused on one shared task, with everyone using the same approach, produces something that survives past week one.

They run the week when things are already too busy to pay it attention. Trying to introduce a new shared habit during the business's busiest week guarantees it gets deprioritised the moment something urgent comes up. A quieter week, deliberately chosen, gives the habit an actual chance to take hold before it gets tested by real pressure.

Why a whole-team structure, not an individual one

Most AI adoption advice is written for individuals — one person, one tool, one workflow. That's genuinely useful, but it misses something specific to small teams: a habit that only one person uses doesn't compound the same way a shared one does. If only the owner uses AI to draft follow-up emails, the business gets one person's worth of time back. If the whole team adopts the same approach to the same task, the business gets everyone's worth of time back, and just as importantly the habit survives if that one person is away, busy, or moves on. A shared structure, even a simple one, builds a capability that belongs to the business rather than to an individual.

This is also why the five-day structure below deliberately puts "list, don't solve" first, rather than starting with a tool. Teams that start by picking a tool tend to reverse-engineer a use case to justify it. Teams that start by naming the actual repeated task, and only then look for the smallest tool that helps with it, end up with something that fits the real problem rather than a solution looking for one.

A practical frame: the five-day structure

Day one — list, don't solve. Every team member writes down the three most repetitive tasks they did last week: not the most important, the most repeated. Don't touch AI yet. This step alone often surfaces the target task, because patterns become obvious once several lists sit next to each other.

Day two — pick one task, for the whole team, not per person. Choose the task that appears most often across everyone's list, or the one causing the most visible bottleneck. Improving business operations is the most reported AI use among UK businesses of every size (close to 60% of adopters use it for exactly this kind of purpose), so a repetitive operational task is very likely to be a good candidate.

Day three — build the smallest possible version. Whatever tool fits (a general assistant, or something built into a platform you already use), set up the simplest version of AI helping with that one task. Resist adding scope; the goal this week is one task done consistently, not several tasks done ambitiously.

Day four — everyone uses it, and someone writes down what happened. Have the whole team actually use the new habit on real work, and keep a simple running note of what worked and what didn't. Enterprise Nation's research (based on OpenAI-commissioned data) found UK SMEs using AI save an average of 5.2 hours a week — real, but only realised if people actually adopt the habit rather than trying it once.

Day five — decide, out loud, as a team. Does this task keep its AI-assisted habit permanently, or does it get dropped? Say the decision explicitly rather than letting it fade unaddressed — this is the single biggest difference between the 21% of small businesses using AI regularly and the majority who've tried it once and moved on, per Enterprise Nation's Tech Hub findings.

What this week deliberately doesn't attempt

It doesn't try to transform how the whole business works. It doesn't try more than one task. It doesn't require a big software purchase — most of what's described here can be done with tools your team may already have access to. The ambition is narrow on purpose: one shared task, one shared habit, one clear decision at the end, repeatable next month with a second task once the first genuinely sticks.

There's a reason for keeping the ambition this narrow, beyond just manageability. Enterprise Nation's Tech Hub research found that real AI use among UK small businesses "remains at an early stage" even where broader digital adoption is more advanced — the gap isn't awareness, it's embedding. A five-day structure that produces one genuinely embedded habit does more for a small team's actual capability than a much more ambitious plan that produces several habits nobody keeps up past the first fortnight.

Running it again next month

Once the first task has survived a proper month of real use, the same five-day structure works again for a second task — and by the second or third round, most teams find the days get faster, because everyone already understands the process and the kind of task worth choosing. This is a genuinely different pattern from a single big "AI overhaul" push: it's slower to start, but it produces habits that actually stick, one at a time, each one tested properly before the next one begins.

The one decision to make this week

Don't decide "how do we transform the business with AI." Decide: what is the one task, done by more than one person, that we will run this five-day structure against — and who is responsible for the day-five verdict?

Naming that person matters as much as naming the task. Without someone explicitly owning the decision, the habit drifts, whichever way it was heading.

A soft word before you go

If you'd like help running this structure properly the first time, My AI Apprentice's SMB AI sessions are built for exactly this — a facilitated version of the same five days. Entirely optional; the structure above is designed to be run without us.