15 July 2026
From pilot to production: what actually has to change
Licenses, a few pilots and a deck that promised results. What actually has to change for an AI pilot to become the way the work runs.
Writing
Notes on redesigning work around AI: what changes inside a task, what stays human, and what a leader actually has to decide.
The tools are capable and the pilots ran. These are the reasons the work still looks the same afterwards.
15 July 2026
Licenses, a few pilots and a deck that promised results. What actually has to change for an AI pilot to become the way the work runs.
1 April 2026
Tools bought, pilots launched, teams trained — and still no change in the work. The five stages AI actually moves through inside a company.
28 March 2026
Most companies can point to something that looks like AI progress. Far fewer can point at a workflow that was actually redesigned around it.
What has to be defined about the work itself before AI can change how any of it gets done.
18 April 2026
Most executive conversations about AI start by assuming the goal is speed. AI is better understood as a diagnostic: it shows you where the work is already broken.
18 April 2026
Why most organizations struggle with AI and misdiagnose the problem entirely. The constraint is not the model. It is how little the work is defined.
8 April 2026
The phase after the hype cycle is different in kind. AI adoption is exposing an architecture problem in how work is organized, not a tooling problem.
28 March 2026
AI transformation conversations still start at the technology layer — which models, which tools. The layer that decides the outcome sits above it.
23 March 2026
Companies rarely struggle because people are unwilling to perform. They struggle because the work itself was never clearly defined. A practical guide.
21 March 2026
Most companies think they have an AI adoption problem. They have a work design problem that AI is making impossible to ignore.
20 March 2026
Organizations assume AI will improve how work gets done. What AI exposes is deeper: the work was never clearly defined in the first place.
20 March 2026
Organizations spend enormous effort hiring, evaluating and managing underperformance, and very little on designing how the work actually flows.
20 March 2026
Organizations treat AI adoption as a tooling problem. The models are capable. What is missing is a definition of the work precise enough to act on.
What a role stops telling you once the task mix moves, and what replaces the job description.
18 April 2026
A practical shift from static job descriptions to defined work systems — what changes, and what a work architecture has to specify to be usable.
18 April 2026
The abstraction layer that held organizations together is starting to collapse. What a job title stops telling you once AI changes the task mix.
21 March 2026
Job architecture sounded like internal HR maintenance — necessary, rarely strategic. Once AI reads and routes work, it became infrastructure.
21 March 2026
Most AI conversations focus on job loss. A quieter risk sits at the bottom of the ladder: the entry-level work that trained everyone above it.
20 March 2026
AI adoption fails less on technology than on definition: who owns what, how decisions get made, and what each role is actually accountable for.
Funding, sequencing, and where decision authority sits when AI is inside the workflow.
13 April 2026
The market says AI will automate your tasks. For an operator that framing is dangerously incomplete — the durable advantage is where decisions sit.
21 March 2026
Companies talk about AI as an innovation story. It is also a resource allocation story, and in many companies the budget it draws on is the people budget.
Two weeks, one function, one sponsor — the work read task by task, and a decision you can act on at the end of it.