Back to Details

scpr-framework

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

SCPR Framework

SCPR Framework

A structured approach to problem-solving and executive communication used in management consulting.
一种用于管理咨询领域的结构化问题解决与高管沟通方法。

Framework Components

框架组件

S - Situation: Current state of the market/business
  • What is the lay of the land?
  • Establish baseline context
  • Describe the stable environment before changes
C - Complication: Recent shift or change
  • What has changed recently?
  • New market dynamics (AI boom, regulatory changes, competitive threats)
  • The catalyst that creates urgency
P - Problem: Crisp question to solve
  • What specific strategic question must be answered?
  • Common examples: "How to grow revenue?", "How to enter new market?", "How to reduce costs?"
  • Must be specific and answerable
R - Recommendation: Proposed actions
  • What should be done and by when?
  • Priority actions to address the problem
  • Can be structured as issue tree branches (doesn't have to be only high-priority items)
  • Specific, actionable, time-bound
S - Situation（情境）：市场/业务的当前状态
  • 行业现状如何？
  • 确立基准背景
  • 描述变化发生前的稳定环境
C - Complication（复杂性）：近期的转变或变化
  • 最近发生了哪些变化？
  • 新的市场动态（AI热潮、监管变化、竞争威胁）
  • 制造紧迫性的触发因素
P - Problem（问题）：需要解决的明确问题
  • 必须回答的具体战略问题是什么？
  • 常见示例："如何提升营收？"、"如何进入新市场？"、"如何降低成本？"
  • 必须具体且可解答
R - Recommendation（建议）：拟采取的行动
  • 应该做什么，以及何时完成？
  • 解决问题的优先行动
  • 可拆解为议题树分支（不必仅限于高优先级事项）
  • 具体、可执行、有时间限制

Core Principles

核心原则

MECE (Mutually Exclusive, Collectively Exhaustive)
  • Recommendations should not overlap
  • Together they should cover all necessary actions
  • Each recommendation addresses distinct aspect of the problem
Clarity
  • Each section should be concise
  • Problem statement must be answerable
  • Recommendations must be actionable
MECE（相互独立，完全穷尽）
  • 建议之间不应重叠
  • 合起来应涵盖所有必要行动
  • 每条建议针对问题的不同方面
清晰性
  • 每个部分应简洁明了
  • 问题陈述必须可解答
  • 建议必须可执行

Example: Tech Startup Product Pivot

示例：科技初创企业产品转型

Situation Series B SaaS startup with $15M ARR selling project management software to creative agencies and marketing firms. Product focuses on task management, resource allocation, and client collaboration. 200 agency customers with average contract size $75K. Historically strong product-market fit with 25% YoY growth and 90% gross retention.
Complication AI-powered tools like ChatGPT, Notion AI, and Claude emerging as workflow automation alternatives. Customer usage metrics declining 15% over last 6 months. Exit interviews reveal agencies using AI for project briefs, status updates, and resource planning - core features of current product. Three enterprise deals ($500K pipeline) paused citing "evaluating AI-first solutions."
Problem How should we reposition the product and business model to return to 25%+ growth within 12 months while competing against general-purpose AI tools?
Recommendations
  1. Product: Launch AI-native workflow engine by Q2 2025
    • Integrate LLM for automated project scoping and task breakdown
    • AI-powered resource matching based on skills and availability
    • Differentiate on agency-specific context (brand guidelines, client history, creative workflows)
  2. Positioning: Shift from "project management" to "AI-augmented agency operations" by Q1 2025
    • Rebrand messaging around AI that understands agency workflows
    • Emphasize integration advantages over general tools
    • Target gap: ChatGPT lacks agency-specific memory and processes
  3. Pricing: Introduce usage-based AI tier by Q2 2025
    • Base platform remains flat fee ($75K)
    • AI features charged per automation/generation
    • Capture value from high-usage customers, protect downside
情境 一家处于B轮融资阶段的SaaS初创企业，ARR达1500万美元，为创意机构和营销公司销售项目管理软件。产品聚焦任务管理、资源分配和客户协作。拥有200家机构客户，平均合同规模7.5万美元。历史上产品市场契合度良好，同比增长25%，客户毛利率留存率90%。
复杂性 ChatGPT、Notion AI和Claude等AI驱动工具作为工作流自动化替代方案兴起。过去6个月客户使用指标下降15%。离职访谈显示，机构正在使用AI处理项目简报、状态更新和资源规划——这些都是当前产品的核心功能。3笔企业级交易（500万美元销售管线）暂停，理由是“评估AI优先解决方案”。
问题 我们应如何重新定位产品与商业模式，以在12个月内恢复25%以上的增长，同时与通用AI工具竞争？
建议
  1. 产品：2025年第二季度前推出AI原生工作流引擎
    • 集成LLM实现自动化项目范围界定与任务拆分
    • 基于技能和可用性的AI驱动资源匹配
    • 突出机构特定场景的差异化（品牌指南、客户历史、创意工作流）
  2. 定位：2025年第一季度前从“项目管理”转型为“AI增强型机构运营”
    • 围绕理解机构工作流的AI重塑品牌 messaging
    • 强调相较于通用工具的集成优势
    • 瞄准市场空白：ChatGPT缺乏机构特定记忆与流程
  3. 定价：2025年第二季度前推出基于使用量的AI层级定价
    • 基础平台保持固定费用（7.5万美元）
    • AI功能按自动化/生成次数收费
    • 从高使用量客户处获取价值，降低风险

Usage Patterns

使用模式

When creating SCPR structure:
  1. Start with Situation (establish baseline)
  2. Identify Complication (what changed?)
  3. Frame Problem as specific question
  4. Develop MECE Recommendations with timeline
When analyzing existing content:
  1. Extract facts into S/C/P/R categories
  2. Test Problem for specificity
  3. Verify Recommendations are MECE
  4. Add timelines if missing
When reviewing SCPR:
  • Is Situation necessary context only (not exhaustive)?
  • Is Complication recent and urgent?
  • Is Problem answerable and specific?
  • Are Recommendations mutually exclusive and collectively exhaustive?
  • Does each Recommendation include "by when"?
构建SCPR结构时：
  1. 从情境开始（确立基准）
  2. 识别复杂性（发生了什么变化？）
  3. 将问题框定为具体的疑问
  4. 制定符合MECE原则且带有时间线的建议
分析现有内容时：
  1. 将事实提取到S/C/P/R类别中
  2. 检验问题的具体性
  3. 验证建议是否符合MECE原则
  4. 若缺少时间线则补充
审核SCPR时：
  • 情境是否仅包含必要背景（而非详尽无遗）？
  • 复杂性是否是近期且紧迫的？
  • 问题是否可解答且具体？
  • 建议是否相互独立且完全穷尽？
  • 每条建议是否包含“何时完成”？

Common Mistakes to Avoid

需避免的常见错误

  • Situation too detailed: Keep to essential context only
  • Complication = Problem: They're different. Complication is "what changed", Problem is "what question to solve"
  • Vague Problem: "Improve business" is too broad. "Increase revenue 40% in 12 months" is specific
  • Overlapping Recommendations: Ensure MECE structure
  • No timelines: Always include "by when" in Recommendations
  • 情境过于详细：仅保留必要背景
  • 混淆复杂性与问题：二者不同。复杂性是“发生了什么变化”，问题是“需要解决什么疑问”
  • 问题模糊：“改善业务”过于宽泛。“12个月内营收增长40%”才是具体的
  • 建议重叠：确保符合MECE结构
  • 缺少时间线：建议中务必包含“何时完成”