Purpose

First, we need to clarify why we’re doing this. What value does it create, and what outcomes do we expect? The “everyone” here includes three parties: the company, the team, and the individual. Each has different expectations from tech learning and sharing. Here are the key purposes:

• Learn new technologies, improve ourselves, and build a knowledge system
• Build experience in professional domains
• Improve communication and presentation skills
• Use learning and analysis to advance product architecture, performance, and tooling
• Accumulate technical materials and form long-term company value

How to Start

Once the purpose is clear, we need to think about how to make it happen. Adult learning and training are hard to push forward. Heavy delivery workload, human inertia, and whether leaders truly support it are all common blockers, which is why many teams give up halfway. To avoid these pitfalls:

• Align management: tech learning and sharing is long-term work, and impact should be evaluated over time
• Ensure content quality: content cannot be too shallow
• Define a clear cadence and responsibilities for both speakers and audiences
• Choose topics based on the audience, focusing on what they care about

How to Do It

1. Sharing Members

Reduce the responsibility denominator. In a 12-person team, the denominator is 12, and people tend to think “it’s not just me,” so they don’t take initiative. Make it small groups instead, with a denominator of 2 or 3. Groups tend to be more reliable than pure self-drive.

Our current R&D team has three roles:

• RD: 4
• FE: 5
• QA: 3

We form three groups and rotate tech learning and sharing in sequence. A group can have multiple speakers per session or just one.

2. Decide the Cadence

The cadence must be explicit so both speakers and listeners can prepare.

Sharing Time Rules

• Frequency: once every 2 weeks (groups rotate)
• Time: Thursday at 19:15
• Duration: within 60 minutes

Speaker Preparation

• Share the outline: one week in advance (by the previous Thursday)

Audience Preparation

• Read the materials: within the week before the session. Studies show that if you don’t pre-read, you may only understand about 20% during the session. Don’t waste your time—read beforehand.

3. Content Selection

The goal of learning and sharing is to raise the team’s technical level and expand its cognitive range. We suggest two types of content: technical topic sharing and free-theme sharing.

How to Choose Content

Selection should vary by team context and product architecture. Plan quarterly, learn the team’s management and technical weaknesses, what people want to improve, and what the product needs next. Then choose topics accordingly (we currently use Lagou Education for training).

Technical Topic Sharing

• Targeted improvement in a specific technical area
• Quickly applicable to current architecture and product
• Often needs a shallow-to-deep progression

Free-Theme Sharing

• Broaden perspective
• Content can be wider, even inviting non-technical colleagues
• Requires strong logical expression to explain unfamiliar topics clearly

Alternate between technical topics and free themes.

Reject Simple

If you want the content and format to be great, you need great content. We reject overly simple topics like “how to install X” or “getting started with Y.”

4. Team Atmosphere

Tech learning and sharing improves team culture, strengthens mutual understanding, and increases cohesion.

Provide drinks and snacks, create a relaxed atmosphere, and people will be more willing to join. Initiative improves naturally.

Summary

Beyond learning and sharing, we should also practice gratitude.

Thanks to the company for providing the platform; thanks to the speakers for preparing on their own time; thanks to the audience for listening carefully and asking questions.

With a grateful heart, you’ll see better things and reach new heights by thinking from others’ perspectives.