Back to Details

pm-gap-analysis

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Gap Analysis (Pragmatic Framework: whole-framework self-assessment)

差距分析（Pragmatic Framework：全框架自我评估）

Best done with a small cross-functional group (product management, product marketing, sales, development, executives). It scores every activity in the framework so the team can agree where to invest. See the full 37-box list in 
../pm-copilot/references/framework.md
.
最好由一个小型跨职能小组（产品管理、产品营销、销售、开发、高管层）共同完成。它会为框架中的每项活动评分，让团队能够就应在何处投入达成一致。完整的 37 个方框列表见 
../pm-copilot/references/framework.md
。

The scale

评分标准

  • Importance — how important is this activity to the company? 0 (low) – 5 (high).
  • Assessment — how well are you performing it today? 0 (not doing) – 5 (high).
  • Gap = Importance − Assessment. The largest positive gaps are where you're under-performing on things that matter most.
  • Also estimate Target Hrs/Wk vs Actual Hrs/Wk per activity; divide total hours by 40 to sanity-check how many people are needed.
Owner role abbreviations: PM (Product Manager), PMM (Product Marketing Manager), MC (Marketing Communications), SE (Sales Engineer), Dev (Development), Exec (Executive), PgM (Program Manager), PjM (Project Manager), PO (Product Owner), TPM (Technical PM), Other.
  • 重要性——这项活动对公司有多重要？0（低）– 5（高）。
  • 评估得分——团队目前执行得怎么样？0（未开展）– 5（高）。
  • 差距 = 重要性 − 评估得分。 最大的正差距，正是团队在最重要事项上表现不足的地方。
  • 此外，还要估算每项活动的目标 Hrs/Wk与实际 Hrs/Wk；将总工时除以 40，以合理校验需要的人员数量。
**负责人角色缩写：**PM（产品经理）、PMM（产品营销经理）、MC（营销传播）、SE（销售工程师）、Dev（开发）、Exec（高管）、PgM（项目群经理）、PjM（项目经理）、PO（产品负责人）、TPM（技术产品经理）、Other（其他）。

Method

方法

  1. For each of the 7 columns' activities, agree the Current Owner and discuss the Proposed Owner.
  2. Score Importance (0–5) and Assessment (0–5); compute the Gap.
  3. Triage: pick the top 2–3 gaps to focus on over the next few quarters. If more than three tie, the group chooses the three most important.
  4. Fix the strategic (left) side first. If Market Problems has a large gap, fix it first — it improves everything downstream.
  5. Build an action plan for the top gaps (barriers, how to close, owner).
  6. Redo the Gap Analysis in 6–9 months to measure improvement and find the next gaps.
  1. 针对 7 个栏目中的各项活动，确定当前负责人（Current Owner），并讨论建议负责人（Proposed Owner）。
  2. 给出重要性（0–5）和评估得分（0–5）；计算差距。
  3. 筛选重点：选出未来几个季度需要重点关注的前 2–3 个差距。如果超过三个差距并列，由小组选出其中最重要的三个。
  4. **优先修复战略端（左侧）。**如果 Market Problems 存在较大差距，应先修复它，因为这会改善所有下游环节。
  5. 为最重要的差距制定行动计划（障碍、如何弥合、负责人）。
  6. 6–9 个月后重新进行差距分析，衡量改进效果并找出下一批差距。

Interview the user for inputs (batch questions)

向用户询问输入信息（批量提问）

  1. What's the scope — a product, portfolio, or business unit? (Startups: whole org.)
  2. Who's in the assessment group (which functions)?
  3. Walk column by column: for each activity, Importance (0–5) and Assessment (0–5), current owner, and rough hours. (Offer to go column-by-column so it's not overwhelming.)
  1. 评估范围是什么——是一个产品、产品组合，还是业务单元？（初创公司：整个组织。）
  2. 评估小组由哪些人员组成（涉及哪些职能）？
  3. 按栏目逐一推进：对每项活动，填写重要性（0–5）和评估得分（0–5）、当前负责人及大致工时。（可建议按栏目逐一推进，以免问题过多造成负担。）

Artifact templates

交付物模板

Gap Analysis

差距分析

markdown
undefined
markdown
undefined

Pragmatic Framework Gap Analysis — <scope>

Pragmatic Framework Gap Analysis — <scope>

Company: <company> · Scope / Product: <product, portfolio, or BU> Author: <author> · Assessed by: <names/functions> · Date created: <date> Scale: Importance 0–5 · Assessment 0–5 (0 = not doing) · Gap = Importance − Assessment
Company: <company> · Scope / Product: <product, portfolio, or BU> Author: <author> · Assessed by: <names/functions> · Date created: <date> Scale: Importance 0–5 · Assessment 0–5 (0 = not doing) · Gap = Importance − Assessment

MARKET

MARKET

ActivityCurrent OwnerProposed OwnerImportanceAssessmentGapTarget Hrs/WkActual Hrs/Wk
Market Problems
Win/Loss Analysis
Distinctive Competencies
Competitive Landscape
Asset Assessment
<!-- Repeat a table for FOCUS, BUSINESS, PLANNING, PROGRAMS, ENABLEMENT, SUPPORT using the activity lists in references/framework.md -->
Total hours/week: <sum> → People needed (÷40): <n>
undefined
ActivityCurrent OwnerProposed OwnerImportanceAssessmentGapTarget Hrs/WkActual Hrs/Wk
Market Problems
Win/Loss Analysis
Distinctive Competencies
Competitive Landscape
Asset Assessment
<!-- Repeat a table for FOCUS, BUSINESS, PLANNING, PROGRAMS, ENABLEMENT, SUPPORT using the activity lists in references/framework.md -->
Total hours/week: <sum> → People needed (÷40): <n>
undefined

Top-3 Gaps Action Plan

前三大差距行动计划

markdown
undefined
markdown
undefined

Action Plan — Top Gaps

Action Plan — Top Gaps

RankActivityGapBarrierHow we'll close itOwnerBy when
1
2
3
Re-assess on: <date + 6–9 months>
undefined
RankActivityGapBarrierHow we'll close itOwnerBy when
1
2
3
Re-assess on: <date + 6–9 months>
undefined

Deliver the artifact

交付成果文件

Follow 
../pm-copilot/references/artifact-output.md
: confirm inputs, ask Markdown or .docx, write the 
.md
, convert via your environment's native document-creation capability on request. Then route to the worst-scoring box using 
../pm-copilot/references/journey.md
(e.g. a Market Problems gap → run 
pm-market-problems
). Not every one of the 37 boxes has a dedicated skill (e.g. Pricing, Asset Assessment, Market Definition, Distribution Strategy, Buyer Experience) — if the top gap lands on one of those, say so plainly and advise directly from that box's definition in 
../pm-copilot/references/framework.md
instead of forcing the nearest skill.
按照 
../pm-copilot/references/artifact-output.md
：确认输入信息，询问用户需要 Markdown 还是 .docx，编写 
.md
文件；如用户提出要求，再通过当前环境原生的文档创建能力进行转换。随后，使用 
../pm-copilot/references/journey.md
将执行流程路由至得分最低的方框（例如，Market Problems 存在差距 → 运行 
pm-market-problems
）。并非 37 个方框中的每一个都有专用 skill（例如 Pricing、Asset Assessment、Market Definition、Distribution Strategy、Buyer Experience）；如果最重要的差距恰好落在其中一项上，应明确说明，并直接依据 
../pm-copilot/references/framework.md
中该方框的定义提供建议，而不是强行套用最接近的 skill。