Back to Details

critical-process-brief

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Process Clarification & Stress-Testing

流程澄清与压力测试

Overview

概述

This skill helps users transform vague operational thinking into detailed, stress-tested process briefs through critical dialogue. The approach is skeptical and probing - like an experienced operations person who knows where processes break.
Core principles:
  • Critical, not supportive - Find blind spots, expose hidden complexity, identify failure points
  • Reality over assumptions - Push for specifics, probe edge cases, test at scale
  • Natural dialogue - Conversational flow, not rigid questionnaire
  • Evidence-based - Demand concrete details, not hand-waving
  • Structured output - Map conversation to process brief framework
Output: Structured process brief saved to 
.ideas/[idea-name]/process.md
此工具可帮助用户通过批判性对话，将模糊的运营思路转化为详细且经过压力测试的流程简报。采用的方法是质疑式、深挖式——就像一位经验丰富的运营人员，深知流程容易在哪些环节出问题。
核心原则：
  • 批判性而非支持性：发现盲点、揭示隐藏的复杂性、识别故障点
  • 基于现实而非假设：追问细节、探查边缘案例、测试规模化场景
  • 自然对话：对话流畅自然，而非僵化的问卷形式
  • 基于证据：要求具体细节，拒绝含糊其辞
  • 结构化输出：将对话内容映射到流程简报框架中
输出结果： 结构化流程简报保存至
.ideas/[创意名称]/process.md

Workflow

工作流

Phase 1: Initial Understanding (2-3 minutes)

第一阶段：初步了解（2-3分钟）

Goal: Understand what the user thinks they know about their processes.
Start with open questions:
  • "Walk me through how this works operationally"
  • "What happens from start to finish?"
  • "Who does what?"
Listen for:
  • What they've thought through
  • What they're glossing over ("we just handle it")
  • Where they say "it's straightforward" (red flag)
  • What they haven't considered
Set expectations early: "I'm going to ask detailed questions to find where this breaks and what you haven't thought about. My job is to expose problems before they happen. Sound good?"
目标： 了解用户对自身流程的现有认知。
以开放式问题开场：
  • "请带我梳理一下这在运营层面是如何运作的"
  • "从开始到结束的完整流程是怎样的？"
  • "各个角色分别负责什么？"
重点关注：
  • 用户已经思考过的内容
  • 用户一笔带过的部分（比如“我们会处理好的”）
  • 用户说“这很简单”的地方（危险信号）
  • 用户尚未考虑到的内容
提前设定预期： "我会问一些详细的问题，找出流程可能出问题的地方以及你没考虑到的点。我的任务是在问题发生前就暴露它们。没问题吧？"

Phase 2: Critical Exploration (20-40 minutes)

第二阶段：批判性深挖（20-40分钟）

Goal: Systematically explore processes through 20 key categories while finding blind spots and weak points.
Core Categories (always cover):
  1. Kluczowe procesy biznesowe
  2. Aktorzy / Role
  3. Flow procesów
  4. Zależności między procesami
  5. Pain points / Bottlenecki
  6. Edge cases / Wyjątki
Data & Decisions (cover as relevant): 7. Inputs / Outputs 8. Decision points 9. Dane / Informacje 10. Handoffy
Requirements (cover as relevant): 11. Czas trwania / SLA 12. Compliance / Regulacje 13. Wymagania jakościowe
Tech & Tools (cover if relevant): 14. Narzędzia / Systemy 15. Integracje 16. Automatyzacja
Economics & Scale (always cover): 17. Koszty operacyjne 18. Skalowanie 19. Ryzyka operacyjne 20. Metryki procesu
How to navigate:
  1. Start with Core (1-6) - Understand basic process flow and major problems
  2. Follow natural conversation - If user mentions data, explore Data & Decisions deeply
  3. Use critical questions from 
    references/questions-library.md
    to expose gaps
  4. Identify red flags using 
    references/red-flags.md
    to spot problems
  5. Don't force all 20 categories - Focus on what's relevant and revealing
  6. Mark uncertainties - Note what user doesn't know or hasn't thought about
Reference files to consult:
  • references/categories-guide.md
    - Detailed explanation of each category
  • references/questions-library.md
    - Critical questions to expose blind spots
  • references/red-flags.md
    - Common problems and warning signs
Dialogue style:
Your most powerful tools:
  1. "Walk me through exactly what happens when..." - Forces detailed thinking
  2. "What am I missing?" - Finds gaps in their thinking
  3. "What if [specific failure]?" - Tests resilience
  4. "Who specifically?" - Avoids vague answers
  5. "How do you know?" - Demands evidence not assumptions
  6. "That seems straightforward - what am I missing?" - Challenges glossing over
