Why Team Culture Can’t Be Copied: Lessons from Building a Product Engineer Team

Recent low morale in the company prompted a push for a "wolf‑like" culture, while the author admired Alibaba’s "customer first" principle and wondered if a proactive, excellence‑seeking culture could work.

The author argues that team culture cannot be copied or learned superficially; it must become a lived habit.

In 2013 the author left a six‑year foreign‑enterprise job to join UC, facing the biggest challenge of forming a team. The difficulty was not recruiting but "surviving" in a new environment.

The new team consisted of members without mobile‑internet backgrounds, making product development especially hard.

There was no one to translate customer requirements; the author became the system analyst.

No one took responsibility for the final outcome; the author was the first accountable person when issues arose.

Feedback became immediate; performance could be judged the next day by data.

Realising the old ways would lead to failure, the author forced a shift in habits, establishing several agreements:

Use the product you develop yourself (e.g., purchase through the group‑buy navigation app).

Learn basic product metrics (PV, UV, conversion, retention) and review them daily.

Adopt a "empty‑cup" mindset, turning criticism into motivation.

These principles were later distilled into three concise slogans:

Product Awareness: Be the angel user of your own product

Data‑Driven: Let data guide strategy decisions

Daily Reflection: Advance through continuous introspection

As the team grew with members from various backgrounds (BAT, etc.), cultural clashes emerged, highlighting the need for a unified set of values.

Two quotes from "Zhi Xing: The Management Path of Technologists" emphasize that culture originates from leaders and must reflect their qualities, acting as both a filter and a furnace for the team.

The author coined the term "Product Engineer" to capture the desired culture, defining it with five traits: focus on product, face users directly, data awareness, technical innovation, and embracing change.

Later, the author notes that merely promoting user‑centric or data‑aware slogans without personal embodiment leads to empty slogans.

A team’s cultural values mainly come from its leader; the team mirrors the leader’s style and values. — Liu Jianguo, "Zhi Xing: The Management Path of Technologists", p.157

The article concludes with practical questions to help readers extract their own team culture and invites further discussion on implementing the "Product Engineer" mindset.

Today’s article ends with a hope to be helpful.