For years I did the same thing every Monday: block 30 to 60 minutes, pull numbers, build a slide, walk through it, get a question I had already answered in the slide, make a decision, then reverse it by Friday when new information arrived. I estimate I have spent about 2,000 hours of my career in this ritual, roughly a full year of working time, mostly repeating out loud what should have been visible on a screen. So yes, kill the status meeting.
What the meeting actually costs
Look at a typical weekly status meeting. Someone presents numbers, someone asks a clarifying question, someone presents engineering progress, someone asks why X is late, someone summarizes, and a decision is either avoided or reached with half the context. The meeting is 45 minutes, prep was 90, notes take 20 and get read by maybe two people. That is four person-hours to communicate roughly 200 words of new information, a 100x write-amplification ratio you would never tolerate in your product.
The status meeting is not a planning practice. It is a trust deficit papered over with calendar time, and the calendar time costs more than fixing the trust deficit would.
The replacement: one live product page
I run a single URL per product. It updates automatically and anyone can refresh it at any time. Six strips. Product health is eval score per surface with the delta from last week, color coded. Adoption is daily active usage of the top five features with 7-day and 30-day trends. Customer signal is the top five themes from support tickets, sales calls, and churn surveys in the last seven days, auto-clustered by an agent. Bets are the active experiments with hypotheses, kill conditions, and next decision dates, pulled from the bet portfolio. Cost is cost per successful action by surface. Incidents are open and recently closed with post-mortems linked. At the bottom: last updated, auto. The page never goes stale.
Once the page exists, what survives is a 20-minute optional weekly product review where I just walk the page, decision conversations called as needed, and a weekly cross-functional customer signal sync. What dies is the weekly status deck, the monthly roll-up, the quarterly board prep that compiles the rollups, and most 1:1s that were really status updates in disguise. When I did this at Smartcat, I reclaimed about six hours a week of calendar time and filled it with shipping, not more meetings.
The build and the pushback
The page is less than a week of work, most of it instrumentation you should already have. Notion, Linear, a stitched Looker dashboard, or a small Next.js page all work. If your team cannot stand up a v1 in two weeks, that is your discovery exercise. When someone will not read the page, they do not get to participate in the decision. When execs want a written narrative, auto-generate it at the top with an agent that reads the strips every Monday.
This week, pick one surface you own, build a rough 3 to 5 strip dashboard, share the URL, and on Monday just walk the page. Notice the meeting ends 15 minutes early. By the fourth week it is either dead or transformed.