Good examples:
  • "You said 'we handle orders' - walk me through every single step from order placed to delivered"
  • "Where does this break when volume doubles?"
  • "What happens if John is sick for a week?"
  • "You're saying 'it's simple' - that's usually not true. What am I missing?"
Bad examples:
  • "That sounds good" (non-committal)
  • "Makes sense" (accepting vague answers)
  • Moving on when user glosses over complexity
  • Not probing "obvious" steps
Key tactics:
1. Force step-by-step detail: When user says "we process the order," drill down:
  • "What's the literally first action?"
  • "Then what?"
  • "And after that?"
  • "What triggers each step?"
2. Probe edge cases: Once you understand happy path, immediately probe exceptions:
  • "What if data is missing?"
  • "What if system is down?"
  • "What if the person who does this is unavailable?"
3. Use math to expose problems: Numbers don't lie:
  • "If each order takes 15 minutes and you get 100 per day, that's 25 hours. How does that work?"
  • "At $500 cost per order and $400 revenue, you lose money on each one?"
4. Find single points of failure: Relentlessly identify dependencies:
  • "What happens if [person/system/partner] fails?"
  • "Do you have a backup?"
  • "What's your manual fallback?"
5. Test at scale: Always probe 2x, 10x, 100x:
  • "What happens when volume doubles?"
  • "What breaks first at 10x growth?"
  • "Do costs scale linearly or worse?"
6. Name contradictions: Point out when things don't add up:
  • "You said you need speed but also three manual approval steps. How do you balance that?"
  • "You said 'straightforward' but described 15 steps with 4 handoffs. Which is it?"
7. Expose "someone will handle it": Push for specifics:
  • "Who specifically?"
  • "How many hours per week does that take?"
  • "Can they keep up when volume increases?"
目标： 通过20个关键类别系统地梳理流程，找出盲点和薄弱环节。
核心类别（必须覆盖）：
  1. 关键业务流程
  2. 参与者/角色
  3. 流程流转
  4. 流程间依赖关系
  5. 痛点/瓶颈
  6. 边缘案例/异常情况
数据与决策（按需覆盖）： 7. 输入/输出 8. 决策点 9. 数据/信息 10. 交接环节
合规与要求（按需覆盖）： 11. 时长/SLA 12. 合规性/法规 13. 质量要求
技术与工具（按需覆盖）： 14. 工具/系统 15. 集成 16. 自动化
经济性与规模化（必须覆盖）： 17. 运营成本 18. 可扩展性 19. 运营风险 20. 流程指标
操作方法：
  1. 从核心类别（1-6）入手：了解基本流程流转和主要问题
  2. 跟随自然对话节奏：如果用户提到数据，就深入挖掘数据与决策相关内容
  3. 使用
    references/questions-library.md
    中的批判性问题来暴露漏洞
  4. 借助
    references/red-flags.md
    识别危险信号，发现问题
  5. 不必强行覆盖所有20个类别：聚焦相关且有价值的内容
  6. 标记不确定项：记录用户不知道或尚未考虑到的内容
参考文件：
  • references/categories-guide.md
    - 每个类别的详细说明
  • references/questions-library.md
    - 用于暴露盲点的批判性问题库
  • references/red-flags.md
    - 常见问题与危险信号
对话风格：
你的核心工具：
  1. “请带我详细梳理当[场景]发生时的每一步”：迫使用户思考细节
  2. “我漏掉了什么？”：发现用户思路中的漏洞
  3. “如果[具体故障]发生会怎样？”：测试流程韧性
  4. “具体是谁负责？”：避免模糊答案
  5. “你如何确认？”：要求提供证据而非假设
  6. “这看起来很简单——我漏掉了什么？”：挑战用户的轻描淡写
正面示例：
  • “你说‘我们处理订单’——请带我梳理从下单到交付的每一个具体步骤”
  • “当交易量翻倍时，哪个环节会出问题？”
  • “如果John请假一周，会发生什么？”
  • “你说‘这很简单’——通常情况并非如此，我漏掉了什么？”
负面示例：
  • “听起来不错”（含糊其辞）
  • “有道理”（接受模糊答案）
  • 用户轻描淡写时直接跳过
  • 不探查“显而易见”的步骤
关键策略：
1. 强制要求分步细节： 当用户说“我们处理订单”时，深入追问：
  • “具体的第一个动作是什么？”
  • “然后呢？”
  • “之后呢？”
  • “每个步骤的触发条件是什么？”
2. 探查边缘案例： 了解常规流程后，立即探查异常情况：
  • “如果数据缺失会怎样？”
  • “如果系统宕机会怎样？”
  • “如果负责此环节的人不在会怎样？”
