An AI Committee Needs Every Department and Real Authority

Episode Summary

Isar Meitis, CEO of Multiplai, spends most of this episode on one structure. After continuous education, which he makes step one of his blueprint, he wants an AI committee: at least one person from every department, somebody from the leadership team and preferably the CEO, and a few people who will stay up late playing with a new tool. The departmental spread gives you the needs and the limits from everywhere and a champion inside each function. Leadership gives the committee authority, because a group that has to route every decision through a VP loses opportunities while AI moves. The committee then owns the guardrails, the education, the tool selection, the processes and the budget. He argues guardrails widen what people try rather than narrowing it, and says tools do absolutely nothing for efficiency until the process around them is right.

Key takeaways

  • Step one is continuous education, and he frames it as a standing duty rather than a launch. Find a way for you, your team, your leadership and your employees to stay on top of what AI can do, where it is going, what the potential is and what the risks are

  • Step two is the one everything else hangs on. Starting an AI committee is what makes the effort survive and get across the entire company, rather than staying with the one or two people already tinkering

  • His reason for wanting the departments represented is two-sided, and he numbers the halves himself. You collect the needs, the struggles, the technical limitations and the data privacy constraints from everywhere, and you get a champion inside each department so the implementation meets less resistance when it reaches the people in the trenches

  • He wants somebody from the leadership team on the committee, preferably the CEO, and is explicit that it does not have to be. The first reason is that leading by example shows the company actually cares and that the work is important to it

  • His second reason for putting leadership on the committee is authority rather than symbolism. He wants an actionable committee that can make a decision and run with it, because waiting three or four weeks to route something through a VP loses opportunities while AI keeps moving

  • The committee’s first job is to define the rules, guidelines, regulations or guardrails, some of them tactical and some of them ethical, covering what may and may not be done with what kind of data in what kind of scenario

  • Education stops being an individual duty and becomes a committee one. The group divides and conquers across newsletters and YouTube channels, aggregates once a week, and distributes what is already digested and summarized to the people it is relevant to

  • His argument for putting tool selection under the committee is that the choosing is already happening without one. He says the research, from McKinsey or the others publishing on this, shows about 75 percent of employees are using AI tools they are not reporting to their leadership

  • He calls the next point a little secret, and it is the one that reorders everything above it. Tools do absolutely nothing for your efficiency on their own; using them properly in the right process is what does, so the committee owns the processes and the procedures for using them

  • Budget and infrastructure are committee work too, and he includes time in that. Budget for tools, budget for training, and protected time to experiment, because a committee also handed another marketing project and a strategy piece will not get to the experimenting

  • Asked what feeds the committee, he names three assessments and takes the strategic one first. His premise is that almost every industry will change dramatically in how people use things and in what products and services they will pay for

  • His worked example is a law firm billing on paralegal time. Nobody three, five or seven years from now will agree to pay for research, he argues, because they will know one prompt returns the information

  • He puts a number on the consequence and treats it as a planning problem rather than a prediction. If 30 percent of a firm’s income is paralegal time and that goes away inside five years, the strategic question is how you plan for it now

  • The second assessment is an HR skills gap analysis. What do people know today, what will they need to know tomorrow or in two years for the company to stay competitive, and do you hire for those skills or train for them

  • The third assessment is low-hanging fruit, and he means tactical things available immediately. What small changes right now save time, save money or make operations more efficient across every aspect of the business

  • His answer on adoption puts the people ahead of the technology. It is another exercise in change management, and you can have the best AI tools and the greatest infrastructure and still fail the transformation, because it is the people who make it or break it

  • Celebrating a win is a mechanism rather than a morale exercise, and he sizes both halves of it. His example is a marketing colleague doing in 37 seconds something that used to take three days, and his instruction is to spend ten minutes letting that person explain how, because it shows the thing is doable and it shows the company cares

  • His arithmetic on small wins is the case for gamifying them. Forty small wins across 40 different people in different departments leaves the whole organization about 5 percent more efficient than it was, which he calls significant

  • Asked how a company differentiates once everyone has the same tools, he answers human relationships and calls it the more important of his two answers. Relationships have always mattered, especially in B2B, and he expects them to matter a lot more

  • His reason is a research finding about who gains most from AI. Bottom performers using it get a significantly bigger efficiency increase than top performers, so the spread between people narrows, and if you aggregate that, companies converge too

  • What is left when output converges is relationships, and he names three kinds. Your employees, who you can drive and motivate; your ecosystem of suppliers, distributors and people who are not direct competitors; and your clients and prospects

  • His closing ask is to stop reading about it. You can listen to a million podcasts and follow YouTubers, and if you do not try it and start playing with it you will not learn, which he says holds for himself, for his company and for his own children equally

