How to bring AI into your department when you are not the boss

How to bring AI into your department when you are not the boss

Asking permission to introduce something new before a result has been shown is a losing move: you will be told "not now". Below is the order in which permission is not required: start with your own tasks, gather the figures and arrive with something finished rather than with a request.

Asking permission to introduce something new before a result has been shown is a losing move: you will be told "not now". Below is the order in which permission is not required: start with your own tasks, gather the figures and arrive with something finished rather than with a request.

---

"I'm junior and it's a public sector organisation"

A phrasing from my survey. Behind it is a typical situation: somebody is already using AI and getting results. A document analysis that took a day now takes ten minutes. A report gets assembled in an evening.

And then a dead end. They cannot bring it into the department because they decide nothing. Proposing it to management is frightening: either they will not understand, or they will forbid it, or they will decide this person is playing about instead of working. Carrying on quietly is also bad: there is a result and no way to explain where it came from.

A separate irritation: the larger and more formal the organisation, the slower any change moves through it — and the stronger the sense that trying is pointless.

Trying is not pointless. You simply have to come at it from a different side than people usually do.

Why "let's introduce AI" fails

The root cause: you are proposing a tool and the decision gets made about risk.

The manager you bring it to is not thinking "interesting or not". They are thinking about what happens if it breaks, who will answer for it, whether anything leaks and whether they will have to explain themselves upwards. Your ten minutes instead of a day does not enter that frame at all.

The misconception: "I need to explain more persuasively how good this is". The more vividly you explain, the stronger the sense of risk. A junior employee's enthusiasm reads to a manager as "they don't understand the consequences".

A second misconception: "I need permission from above to start". You do not. You need one finished result shown at the right moment. Permission gets granted for what already works, not for an idea.

And a systemic layer. In a large structure no single person can say yes to a big change — but almost anybody can say yes to a small one. So the size of the first step matters more than any argument.

The order that works

Step 1. Do it on yourself, quietly

No announcements. Choose one of your own tasks that takes a lot of your time and is visible to nobody: a reconciliation, preparing a summary, drafting a document, sorting incoming enquiries.

Do it the new way for two or three weeks. Quietly. The job at this stage is one: gather facts. How long it used to take, how long it takes now, how many errors turned up.

Compulsory: everything that goes out gets verified by you at source. A mistake at this stage will close the subject for years.

Step 2. Gather a figure, not an impression

After three weeks you should have a one-line proposition with no mention of AI in it:

> "Preparing the weekly summary used to take four hours, now it takes forty minutes. Over three weeks that is twelve hours freed up."

That is the language decisions get made in. "I've been trying out AI" is not that language.

Step 3. Arrive with a result rather than a request

The difference is fundamental.

Not this: "Can I try using AI for the reports?" — that is a request to permit a risk, and the default answer is no.

This: "Here is this week's summary, I assembled it differently and it took forty minutes instead of four hours. I verified it at source, here is the check. If it works for you, I can do it this way regularly."

In the second case the manager is assessing finished work already in front of them. There is no visible risk, because the result already exists.

Step 4. The first pilot: small and reversible

If permission comes, do not expand at once. Take one task, one person, one month and name the rollback condition without fail: "if anything goes wrong we go back to the old way and lose nothing".

Reversibility is the main argument for a cautious manager. A change that can be undone requires no courage to approve.

Step 5. Pass the result upwards

An unpleasant but necessary point. Frame the effect so your manager can own it — it is their department that got faster.

Adoptions fail not on the technology but on the author of the idea looking like a show-off. Somebody who brought a result and did not pull the credit gets a second yes far more easily than the first.

How to answer the three standard objections

They will almost certainly come up, so prepare the answers in advance.

"What if it makes a mistake?" Do not argue and do not say "it doesn't make mistakes". Answer with process: "Everything that goes out I verify at source — here is the check for this summary. An error gets caught at the same stage as before, it just reaches that stage faster."

