How do I measure the gap between what the owner thinks and what the team says?

The three views

So I have three entry points. The owner's view of how things are. The view from connecting to the systems: processes, data. And the view from the team. Then we compare the three to see how well each one matches reality.

How to collect each view

The owner. I want to see what the owner, or the main person in the company, thinks. Then I fill in the same test myself as we go. The operational AI readiness check records the owner's view before anyone else talks.

The team. Asking the same questions, I always go through Level 1, Level 2 and Level 3. If the people further down are a large group, I send them surveys. Example questions:

1. Which decisions can you make without asking?
2. Who do you go to when something goes wrong?
3. Where do you look up how a job is done?
4. What did you wait on last week?

The systems. Connect the CRM, accounting and scheduling tools. Then check how far you can trust the data. Whether the processes are written down. Whether they're followed, and whether they're tracked.

For reality, I mostly rely on the connections, the review of data and processes, and my own objective judgment.

Reading the gap

The gap between what the owner thinks and what the team thinks shows me how big a gap exists in the company. That usually shapes the order of the work and the time it takes to improve.

From Luba Inz's engagements with 10+ owner-led companies: 7 in 10 owners believe they've delegated when their team says they haven't.

Every row is an example.

The gap between what the owner thinks and what the team says is the first thing worth measuring.

What to do first

I often hit the same wall: no ownership, no people. People are the hardest part, because it takes a long time to find them. Everything else moves faster.

With a small gap, the work can start with data and processes. With a large one, start with people: who owns each decision, and up to what limit. That's a decision authority matrix. Until one exists, people wait for the owner.

Where each view shows up in SCOPE™

SCOPE™ by Efficiency Sprint maps where a company stands. Each state has a tell in one of the three views:

1. Stabilize: two systems give two answers to the same question.
2. Codify: the team describes the same job three different ways.
3. Ownership: the team's answer is "ask the owner."
4. Pulse: the owner can't see the week's numbers without asking for them.
5. Engine: the three views agree, and AI acts within guardrails.

AI scales whatever's already there. If the three views disagree, an agent inherits the disagreement.

Find out where your company stands

Efficiency Sprint makes companies operationally ready for AI. The operational AI readiness check takes about two minutes and records the owner's view, the first of the three. More about how I work: About Luba.