Frequently Asked Questions

I help leaders establish a clear view of the AI across their organization and decide what requires attention, where accountability sits, and what should happen next. AI may already be distributed across embedded software, enterprise platforms, departmental purchases, vendor solutions, employee-selected tools, custom development, and automated workflows, without a single view bringing it together.

The work can help clarify the underlying question, establish an AI estate baseline, identify ownership and governance gaps, and, where needed, design the portfolio governance operating model required to sustain visibility, accountability, and oversight over time.

Engagements may begin with a focused Diagnostic Conversation, move into AI Estate Discovery, or extend into an AI Portfolio Governance Operating Model depending on the need. Each offering is described on the Approach page.

AI capabilities have entered organizations through many channels, while the ability to see and account for that activity in one consolidated view has often lagged behind. Vendors activate new capabilities inside existing software. Teams adopt tools directly. Access and integrations accumulate over time. Each may be reasonable on its own, but together they can create an AI estate that is fragmented across systems, functions, and decision processes.

That is the void. There is often a gap between the AI an organization believes it has adopted and the broader AI estate already taking shape across the business. I help make that estate visible, establish clearer ownership and accountability, and give leadership the footing to decide what requires attention and how the portfolio should be governed.

No. I do not need administrative access, credentials, or control of your systems, and I do not ask for them. The work runs from conversations and from your own people walking me through what they see, using the access they already have. Where a list or a settings screen needs to be reviewed, someone on your side with the appropriate access drives, and I observe and record.

The goal is a clear view of the AI estate within the agreed scope, produced without adding risk in the process of looking for it

The level of involvement depends on the scope, but the work is designed to be focused and proportionate. A Diagnostic Conversation requires very little time from your team. AI Estate Discovery typically involves a small number of focused conversations and guided reviews of the tools, records, or information already available. An AI Portfolio Governance Operating Model may require broader participation across business, technology, and governance functions.

What surfaces may prompt real decisions. The work itself is designed to create clarity without unnecessarily pulling teams away from their day-to-day responsibilities.

Not necessarily. The Diagnostic Conversation and AI Estate Discovery can be completed using the systems, records, and tools already available in the organization.

If the need extends into an AI Portfolio Governance Operating Model, the organization may choose to use an existing platform or introduce a tool to support intake, review, decision tracking, and ongoing oversight. That choice depends on the existing environment and how the governance process needs to operate over time.

The AI operating across your organization remains your responsibility whether or not you can clearly see it. When a customer questionnaire arrives, a board member asks, or something requires attention, uncertainty about what is in use is itself a problem.

The technology may come from a vendor, but responsibility for how it is adopted, owned, and governed remains with the organization. Establishing a clear view of the AI estate gives leadership the footing to decide what requires attention and what should happen next.

Because I bring more than 20 years of experience making complex technology portfolios visible, accountable, and easier for leadership to govern.

I apply that same discipline to AI: establishing a clear view of what exists, why it is being used, who owns it, what it depends on, and where additional review or action is needed. The goal is to give leadership a decision-ready view rather than another disconnected list of tools.

My role is to connect business, technology, and governance perspectives so that AI can be managed as a portfolio, with clearer ownership, stronger oversight, and a practical path forward.

I bring a portfolio governance lens to AI: turning activity that may be distributed across functions, platforms, vendors, and teams into a clear, accountable view leadership can use to make decisions.

The work establishes what AI exists, why it is being used, who owns it, what it depends on, what governance or validation has already occurred, and where additional review or action is needed. That creates a stronger foundation for decisions about ownership, prioritization, investment, remediation, consolidation, and ongoing oversight.

Where the need extends beyond visibility, I help translate that clarity into a practical AI portfolio governance operating model, connecting business ownership, specialist review, decision processes, actions, and leadership oversight.

The result is a clearer basis for deciding what matters, who is accountable, and what should happen next. The ways I can support that work are described on the Approach page.

The outcome depends on what the work needs to establish.

A Diagnostic Conversation produces a written recommendation that clarifies the underlying issue and whether the right next move is to proceed, pause, or reframe.

An AI Estate Discovery produces an AI estate baseline, written findings, and a governance action view showing what was identified, where ownership or governance gaps remain, what requires additional review, and what needs leadership attention.

