Thinking in public
Writing
Essays on AI transformation, governance, and building things that work. Written from the vantage point of a former bank examiner and enterprise AI leader.
Featured
AI Amplifies the Same Problem — In Two Regimes
Generative AI doesn't introduce a new kind of organizational failure. It speeds up and surfaces the failure you already had.
Why I Started Thinking About AI Like a Bank Examiner
The discipline I learned examining banks is exactly what AI programs are missing. Not bureaucracy. The actual discipline: evidence, accountability, traceability.
Federal Agencies Don't Need More AI Strategy. They Need Someone to Finish What They Started.
The strategy, the framework, and the mandate all exist. What's missing is someone who can make any of it work. Federal agencies need implementation, not more deliverables.
Where the Decision Boundary Goes When AI Can Do the Work
We are not figuring out how to deploy AI. We are figuring out how organizations should change when machines can do increasingly consequential cognitive, creative, coordination, and decision work.
What a Bank Examiner Sees When They Look at an AI Program
Most AI teams see their program from the inside. An examiner sees it from the outside — and the view is different. Here's what I actually look at.
The Examiner's Checklist: What Financial Regulators Actually Look for in AI Governance
A former bank examiner explains what financial regulators actually look for in AI governance — documentation trails, named accountability, monitoring evidence, and the FS AI RMF's 230 control objectives.
Where Should Your Thinking Live?
The hard part isn't figuring out what AI can do. It's deciding what it should do.
The M-25-21 Deadline Passed. Here's What Agencies Need to Do Now.
OMB M-25-21 required agencies to have AI governance in place by April 2026. Most don't. Here's the four-step remediation path and why the clock is still ticking.
The M-25-21 Compliance Theater Crisis: What Agencies Built vs. What They Actually Have
Agencies filed M-25-21 compliance plans. Most never operationalized them. Three patterns of compliance theater and why the IG is in the audience.
The Dashboard Is Green. Now What?
AI products can look healthy long before you know whether they actually helped anyone.
AI Governance for State Agencies: What's Different
Federal mandates get the headlines. But state agencies are adopting AI with fewer guardrails, less guidance, and the same risks. The governance gap at the state level is real and largely unaddressed.
The Year AI Governance Got Real
At the start of 2025, AI governance was a conference-panel topic. By the end, it was a board-level agenda item. The shift happened because the consequences arrived.
Your AI Can Be Wrong Without Making a Single Reasoning Mistake
A smart system can reason perfectly from a bad premise. Once that premise survives as context, the cost is not just one wrong answer. It is figuring out how much downstream work you can no longer trust.
Eight Questions That Tell You Whether Your AI Is Actually Governed
Most AI governance programs start and end with the model. Here are eight questions that cover the full surface. Most organizations can answer three.
If Your Governance Lead Quit Tomorrow, Would Your Controls Survive?
Five questions that expose whether your AI governance program is persistent or fragile. Most organizations score between 8 and 14.
Your AI Ethics Statement Is Not a Governance Program
Every major company published responsible AI principles this year. Beautiful PDFs. Professional design. And operationally meaningless.
Before an AI Agent Enters a Live Workflow, Finish These Five Sentences
Capabilities tell you what an agent can do. Authority defines which judgments the organization has actually delegated.
The Org Chart Doesn't Have a Role for AI Governance
Find the person responsible for ensuring AI systems are governed throughout their lifecycle. You won't find them. The role doesn't exist.
The AI Inventory Problem: Most Companies Don't Know What They're Running
The first time most large enterprises try to build an AI inventory, they send an email. The response rate hovers around 30%. The teams that respond are the ones already doing governance well.
Enterprise AI Fails at the Handoff, Not the Algorithm
The model worked. The problem was everything that happened after the algorithm was finished. Four teams. Four handoffs. At each one, context is lost.
Your AI Pilot Worked. That's the Dangerous Part.
A successful AI pilot is one of the most dangerous things that can happen to an organization. Not because the technology doesn't work — it does. The danger is in what a successful pilot makes people believe.
Three AI Programs, Same Three Failures
Different organizations, different industries, different models, same three patterns. These failure modes show up so consistently they're practically a taxonomy.
The Meeting Where the AI Project Actually Dies
The project didn't fail when the model produced bad outputs. It failed five months earlier, in a conference room, during a meeting that lasted forty-five minutes.
The Question That Outlasts the Pilot
Every serious AI initiative eventually stops asking what the tool can do and starts asking what the organization can defend.
Enterprise AI Has a Middle Management Problem
Leadership is enthusiastic, engineering is capable, and nothing moves. The bottleneck is not at the top or the bottom. It is in the middle.
The Business Case for AI Is Almost Always Wrong
The math always works on the slide. The math almost never works in production. The standard business case format was designed for deterministic investments. AI does not work like that.
Nobody Gets Fired for Buying AI. They Get Fired for What Happens After.
The procurement decision was unanimous. Eighteen months later, the system is live in name only. This isn't an edge case. This is the modal outcome.
The Vendor Demo Is Not the Product
The demo is designed to produce a wow reaction. It is not designed to show you what the product will actually do in your environment, on your data, at your scale.
How to Kill a Project That Leadership Loves
Adjacent to an enterprise AI program, I watched a project that everyone knew was failing. Everyone knew. Nobody said it. This is the hardest problem in enterprise AI.
Data Pipelines Are Decisions. Treat Them That Way.
Nobody calls a meeting to decide how to handle nulls in the customer address field. These decisions get made at 4pm on a Wednesday and become load-bearing the moment someone builds on top of them.
The Data Problem Nobody Wants to Talk About Before the AI Demo
The demo looked great. Nobody in the room asked where the data comes from at 2am on a Tuesday. That question is where most AI programs live or die.
AI Readiness Is a Data Problem, Not a Model Problem
AI projects that stall tend to have the same root cause. It isn't the model. It's the data underneath it — the pipelines, the quality, the governance, the lineage.
Building Best Practices in a Data Engineering Team That Didn't Have Any
Most data engineering teams don't have a best practices problem. They have a 'nobody ever stopped to write it down' problem.
Why Your Data Scientists and Your Compliance Team Don't Talk to Each Other
The compliance team schedules a risk review. The data scientist shows up with performance metrics. The compliance analyst shows up with a checklist. For forty-five minutes, they talk past each other.
Most AI Teams Build. Very Few AI Teams Maintain.
The data science team builds a model. It ships. The team moves to the next project. The model runs in production. Nobody owns it. This is the default operating model for enterprise AI.
What 'Production-Ready' Actually Means for AI
The gap between 'it works' and 'it's production-ready' is where AI projects go to stall. Nobody agreed on what 'ready' meant before the building started.
The Difference Between Monitoring and Watching
Every AI team says they monitor their models. When you ask what that means, the answer is almost always: there is a dashboard. That is not monitoring. That is watching.
What Happens When Your AI Model Updates and Nobody Tells Compliance
The compliance team spent six weeks documenting an AI system. By the time they finished, the model it described no longer existed.
The Documentation Standard Nobody Follows — and Why It Matters
Ask an AI team if they document their models and they will say yes. Ask to see the documentation and you will get a README that has not been touched since development.
The Real Cost of Technical Debt in ML Systems
ML technical debt is quiet. The system runs. The metrics look green. And somewhere underneath, the foundation has shifted in ways nobody is measuring.
Every Generative AI Deployment Has Exactly Three Risks
Hallucination, data leakage, and prompt injection. If your organization can't name the controls for each, you're not governed — you're hoping.
Stop Measuring AI by Accuracy. Start Measuring It by What Happens When It's Wrong.
Ninety-five percent accuracy on a loan approval system means one in twenty applicants gets the wrong decision. Accuracy tells you nothing about who bears the cost of the 5%.
AI Product Management Is Not Software Product Management
The mental models from software PM work do not transfer to AI. Some of them are actively misleading. The gap changes almost everything about the job.
Three Questions Every Executive Should Ask About Their AI Program
If an executive asked only these three questions in every AI briefing, they'd have more governance insight than most organizations generate with entire committees.
What the Military Taught Me About Evaluating Systems Under Pressure
Before I was a bank examiner or an AI PM, I was an OC/T and Drill Sergeant. The gap between military evaluation standards and enterprise AI evaluation is enormous.
I Spent a Year Inside an Enterprise AI Program. Here's What I'd Do Differently.
A practitioner retrospective — the kind of honest accounting that usually happens over drinks at a conference but rarely makes it into writing.
The Solo Business Just Got the Enterprise's AI Problem
For the first time, solo and small businesses have access to AI infrastructure that was previously enterprise-only. The tools are here. The real question is whether the system around them is built to last.
47 pieces