How One Simple Table Can Slash Meeting Waste by 80%

"This demand is simple, I don't care how you implement it, launch tomorrow!" – "We can't do this unless you add two more developers!" A classic demand‑review meeting often starts with the boss and engineers passing the buck and ends with the product manager taking the blame.

I'm a product manager who fills potholes in e‑commerce systems by day and relaxes in games by night. Today I’ll show how to use one table to reduce nonsense by 80% and compress an eight‑hour review into eight minutes.

Death Case: A Meeting That Could Have Bought a Tesla

A 3C home‑appliance company once held a demand‑review from 10 am to 8 pm with 12 participants (including boss, engineers, operations, design) and the final decision was “discuss next time.”

Cost Calculation

Labor cost: 12 people × 10 hours × ¥100/hour = ¥12,000

Opportunity cost: delayed launch caused promotion loss ≈ ¥200,000

Psychological loss: product manager submitted a resignation overnight (priceless)

Retrospective Conclusion

80% of meeting time is wasted explaining *why* a demand exists, not *how* to implement it.

Counter‑Intuitive Methodology: Use E‑Commerce Thinking to Beat Inefficient Meetings

1. Tag Demands with an "Evil Index"

Borrow the tiered approach of e‑commerce promotions and label each demand. The higher the rating, the more scrutiny it receives.

Case Practice

A boss asked to add an AR try‑on feature on the order page. I tagged it ★★★★☆ (core process change) and proposed alternatives:

Low‑Cost Substitute : Add a "buyer‑show video collection" on the product detail page.

Data Support : AR development needs 3 months/¥500k, video collection needs 1 week/¥50k, with comparable conversion uplift.

Result : The boss accepted and praised my cost awareness.

Tag Usage

2. Tame Engineers with Promotion‑Style Pitch

Treat engineers as "hard‑to‑please suppliers" and use procurement‑style language:

Essence

Use data to hostage‑hijack the discussion instead of emotions, prompting engineers to voluntarily cut the demand.

3. Replace Axure Flowcharts with a Decision‑Tree Table

If a demand is delayed, who takes the blame? Use a table to clarify responsibility ownership.

Additional Tools

1. "Demand Review Madness" Template

When a meeting stalls, throw out lines like:

"This demand is like a Pinduoduo cut‑the‑price deal – it looks only 0.01% off, but you need 100 people to pull it off."

"If we must do it, I suggest we procure fast‑acting heart‑rescue pills, with the tech team getting priority."

"Boss, if this demand launches and fails, I’ll livestream myself swallowing a keyboard – of course, drawn in Axure."

2. Time‑Assassin Toolbox

Physical Hack : Search Taobao for a "countdown bell" and set each speaker to ≤3 minutes.

Digital Monitoring : Display real‑time "meeting cost" (participants × duration × hourly wage) on the conference room screen.

Biochemical Weapon : Serve a strong‑smelling snack 30 minutes before the meeting so everyone wants a quick finish.