"That's not permitted here." A clarifying question rather than an argument: "Where can I look at the policy — I want to check I'm working within it." Half of all prohibitions turn out not to be prohibitions but an absence of precedent. The other half are a real constraint, and it is better to know about it in advance.

"Have you got nothing better to do?" The most frequent and most stinging. Answer with a figure and nothing else: "The summary now takes forty minutes instead of four hours; the time freed up went into handling enquiries." Arguing with hours released is hard.

What must not be done

Do not send out anything that must not leave the building. Personal data, internal information, restricted documents. One such case cancels everything, and rightly. If unsure, assume you must not.

Do not deliver unverified work. Your reputation here is worth more than the hours saved.

Do not promise headcount reductions. Even if it is true. The first mention turns every colleague into an opponent and you into the person who came to sack them.

Do not start with the most important process. Start with something dull and your own.

Do not argue with "that's not how we do things". That is not an argument to be refuted — it is a state that changes with one demonstrated result.

What to do if the answer is no

That happens too, and not rarely. It is not the end.

Clarify what exactly the no is. A ban on the tool, a ban on this process, or a ban right now are three different things. Usually it is the third.

Carry on with your own tasks. A ban on changing a departmental process is not a ban on how you personally prepare your draft. That boundary is worth clarifying rather than assuming.

Keep gathering figures. In a quarter you will have four months of observations rather than three weeks, and the conversation will go differently. More often still, what changes is not your argument but the surroundings: a neighbouring department picks up a similar practice and the question resolves itself.

And the most practical part: this skill stays with you. Even if bringing it into the department does not work out, you have gained something worth money on the market — and that no longer depends on your job title.

Which tasks to take first

What works is where you supply the material — there is nothing to invent there, and verification takes minutes:

Do not take first: any task involving rules, reference numbers or figures that were not in the source material. Those can be done, but only with full verification at source, and it is not the case to start a pilot with.

Where to start

Ready specialists for most departments are already assembled: more than 140 AI assistants across 14 categories — legal, HR, marketing, sales, analytics, e-commerce, engineering, media. These are not prompts to be tuned: you open a chat on your subject, describe the task and get a document.

Plus automation templates for repeating processes — once the pilot has passed and the task has become regular.

Registration is free and opens three days of full Basic access — every assistant, the prompt texts, the skill files and six foundational express courses.

Today, one task. Take something you do by hand every week and time it before and after. In three weeks you will have a figure rather than an opinion. With a figure, the conversation with your manager looks entirely different.

You start not with permission but with a result there is nothing to dispute.

If you have a colleague doing the same thing quietly and afraid to say so, forward this to them.

---

Which task to start with so there is nothing to argue about

There is a class of tasks requiring nobody's permission and producing a measurable result immediately.

Module 5, "The automator", is twelve lessons on working with files, and the first is about analysing reports: any analytics, cost documentation, accounting exports, advertising reports.

Why that is the right first step. You are working with your own work files, involving nobody and introducing nothing. In two weeks you have a figure: it used to take this long, it now takes this long.

And the most reliable property of that class of task. You supply the material — so the model retrieves nothing from memory and has nothing to invent. An error is almost excluded, and that matters when you are showing a manager a result for the first time.

From there, by degrees: analysing website performance, turning books and documents into summaries, transcribing meetings. All of it your own tasks rather than the team's.

Module 5 comes with the Plus plan.

---

What to read next

[AI for business owners](/en/blog/ai-for-business-owner) — how this looks from the other side of the desk.

[A company knowledge base as a service](/en/blog/company-knowledge-base) — the next step once it works.

[Local AI models for sensitive data](/en/blog/local-models-sensitive-data) — if the company has data requirements.

[How to check what a model tells you](/en/blog/how-to-verify-ai-output) — without which an adoption falls apart at the first mistake.

[AI API pricing in 2026](/en/blog/llm-api-pricing) — what a request costs and how to work out your own costs.