The Six Lenses in Five Minutes

Every AI sponsor I've talked to in the last twelve months has a version of the same problem.

They have pilots running. They have a CFO asking when AI shows up in the numbers. They have a CMO or a CIO wanting more authority over what gets deployed. They have business unit leaders sponsoring their own use cases without telling anyone. They have a workforce that is some mix of curious, skeptical, and exhausted.

And they have very little time to think about it.

This piece is for that sponsor. It is a five-minute reference for how to hold the whole picture at once, without becoming an expert in any single piece of it.

It uses a framework I write about often, the Six Lenses, but you don't need to know the framework or this site to get value from this piece. The point is to give you a way to walk into your next AI conversation knowing which question you're actually trying to answer.

The thing no one names out loud

Most AI conversations inside complex organizations are confused conversations, even when they sound coherent.

Someone says "we need to do more with AI" and means something different from the person nodding next to them. One person is talking about cost reduction. The next is talking about clinician burden. The third is thinking about Stars, or denials, or member experience, or workforce strategy. A fourth person is worried about CMS scrutiny, and a fifth is wondering whether the EHR vendor's new feature counts as AI or not.

These are not the same conversation. They are five conversations happening at once, all using the same word.

The Six Lenses give a sponsor a way to name which conversation is which, and to know which one needs attention today.

The lenses

Lens 01 Value Where AI should help first, and why.

This is the lens most organizations skip. They start with the technology and look for a problem to apply it to. The leaders who get this right start with the business outcome, cost, growth, quality, workforce, experience, and ask whether AI is the right answer there.

AI tends to create real value where the work is high volume, has a clear right answer, generates proprietary data, and has a verifiable outcome. It struggles everywhere else.

If you cannot tie a use case to a business outcome, the use case is a hobby.

Lens 02 Operating model How humans and AI share the work.

The biggest mistake in AI adoption is dropping AI into existing workflows and hoping productivity follows. The workflow itself has to be redesigned around what AI does well and what humans do better.

The framing that holds up is simple: automate the work that is high-volume and rule-based, augment the work that requires judgment, preserve for humans the work where empathy, ethics, or relationship value cannot be replaced.

The unit of design is the task, not the role. A claims processor's job contains tasks in all three categories. So does a physician's. So does a member services rep's. The leaders who do this well map work at the task level and then redesign the job.

Lens 03 Governance What gets decided centrally, what gets decided locally.

Governance is where AI adoption either accelerates or stalls. Too little, and you get duplication, risk exposure, and fragmented data. Too much, and you smother the experimentation that creates value.

Centralize what protects the enterprise. Decentralize what creates value.

Centralize the risk framework, the model inventory, vendor evaluation, ethics review, and security. Decentralize use case selection, workflow design, and the rhythm of testing inside each function. The job of central governance is not to approve every idea. It is to set the guardrails so the business can move fast inside them.

Lens 04 Data What's ready, what isn't, and what to do about it.

Models are commodities. Compute is a commodity. The thing competitors cannot replicate is your data, and the workflows it sits inside.

But most organizations are not data-ready. The data exists, but it's locked in systems that don't talk to each other, governed by rules nobody wrote down, and described in language only one team understands.

The work is unglamorous and decisive. Identify the data your highest-value use cases actually depend on. Make that data clean, accessible, and trusted. Expand outward from there. You don't need to fix all your data. You need to fix the data that matters for the work that matters.

Lens 05 Capability The skills, roles, and rhythm needed to execute.

The scarce skills in AI adoption are not data scientists. They are the people who can sit between the business and the technology and translate without losing meaning in either direction.

Three roles matter most: translators, who connect business problems to AI possibilities; designers, who can rebuild a workflow around a human-plus-AI model; and operators, who own the outcome inside the business, not just the pilot.

The rhythm matters as much as the roles. AI adoption is not a project with a finish line. It is a quarterly cycle of learning, deploying, measuring, and adjusting. Organizations that treat it like an initiative get initiative-shaped results.

Lens 06 Adoption How the organization actually changes.

This is the lens most sponsors skip. They fund the strategy, approve the pilots, and assume adoption follows. It usually doesn't.

People adopt AI when three things are true at the same time: they want to use it, they are able to use it, and they are prompted to use it at the right moment in their work.

Most resistance to AI is not irrational. It's people protecting their judgment, their craft, or their job.

The leaders who handle adoption well take that resistance seriously rather than trying to override it.

---

How to actually use this

The six lenses are not a sequence and not a checklist. They are a way to look at the same problem from six angles so you know which conversation you are having.

A practical way to use them, the next time you are in an AI conversation: ask yourself which lens the room is actually talking about. Most of the confusion in AI meetings comes from people standing in different lenses without realizing it. The sponsor's job is to name which lens needs the decision today, and to make sure the people in the room are all looking at the same one.

A second use, harder and more valuable: every six months, ask which lens is the weakest in your organization. Not which one is most exciting. Not which one your team is best at. Which one is the bottleneck right now. That is where the next investment of attention should go. Strong value strategy fails without governance. Good governance fails without capability. Capability without adoption is wasted hiring.

The honest answer to which lens is weakest is rarely the one the executive team has been spending the most time on. That is the point of asking.

What this means for the next conversation

If you take one thing from this piece, take this: AI adoption inside a complex organization is not a technology problem. It is six conversations happening at once, and the sponsor's job is to know which one is yours today.

You will not master all six. You do not need to. You need to know they exist, who in your organization owns each one, and which one needs your attention this quarter.

The point is not to know everything about AI. The point is to know which conversation you are in.

That is a smaller, more useful job than the one most AI sponsors think they have. It is also the one that actually moves the work forward.