Five Key Stages to Improve Tech Talk Event Operations

As the main operator of the internal technical sharing platform Techtalk, I have been responsible for its operation for almost half a year. During this period we have optimized both the effectiveness of the events and the efficiency of the operation.

Currently Techtalk runs stably: a session is organized every two weeks, and the efficiency and impact have increased severalfold compared with the early stage. Below are the five key stages we went through to improve the process.

01. Launch an MVP to get the activity running

In the first version we kept the workflow simple: find speakers, create promotional posters, announce in DingTalk groups, collect registrations, book a meeting room for on‑site sharing and live streaming. This allowed us to run the first two sessions quickly.

02. Establish a standard SOP to boost organization efficiency

We standardized every step of the event, created an operation manual, and templated repetitive tasks such as poster design (reducing creation time from 0.5 day to 0.5 hour). This prevented simple mistakes (e.g., microphone battery dead) and allowed the process to be executed almost automatically.

We also introduced a “technical partner” mechanism, letting senior engineers help with promotion and organization.

At this stage we faced a new challenge: ensuring speaker content quality and presentation effectiveness. Some sessions performed poorly because speakers were unprepared and the on‑site format was monotonous.

03. Build a speaker quality control mechanism

We invited the training department to review content, created a unified PPT template, and produced a speaker training document. Most importantly, we scheduled at least one rehearsal for every speaker.

To motivate speakers we offered Hello (哈啰) branded gifts, shared photo collections and activity data after each session, and awarded points to help them become star speakers.

We also improved the host’s facilitation skills, added warm‑up music, a lottery for the public account, and a more interactive Q&A segment.

04. Introduce a comprehensive feedback mechanism for continuous improvement

We adopted the Kirkpatrick Four‑Level model (reaction, learning, behavior, results) and designed questionnaires based on it. We also collected offline feedback from speakers.

05. Increase participation and improve user experience

We held a co‑creation workshop with Techtalk users and identified several optimization suggestions:

Adjust the frequency: weekly sessions are too demanding for developers during test weeks and cause fatigue.

Simplify registration: replace the cumbersome questionnaire with DingTalk’s internal one‑click sign‑up.

Target potential user groups more precisely (e.g., business‑mid‑platform, tech‑mid‑platform).

Enhance promotion: send reminders one week, three days, and one day before the event, and craft compelling titles and copy to create scarcity.

These steps, along with many smaller tweaks, have significantly improved Techtalk’s operation.

Key takeaways for broader product and project work:

Treat SOPs as double‑edged swords: they boost efficiency but can hinder continuous improvement if followed blindly.

Iterate constantly; small, fast improvements lead to better solutions.

Take responsibility for outcomes, not just completing tasks.

Become a T‑shaped professional: acquire complementary skills such as design, coaching, copywriting, and event support.