Coowoolf The PPS (Problem-People-System) Diagnostic
The PPS (Problem-People-System) Diagnostic（PPS（问题-人-系统）诊断）
概述 / Overview
一套循序渐进的诊断框架，旨在避免过早陷入工具选型的误区。它倒逼管理者在着手配置软件权限或启动采购流程之前，必须先明确核心问题及相关干系人。
来源 / Source
- 嘉宾: Austin Hay
- 职位: Head of Marketing Technology
- 公司: Ramp
核心步骤 / Core Steps
- Step 1: Define the Problem (What specific friction exists?)
- Step 2: Identify People (Who are the stakeholders/owners?)
- Step 3: Design System (What tool/automation solves this?)
核心原则 / Core Principles
- Tools are meant to solve problems; do not start with the tool.
- Identify the root friction (Problem) first.
- Identify the stakeholders and workflow owners (People) second.
- Only design or modify the technology (System) after the first two are clear.
适用场景 / When to Use
当团队成员申请引入新工具、索要管理权限以试图“修补”问题，或对失效流程进行复盘诊断时。
常见错误 / Common Mistakes
在未厘清背景的情况下，直接跳到“系统”层面（例如：开通权限或采购软件）。
实战案例 / Real-World Example
销售经理希望实现入职流程自动化（Problem）。与其直接搭建自动化系统（System），你首先要确认 CRO 是否需要审批录用，或是否涉及必要的培训环节（People）。
金句 / Quote
"I like to first say what's the problem? Who are the people involved and what system does it impact? Usually people just jump straight to the system."