Leveraging Leverage Points to Boost Team Performance and Core Employee Capability

The Youzan technology team has grown to about a thousand engineers, leading to challenges such as rapid onboarding, declining internal collaboration efficiency, and the need to build a high‑performance technical team.

The speaker emphasizes three fundamental principles that appear in classic management books (e.g., "The First Lesson for Managers" by Andy Grove, "Management Achieves Life", and "The Practice of Management"):

1. Flow Value – an individual’s value changes over time (e.g., after one month, three months, one year). Early-stage employees contribute low value (coding), which rises as they move to testing and beyond.

2. Hole Theory – think of a process as a black box; by creating well‑designed KPI “holes” you can control output quality even as the team scales.

3. Management Leverage Points – identify a small set of actions that have outsized impact on the whole organization. For a 1,000‑person team, the leverage point is improving the capabilities of the core 50 employees through training, mentorship, or replacement.

The speaker describes how the team’s previous leverage point was process and efficiency during a rapid growth phase (from 300 to 1,000 engineers). Establishing a performance‑improvement (PMO‑like) team early, once the organization reaches ~200 people, helps increase work transparency and quantifiable metrics. By tracking the proportion of work that can be traced and measured, the team raised this ratio from about 10% to 40% within six months.

When the engineering collaboration scope exceeds 300 people, a dedicated technical support team becomes essential to reduce interruptions, improve bug‑fix turnaround (from ~30% to >90% same‑day resolution), and maintain high‑quality delivery.

The talk also covers horizontal committees (quality, recruitment, etc.) that delegate authority, reduce bottlenecks, and align incentives. Delegating fault‑approval to test leads, for example, cut release‑related failures dramatically.

Finally, the speaker stresses the distinct roles of architects (future‑oriented) and technical leaders (current‑oriented) in large‑scale teams, and encourages early open‑source contributions to build influence and attract talent.