Kill the Status Meeting

A thing I used to do every Monday for years

Block 30 to 60 minutes. Pull numbers. Build a slide. Walk through it. Get a question I'd already answered in the slide because no one read it carefully. Make a "decision." Reverse the decision by Friday because new information arrived. Repeat.

If you've been a PM for more than a year, you know this ritual. I estimate I've spent about 2,000 hours of my career in it across various companies. That's a full year of working time, mostly spent verbally repeating what should already have been visible on a screen.

The status meeting isn't a planning practice. It's a trust deficit being papered over with calendar time. And the calendar time costs more than fixing the trust deficit would.

What the meeting actually does

Look at what actually happens in a typical weekly status meeting:

• Someone presents numbers.
• Someone asks a clarifying question.
• Someone presents engineering progress.
• Someone asks why X is delayed.
• Someone presents design updates.
• Someone asks if the design is final (it's not).
• Someone summarizes.
• A "decision" is either avoided or reached with half the context.

The meeting is 45 minutes. Prep was 90 minutes. Post-meeting notes take 20 minutes and are read by maybe two people. Total cost: four person-hours to communicate roughly 200 words of new information.

That's a 100x write-amplification ratio. You'd never tolerate that in your product. Somehow we tolerate it in our own workflow.

The replacement: a live product page

I run a single URL for each product I own. It updates automatically. Anyone in the company can refresh it at any time. It replaces the weekly status meeting almost entirely.

Six strips:

Product health. Eval score per surface, with delta from last week. Color coded. If something is red, I click in and see the failing inputs. No prep required.

Adoption. Daily active usage of the top 5 features, with 7-day and 30-day trend lines. Includes the leading indicator metric for each one (like "percent of users hitting the new flow in week 1"), not just the lagging metric.

Customer signal. Top 5 themes from support tickets, sales calls, and churn surveys in the last 7 days, auto-clustered by an agent. Each cluster links to the underlying conversations. This is the new voice of the customer, except it's voice from yesterday, not voice from last quarter.

Bets. Active experiments, their hypotheses, their kill conditions, their next decision date. Pulled from the bet portfolio (see Kill the Roadmap).

Cost. Cost per successful action by surface, 7-day trend. The number that's about to ruin gross margin shows up here before it shows up in the QBR.

Incidents. Open incidents, time since open, severity. Closed incidents in the last 7 days with their post-mortems linked.

At the bottom: "last updated: auto." The page never goes stale. That's the whole point.

What survives, what dies

Once the page exists, the weekly status meeting doesn't need to exist. What survives:

• Weekly product review (20 minutes, optional attendance). I walk the page. We identify the one or two surfaces that need a decision. We decide. We end early. I don't prep slides. The page is the prep.
• Decision conversations (called as needed, 20-30 minutes). When a bet hits its kill condition or a regression needs human judgment. Everyone shows up having read the page. The meeting is the decision, not the briefing.
• Customer signal sync (weekly, 30 minutes, cross-functional). PMs, support, sales, CS, design, eng. We go through the top customer signal clusters together. This is the only meeting where new information actually gets generated.

What dies:

• The weekly status deck.
• The monthly roll-up of weekly status decks.
• The quarterly board prep that compiles all the rollups.
• Most of the recurring 1:1s that were really status updates disguised as 1:1s.

When I did this transition at Smartcat, I reclaimed about 6 hours a week of calendar time. I filled it with shipping. Not more meetings.

The build

"But how do I build the page?" It's less than a week of work, most of which is instrumentation you should already have.

• Notion, Linear, a stitched Looker dashboard, or a small Next.js page. Format doesn't matter. Discipline does.
• Connect your eval runner output, your analytics, your signal clustering agent, your cost telemetry, your incident tool.
• Autogenerate a one-paragraph summary at the top, written by an agent that reads the strips every Monday morning. Execs get their narrative without you spending two hours writing it.

If your team can't stand up a v1 of the page in two weeks, that's your discovery exercise. The act of figuring out what goes on the page is the act of figuring out what your team actually cares about, and where your instrumentation is missing.

The pushback you'll get

"But what about people who don't read the page?" They don't get to participate in the decision. That's the new contract. I'm not reading aloud at the meeting. The social pressure this creates is the point. It moves the cost of being uninformed from the team to the individual, which is where it belongs.

"But the exec team wants a written narrative." Give them one. Auto-generated at the top of the page. I write the prompt once, the agent regenerates the paragraph every Monday morning, execs get their narrative without me spending two hours on it.

"But my company's culture won't let me cancel the meeting." Fine, keep the meeting on the calendar. But change its content. Start with "has anyone read the page?" If the answer is yes, the meeting ends in 10 minutes. If the answer is no, the meeting ends in 15 minutes and you schedule a follow-up for after they've read the page. Within a month, everyone reads the page.

Pick one thing this week

Don't try to kill the meeting Monday. Do this instead.

1. Pick one product or surface you own.
2. Build a one-page dashboard for it. 3-5 strips. Rough is fine. It doesn't need to be pretty.
3. Share the URL in the channel where your status meeting happens.
4. On Monday, start the meeting by saying "I'll just walk through the page." Do it. Notice that the meeting ends 15 minutes early.
5. Next week, say "you don't need me to walk through it. Read it, then come with questions." Notice how much faster the meeting is.
6. The third week, suggest that the meeting become "decisions only, optional attendance."

By the fourth week, the meeting is either dead or transformed. Either is a win.

Every status meeting on your calendar is a tax on your team's trust in its own dashboard. Pay the tax once to fix the dashboard. Stop paying it every week forever.