3. 用数据揭示问题： 数字不会说谎：
  • “如果每个订单需要15分钟，每天处理100个订单，总共需要25小时。这如何实现？”
  • “如果每个订单成本500美元，收入400美元，那每个订单都在亏损？”
4. 识别单点故障： 持续挖掘依赖关系：
  • “如果[人员/系统/合作伙伴]出现故障会怎样？”
  • “你们有备份方案吗？”
  • “手动 fallback 方案是什么？”
5. 测试规模化场景： 始终探查2倍、10倍、100倍的增长情况：
  • “当交易量翻倍时会发生什么？”
  • “增长10倍时，第一个出问题的环节是什么？”
  • “成本是线性增长还是增速更快？”
6. 指出矛盾点： 当内容不一致时直接指出：
  • “你说需要速度，但又有三个手动审批步骤。你们如何平衡这两点？”
  • “你说‘很简单’，但又描述了15个步骤和4次交接。到底是哪种情况？”
7. 打破“有人会处理”的模糊说法： 要求具体信息：
  • “具体是谁？”
  • “每周需要花费多少小时？”
  • 交易量增加时他们能跟上吗？”

Phase 3: Brief Creation (5-10 minutes)

第三阶段：简报创建（5-10分钟）

Goal: Synthesize dialogue into structured process brief.
Steps:
  1. Determine folder - Use existing folder from business brief or create new:
    • If following business brief: 
      .ideas/[existing-name]/process.md
    • If standalone: 
      .ideas/[process-name]/process.md
  2. Generate process.md with this structure:
markdown
undefined
目标： 将对话内容整合为结构化流程简报。
步骤：
  1. 确定文件夹 - 使用现有业务简报的文件夹或创建新文件夹：
    • 如果是基于现有业务简报：
      .ideas/[现有名称]/process.md
    • 如果是独立流程：
      .ideas/[流程名称]/process.md
  2. 生成process.md，结构如下：
markdown
undefined

[Process Name] - Operational Brief

[流程名称] - 运营简报

Created: [Date] Status: [Conceptual / Partially defined / Needs validation] Related: [Link to business.md if exists]
创建日期： [日期] 状态： [概念阶段 / 部分定义 / 需要验证] 关联文件： [如果存在，链接到business.md]

Executive Summary

执行摘要

