My point of view on AI

AI is a multiplier

In strong systems, AI accelerates value, learning, and delivery. In weak systems, it accelerates defects, risk, and fragility.

Leaders: if you are not hands-on with AI by now, that is a problem. AI is not going away. Learn to leverage it.

Strong system × AI = leverage

Weak system × AI = amplified dysfunction

AI does not remove the need for a robust operating system. It increases the requirement for one.

AI reveals the truth about your delivery system: it exposes the gaps between what organizations say they do and what actually happens when work needs to reach customers.
The goal is not the smallest team. The goal is the smallest sustainable system.
This is a system conversation, not a tooling conversation.

This thesis began as an article: AI Is a Multiplier.

Operating evidence

What I led

This point of view comes from operating experience, not observation. I introduced and led responsible AI adoption across Engineering and Product: AI literacy programs built through real use, secure SDLC controls, IP and PII safeguards, human-review workflows, and evaluation guardrails. Engineering and Product leaders helped shape the practices required to make it usable in daily delivery.

Adoption was measured at the system level, through flow and realized outcomes, not individual output. The result was improved delivery effectiveness while supporting responsible, scalable use across the organization.

Framework

How I approach AI adoption

My approach is practical, and it runs on a simple rule: match the level of AI autonomy to the level of consequence. Six steps, in order.

  1. Start with the problem and the outcome

    Map the need, workflow, dependencies, constraints, and economics, then establish measurable customer, business, delivery, or operational success.

  2. Build AI literacy through real use

    Give leaders and teams practical exposure and shared learning.

  3. Decide where AI belongs and who is accountable

    Allocate work among humans, deterministic systems, assistants, collaborators, and agents, with clear stewardship for outcome, data, risk, and escalation.

  4. Match autonomy to consequence

    Higher consequence requires stronger controls, clearer human accountability, and more evidence.

  5. Design for verification

    Build correctness, security, regression, architecture, policy, operational, and outcome checks into the workflow.

  6. Measure the system and earn greater autonomy

    Measure Flow, Realization, and cost per outcome. Increase autonomy only after evidence demonstrates quality, reliability, security, and realized value.

What AI changes

AI changes who performs the work

The role of experienced engineers is expanding, not shrinking. AI reduces task effort, but it does not remove technical judgment, product context, quality thinking, operational ownership, or accountability. Experienced people become more important because they know how to guide, review, orchestrate, and validate what AI helps create. AI may shrink parts of the team, but it cannot shrink the work of judgment, learning, validation, and ownership.

I have written in depth about the work that remains as teams change and how AI reshapes development teams.

Reflection

The real question

I am optimistic about AI. I have been using it since February 2023 and have seen significant gains in the recent wave of frontier models and agents. I can already see how it is reshaping how modern organizations work.

But I am also practical. AI will not rescue a broken operating model. It will reveal it. The organizations that benefit most will be the ones with the strongest systems, clearest priorities, healthiest teams, and most disciplined path from idea to outcome.

Is your system strong enough for AI to make you better, or will it simply make your existing problems move faster?

Let’s talk

If you’re navigating AI adoption at the enterprise level, I’m happy to compare notes.

Start a conversation Read the AI articles