Who should lead AI in a professional services firm?

What happens when nobody owns it?

In a firm of 20 to 200 people, AI usually arrives without an owner. Someone buys a few licences. A partner forwards an article round. Two associates start using a chat assistant for first drafts and tell nobody. A year later the managing partner asks what the firm has to show for it, and the honest answer is a subscription line in the accounts and a handful of private habits.

That is not a technology failure. It is an ownership failure. Nothing moved because nobody had both the remit to change how a job is done and the standing to make the change hold. The wider pattern is set out in why AI rollouts fail, but the usual root cause is this one: the work was everyone's interest and nobody's responsibility.

So the first decision is not which tool or which supplier. It is which name goes next to the work.

Should a partner lead it?

A partner has the authority, and authority is usually the missing ingredient. If a senior fee earner decides the new method is not for them, only a partner settles that quickly. A partner can also protect the time of whoever is doing the work, which matters more than any other form of support.

The difficulty is capacity. Partners have the least uninterrupted time in the firm, and owning a change is relentless, unglamorous follow-up: chasing a template, sitting in on a test, reminding a team that the old spreadsheet is retired. A partner who takes the title and then vanishes into their own matters is worse than no owner at all, because the vacancy now looks filled.

The workable version is partner sponsorship rather than partner leadership. A named partner says out loud that this is happening, that a particular person is running it, and that the firm will use the new method once it is live. Then they appear when a decision is needed. If your partners have not reached that much agreement, begin with getting the partners to agree.

Should the operations lead own it?

In most firms this size, yes. The practice manager, operations director or head of business services already owns what this work touches: templates, file structures, onboarding steps, reporting deadlines, who does what and in what order. They know where the handoffs are because they built half of them. They are also often the only person whose job is the firm itself rather than a client portfolio.

There is a second reason, less often said. Operations people are used to being told a process is fine when it is not, so they go and watch the job being done rather than accept the description of it. That instinct is exactly what a build needs in its first week, because the documented process and the real one are rarely the same thing.

Their weakness is standing. If a senior fee earner digs in, an operations lead may not be able to force it alone. That is what the partner sponsor is for, which is why the two roles work as a pair rather than as alternatives.

Should IT own it?

IT belongs in the room and not in the chair. Your internal IT person or managed service provider should be involved early on access, security, where data sits and what existing agreements already permit. Those are real questions, and the questions to put to your IT provider are worth working through before anything is built.

But this is not a technology deployment. It is a change to how a piece of work gets produced: which document comes out, in what shape, checked by which named person. Most providers are contracted to keep systems running, not to redesign working methods. Hand them the lead and the project turns into a procurement exercise. Licences are issued, a training session happens, the process is untouched. That is the argument in a tool is not a process.

What does the role actually need?

Strip away titles and the owner needs five things.

• Authority over the method. They can say the job is now done this way, and it sticks without a partners' meeting each time.
• Protected time. A few hours a week, explicitly carved out, for the length of a build. Not goodwill. Not evenings.
• Knowledge of the real process. Close enough to the people doing the job that nobody can fob them off with the official version.
• The right to rule things out of scope. Someone must say no to the second and third idea while the first is being finished. See the trouble with quick wins.
• Accountability for a number. Hours on the process before and after, or turnaround time on a report. Something a person checks.

Note what is absent. Technical skill is not on the list, and neither is enthusiasm. The keenest person in the firm is often the wrong choice, because their interest sits with the tools rather than the job, and they move on to the next thing before the first is embedded.

Does a committee work?

A working group of four is an excellent way to decide nothing. Committees suit policy, where you want several perspectives written into a document, and writing an AI policy is reasonable to do collectively. They are poor at delivery, which needs one person who cannot pass the problem sideways.

If you want breadth, give the owner a short list of people to consult: the partner sponsor, someone from IT, and one fee earner who does the job every week. Three advisers, one decision maker.

How do you know the owner is working out?

Within a month you should get clear answers to three questions. Which process are we changing, and why that one? What does finished look like? What has the owner cancelled or deferred to make room?

Vague answers mean the ownership is nominal. The process priority scorer forces the first question to a conclusion, and the six numbers worth a monthly look covers the second. There is a negative signal too: if staff are still quietly pasting client material into personal accounts, the owner has not reached them, whatever the policy says. Shadow AI is the clearest sign that usage is running ahead of ownership.

Where should the owner start?

With one process, chosen on evidence rather than appetite, and a date by which it is live and in use. Adoption is its own discipline, and getting a team to adopt AI is where owners most often underestimate the effort. Whether the build happens internally or with outside help is a second-order question, covered in consultant versus in house. Either way the named owner stays inside the firm.

If you are unsure which process should be first, the audit takes about three minutes and shows where your fee earners' unbillable hours go. Hand the result to the person whose name you have just written down.