An AI Portfolio Governance Operating Model produces the structure needed to sustain that visibility over time, including roles and decision rights, intake and review workflows, specialist-review routing, operating rhythms, portfolio reporting, and leadership oversight.

Across all three, the goal is the same: give leadership a clearer basis for deciding what matters, who is accountable, and what should happen next. The ways I can support that work are described on the Approach page.

Your AI estate is the full set of AI capabilities across your organization, taken together: the assistants and features inside the software you already use, the standalone tools adopted by teams, the outside services your systems connect to, and the custom or automated solutions developed internally. Most organizations think of AI as a few named tools. The estate is the broader picture, including capabilities that may be distributed across functions, platforms, vendors, and teams.

AI can enter an organization through many ordinary channels. A vendor may activate an AI capability inside software already in use. A team may adopt a tool directly because it solves an immediate need. An outside service may be connected to company data or systems. AI may also arrive through custom development, automation, acquisitions, or changes to existing platforms.

Each decision can appear reasonable and limited on its own. The challenge is that these capabilities may enter through different processes, owners, and systems, so they are not always brought together into a single view.

That is why the answer to “What AI are we using?” can be surprisingly difficult to assemble. The AI estate often develops incrementally, across many parts of the organization, rather than through one deliberate enterprise decision.

There is a meaningful difference between AI that advises and AI that acts. Some systems only produce information: a summary, a suggestion, an answer a person then chooses to use or ignore. Others can take action directly, writing to your records, sending messages, changing settings, or triggering steps in a process, without a person approving each one.

The distinction matters because the governance implications are different. A system that only advises can be wrong. A system that can act can be wrong and carry out the consequence before anyone notices. Knowing which of your systems can only advise, and which can act, is one of the first things the discovery establishes.

IT and Security may already have visibility into parts of the AI estate, particularly capabilities that have moved through established technology or security processes. The challenge is that AI can also emerge through embedded software, business-led adoption, vendor services, employee-selected tools, and other channels that may be documented differently or owned elsewhere.

This is not a gap in your team’s ability. The issue is that the information needed for an enterprise AI view may be distributed across multiple teams, systems, and processes. AI Estate Discovery brings those pieces together so the organization can see what it has, where accountability sits, and what requires further attention.

You can, and it is worth doing. On its own it gives you a partial answer. Each vendor tells you about their own product, one at a time, with no single view across all of them, no record of who owns what on your side, and nothing about the tools your teams adopted outside procurement or the connections granted directly to outside services.

The value is not any one vendor’s disclosure. It is the assembled picture: a consolidated view of the capabilities identified, with ownership and purpose made visible, so leadership can see relationships and gaps that individual vendor responses cannot show.

You could. The challenge is often less about capability than ownership and focus. The work crosses business, technology, security, procurement, governance, and other functions, and the information needed to assemble the AI estate may already exist in several different places without anyone being responsible for bringing it together.

An outside perspective provides dedicated focus and a neutral way to connect those pieces across organizational boundaries. If the organization prefers to run the process internally, the discovery structure can also provide a repeatable foundation for doing so.

You could, and depending on the scope, regulatory requirements, and broader transformation needs, that may be the right choice.

I focus on work where leadership needs a clear view of the AI estate, stronger accountability, or a practical portfolio governance model. That work may involve an entire organization or a defined business function within a much larger enterprise.

The distinction is less about company size and more about the need. I provide senior-level, hands-on support around visibility, decision clarity, and portfolio governance, with the engagement shaped to the part of the organization that needs attention.

Meaning Drift happens when people use the same words but attach different meanings, assumptions, or expectations to them. A group can appear aligned while different people are actually working from different definitions of the problem, the outcome, or even the thing being discussed.

With AI, that matters because different teams may use the word to describe very different things: embedded features, assistants, models, automation, vendor capabilities, or experimental tools. Those differences can affect what gets identified, who believes they own it, which governance processes apply, and what ultimately appears in the enterprise view.

Meaning Drift is one of the patterns I explore in my newsletter, Upstream Thinker, because decision clarity often begins by making those differences visible before they become larger operational or governance problems.

I explore decision clarity, AI adoption, portfolio visibility, and operational change through my newsletter, Upstream Thinker, including short stories about DriftMode, a hypothetical company navigating situations that reflect real organizational challenges.