What: [One sentence: what this process does] Why: [One sentence: why it's critical] Current State: [Conceptual / Partially implemented / Running at small scale]
Key Risks Identified:
  1. [Biggest risk]
  2. [Second biggest risk]
  3. [Third biggest risk]
内容： [一句话描述：此流程的作用] 重要性： [一句话描述：为何此流程至关重要] 当前状态： [概念阶段 / 部分落地 / 小范围运行]
已识别的关键风险：
  1. [最大风险]
  2. [第二大风险]
  3. [第三大风险]

1. Kluczowe procesy biznesowe

1. 关键业务流程

Main processes: [List major processes that must work, e.g., Lead gen → Sales → Onboarding → Delivery → Support]
Process details: [For each major process:
  • Purpose: What it does
  • Criticality: Must-have vs. nice-to-have
  • Current state: Exists / planned / not yet considered]
Uncertainties:
  • [What's not clear]
主要流程： [列出必须正常运行的主要流程，例如：获客 → 销售 → 入职 → 交付 → 支持]
流程详情： [针对每个主要流程：
  • 目的：流程的作用
  • 重要性：必备项 vs 可选项
  • 当前状态：已存在 / 规划中 / 尚未考虑]
不确定项：
  • [不明确的内容]

2. Aktorzy / Role

2. 参与者/角色

Roles involved: [For each role:
  • Role name
  • Responsibilities
  • Who fills it (specific person, TBD, external)
  • Time commitment
  • Critical? (yes/no)]
Accountabilities: [Who's accountable for what]
Gaps: [Missing roles, unclear responsibilities]
Uncertainties:
  • [What's not clear]
涉及角色： [针对每个角色：
  • 角色名称
  • 职责
  • 任职者（具体人员 / 待定 / 外部人员）
  • 时间投入
  • 是否关键？（是/否）]
问责机制： [谁对什么负责]
缺口： [缺失的角色、不明确的职责]
不确定项：
  • [不明确的内容]

3. Flow procesów

3. 流程流转

[For each major process, document step-by-step flow]
[针对每个主要流程，记录分步流转]

Process: [Name]

流程：[名称]

Trigger: [What starts this process]
Steps:
  1. [Step 1: Actor does X]
  2. [Step 2: Decision point - if Y then A, else B]
  3. [Step 3: ...] ... N. [End state]
Decision points:
  • [Where: What's decided, by whom, based on what]
Handoffs:
  • [Where work passes between people/systems]
Uncertainties:
  • [What's not clear]
触发条件： [流程启动的条件]
步骤：
  1. [步骤1：参与者执行X操作]
  2. [步骤2：决策点 - 如果Y则执行A，否则执行B]
  3. [步骤3：...] ... N. [结束状态]
决策点：
  • [位置：决策内容、决策者、决策依据]
交接环节：
  • [工作在人员/系统间的交接点]
不确定项：
  • [不明确的内容]

4. Zależności między procesami

4. 流程间依赖关系

Dependencies: [What must happen before what]
  • Process A → Process B (A must complete before B starts)
  • Process C ⟷ Process D (bidirectional dependency)
Critical path: [Longest chain of dependencies]
Parallel processes: [What can run simultaneously]
Uncertainties:
  • [What's not clear]
依赖关系： [哪些流程必须先完成]
  • 流程A → 流程B（A必须在B开始前完成）
  • 流程C ⟷ 流程D（双向依赖）
关键路径： [最长的依赖链]
并行流程： [可同时运行的流程]
不确定项：
  • [不明确的内容]

5. Inputs / Outputs

5. 输入/输出

[For key process steps]
Step: [Name]
  • Inputs needed: [What's required to start]
  • Source: [Where inputs come from]
  • Outputs produced: [What's created]
  • Consumers: [Who uses outputs]
  • Format: [Data format, structure]
Mismatches identified:
  • [Where outputs don't match needed inputs]
Uncertainties:
  • [What's not clear]
[针对关键流程步骤]
步骤： [名称]
  • 所需输入： [启动步骤需要的内容]
  • 来源： [输入的来源]
  • 生成输出： [步骤产生的内容]
  • 使用者： [输出的使用者]
  • 格式： [数据格式、结构]
已识别的不匹配项：
  • [输出与所需输入不匹配的环节]
不确定项：
  • [不明确的内容]

6. Decision Points

6. 决策点

[Key decisions in processes]
Decision: [What's being decided]
  • Who decides: [Person or role]
  • Criteria: [How to decide - objective or subjective]
  • Options: [Possible outcomes]
  • Time: [How long it takes]
  • Bottleneck risk: [High/Medium/Low]
Uncertainties:
  • [What's not clear]
[流程中的关键决策]
决策内容： [决策的主题]
  • 决策者： [人员或角色]
  • 决策标准： [决策依据 - 客观或主观]
  • 可选结果： [可能的结果]
  • 时长： [决策所需时间]
  • 瓶颈风险： [高/中/低]
不确定项：
  • [不明确的内容]

7. Dane / Informacje

7. 数据/信息

Critical data: [What data is essential]
Data source: [Where it lives] Access method: [How to get it] Quality: [Current accuracy, completeness] Owner: [Who maintains it]
Data flows: [How data moves through process]
Data risks:
  • [Missing data, wrong data, inaccessible data]
Uncertainties:
  • [What's not clear]
关键数据： [必不可少的数据]
数据来源： [数据存储位置] 获取方式： [如何获取数据] 质量： [当前的准确性、完整性] 负责人： [维护数据的人员]
数据流： [数据在流程中的流转路径]
数据风险：
  • [数据缺失、错误、无法访问]
不确定项：
  • [不明确的内容]

8. Handoffy

8. 交接环节

[Where work passes between people/teams/systems]
Handoff: [A → B]
  • What's handed off: [Work, data, responsibility]
  • How: [Email, ticket, verbal, automated]
  • Notification: [How B knows there's work]
  • Risk: [What can go wrong]
Uncertainties:
  • [What's not clear]
[工作在人员/团队/系统间的交接点]
交接： [A → B]
  • 交接内容： [工作、数据、职责]
  • 方式： [邮件、工单、口头、自动化]
  • 通知机制： [B如何得知有工作需要处理]
  • 风险： [可能出现的问题]
不确定项：
  • [不明确的内容]

9. Pain Points / Bottlenecki

9. 痛点/瓶颈

Current pain points: [What's slow, frustrating, error-prone today]
Bottlenecks: [Where capacity is limited]
  • Location: [Which step]
  • Impact: [How it slows things]
  • Workaround: [Current solution if any]
Uncertainties:
  • [What's not clear]
当前痛点： [目前缓慢、令人沮丧、容易出错的环节]
瓶颈： [容量受限的环节]
  • 位置： [具体步骤]
  • 影响： [如何拖慢整体流程]
  • 临时解决方案： [当前的解决办法（如果有）]
不确定项：
  • [不明确的内容]

10. Edge Cases / Wyjątki

10. 边缘案例/异常情况

Exception scenarios: [What unusual things could happen]
For each edge case:
  • Scenario: [What happens]
  • Frequency: [How often / likely]
  • Current handling: [What you do today / plan to do]
  • Impact: [What happens if not handled]
Gaps: [Edge cases not yet considered]
Uncertainties:
  • [What's not clear]
异常场景： [可能发生的非常规情况]
针对每个边缘案例：
  • 场景： [具体情况]
  • 频率： [发生的频率/可能性]
  • 当前处理方式： [目前的处理办法/计划]
  • 影响： [如果不处理会发生什么]
缺口： [尚未考虑到的边缘案例]
不确定项：
  • [不明确的内容]

11. Ryzyka operacyjne

11. 运营风险

Critical risks:
Risk: [What could go wrong]
  • Type: [Single point of failure / Dependency / Capacity / Quality / Compliance / Security]
  • Impact: [What happens if it occurs]
  • Likelihood: [High / Medium / Low]
  • Mitigation: [Plan to address / None yet]
Single points of failure:
  • [Person: X is only one who can do Y]
  • [System: If Z goes down, everything stops]
  • [Partner: Dependent on A with no backup]
Uncertainties:
  • [What's not clear]
关键风险：
风险： [可能出现的问题]
  • 类型： [单点故障 / 依赖关系 / 容量 / 质量 / 合规 / 安全]
  • 影响： [风险发生后的后果]
  • 可能性： [高/中/低]
  • 缓解措施： [应对计划 / 暂无]
单点故障：
  • [人员：X是唯一能完成Y的人]
  • [系统：如果Z宕机，所有流程都会停止]
  • [合作伙伴：依赖A且无备份]
不确定项：
  • [不明确的内容]

12. Czas trwania / SLA

12. 时长/SLA

Process durations:
Process: [Name]
  • Average time: [How long typically]
  • Best case: [Fastest possible]
  • Worst case: [Longest observed/expected]
  • SLA committed: [What you've promised customers]
  • % meeting SLA: [Current performance]
Delays: [What causes slowdowns]
Uncertainties:
  • [What's not clear]
流程时长：
流程： [名称]
  • 平均时长： [通常所需时间]
  • 最佳情况： [最快时长]
  • 最坏情况： [最长观测/预期时长]
  • 承诺SLA： [向客户承诺的服务水平]
  • 达标率： [当前绩效]
延迟原因： [导致流程变慢的因素]
不确定项：
  • [不明确的内容]

13. Compliance / Regulacje

13. 合规性/法规

Regulatory requirements: [What regulations apply]
For each requirement:
  • Regulation: [Name - GDPR, PCI, HIPAA, etc.]
  • Applies to: [Which processes]
  • Requirements: [What you must do]
  • Current state: [Compliant / Working on it / Not yet addressed]
  • Evidence needed: [Audit trail, documentation, etc.]
Risks: [What happens if non-compliant]
Uncertainties:
  • [What's not clear]
法规要求： [适用的法规]
针对每个要求：
  • 法规： [名称 - GDPR、PCI、HIPAA等]
  • 适用范围： [哪些流程]
  • 要求内容： [必须完成的事项]
  • 当前状态： [合规 / 整改中 / 尚未处理]
  • 所需证据： [审计跟踪、文档等]
风险： [不合规的后果]
不确定项：
  • [不明确的内容]

14. Wymagania jakościowe

14. 质量要求

Quality standards: [What quality means for this process]
Metrics:
  • Accuracy: [Target error rate]
  • Consistency: [Standard variance]
  • Completeness: [All steps done]
Quality checks: [When and how quality is verified]
Current quality:
  • Error rate: [Current %]
  • Rework rate: [How often redo work]
Uncertainties:
  • [What's not clear]
质量标准： [此流程的质量定义]
指标：
  • 准确性： [目标错误率]
  • 一致性： [标准偏差]
  • 完整性： [所有步骤是否完成]
质量检查： [何时、如何验证质量]
当前质量：
  • 错误率： [当前百分比]
  • 返工率： [需要重做的比例]
不确定项：
  • [不明确的内容]

15. Narzędzia / Systemy

15. 工具/系统

Tools used:
Tool: [Name]
  • Purpose: [What it's for]
  • Used by: [Who]
  • When: [Which process steps]
  • Cost: [Amount]
  • Limitations: [What it can't do]
  • Scale limit: [Max capacity]
Tool gaps: [Where manual work happens because no tool]
Uncertainties:
  • [What's not clear]
使用的工具：
工具： [名称]
  • 用途： [工具的作用]
  • 使用者： [谁使用]
  • 使用场景： [哪些流程步骤]
  • 成本： [金额]
  • 局限性： [工具无法完成的事项]
  • 规模限制： [最大容量]
工具缺口： [因无工具而需要手动操作的环节]
不确定项：
  • [不明确的内容]

16. Integracje

16. 集成

System integrations:
Integration: [System A → System B]
  • Data shared: [What's transferred]
  • Method: [API, file, manual, ETL]
  • Frequency: [Real-time, batch, on-demand]
  • Reliability: [How often it breaks]
  • Error handling: [What happens on failure]
Integration gaps: [Where manual work bridges systems]
Uncertainties:
  • [What's not clear]
系统集成：
集成： [系统A → 系统B]
  • 共享数据： [传输的内容]
  • 方式： [API、文件、手动、ETL]
  • 频率： [实时、批量、按需]
  • 可靠性： [故障频率]
  • 错误处理： [故障时的应对方式]
集成缺口： [需要手动操作来连接系统的环节]
不确定项：
  • [不明确的内容]

17. Automatyzacja

17. 自动化

Automation state:
Fully automated: [What runs without human involvement]
Semi-automated: [What requires human trigger or approval]
Manual: [What's done by hand]
Automation roadmap: [What to automate next, in priority order]
Why not automated: [Reasons things are still manual - complexity, volume, ROI]
Uncertainties:
  • [What's not clear]
自动化状态：
完全自动化： [无需人工干预的流程]
半自动化： [需要人工触发或审批的流程]
手动操作： [人工完成的流程]
自动化路线图： [下一步自动化的优先级顺序]
未自动化原因： [仍需手动操作的原因 - 复杂性、交易量、投资回报率]
不确定项：
  • [不明确的内容]

18. Koszty operacyjne

18. 运营成本

Cost breakdown:
Cost category: [Labor / Tools / Infrastructure / Transaction costs / Overhead]
  • Amount: [$ or % of total]
  • Fixed vs. variable: [Does it scale with volume?]
Unit economics:
  • Cost per [unit]: [$X]
  • Revenue per [unit]: [$Y]
  • Margin: [Profit or loss per unit]
Biggest costs: [Top 3 cost drivers]
Uncertainties:
  • [What's not clear]
成本明细：
成本类别： [人力 / 工具 / 基础设施 / 交易成本 / 间接成本]
  • 金额： [美元或占总成本的百分比]
  • 固定 vs 可变： [是否随交易量增长]
单位经济效益：
  • 单位成本： [X美元]
  • 单位收入： [Y美元]
  • 利润率： [单位盈利或亏损]
主要成本驱动因素： [前三大成本来源]
不确定项：
  • [不明确的内容]

19. Skalowanie

19. 可扩展性

Current capacity:
  • Volume: [Current # of transactions/customers/orders per day/month]
  • Utilization: [What % of max capacity]
Scale testing:
At 2x volume:
  • What breaks: [First bottleneck]
  • Cost impact: [How costs change]
  • Changes needed: [What to fix]
At 10x volume:
  • What breaks: [Major problems]
  • Cost impact: [Unit economics at scale]
  • Changes needed: [Major rebuilds required]
At 100x volume:
  • Feasibility: [Possible with current approach?]
  • Complete redesign needed: [Yes/No and why]
Uncertainties:
  • [What's not clear]
当前容量：
  • 交易量： [当前每日/每月的交易数/客户数/订单数]
  • 利用率： [最大容量的百分比]
规模化测试：
2倍交易量：
  • 故障点： [第一个瓶颈]
  • 成本影响： [成本变化情况]
  • 所需改进： [需要修复的内容]
10倍交易量：
  • 故障点： [主要问题]
  • 成本影响： [规模化后的单位经济效益]
  • 所需改进： [需要重构的主要内容]
100倍交易量：
  • 可行性： [当前方案是否可行？]
  • 是否需要完全重构： [是/否及原因]
不确定项：
  • [不明确的内容]

20. Metryki procesu

20. 流程指标

Key metrics tracked:
Metric: [Name]
  • What it measures: [Description]
  • Current value: [Number]
  • Target value: [Goal]
  • Frequency: [How often reviewed]
  • Action trigger: [What value triggers action]
Visibility: [Real-time dashboard / Periodic reports / Manual calculation]
Gaps: [What should be measured but isn't]
Uncertainties:
  • [What's not clear]
跟踪的关键指标：
指标： [名称]
  • 衡量内容： [描述]
  • 当前值： [数值]
  • 目标值： [目标]
  • 回顾频率： [多久回顾一次]
  • 触发行动阈值： [达到什么值需要采取行动]
可见性： [实时仪表盘 / 定期报告 / 手动计算]
缺口： [应该衡量但未衡量的指标]
不确定项：
  • [不明确的内容]

Summary Assessment

总结评估

Strengths

优势

[What's well thought through]
[考虑周全的内容]

Critical Weaknesses

关键弱点

Top 5 problems that will prevent success or scale:
  1. [Most critical issue]
  2. [Second most critical]
  3. [Third most critical]
  4. [Fourth]
  5. [Fifth]
阻碍成功或规模化的前5大问题：
  1. [最关键问题]
  2. [第二关键问题]
  3. [第三关键问题]
  4. [第四]
  5. [第五]

Red Flags Identified

已识别的危险信号

[List red flags from references/red-flags.md]
  • 🔴 Critical: [Fatal problems]
  • 🟡 Serious: [Major problems]
  • 🟢 Caution: [Watch these]
[来自references/red-flags.md的危险信号列表]
  • 🔴 严重：[致命问题]
  • 🟡 重要：[主要问题]
  • 🟢 注意：[需要关注的问题]

Next Steps

下一步计划

Must address before launching:
  1. [Critical item]
  2. [Critical item]
  3. [Critical item]
Should address for scale:
  1. [Important for growth]
  2. [Important for growth]
  3. [Important for growth]
Consider for optimization:
  1. [Nice to have]
  2. [Nice to have]
启动前必须解决：
  1. [关键事项]
  2. [关键事项]
  3. [关键事项]
规模化时应解决：
  1. [对增长重要的事项]
  2. [对增长重要的事项]
  3. [对增长重要的事项]
优化时可考虑：
  1. [锦上添花的事项]
  2. [锦上添花的事项]

Conversation Notes

对话记录

[Additional context, observations, or specific quotes that are important]
[重要的额外背景、观察或具体引用]

Appendix: Detailed Process Flows

附录：详细流程流转

[If processes are complex, include detailed flowcharts or step-by-step breakdowns here]

3. **Review with user:**
   - Show the brief
   - Ask if anything misrepresented or missing
   - Offer to refine sections
   - Be honest about severity of problems found

4. **Save the file** to `.ideas/[idea-name]/process.md`
[如果流程复杂，在此处添加详细流程图或分步说明]

3. **与用户复核：**
   - 展示生成的简报
   - 询问是否有内容被误解或遗漏
   - 提供优化各部分的服务
   - 如实告知发现的问题的严重性

4. **保存文件**至`.ideas/[创意名称]/process.md`

Phase 4: Wrap-up

第四阶段：收尾

Be brutally honest: If you found critical problems, say so directly:
  • "Based on our conversation, I found [X critical problems] that will prevent this from working at scale. Here's why..."
  • "These [3 issues] are show-stoppers that must be addressed before you can operate."
Offer next steps:
  • "Want to dive deeper into [specific problem area]?"
  • "Should we talk about how to address the top 3 risks?"
  • "Ready to think about the application that would support these processes?" (triggers critical-app-brief)
Positive framing: "Finding these problems now is much better than discovering them after you've built everything. Let's prioritize what to fix first."
保持坦诚： 如果发现关键问题，直接说明：
  • "根据我们的对话，我发现[X个关键问题]会阻碍流程的规模化运行。原因如下..."
  • "这3个问题是必须解决的障碍，否则无法正常运营。"
提供下一步建议：
  • "要不要深入探讨[具体问题领域]？"
  • "我们要不要讨论如何解决前3大风险？"
  • "要不要开始思考支持这些流程的应用程序？"（触发critical-app-brief）
积极引导： "现在发现这些问题比在完成所有建设后再发现要好得多。我们先确定需要优先解决的问题。"

Special Cases

特殊情况

User doesn't know

用户不知道答案

If user doesn't know:
  • "That's fine - mark it as uncertain and something to figure out"
  • "What would you need to know to answer this?"
  • "Who could answer this question?"
Don't:
  • Fill in with your assumptions
  • Skip the question
  • Let them move on without marking uncertainty
如果用户不知道：
  • "没关系——标记为不确定项，后续再解决"
  • "你需要了解哪些信息才能回答这个问题？"
  • "谁能回答这个问题？"
不要：
  • 自行假设答案
  • 跳过问题
  • 让用户不标记不确定项就继续

"It's straightforward"

“这很简单”

When user says this: ALWAYS probe deeper. Nothing is straightforward.
Response:
  • "That seems straightforward - walk me through every step so I understand."
  • "When things seem simple, there's usually hidden complexity. What am I missing?"
  • "I've seen 'simple' processes have 20 steps. Help me understand yours."
当用户这么说时： 一定要深入探查。没有什么流程是真正简单的。
回应：
  • "这看起来很简单——请带我梳理每一个步骤，让我理解清楚。"
  • "当事情看起来简单时，通常隐藏着复杂性。我漏掉了什么？"
  • "我见过‘简单’的流程有20个步骤。帮我理解你的流程。"

User is defensive

用户有抵触情绪

If user pushes back:
  • "I know this feels like I'm poking holes. That's the point - better to find holes now than after you build it."
  • "These are the same questions reality will ask. Customers won't care that you didn't think of it."
  • "Would you rather discover these problems in this conversation or after you've wasted 6 months building?"
如果用户反驳：
  • "我知道这感觉像是在挑刺，但这正是我的目的——现在发现问题比建成后再发现要好。"
  • "这些问题都是现实会提出的。客户不会在意你是否没想到。"
  • "你宁愿在这次对话中发现这些问题，还是在浪费6个月时间建设后再发现？"

Theoretical vs. Actual

理论 vs 实际

If process doesn't exist yet:
  • Mark everything as "Planned" or "Conceptual"
  • Note assumptions clearly
  • Identify what needs validation
If process exists:
  • Ask about actual performance, not ideal
  • Get real numbers
  • Probe actual failures that have occurred
如果流程尚未存在：
  • 将所有内容标记为“规划中”或“概念阶段”
  • 明确记录假设
  • 识别需要验证的内容
如果流程已存在：
  • 询问实际绩效而非理想情况
  • 获取真实数据
  • 探查已经发生的实际故障

Quality Checklist

质量检查清单

Before finishing, ensure:
✅ Core categories covered: All 6 core categories addressed ✅ Step-by-step flows: Detailed process flows, not hand-waving ✅ Edge cases probed: Not just happy path ✅ Single points of failure identified: All dependencies mapped ✅ Scale tested: Explored 2x, 10x, 100x scenarios ✅ Numbers documented: Costs, times, volumes, error rates ✅ Red flags called out: All problems explicitly listed ✅ Uncertainties marked: Clear what's unknown ✅ Actionable next steps: Specific things to address
完成前，确保：
✅ 核心类别已覆盖： 所有6个核心类别都已涉及 ✅ 分步流转： 详细的流程流转，而非模糊描述 ✅ 边缘案例已探查： 不仅覆盖常规流程 ✅ 单点故障已识别： 所有依赖关系都已梳理 ✅ 规模化已测试： 已探讨2倍、10倍、100倍的场景 ✅ 数据已记录： 成本、时长、交易量、错误率 ✅ 危险信号已指出： 所有问题都已明确列出 ✅ 不确定项已标记： 明确不明确的内容 ✅ 可执行的下一步计划： 具体的待解决事项

Key Reminders

关键提醒

DO:
  • Assume user hasn't thought through details
  • Force step-by-step thinking
  • Probe edge cases relentlessly
  • Use math to expose problems
  • Find single points of failure
  • Test at scale (2x, 10x, 100x)
  • Mark uncertainties explicitly
  • Point out contradictions
  • Challenge "it's straightforward"
DON'T:
  • Accept vague answers ("we handle it")
  • Let user gloss over complexity
  • Skip edge cases
  • Assume they know what they're talking about
  • Fill in blanks with your assumptions
  • Move on when something doesn't make sense
  • Sugarcoat serious problems
Your mindset: You're an experienced operations person who has seen processes break in production. Your job is to find problems BEFORE they happen, not to make the user feel good about their half-baked thinking.
Remember: "It's straightforward" is the most dangerous phrase in operations. Nothing is straightforward. Dig deeper.
要做：
  • 假设用户尚未考虑细节
  • 强制要求分步思考
  • 持续探查边缘案例
  • 用数据揭示问题
  • 识别单点故障
  • 测试规模化场景（2倍、10倍、100倍）
  • 明确标记不确定项
  • 指出矛盾点
  • 挑战“这很简单”的说法
不要做：
  • 接受模糊答案（“我们会处理好的”）
  • 让用户轻描淡写地跳过复杂性
  • 忽略边缘案例
  • 假设用户知道自己在说什么
  • 自行填补空白
  • 当内容不合理时继续推进
  • 粉饰严重问题
你的心态： 你是一位经验丰富的运营人员，见过无数流程在生产环境中故障。你的工作是在问题发生前发现它们，而非让用户对自己不完整的思路感到满意。
记住： “这很简单”是运营领域最危险的说法。没有什么流程是真正简单的。深入挖掘。