In 90 minutes you can see who really owns your AI

In 90 minutes, you can see who really owns your AI.Hint: it's usually not you.

I run this 3-question Ownership Workshop with operations leaders and department heads before we start work at Omniance. One session, a whiteboard, and a clear map of where you're exposed.

You can run the same session with your own team.

Here's how—and what to watch out for.

(💾 Save for later)

𝗦𝘁𝗲𝗽 𝟭 – 𝗕𝘂𝗶𝗹𝗱 𝘆𝗼𝘂𝗿 𝗱𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁𝗮𝗹 𝗶𝗻𝘃𝗲𝗻𝘁𝗼𝗿𝘆

Create a simple template with five columns: tool name, vendor, process owner, processes it supports, and data it touches.

Ask your direct reports to fill in their AI tools before the meeting. Only tools touching real work, not experimental setups with test data.

Don't wait for a perfect list. Get 80% coverage from the people actually using tools daily - that's enough to run a sharp workshop.

One thing this inventory won't catch: shadow AI—tools your people use without IT approval. That's a separate, deeper problem. But this workshop will show you how much you don't control even among the tools you do know about.

𝗦𝘁𝗲𝗽 𝟮 – 𝗥𝘂𝗻 𝘁𝗵𝗲 𝘄𝗼𝗿𝗸𝘀𝗵𝗼𝗽 𝘄𝗶𝘁𝗵 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺

Put the full inventory on a screen. Go through each tool. No vendor slides, only your own view of what these tools actually do and where they sit in your operations.

𝗦𝘁𝗲𝗽 𝟯 – 𝗔𝗽𝗽𝗹𝘆 𝘁𝗵𝗲 𝟯-𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗧𝗲𝘀𝘁

For each tool, ask:➝ Continuity – Can you operate if vendor disappears or changes terms tomorrow?➝ Advantage – Does it touch regulated data or competitive knowledge?➝ Accountability – Can you explain and trace its decisions when required?

The more "no" answers you get, the higher your exposure.

Three "yes" answers? 🟢 You can rent this safely.Mixed answers? 🟡 You need to guard it with limits and fallback plans.Three "no" answers? 🔴 You need to own this, or accept strategic risk.

𝗦𝘁𝗲𝗽 𝟰 – 𝗗𝗲𝗳𝗶𝗻𝗲 𝗮𝗰𝘁𝗶𝗼𝗻𝘀

🟢 Rent → Keep, standardize, negotiate price🟡 Guard → Set clear limits, plan migration or sovereign rebuild🔴 Own → Document the risk and build your case for internal control

This doesn't mean building everything from scratch. It often means rebuilding on open-source models you control, hosting on EU infrastructure, or putting strict governance around what must stay with a vendor. Concrete steps, not a revolution.

In 90 minutes, you see where your function is safe, where it's fragile, and where someone else holds the keys.

The most revealing moment?

When red boxes appear where you expected green. Those aren't broken tools. They're your next strategic priorities.

If you're the one driving AI in your department, you don't need to wait for a mandate from above.

Run this for your own team first. Bring the results to leadership. A single red box on a whiteboard starts a better conversation than any slide deck.

And if you want to run it together - that's what the workshop with us is for.