Industry-leading insights

Three people in the same company opened the same AI assistant one afternoon. One got a cautious editor. One got a bold strategy partner. One got something that agreed with everything she said. The same tool, in the same hour, produced three different workers, and nobody found it strange, because nob ...

There is a moment that shows up in almost every team running an AI specialist for more than a couple of quarters. Someone goes to correct something, and realizes they have corrected it before. The exception that was explained in March gets explained again in June. The context somebody wrote out care ...

Ask a leadership team what they should do about AI right now and the question usually comes back the same way. Which one should we buy? That question comes from procurement, and procurement is the wrong verb for what actually has to happen next. You are not buying AI. You are standing up a workforce ...

The second specialist is where the trouble shows up. The first one goes fine. A team stands it up, shapes it over weeks of configuration and correction, and ends up with a worker that genuinely does the job. Then the team goes to stand up a second one, for an adjacent role, and discovers something u ...

The day a specialist goes live inside a team is a milestone. It is not a finish line. A specialist looks great in the first week. The role is defined, the scope is clean, the specialist is doing the slice of work it was designed for. The team around it feels the lift. That part is the easy part. The ...

Somewhere in your organization right now, an AI system is waiting for someone to open a window and talk to it. That detail sounds trivial. It is actually the design assumption holding the current generation of AI in place, and it has started to come loose. There is a name for what comes after: headl ...