# The weekly eCom management meeting structure that actually works
Most weekly meetings are status updates wearing the clothes of a management meeting. Someone reads numbers from a dashboard. Someone else says "yeah, that was a tough week." A few action items get assigned that no one will follow up on. The meeting ends and nothing is clearer than when it started.
The weekly eCom management meeting we run across 143+ client engagements is built differently. It is a diagnostic. The goal is not to report what happened. It is to find out why, and decide what changes.
The structure
The meeting opens with two minutes of silence. The KPI dashboard is shared, everyone reads it independently, no one talks. This sounds trivial. It is not. Without the silent pre-read, whoever speaks first sets the agenda. With it, the data sets the agenda.
Then we go through four KPIs in this order, and the order matters:
- Sessions
- Conversion rate
- ACOS
- Operating margin
Sessions come first because they are the top of the funnel. If sessions dropped, everything downstream is already compromised. If sessions held but conversion dropped, you have a listing or pricing problem. If sessions and conversion held but ACOS climbed, your ad efficiency degraded. If all three held but operating margin slipped, you have a cost problem, often a COGS or fulfillment fee issue you have not found yet.
The order creates a natural diagnostic sequence. Start at the top of the funnel, work down. Find the leak before prescribing fixes.
Departmental updates: flagged issues only
After KPIs, each department gives an update. The rule is flagged issues only. Not recaps. Not "things are looking good." If there is nothing to flag, say nothing. If there is something to flag, state what it is, what you think caused it, and what you are doing about it.
This rule cuts average meeting time by about 20 minutes. It also forces people to think before speaking. You cannot arrive at a flagged-issues-only meeting and just narrate what happened.
The root cause session
When a number is off, we do not move on. We run a root cause session. The discipline that made the biggest difference came from a June 2024 meeting where operating profit had dropped. The team's first instinct was to call it an ad spend problem. When we decomposed it properly, 40% of the decline came from out-of-stocks and 60% from cut ad spend. Those require completely different responses. Blaming ad spend and adjusting bids would have fixed 60% of the problem while leaving the 40% to compound into rank damage.
The rule now: any KPI that moves more than 10% week-over-week requires attribution to at least two specific causes before the meeting moves to solutions. You cannot discuss the fix until you know what broke.
The 20.5% OOS trigger
In October 2023, bestseller out-of-stock percentage came in at 20.5%. That number changed how we handle inventory flags in the meeting.
Before that reading, inventory was part of the general KPI review. After it, bestseller OOS got its own standing agenda slot with a hard threshold. Any reading above 10% triggers a same-day restock analysis. Any reading above 20% escalates to leadership and a review of all in-transit POs and transfer options. The 20.5% reading that week launched the urgency that drove the Flieber onboarding. It took six more weeks to recover inventory, and the cost in lost BSR rank was real. That threshold now lives in the meeting template permanently.
Why meetings degenerate into status updates
Three things cause it. People arrive without having reviewed the dashboard. KPIs are reported in no particular order with no diagnostic logic connecting them. And "things to fix" replaces "what caused this."
Status updates feel productive. Numbers get read aloud. People nod. But decisions do not get made and problems do not get found until they are large enough to be unavoidable.
The fix is structural. A silent pre-read forces everyone to engage with the data before the conversation starts. A fixed KPI sequence builds a diagnostic habit. A root cause requirement before solutions prevents the team from treating symptoms. None of this requires a better team. It requires a better meeting design.
The next seven days
Every meeting ends the same way: what changes in the next seven days, who owns it, and what does done look like. Not "let us look into the sessions drop." Something like: Petros reviews the top five non-converting keywords by Thursday and cuts anything with more than 30 clicks and zero conversions. Specific enough that next week's meeting can open with a yes or a no.
A well-run diagnostic meeting with no clear owners at the end is still a status update.
