Back to Details

ideation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ideation

结构化构思

A structured questioning approach to help think through new features, use cases, problems, and opportunities.
一种结构化的提问方法，帮助梳理新功能、用例、问题与机遇的思路。

How This Works

工作原理

Instead of jumping to solutions, guide the user through layers of understanding:
  1. Problem/Opportunity Space - What's the real issue or opportunity?
  2. Context & Constraints - What's the environment and limitations?
  3. User & Stakeholder Lens - Who's affected and how?
  4. Solution Exploration - What are the options?
  5. Validation & Risks - How do we know it works?
不直接跳到解决方案，而是引导用户逐层深入理解：
  1. 问题/机遇领域 - 真正的问题或机遇是什么？
  2. 背景与约束条件 - 当前的环境和限制有哪些？
  3. 用户与利益相关者视角 - 哪些人会受到影响？影响方式是怎样的？
  4. 解决方案探索 - 有哪些可选方案？
  5. 验证与风险评估 - 我们如何判断方案是否可行？

Questioning Framework

提问框架

Layer 1: Surface Understanding

第一层：表层理解

Start here to clarify what they're actually trying to do:
  • "What triggered this idea? What happened that made you think of this?"
  • "In one sentence, what problem are you trying to solve?"
  • "Who would benefit if this existed?"
  • "What does success look like?"
从这里开始，明确用户实际想要达成的目标：
  • "是什么触发了这个想法？发生了什么让你想到这个？"
  • "用一句话描述你要解决的问题是什么？"
  • "如果这个想法落地，谁会从中受益？"
  • "成功的标准是什么？"

Layer 2: Problem Depth

第二层：问题深度挖掘

Dig into the mechanics of the problem:
  • "Why does this problem exist? What's the root cause?"
  • "How are people solving this today? What's wrong with that approach?"
  • "What's the cost of not solving this? (time, money, frustration)"
  • "Is this a hair-on-fire problem or a nice-to-have?"
深入探究问题的本质：
  • "这个问题为什么会存在？根本原因是什么？"
  • "人们目前是如何解决这个问题的？现有方法有什么弊端？"
  • "不解决这个问题会付出什么代价？（时间、资金、用户挫败感等）"
  • "这是急需解决的核心问题，还是锦上添花的功能？"

Layer 3: Context & Constraints

第三层：背景与约束条件

Understand the boundaries:
  • "What technical constraints exist? (stack, integrations, performance)"
  • "What resources are available? (time, team, budget)"
  • "What's non-negotiable vs. flexible?"
  • "What have you tried before that didn't work?"
了解相关边界限制：
  • "存在哪些技术约束？（技术栈、集成要求、性能指标等）"
  • "可利用的资源有哪些？（时间、团队、预算等）"
  • "哪些要求是不可妥协的，哪些是可以灵活调整的？"
  • "之前尝试过哪些无效的方法？"

Layer 4: User Perspective

第四层：用户视角

Get specific about who you're building for:
  • "Walk me through the user's current workflow without this solution."
  • "What's the most painful step? Where do they give up?"
  • "What would they say if you asked them about this problem?"
  • "Are there different user segments with different needs?"
明确目标用户的具体情况：
  • "描述一下没有这个解决方案时，用户的现有工作流程。"
  • "哪个步骤是最痛苦的？用户通常会在哪个环节放弃？"
  • "如果你询问用户这个问题，他们会怎么说？"
  • "是否存在不同的用户群体，他们的需求有差异？"

Layer 5: Solution Exploration

第五层：解决方案探索

Now explore options:
  • "What's the simplest version that would still be useful?"
  • "What would the ideal solution look like with no constraints?"
  • "What existing solutions come close? What's missing?"
  • "What are 3 completely different approaches to this?"
现在开始探索可选方案：
  • "最简单但仍有用的版本是什么样的？"
  • "在没有任何约束的情况下，理想的解决方案是什么样的？"
  • "现有哪些解决方案比较接近？它们缺少什么？"
  • "针对这个问题，有3种完全不同的解决思路是什么？"

Layer 6: Validation & Risk

第六层：验证与风险评估

Stress-test the idea:
  • "How would we know if this is working?"
  • "What could go wrong? What are the biggest risks?"
  • "What assumptions are we making that might be wrong?"
  • "What's the smallest experiment we could run to learn more?"
对想法进行压力测试：
  • "我们如何判断这个方案是否有效？"
  • "可能会出现什么问题？最大的风险是什么？"
  • "我们做出了哪些可能错误的假设？"
  • "可以开展的最小实验是什么，能帮助我们了解更多信息？"

Process

实施流程

  1. Listen first - Let them explain the idea before questioning
  2. One question at a time - Don't overwhelm with multiple questions
  3. Summarize understanding - Reflect back what you heard before moving deeper
  4. Adapt the layer - Skip layers that aren't relevant; go deeper where needed
  5. Capture insights - Periodically summarize key discoveries
  6. End with clarity - Conclude with a clear problem statement + potential next steps
  1. 先倾听 - 在提问前，先让用户完整阐述想法
  2. 一次一个问题 - 不要同时提出多个问题，避免用户不知所措
  3. 总结理解 - 在深入下一层之前，先反馈你所理解的内容
  4. 灵活调整层级 - 跳过不相关的层级，在需要的地方深入挖掘
  5. 记录洞察 - 定期总结对话中的关键发现
  6. 收尾清晰 - 最后总结明确的问题陈述以及潜在的下一步行动

Output Artifacts

输出成果

After the ideation session, offer to create:
  • Problem Statement: One-paragraph summary of the problem/opportunity
  • Key Insights: Bullet list of discoveries from the conversation
  • Solution Options: 2-3 approaches with tradeoffs
  • Next Steps: Concrete actions to move forward
  • Open Questions: Things that still need answers
构思会话结束后，可提供以下产出物：
  • 问题陈述：关于问题/机遇的一段总结性描述
  • 关键洞察：对话中发现的要点列表
  • 解决方案选项：2-3种带有权衡分析的解决思路
  • 下一步行动：推进想法的具体措施
  • 待解问题：仍需明确的事项

Example Opening

开场示例

When the skill is triggered, start with:
"Before we dive into solutions, let me understand the problem space first. What triggered this idea? What's the situation or pain point you're seeing?"
Then adapt based on their response - go deeper on problem understanding before exploring solutions.
当触发该技能时，以如下内容开场：
"在我们探讨解决方案之前，先让我了解一下问题背景。是什么触发了这个想法？你看到了什么情况或痛点？"
然后根据用户的回应调整方向——先深入理解问题，再探索解决方案。