About Isar Meitis

Isar Meitis is the CEO of Multiplai, and at the time of this conversation had spent a year and a half teaching an AI course to business executives, with hundreds of them through it, alongside consulting work with companies putting AI in place. He describes the blueprint on this episode as something that refined itself over that year and a half on real scars rather than in theory. He also hosts the Leveraging AI podcast. His argument here is that an AI effort survives and reaches a whole company only when a standing cross-functional committee owns it: one person from every department for the inputs and the champions, someone from leadership so it can decide and act, and clear guardrails so people experiment more rather than less. Underneath that he is a change management person more than a technology one, and says it is the people who make or break the transformation.

 

In this episode

00:41 Welcome, and who Isar Meitis is
01:16 The question: a blueprint for implementing AI
01:26 The biggest question people ask, and where the blueprint came from
01:59 Step one: continuous education
02:27 NotebookLM, and testing a new tool the day it ships
03:33 Step two: start an AI committee
04:19 Inputs from every department, and a champion in each one
04:45 Someone from the leadership team, preferably the CEO
05:05 An actionable committee that can decide and run
05:23 And you want geeks on it
05:42 Committee job one: rules, guardrails, do’s and don’ts
06:22 Why guardrails prevent the wrong things
06:45 The playground fence, and why boundaries widen the field
07:24 Committee job two: divide and conquer on education
08:20 Committee job three: tools, and the 75 percent nobody reports
08:54 How a tool request becomes a test case and then licenses
09:09 Tools do nothing; the process around them does
09:54 Committee job four: budget, infrastructure and time
10:57 Committee job five: the strategic conversation, kept smaller
11:23 Three assessments, starting with the strategic one
11:38 The law firm and its paralegal hours
12:02 Thirty percent of income that goes away
12:44 Assessment two: the HR skills gap
13:03 Assessment three: low-hanging fruit
13:33 Fifty-seven to 230 processes per department
14:00 How to drive adoption and create excitement
14:21 It is change management, not a technology problem
14:42 What a committed CEO looks like, and what the other kind looks like
15:20 Celebrate wins: three days to 37 seconds
16:03 Gamify it, and what 40 small wins add up to
16:29 Encourage experiments inside the guardrails
16:51 Differentiating when everyone has the same tools
16:57 The first answer: human relationships
17:17 Bottom performers gain more than top performers
18:12 Relationships with employees, ecosystem, clients and prospects
19:03 What listeners should take away
19:12 Do not be afraid
19:14 Get your hands dirty, or you will not learn

In Guest’s words

“The process on how this thing survives and gets across the entire company, is starting an AI committee.”

— Isar Meitis  (03:33)

“You want somebody from the leadership team in that committee, preferably the CEO, but it doesn’t have to be.”

— Isar Meitis   (04:45)

“You wanna be able to move very quick because the AI moves very quick.”

— Isar Meitis   (05:05)

“When there was a fence, kids were playing at the fence, so they filled out the entire playground.”

— Isar Meitis   (06:45)

“Tools do absolutely nothing as far as your efficiency.”

— Isar Meitis   (09:09)

“Nobody, three years, five years, seven years from now will agree to pay for research.”

— Isar Meitis   (12:02)

“Human relationships have always played a very important role in businesses, especially B2B businesses, but it’s gonna become a lot more important.”

— Isar Meitis   (16:57)


 

Resources

Isar Meitis

Named on air

  • NotebookLM: The Google tool he uses at 02:27 as his example of staying current. He describes it as having shipped the week of the recording and says listening to the audio overview it generated blew his mind

  • McKinsey: Named at 08:20 as one source among others for the figure of about 75 percent of employees using AI tools they do not report

  • The playground fence experiments: The psychological research he refers to at 06:22 without naming it, in which children used the whole playground once there was a fence and stayed away from the edge without one

Ideas and terms discussed

  • The AI committee: A standing cross-functional group with one person from every department, somebody from leadership, and the authority to decide and act

  • Guardrails: His preferred word among rules, guidelines and regulations. Tactical and ethical boundaries on what may be done with what data, set by the committee before anything else

  • Continuous education: Step one of the blueprint and, once the committee exists, one of its duties. Divided across the group, aggregated weekly, and distributed already digested

  • The three assessments: Strategic, HR skills gap, and low-hanging fruit. What feeds the committee rather than what the committee produces

  • Change management: His framing for the adoption half of the episode. The transformation is a people problem, and the best tools and infrastructure will not save it if the people are not on board

Related AI Realized episodes and events

 

Frequently Asked Questions

 
 
 
 
 
 
 
 
 
 
 
Previous
Previous

AI Is a Tool for Augmenting People, Not Replacing Them