AI IS OK • FREE WEEKLY NEWSLETTER

Your AI Trial Worked. What Gets Permission to Grow?

Steve Agi · 11 November 2026

It worked. Now what? Grow the workflow. Keep the boundaries.

Last week we looked at turning a promising AI test into a useful team habit: one colleague, a clear handoff and a booked second use.

Suppose that second use goes well. Someone else can follow the instructions. The output is useful. The checking is manageable.

Now comes the tempting bit: “Great. Can we connect it to everything?”

Perhaps eventually. First, decide what has actually earned permission to grow. More work through the same process and more authority for the software are two separate decisions.

1. Say exactly what is expanding

“Scale the pilot” sounds decisive. It can also hide several different changes.

Are you adding another colleague? More examples of the same task? A different department? A new source of information? Permission to send something to a customer?

Write the change as a sentence. If it contains three new jobs, two new systems and a promise that nobody will need to check anything, you have moved beyond the original test.

Choose one extension you can observe. Keep everything else within the existing boundary.

2. Carry the checks with the work

Here is a fictional example. A team uses AI to turn approved meeting notes into a draft action list. A person checks what was agreed, confirms the owner and date, and puts approved actions in the team’s register.

The first extension might be another authorised colleague using the same process for the same type of meeting. Keep the source requirements, reviewer and exception path.

Automatically assigning tasks from every recording is a different proposition. So is emailing clients about deadlines that AI inferred rather than someone agreed.

The first test demonstrated drafting under supervision. It did not demonstrate authority to make commitments.

When a workflow moves to a second person, move the checking instructions too. Otherwise, what spreads is the shortcut and what disappears is the judgement that made it useful.

3. Find the exception before adding volume

A process that handles straightforward cases can still fall apart when an ordinary exception arrives.

For our meeting example, what happens when two people disagree about the decision? When no owner was named? When the notes contain a suggestion rather than a commitment?

Keep those items visibly unresolved. Send them to the person authorised to clarify them. Do not let an empty field become an invitation to invent an answer.

Before expanding, ask the next colleague to walk through one difficult example. Can they recognise the problem, stop the task and find the right person without hunting through your chat history?

If every exception still returns to you, the process has not become independent. You have acquired a busier help desk.

4. Check the economics of the next step

Last fortnight we counted the whole task, including corrections and handoffs. Keep doing that as the work grows.

Include the extra reviewer time, software costs and time spent maintaining instructions. Ask the person receiving the output whether their job became easier.

A faster draft is useful only if the business can use it. Ten additional drafts waiting for the same overloaded approver may simply give the queue a new source.

Keep the comparison honest. State what you observed, how many comparable cases you reviewed and what remains unknown. A small promising sample can justify another bounded test. It cannot tell you what happens at every volume or in every department.

You may decide the next investment is a clearer approval process. That is a perfectly good result, even if it produces a less exciting screenshot.

5. Make the expansion reversible

Name the person approving the extension, its review date and the condition that stops it. Keep a usable way to do the task if the tool is unavailable or the output is unreliable.

If the proposal changes data access, recipients, spending or customer commitments, review that change explicitly before proceeding. “It worked last week” is not an approval for a different job.

Keep the old instructions until the new version has been checked. Record what changed so a colleague can explain why today’s process differs from yesterday’s.

You do not need a committee for every small improvement. You do need someone who can say what is allowed, who decides and how to undo the change.

Your next action: write an expansion brief

Take the habit you tested last week and make six short notes:

  • The evidence: what worked, for which cases, including the checking.
  • The one extension: exactly what will change next.
  • The boundary: what the tool still cannot do.
  • The people: owner, reviewer and person handling exceptions.
  • The stop condition: what sends the work back to the existing process.
  • The review: when you will decide whether to keep, refine or stop the extension.

If you cannot finish one line, resolve that question before adding another system connection.

The aim is a useful process that another person can run and explain. Expansion should make the business more capable without making its responsibilities harder to find.

What would you expand first: the number of people using the process, the amount of comparable work, or the authority you are willing to give it?

Put the next decision in a working brief

The AI is OK Working Playbook is A$10/month self-service access to the original 21-page Systems That Work PDF, an editable workbook and the interactive Find the Problem exercise. Define one problem, build a small test and review the result at your own pace.

Download your project file and reopen it to continue. Progress stays in your file, not in your member account. Selected resources are added when useful and ready. Consulting and individual implementation are separately scoped. Recurring monthly access; cancel any time.

Explore the A$10/month Working Playbook

The weekly newsletter stays free. Subscribe by email or read past issues, with no LinkedIn account required.

Start small. Keep people accountable. Check what actually changed.

Until next time, stay curious, stay scrappy, and remember: AI is OK.

Steve AGI / C51

Previous editions and references

Share this post

Subscribe to our newsletter

Keep up with the latest blog posts by staying updated. No spamming: we promise.
By clicking Sign Up you’re confirming that you agree with our Terms and Conditions.

Related posts