huawei-6p-launch

name	huawei-6p-launch
description	Use when creating Huawei-terminal-inspired 6P collaborative launch strategies, overseas product launch plans, GTM war rooms, launch PPT outlines, or commercialization playbooks covering GTM, Marketing, Retail, Channel, Service, and Ecosystem.

Huawei 6P Launch

Overview

Use this skill to turn a product launch request into a Huawei-terminal-inspired 6P operating plan. Treat 6P as a project operating system, not a marketing slogan: GTM is the command tower, and Marketing, Retail, Channel, Service, and Ecosystem run as synchronized workstreams.

Boundary: do not claim "GTM, Marketing, Retail, Channel, Service, Ecosystem" is a formally published Huawei official 6P definition unless the user provides a source. Frame it as a launch methodology adapted from the user's six pillars and public Huawei-style IPD/IPMS/GTM/ROADS thinking.

Workflow

1. Separate facts from assumptions.

   • Identify verified product facts, market facts, and regulatory facts.
   • Mark launch country, price, certification, channel, and timing details as assumptions unless sourced.
   • For current market, policy, pricing, competitor, or product facts, verify with live sources.

2. Build the launch charter first.

   • Product: positioning, target users, core value proposition, proof points.
   • Market: country priority, launch sequence, city pilots, regulatory gating.
   • Business: price corridor, version ladder, volume, margin, budget, ROI.
   • Operating model: GR gates, launch war room, KPI dashboard, escalation path.

3. Design the 6P system.

   • For a full strategy, read references/6p-operating-system.md.
   • For required outputs, read references/deliverables.md.
   • For day-level GTM planning, read references/day-level-launch-plan.md.
   • For Europe, Southeast Asia, Middle East, or multi-region launches, read references/market-adaptation.md.

4. Make GTM the integrator.

   • GTM owns launch goals, GR gates, day-level countdown, pricing, lifecycle moves, and cross-functional arbitration.
   • GTM countdown milestones must be managed in Excel when the user asks for detailed execution, war-room follow-up, or launch readiness tracking. Use assets/gtm-6p-milestone-tracker.xlsx as the baseline template.
   • Each other P must produce concrete launch deliverables, not just recommendations.

5. Add data-backed competitive attack logic for every P.

   • Each P must have data arguments, country/region same-price-segment stock or market size, competitor insight, and parameter-level attack points.
   • Parameter attacks must compare concrete specs or measurable proof, then translate the gap into sales, marketing, retail, service, or ecosystem talking points.

6. Create the 6P flywheel.

   • GTM sets direction -> Marketing creates demand -> Retail converts experience -> Channel secures supply -> Service builds trust -> Ecosystem increases retention -> VOC/data flows back into GTM and IPD.

7. Verify the output.

   • Every market has a differentiated 6P focus.
   • Every P has owner, deliverables, KPI, timeline, and risks.
   • Every P has data thesis, same-price-segment stock or market size, competitor insight, and parameter-level attack points.
   • GTM includes lifecycle coverage: launch, hot sale, promotion, run-out, retirement, iteration.
   • Launch readiness includes weekly 6P milestone review and three pre-launch PPT/report rounds from every P, so the whole organization uses one consistent story and evidence base.
   • Claims are either sourced facts or clearly labeled assumptions.

Output Contract

For a complete launch strategy, include:

• Executive thesis and launch logic.
• Product and market fact base with evidence boundary.
• 6P strategy, one section per P.
• Regional adaptation for target markets.
• 6P flywheel and war-room governance.
• SWOT and risk response table.
• GTM day-level reverse plan and Excel milestone tracker with 6P swimlanes.
• Same-segment competitor benchmarking and parameter-by-parameter attack table.
• Deliverables checklist and next 30-day action plan.

For a PPT, prefer 50+ pages for full-market strategies and keep each slide action-oriented: one decision, one framework, one table, or one execution artifact per slide.