How to Build High‑Performance R&D Teams: Insights from NetEase CTO Yin Jingcheng

First, please introduce yourself and your career experience.

I graduated from Zhejiang University in 2005, worked two years in Japan, and joined NetEase in November 2008, staying for 14 years. I have rotated across multiple internal businesses, from client‑side email applications to PC and mobile game development, and later to ToB SaaS services at NetEase Zhiji.

How would you divide your work experience into stages?

Three stages: (1) pure coder – writing code, designing architecture, refactoring, with limited management; (2) ToB technical leader – responsible for tech stack selection, architecture, delivery quality, team structure, resource negotiation, and cross‑team coordination; (3) business‑oriented leader – balancing technical work with business metrics, product planning, and large‑scale team design.

What challenges did you face when first becoming a manager?

I ran internal management‑training sessions and saw many new managers struggle with the shift from individual contribution to team responsibility, handling emotions, performance feedback, and the temptation to solve problems personally. I recommend setting expectations, treating management as a discipline, improving efficiency with tools like OKR, and communicating openly.

Is upward communication more important than downward communication?

Both are essential; the key is proactive communication. Upward communication aligns resources and goals, while downward communication provides feedback, guidance, and motivation.

How do you allocate your time as a technical leader?

Time allocation depends on the business stage. During rapid growth I focus on core coding, architecture, and tech selection; once the platform stabilises I shift to customer and product communication, delegating technical work to senior architects.

How can a junior engineer decide between a management or architect path?

First master fundamentals, then take ownership of small modules and projects, assess communication and coordination skills, and let the organization recognize leadership potential.

What defines an excellent manager – technical or management ability?

Technical competence is crucial early on; as one rises to senior leadership (CTO, technical director) management capability becomes more important. Effective leaders balance both according to the team’s maturity.

How has technology’s role in business changed in uncertain times?

Growth has slowed; cloud services reduce the need for in‑house infrastructure. Technology teams must now deliver value that cannot be outsourced, think like CEOs—understand industry, customers, competition, cost, and innovation—to drive business success.

How should new technologies be evaluated for adoption?

Assess business stage, team capability, and maturity; start with small‑scale pilots, gather real‑world feedback, and decide on broader rollout based on concrete results.

What makes a high‑efficiency R&D team?

Low‑cost, continuous, fast, high‑quality delivery; control entropy as systems grow, foster self‑observation, learning, and improvement.

How do large and small enterprises differ in R&D efficiency work?

Large firms have dedicated efficiency teams, systematic tools, metrics, and processes; small firms often lack resources and rely on lightweight processes, focusing on getting things done.

What has been your biggest challenge?

Securing resources for efficiency projects and gaining trust; early efforts may show negative short‑term ROI, requiring conviction and evidence to convince leadership.

Is DevOps the same as R&D efficiency?

DevOps is a component of efficiency—one of many tools and practices—but efficiency also includes talent development, training, metrics, and organizational processes.

How should demands be measured fairly?

Avoid metric‑for‑metric evaluation; use result metrics (delivery cycle, defect density) and process metrics (defect resolution rate, lead time) with baselines from industry or historical data.

Advice for companies seeking to improve R&D efficiency?

Do not blindly copy others; assess internal context, focus on systemic improvements, and prioritize people—engage teams, avoid forced metrics, and co‑create solutions.

How to plan a technology team’s annual roadmap?

Three dimensions: align with business outcomes, reduce technical debt and entropy, and build organizational capabilities (skill gaps, structure, culture).