How Ineffective Meetings Are Driving Product Managers Crazy (and What to Do)

Yesterday I sat through five meetings—from requirement reviews to project retrospectives—only to realize that the documents I wrote were the same as last week’s, the problems discussed were the same as last month’s, and progress was almost zero. My "three‑day rollout" plan was stalled in the conference room for three whole weeks.

1. When "communication" turns into "squabbling", who still wants to speak?

Dealing with endless back‑and‑forth is exhausting, not because communication itself is hard—I've organized product communities and negotiated with investors—but because I know I’m wasting time yet forced to play along.

A seemingly simple decision chain gets bloated with seven or eight people, and a clear proposal is twisted by layers of "approval". The worst part is that this squabbling is unrelated to my salary or product success; it serves process compliance or personal control.

Sometimes I think it would be better to skip work entirely and spend evenings coding on GitHub or writing articles, where I can see tangible output.

However, managers need the appearance of "collective decision‑making" to share responsibility and the illusion of democracy.

When communication becomes a passive, forced activity, it loses its original purpose.

2. Plain analysis: why does communication in companies always go sour?

In short, four reasons:

1. "Liability avoidance" outweighs "responsibility" – In startups people focus on getting things done; in large firms many aim to avoid blame. Adding more attendees and minutes creates a paper trail that can be used to deflect responsibility later.

2. "Performance" outweighs "execution" – Some attend meetings just to showcase presence. Speaking up, even with meaningless opinions, is visible, while quietly delivering results is invisible.

3. "Process" outweighs "outcome" – Companies treat the process as the goal: three meetings, five approvals, eight departmental inputs, regardless of whether the process improves the product or serves users.

4. "Power" outweighs "truth" – The final decision often rests with the highest‑ranking person, not the most knowledgeable. Teams stop evaluating ideas on merit and start guessing what the boss wants.

3. From "speaking freely" to "holding back": a product manager's transformation

When I first entered the field I prepared thoroughly for every review, voiced my opinions loudly, and called out problems directly. The result?

"This requirement doesn’t match user habits" → "It’s a directive from leadership".

"The schedule is too tight and will hurt quality" → "The business can’t wait".

"We should start with data analysis" → "No time, just ship it".

Later I learned to be smarter:

Before the meeting, find out who will host, the leader’s attitude, and each participant’s stance.

During the meeting, read the room: if the boss frowns, shift the topic; if a colleague signals, stop speaking.

Start your comment with a disclaimer: "This may be immature, just my shallow view…".

Leave the conclusion open: "This solution works, but only if we have time…".

I shifted from wanting to build a great product to wanting to run meetings well.

4. My "stay clear" guide: doing the right thing in a squabbling environment

Changing the whole environment is hard, but you can avoid being assimilated.

1. Distinguish "mandatory performance" from "worthwhile battles"

A‑type meetings (core battles) : Directly affect product direction, user satisfaction, or key metrics. Give them your full effort.

B‑type meetings (necessary processes) : Routine reports, syncs, reviews. Complete the required actions and move on.

C‑type meetings (pure performance) : No clear goal or decision power, just to let everyone know something. Attend if you can push it out; otherwise listen while continuing your own work.

2. Build a "offline consensus, online formality" mechanism

Never push a major decision in a large meeting. Follow three steps:

Privately discuss with key stakeholders one‑on‑one to reach basic agreement.

Hold a small‑group discussion to resolve major disagreements.

Use the big meeting only as a formal checkpoint to quickly pass the decision.

This respects the process while preserving efficiency.

3. Use user data as your indisputable sword

"In the past week, 23 users reported the same issue."

"A/B testing shows solution B improves conversion by 15%."

"Customer‑service complaints for this problem rose 300%." Data doesn’t lie and is hard to refute.

4. Reserve "creator time" for yourself

Every day I protect a block of deep‑work time:

10 am–12 pm: No messages, no calls, focused work.

Evening: Code, write articles, work on personal projects.

5. Remember: who are you really working for?

Your salary comes from the company, but your career is yours. Every minute wasted in meaningless meetings drains your professional life and creative capacity.

5. Closing: protect your "product heart"

Last week another endless meeting erupted over departmental responsibility. I wrote in my notebook: "Users won’t love us because we clarified responsibilities; they’ll love us because the product works." I decided to cut meeting time by 50 % and double the time spent talking to real users.

Talk to one real user daily.

Analyze a complete user journey weekly.

Do an in‑depth competitor experience each month.

When I understand users better, my proposals become more persuasive, and the number of required meetings drops.

Instead of guessing what the boss wants in a conference room, go to the users for answers. After all, we are product managers first, and only then employees.

Protect the part of you that wants to build great products—that’s the final fortress against workplace squabbling.