400,000+ business leaders (and teams at IBM, AWS & Zapier) start their day with The AI Report. 5 minutes. Plain English. No hype.

Expert analysis from
Marie-Lou PoirrierSomeone in your organization, maybe you, discovers that with AI, what used to take a day now takes two hours. The first reaction isn’t relief. It isn’t curiosity about what to do with the recovered time. It’s a faster, instinctive thought: should I be doing more now?
They don’t say it out loud. They look up from their screen. Look at their team. And for a split second, they don’t know if they are a good leader or a demanding one. They don’t know if what they are about to think is reasonable, or if it’s just an old script running.
That silence. That’s where this piece lives.
A few weeks ago a question was circulating among leaders implementing AI: “Some of my employees are twice as fast thanks to AI. Should I expect twice as much from them?”
It sounds like a management question. A reasonable one, even.
Something about it felt off. Not wrong, exactly. Just revealing.
The question isn’t really about employees. It’s about the logic we carry into the room before we even open our mouths. The assumption underneath: that value equals output. That more capacity means more obligation. That time recovered is time owed.
That logic didn’t arrive with AI. We brought it with us.
Most of us learned, somewhere early, that worth is demonstrated through output. A finished project. A grade. A delivered result. The feeling of having done enough, which, if we’re honest, was rarely a feeling we got to keep for long.
So when AI hands back two hours in a day, the nervous system doesn’t register it as a gift. It registers it as a gap. An unfilled obligation. A question: what are you going to do with that?
Not: what do you want to do. What are you going to do. The pressure is already built in.
That’s not ambition. That’s conditioning. And the difference matters, because ambition moves toward something. Conditioning just fills space.
Not all time saved is equal.
Some of the time AI compresses was pure execution. Formatting, summarizing, first drafts. That time, yes, can become more output if that’s what’s needed.
But some of it was something else. The slow read of a document that also happened to surface a question worth asking. The slightly longer meeting that ended with everyone actually aligned. The thinking that happened in the friction, not despite it.
When that space gets filled automatically, because the logic says it should be filled, something gets crowded out. Not dramatically. Gradually. And the organization gets faster. Just not necessarily sharper.
The question is whether it’s being made consciously, or whether the old logic is just making it by default.
So: should you expect twice as much?
Maybe the more honest question is: why was that the first thing you asked?
Not as a criticism. As a genuine invitation. Because the reflex, the automatic move toward more, didn’t start with AI. It started somewhere earlier. In a classroom, maybe. In a family. In a moment when someone’s approval felt conditional on what you produced.
AI just made the script visible. Gave it a new context to run in.
Where does that urge come from, for you? The answer will tell you more about how you lead than any productivity metric ever will.
The technology is ready. The question nobody is asking is: ready for what, exactly? MarieLou works with AI-forward companies on the layer that doesn’t show up in implementation plans – the human one. The silent resistance. The leaders projecting certainty while their teams are overwhelmed. The emotional realities that no tool resolves, and that quietly determine whether transformation actually lands. Through keynotes and workshops, she helps leaders and teams do the work that makes AI adoption real instead of performed. At The AI Report, she contributes across creative, design, and editorial – and writes the Human & AI Debrief, where the focus is always the human layer underneath the technology. TEDx speaker. Human sciences researcher. Graphic designer turned writer.

.png)