When agents do more of the work, and the system already knows what’s moving, a meeting to report status is a meeting to read aloud what’s already written down. The time is better spent deciding things, and on something that gets harder as products change faster: telling the company and customers a clear story about what changed and why it matters to them.
Status meetings, standups and sprint ceremonies were built for a world where people did all the work and the only way to know where things stood was to ask them. A project manager’s week went to collecting updates, and everyone else’s went to giving them. That made sense when work moved at human speed.
Two things break it now. Agents and tools already record what’s happening, in more detail than anyone would say out loud. And the product can change weekly, so the harder problem isn’t knowing what shipped. It’s making sure sales can sell it, support can support it, finance and compliance aren’t surprised, and customers understand why it’s good for them.
I’ve sat in many status meetings where the most useful minute was the one where someone finally raised a real decision. And I’ve watched good features land badly because the people who had to sell and support them heard about them the same day customers did.
The ideaLet status fall out of the system. Save meetings for decisions, customers and strategy. Brief every department before customers see a change. And tell customers a consistent story, tied to their pain and the product’s direction, instead of handing them a list.
My illustration of a typical week. Switch eras to see reporting give way to deciding.
When work runs through tools and agents, the system already knows what moved, what’s blocked and what shipped. Asking people to type that into a status report, or say it in a meeting, is duplicate work that interrupts the work itself. The useful version of status is automatic, and it only asks humans about the exceptions.
The same question, asked two ways on a Thursday afternoon.
Nobody should have to report what the system already knows. People should only be asked for what it can’t know: judgment.
This isn’t an argument for no meetings. Shopify’s purge worked because people were asked to bring back only what earned its place. What earns it now is anything that needs people together: deciding, understanding a customer, setting direction, and simply knowing each other.
Pick a meeting to see what I’d do with it.
When the product changes weekly, every department needs to know what’s coming before customers do, in terms that matter to its job. Sales needs a talk track, support needs to know what will break habits, finance needs to know if billing changes, and compliance needs to know what to validate. Each department’s agents need their skills updated too.
AI makes this practical. The same approved release can produce a brief for every team, written for their role, days before customers see anything.
Release: bulk actions on the list screen. Pick a team to see its brief, generated from the same approved release.
A release note that lists ten items tells customers the product changed again and they have to figure out whether they care. A story tells them what used to be painful, what’s easier now, and why the company built it, often because they asked. The first feels like homework. The second feels like being listened to.
For AI features especially, the framing matters. “This does the tedious part so you can spend your time on the judgment calls” lands very differently from “this automates your job.” And with AI, the same release can be told differently to each kind of customer, at no extra cost.
Start with the list, then see it as a story for each persona.
Consistency comes from a spine. Every release hangs from a quarter’s theme, every theme from the product strategy, and the strategy from the company’s goal. When a customer or a salesperson hears about a new feature, they should be able to trace it back, and each release should feel like the next chapter, not a random addition.
Releases as chapters under the quarter’s theme, all traced back to the goal.
More change needs more structure in how it’s told, not more messages. I’d set four rhythms, each with a clear audience, and keep them predictable so nobody is caught off guard.
Cutting meetings can cut connection, and teams that never talk stop trusting each other; keep time that’s just for people. An automatic status feed can become surveillance if it’s used to watch individuals rather than the work. Personalized customer messaging can slide into spin; the story has to be true, including what’s not better yet. And in regulated products, some ceremonies exist for good reasons, like formal change review, and should be made faster, not removed.