From Ops Engineer to Product Manager: My 6‑Month Journey and Lessons Learned

1. Starting Point

After joining Tencent as an operations engineer for the HandQ product, the author began interacting with product managers during resource‑demand incidents, which sparked interest in product work.

1.1 Basic Concepts

What is a product?

What does a product manager do?

What is the value of a B2B product manager?

What are the responsibilities of a product manager?

What abilities are required?

What roles compose a product team?

1.2 What Is a Product?

A product is anything that can be offered to the market, used and consumed to satisfy a need, ranging from tangible goods to services, ideas, or combinations thereof.

1.3 What Is a Product Manager?

In the IT/Internet industry, a product manager is responsible for product planning, design, and lifecycle management, focusing on value, usability, and feasibility.

Entry barriers are low, but mastering product thinking, execution ability, and industry sense is challenging.

Product managers often act as “potential CEOs” while also shouldering all blame.

1.4 Value of a B2B Product Manager

The core value is to design (or evolve) the right product that meets user needs and directly or indirectly generates revenue for the company.

1.5 Product Manager Work Content

Market Research & Analysis

Assess market size, growth potential, competitors, customer segments, and their needs.

Product Planning

Define product positioning, target user groups, and scenarios, often visualized in a feature map.

Product Design

Create high‑fidelity prototypes that convey the product’s experience and functional structure.

Requirement Documentation

Combine prototypes with detailed PRDs (e.g., in TAPD) for developers.

Implementation

Collaborate closely with developers to deliver and launch features.

Product Acceptance

Validate that business logic aligns with the design; quality is ensured jointly with testing.

User Manuals & Scenario Videos

Provide documentation and short videos to aid user adoption.

Iterative Optimization

Collect user feedback, identify improvement points, and iterate the product.

1.6 Required Abilities

Tool Proficiency

Axure RP (prototyping)

Xmind (mind‑mapping)

Visio (process diagrams)

Thinking Skills

Abstract thinking

Structured logical reasoning

Communication

Explain user stories clearly

Write understandable documentation

Design & Interaction Awareness

Avoid anti‑user interactions

Improve layout aesthetics

Technical Understanding

Enough technical background to converse effectively with developers.

Industry Knowledge

Understanding of the specific domain (e.g., operations platforms).

Data Analysis

Identify metrics needed for iteration.

Project Management

Core abilities: thinking, communication, industry knowledge; other skills are foundational.

1.7 Product Team Roles

Product Manager

Designer (visual & interaction)

Technical (frontend, backend, testing, pre‑sale, post‑sale)

Operations

Marketing

Business

Project Manager (PM)

2. On the Road

2.1 Elementary Stage – Finding an Entry Path

Strengths : deep operations knowledge, experience with system rollout, familiarity with development, project management basics.

Weaknesses : no full 0‑to‑1 product experience, lack of prototyping, PRD writing, and competitive analysis skills.

Focus : practice Axure, study foreign products, read methodology books, start simple competitor analysis, and dissect business logic before implementation.

2.2 Middle Stage – Hands‑On & Familiarization

Learn the full 0‑to‑1 product flow, conduct deeper competitor analysis (onion method), apply the 80/20 principle, identify real user needs, prioritize features, and refine business logic and interaction.

2.3 Advanced Stage – Global Vision & Product‑Line Planning

Master MVP principles, balance scope vs. resources, plan version roadmaps, ensure logical consistency across releases, and manage the product lifecycle (usability, feasibility, value, operation, market feedback).

3. Requirement Pool Management

3.1 Sources of Requirements

Leadership‑driven requests

Customer feedback (filtered for real needs)

Core product‑line initiatives

Sales‑driven “sign‑off” features

Partner‑suggested items

3.2 Requirement Management Methods

Adopt the “Pram Principle” and use a structured template that captures company priority, stakeholder role, and sales confidence to evaluate and prioritize requirements.

4. Self‑Cultivation of a Product Manager

4.1 Cultivation Principles

Read widely (industry, competitors)

Listen to first‑hand customer voices

Think about user stories, product value, and roadmap

Speak with peers

Experiment within tolerable risk

Reset thinking to avoid fixed mindsets

4.2 Common Pitfalls

Over‑optimism and perfect‑ism that users don’t need

Neglecting logical consistency before implementation

Being overly stubborn without external feedback

Building overly comprehensive features instead of MVP

Focusing too much on minor details early on

5. Let’s Practice B2B Together

5.1 Characteristics of B2B Products

Solve concrete work problems and systematize processes

Users have professional backgrounds and receive training

Low tolerance for errors; high cost of failure

High quality expectations; need one‑stop solutions

Functionality outweighs visual polish in early stages

5.2 B2B Design Thinking

Complex business logic and scenario granularity

Horizontal breadth first, then vertical depth

Prioritize functionality and reliability over UI aesthetics

Design for multiple roles (front‑line, middle, senior)

Fine‑grained permission control

Manage user expectations and reduce operation cost

5.3 Pitfalls in B2B Design

Over‑investing in UI polish at the expense of core workflow

Unclear business logic leading to incomplete feature loops

6. Summary

Becoming an excellent product manager requires continuous curiosity, systematic learning, and practical experience; seeing a product evolve from nothing to user‑approved success brings great fulfillment.

Book List

"Outstanding Product Manager" – practical methods

"Everyone Is a Product Manager" – actionable guidance

"Don't Make Me Think" – fundamentals of interaction design

"The Revelation: Building Products Users Love" – comprehensive methodology and team building