When Product Managers and Developers Clash: Lessons from a Real‑World Office Fight

Product and technology teams often act like a pair of happy enemies; when they are not in the same team, conflicts arise easily, especially on hot days. Recently, a product manager and an app developer at China Ping An reportedly got into a physical fight in the office after a request that the app’s theme color change with the user’s phone case color.

The two were eventually fired by the company.

Students discussed the incident, sharing screenshots and memes that illustrated the absurdity of the demand.

Despite the chaos, the technical team already had a solution, which they later shared as a series of images.

Beyond this specific incident, similar clashes between product managers and developers happen frequently. Common reasons include unclear requirements, misinterpretation of needs, flawed requirements, and unreasonable deadlines.

To avoid such conflicts, a product manager should understand user habits, requirement mining, product positioning, visual design, and development processes. Developers, on the other hand, should recognize the technical boundaries and communicate effectively, proposing alternative solutions when faced with unreasonable requests.

Key advice for developers includes:

Analyze why the product manager wants the feature and what problem it solves.

Consider alternative implementations that stay within technical limits.

Communicate your thought process clearly to the product manager.

Use conflicts as growth opportunities to develop product sense.

Remember that many workplace disagreements stem from relational issues, not just technical ones.

By approaching unreasonable demands with a problem‑solving mindset and clear communication, developers can turn potential fights into learning experiences and improve overall product development efficiency.

21CTO compiled this from various programmer media sources.