How Huawei Crafts Hit Products: An In‑Depth Walkthrough of the Full IPD Development Process

Overview of Huawei IPD

Huawei’s Integrated Product Development (IPD) is a market‑driven, investment‑focused product development framework that uses a six‑stage closed‑loop process to raise success rates and efficiency. The core idea is to treat product development as an investment, align it with strategic goals, and manage risk through structured stage‑gate reviews.

Six IPD Phases

Concept Phase : Capture customer needs, verify strategic fit, produce a Product Requirement Specification (PRS), evaluate business attractiveness, and create a business plan.

Plan Phase : Validate concept assumptions, decompose requirements, allocate resources, define performance commitments, and establish early procurement plans for long‑lead items.

Development Phase : Perform detailed design, module verification, system integration, and develop manufacturing processes in parallel.

Verification Phase : Conduct hardware/software unit tests (BBFV/BBIT), technical reviews (TR4‑TR6), system validation, integration testing, and beta testing; ensure the product meets all requirements before release.

Release Phase : Verify manufacturing readiness, finalize market launch plans, position and price the product, execute branding and promotion, collect early customer feedback, and ramp up production to meet performance, cost, and reliability targets.

Lifecycle Phase : Manage the product from stable production to end‑of‑life, perform B‑ or C‑type changes, monitor performance, and make termination decisions.

Core Highlights of the Process

Emphasis on cross‑department collaboration (Product Development Team – PDT).

Full‑process risk management and continuous optimization based on customer value.

Stage‑gate decisions act as “rapid cooling” points that enforce Go/No‑Go choices, preventing scope creep and uncontrolled changes.

Handling Strong Stakeholders with IPD

Strong stakeholders (dominant customers, senior leaders, or opinionated team members) can disrupt the disciplined IPD flow. The article analyses their behavior patterns and proposes a four‑step mitigation method:

Process Trigger – Emotional Isolation : When pressure arises, immediately invoke the IPD issue‑handling workflow, pause irrational dialogue, and route the request to the Change Control Board (CCB) for formal evaluation.

Rhythm Control – Use IPD Buffers : Leverage scheduled TR reviews and Decision‑Control Points (DCP) as natural buffers, responding with “We will assess this in the next TR4 meeting on [date]”.

Boundary Setting – Anchor to IPD Baselines : Cite approved baselines (e.g., signed Scope Document) and quantify impact (e.g., “Delay of 2 weeks, cost increase of ¥5 M”). Reject out‑of‑baseline requests unless a formal change is submitted.

Capability Building – Data‑Driven Authority : Present data‑backed impact analyses (e.g., “Current schedule will slip 15 %”) to reinforce decisions, and continuously showcase successful stage‑gate outcomes to strengthen team credibility.

Case Study: 2023 MTO New‑Product Launch

In March 2023 a project manager faced three challenges: lack of dedicated hardware resources, rigid tooling and certification timelines (30‑35 days for molding, 75 days for certification), and frequent requirement changes (4‑5 revisions). By applying IPD:

Requirement Management : Established a consensus workshop with market, R&D, ID, and supply‑chain teams; froze requirements after design sign‑off, reducing change count from 5 to 2.

Cross‑Functional Team (IPT) : Integrated hardware, supply‑chain, quality, and marketing roles; weekly sync meetings allowed hardware engineers to borrow R&D capacity and suppliers to pre‑qualify components, eliminating post‑design part shortages.

Critical‑Path Control : Back‑calculated the latest finish dates – mold completion by May 15 and certification by June 20 to meet a July end launch, adding a 20 % time reserve and a backup mold vendor. Actual mold delay was only 2 days; certification finished on schedule.

Supply‑Chain Collaboration : Early involvement of suppliers locked core components, enabling a production ramp of 30,000 units in the first three months.

Change Management : All change requests required impact analysis reports; only approved changes proceeded, keeping the critical path intact.

Result: Launch delayed only to September 12 instead of the original July end, and the product shipped 30,000 units in the first month, meeting market demand.

Why IPD Is Gaining Traction

Accelerating market cycles and shorter product lifespans demand parallel engineering; IPD’s concurrent development cuts time‑to‑market by 30‑50 %.

Increasing technical complexity (AI, 5G, IoT) requires cross‑functional coordination; IPD’s Integrated Product Team (IPT) breaks silos.

Shift from product‑centric to customer‑centric value delivery; IPD’s demand‑to‑spec loop ensures alignment.

Successful benchmarks: Huawei reports >30 % R&D cost savings and a 20 % rise in new‑product success rate after IPD adoption.

Digital tools (ERP, PLM, low‑code platforms) automate IPD gates, making the methodology scalable.

Organizational Framework & Common Pitfalls

IPD relies on four core teams (IPMT, PDT, LMT, and supporting functions). Common mistakes include overlapping responsibilities, skipping technical development reviews (TDT), and neglecting lifecycle management (LMT). The article outlines how to avoid these errors by clearly separating strategic (IRB) and execution (IPMT) roles, enforcing technical reviews, and maintaining a post‑launch feedback loop.

Conclusion

IPD transforms product innovation from an art‑based, hero‑driven effort into a scientific, data‑backed process. By embedding market focus, structured stage‑gate controls, and cross‑functional collaboration, organizations can consistently deliver high‑quality, market‑aligned products while turning stakeholder pressure into leadership strength.