asb-carol-inciting-events

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Inciting Events: What Makes Them Buy Today

触发事件：是什么促使他们今天购买

A prospect can agree the product is a great fit, the keystone is exactly what they want, there are no deal-breakers, the price is fair — and still not buy. Their excuse is genuine: "we can't implement this right now; call back in nine months." The person with buying power has one to three top priorities, and you aren't one of them. What promotes you to the top is an inciting event: nobody wakes up randomly deciding today's the day to buy — something happens in their life, a moment of struggle where action must be taken. This skill maps those moments, keystone by keystone.

潜在客户可能认同产品非常契合，keystone正是他们想要的，没有deal-breakers，价格也合理——但仍然不会购买。他们的理由很真实：“我们现在无法实施这个；九个月后再联系。”拥有购买决策权的人有一到三个首要任务，而你的产品不在其中。让你跻身首要任务的是触发事件：没有人会突然决定今天要购买——他们的生活中一定发生了某些事情，一个必须采取行动的挣扎时刻。本技能会逐个keystone绘制这些时刻。

The mental model

心智模型

The inciting event completes the purchase

触发事件促成购买

Three forces, in order: inciting events are why people buy anything (the struggle that forces action now), keystones are why they buy from you (the circumstance that makes your strength critical), and deal-breakers carve off exclusions. A keystone means the customer could care about the issue; the inciting event is what raises it to a top-three priority they want solved today. That is why every real inciting event couples to a keystone — an event with no keystone attached is a trigger to buy something else. The canonical pairs: the speed keystone's events were "the SEO consultant said poor performance is blocking our rankings" and "we saw the study showing faster sites convert more revenue"; the scale keystone's event was "the biggest traffic day of the year crashed the site — never again"; the security keystone's was "we got hacked, it was terrifying, we paid a consultant $300 an hour and we're still not sure it's fixed"; the support keystone's was "we called for help and were told 'all we do is keep your server powered on.'"

三种力量按顺序排列：触发事件是人们购买任何东西的原因（迫使立即采取行动的挣扎），keystone是他们选择你的原因（让你的优势变得至关重要的情境），deal-breakers用于排除非目标客户。keystone意味着客户可能关心这个问题；触发事件则是将其提升为他们今天想要解决的三大首要任务之一。这就是为什么每个真实的触发事件都与一个keystone相关联——没有关联keystone的事件是购买其他产品的触发因素。典型配对：速度keystone的事件是“SEO顾问表示糟糕的性能阻碍了我们的排名”和“我们看到研究显示更快的网站能转化更多收入”；规模keystone的事件是“全年流量最高的一天网站崩溃了——绝不再发生”；安全keystone的事件是“我们被黑客攻击了，太可怕了，我们每小时支付顾问300美元，但仍然不确定问题是否解决”；支持keystone的事件是“我们打电话求助，却被告知‘我们只负责保持你的服务器开机’”。

Observed beats hypothesized — and both get marked

已观察事件优先于假设事件——两者都需标记

The reliable way to identify inciting events is to ask customers what prompted them to start looking and why they chose you — ideally right after purchase, while the answer is fresh. So when interview evidence exists (a findings report, per-interview debrief files, onboarding survey answers), harvest it FIRST: real trigger stories, in the customers' words, marked observed with their source. Only then work backward for the gaps, and mark those hypothesized — honest labels, because a hypothesized event is a guess wearing a plan, and the next round of customer conversations should test it. Never dress a brainstorm as evidence.

识别触发事件的可靠方法是询问客户是什么促使他们开始寻找产品，以及为什么选择你——理想情况下是在购买后立即询问，此时答案还很清晰。因此，当存在访谈证据（如调查结果报告、每次访谈的汇报文件、入职调查答案）时，首先收集这些证据：来自客户原话的真实触发故事，标记为observed（已观察）并注明来源。只有在证据不足的情况下，才通过反向推导填补空白，并将这些标记为hypothesized（假设）——诚实标注，因为假设事件是带有计划的猜测，下一轮客户对话应验证它。永远不要将头脑风暴伪装成证据。

The work-backward lenses

反向推导视角

When hypothesizing, ask: what would compel a customer to act today, with urgency, with budget, with pre-approval? Brainstorm through these lenses:

Crises that force immediate action — a public breach or data loss; a critical vendor acquired or shut down; a key customer ultimatum; a lawsuit or regulatory investigation; executive turnover; a PR debacle; a competitor announcement that exposes a gap.
Seasonal and recurring cycles — annual planning, fiscal year-end, tax season, quarterly reviews, compliance audits, conference deadlines, the industry's peak season approaching.
Strategic windows — a compliance deadline, a required certification, entering a new market, an acquisition closing, IPO prep, legacy-system modernization, new funding creating budget and expectations at once.
Personal life-changes (for consumer and solo-professional products) — becoming a parent, retiring, a health diagnosis, a death in the family, marriage or divorce, starting a business, changing jobs, graduating, buying a first home.

进行假设时，问自己：什么会促使客户立即采取行动，有紧迫感，有预算，有预先批准？通过以下视角进行头脑风暴：

迫使立即行动的危机——公开数据泄露或丢失；关键供应商被收购或倒闭；重要客户发出最后通牒；诉讼或监管调查；高管变动；公关危机；竞争对手发布公告暴露自身短板。
季节性和周期性循环——年度规划、财年末、报税季、季度审查、合规审计、会议截止日期、行业旺季临近。
战略窗口期——合规截止日期、所需认证、进入新市场、收购完成、IPO筹备、遗留系统现代化、新融资同时带来预算和期望。
个人生活变化（针对消费者和个体从业者产品）——成为父母、退休、健康诊断、家人离世、结婚或离婚、创业、换工作、毕业、购买第一套住房。

Findability makes the file operational

可发现性让文件具备可操作性

For each event, answer: how do you find prospects in this condition? Someone whose site was just hacked isn't searching "secure hosting" — they're searching "how to tell whether my site is hacked" and posting "Help! My site is hacked!" into the void. Findability signals include: official announcements, executive podcast appearances, product launches and press tours, changes in job postings, recurring complaints in reviews or social media, analyst reports, regulatory change notices, leadership changes, funding news — and above all, the exact phrases a person in that moment types into a search box. An event you can't detect from outside is still worth recording, but say so: it can only be exploited in messaging ("if this just happened to you…"), not targeting. Events are often split — the lawsuit half of an enforcement event is public record while the audit-notice half is invisible; annotate which parts are targetable and which are messaging-only.

对于每个事件，回答：**如何找到处于这种状态的潜在客户？**网站刚被黑客攻击的人不会搜索“安全托管”——他们会搜索“如何判断我的网站是否被黑客攻击”，并在网上发布“救命！我的网站被黑客攻击了！”。可发现性信号包括：官方公告、高管播客亮相、产品发布和媒体巡演、招聘信息变化、评论或社交媒体中反复出现的投诉、分析师报告、监管变更通知、领导层变动、融资新闻——最重要的是，处于该时刻的人输入搜索框的确切短语。无法从外部检测到的事件仍值得记录，但需注明：它只能用于消息触达（“如果这件事刚发生在你身上……”），不能用于定向投放。事件通常会拆分：执法事件中的诉讼部分是公开记录，而审计通知部分不可见；需标注哪些部分可定向，哪些仅用于消息触达。

Vivid or it doesn't advertise

生动具体才能有效宣传

In advertising, the inciting event often outperforms the keystone, because it speaks to the customer's current experience — they're reacting to their circumstance, not shopping for product attributes. That only works if the event is written vividly: the specific moment, the emotion, the number. "A hacked website is a personal violation — you pay a consultant $300 an hour and still wonder if it's coming back" advertises; "customers get frustrated with their host" doesn't. Generic events ("realizes they need a better solution") are not recorded, in any form — there is always a specific moment inside a true trigger, and finding it is the work.

在广告中，触发事件的表现往往优于keystone，因为它能引起客户的当下共鸣——他们是在对自身情境做出反应，而不是在挑选产品属性。这只有在事件描述生动具体时才有效：特定时刻、情绪、数字。“被黑客攻击的网站是一种个人侵犯——你每小时支付顾问300美元，仍不确定攻击是否会再次发生”这样的描述有宣传效果；“客户对当前托管服务商感到不满”则没有。通用事件（“意识到他们需要更好的解决方案”）不会以任何形式记录——真正的触发因素背后总有一个具体时刻，找到它就是这项工作的核心。

Vocabulary

词汇表

Inciting event (E1, E2, …) — the specific trigger moment that moves a keystone-fit customer to buy now; cites its [K-number].
Observed / hypothesized — evidence status: harvested from real customer accounts (with source) vs. worked backward (to be validated). Two sanctioned shadings: "OBSERVED (from memory)" for the user's recall of a real account — genuine evidence, weaker sourcing, re-confirm at validation; and a composite of repeated sales-call patterns with no single account stays HYPOTHESIZED. A hypothesized event may cite supporting-but-not-triggering evidence ("plausibility supported — not evidenced — by the June debrief's standing dread") without gaining a Source line.
Findability — how prospects in the event's condition can be detected or reached from outside, including their likely search phrases.

触发事件（E1、E2…）——促使契合keystone的客户立即购买的特定触发时刻；标注对应的[K编号]。
observed（已观察）/ hypothesized（假设）——证据状态：来自真实客户案例（注明来源）vs 反向推导（待验证）。两种认可的细分标注：“OBSERVED (from memory)（已观察（来自记忆））”用于用户回忆的真实案例——真实证据，但来源可信度较低，验证时需重新确认；由重复销售通话模式构成但无单个具体案例的仍标记为假设。假设事件可引用支持性但非触发式证据（“plausibility supported — not evidenced — by the June debrief's standing dread（合理性得到6月汇报中提及的持续担忧支持——但无直接证据）”），无需添加来源行。
Findability（可发现性）——如何从外部检测或触达处于该事件状态的潜在客户，包括他们可能使用的搜索短语。

The mapper's posture

绘制者准则

Be clear, not clever

清晰明了，而非故作聪明

Write to be understood, not admired. The work here wrestles with hard concepts, and clever metaphors, wordplay, or cute turns of phrase make them harder to grasp, not easier. Say plainly what you mean. If a sentence reads more clearly without a flourish, cut the flourish. State the actual point rather than gesturing wittily at it.

写作目的是让人理解，而非让人赞赏。这项工作涉及复杂概念，巧妙的隐喻、文字游戏或俏皮表达会让概念更难理解，而非更容易。直白地表达你的意思。如果去掉修饰后句子更清晰，就删掉修饰。直接陈述实际观点，而非巧妙地暗示。

Restate references; never cite a bare token

重述引用内容；绝不只引用孤立标记

When you mention a numbered or lettered item to the user — K4, W2, O17, H3, and the like — add a few plain words on what it actually is ("K4 — the owner whose career rides on the site"). A bare token is unreadable to a human who saw it defined hours or days ago: the tag is for traceability, the gloss is for comprehension. Keep the tag for accuracy; always add the gloss.

当向用户提及带编号或字母的项目——K4、W2、O17、H3等——时，添加几句直白的话说明它实际是什么（“K4——职业生涯与网站绑定的所有者”）。孤立的标记对几小时或几天前见过其定义的人来说难以理解：标记用于追溯，注释用于理解。保留标记以确保准确性；始终添加注释。

Harvest before you brainstorm

先收集证据，再进行头脑风暴

If interview artifacts exist — a findings report with trigger stories, per-interview debrief files, exit or onboarding surveys — read them first and pull every trigger story into candidate events before hypothesizing anything — and record harvested events as they confirm, even when they belong to keystones later in the walk; E-numbers run in settle order, not keystone order. The user's memory counts too ("what did your last three customers say prompted them to look?"), marked observed-from-memory. Only where the evidence runs out do the lenses come out. If the user has no interview evidence at all, say plainly that everything in this file will be hypothesized until customers are asked — and that asking is the validation path.

如果存在访谈资料——包含触发故事的调查结果报告、每次访谈的汇报文件、退出或入职调查——先阅读这些资料，将所有触发故事提取为候选事件，再进行任何假设——并在确认后立即记录收集到的事件，即使它们属于后续处理的keystone；E编号按确定顺序排列，而非keystone顺序。用户的记忆也可作为证据（“你的最后三位客户说是什么促使他们开始寻找产品？”），标记为“observed-from-memory（来自记忆的已观察事件）”。只有在证据用尽时才使用反向推导视角。如果用户没有任何访谈证据，需明确说明此文件中的所有内容都将是假设，直到询问客户——而询问客户就是验证路径。

Press moments into vividness

让事件描述生动具体

When the user offers a vague trigger ("when they get fed up with their current tool"), press for the moment: fed up by what incident? What happened that morning? What did it cost? What did they type into Google that night? A predefined way to press harder: if a devil's-advocate interrogation skill is installed in the environment (for example Rude Q&A /

asb-rude-qa

, from the same author as this method), invoke it against the draft with this brief: attack these inciting events — find every one that's a mood rather than a moment, every one no real customer story or plausible circumstance backs, every "hypothesized" that's being treated as fact, and every findability note too vague to act on. Don't accept wishful or hand-wavy defenses. If no such skill is available, run that interrogation yourself, visibly — candidates inline, the batch attack at the closing sweep.

当用户提供模糊的触发因素（“当他们对当前工具感到厌烦时”），追问具体时刻：是因为什么事件感到厌烦？那天早上发生了什么？造成了什么损失？那天晚上他们在谷歌上搜索了什么？一种预设的追问方式：如果环境中安装了“魔鬼代言人”质询技能（例如同一作者开发的Rude Q&A /

asb-rude-qa

），请用以下指令对草稿进行质询：*attack these inciting events — find every one that's a mood rather than a moment, every one no real customer story or plausible circumstance backs, every "hypothesized" that's being treated as fact, and every findability note too vague to act on. Don't accept wishful or hand-wavy defenses.（攻击这些触发事件——找出所有只是情绪而非具体时刻的事件、所有没有真实客户故事或合理情境支撑的事件、所有被当作事实的“假设”事件，以及所有过于模糊无法执行的可发现性说明。不接受一厢情愿或含糊其辞的辩解。）*如果没有此类技能，则自行进行质询，清晰展示——候选事件内联，最后进行批量检查。

Couple every event to a keystone

每个事件都必须关联一个keystone

An event that couples to no keystone is a flag, not an entry: either it's a trigger to buy something you don't sell, or it's pointing at a keystone the earlier steps missed. Say which it looks like; if the user believes a real keystone is missing, that's a finding to take back to the keystones file — not a reason to record an orphan event.

未关联任何keystone的事件是一个警示信号，而非有效条目：它要么是购买你未销售产品的触发因素，要么指向之前步骤遗漏的keystone。说明它看起来属于哪种情况；如果用户认为确实遗漏了真实的keystone，这是需要反馈到keystone文件的发现——而非记录孤立事件的理由。

One keystone per exchange

每次处理一个keystone

Walk the keystones in order, one per exchange; a keystone may yield one or several events. Small opening move: what was read, which keystones already have observed trigger material, then the first keystone. Compress ceremony on request, never structure.

按顺序逐个处理keystone；一个keystone可能产生一个或多个事件。开场小步骤：说明已阅读的内容、哪些keystone已有已观察触发材料，然后开始处理第一个keystone。可根据要求简化流程，但绝不改变结构。

How to use this skill

如何使用本技能

Phase A — Ingest

阶段A——导入

Read the keystones file (default:

KEYSTONES.md

in the current directory — ideally already honed with deal-breaker qualifiers; if the change log shows no honing, proceed but note the segments may still be over-broad). Ask what customer evidence exists and read whatever is offered: a customer-interview findings report, per-interview debrief files, survey exports, or just the user's recall of what recent customers said prompted them. If no keystones file exists, don't map triggers for unknown targets: offer the on-ramp — run the keystones step first (if a keystones skill from this method's author is installed, for example Keystones /

asb-carol-keystones

, name it), or capture a minimal keystone list in chat with the caveat that unvetted keystones yield unvetted events. If an INCITING-EVENTS.md exists: in-progress header means resume — and anything not in the file was never settled; re-derive it from the evidence rather than reconstructing the dead session's half-proposal from anyone's memory. Complete means ask whether to revise. (The presence of per-interview debrief files in the question-mapped format is itself evidence the interview process is in use — harvest them without asking.)

Output:

INCITING-EVENTS.md

in the same directory. If the input was pasted and no path is known, ask where the method's files should live before creating anything (default: the current directory) — never scatter files silently.

读取keystone文件（默认：当前目录下的

KEYSTONES.md

——理想情况下已添加deal-breaker限定词；如果变更日志显示未优化，可继续处理，但需注意细分市场可能仍过于宽泛）。询问用户有哪些客户证据，并读取提供的任何资料：客户访谈调查结果报告、每次访谈的汇报文件、调查导出数据，或用户对近期客户提及的触发因素的回忆。如果不存在keystone文件，不要为未知目标绘制触发因素：提供入门路径——先运行keystone步骤（如果安装了同一作者开发的keystone技能，例如Keystones /

asb-carol-keystones

，请提及它），或在聊天中捕获最小化keystone列表，并附带警告：未经验证的keystone会产生未经验证的事件。如果已存在INCITING-EVENTS.md：如果文件头部显示“进行中”，则继续——文件中未包含的内容从未确定；从证据重新推导，而非从任何人的记忆中重建已结束会话的半成型提案。如果文件已完成，则询问是否需要修订。（如果存在按问题映射格式整理的每次访谈汇报文件，本身就表明访谈流程正在使用——无需询问即可收集这些文件。）

输出：同一目录下的

INCITING-EVENTS.md

。如果输入是粘贴的内容且未知路径，询问方法文件应存储在何处再创建（默认：当前目录）——绝不静默分散文件。

Phase B — Walk the keystones

阶段B——处理keystone

Open small: what you read, which keystones already carry observed trigger stories in the evidence, then the first keystone. Per keystone:

Harvest observed events from the evidence — the customers' own words, with source ("FINAL-REPORT.md F5" / "the debrief from the June 12 interview" / "user's recall of the Meridian deal").
Hypothesize the gaps through the lenses, marked as such.
Press each event vivid — the moment, the emotion, the number.
Findability — how to detect or reach someone in that condition, including their likely search phrases; if it can't be detected from outside, say so.
Record with [K-number], evidence status, and findability; move to the next keystone.

Record to the file as you go. Create

INCITING-EVENTS.md

at the first settled event; keep the header pointer current ("Keystones walked: K1; currently on: K2"). The file is the memory, not the chat.

从小处着手：说明已阅读的内容、哪些keystone在证据中已有已观察触发故事，然后开始处理第一个keystone。每个keystone的处理步骤：

收集已观察事件——来自证据的客户原话，注明来源（“FINAL-REPORT.md F5” / “6月12日访谈的汇报文件” / “用户对Meridian交易的回忆”）。
通过视角推导假设事件，并标记为hypothesized（假设）。
让每个事件描述生动具体——具体时刻、情绪、数字。
Findability（可发现性）——如何检测或触达处于该状态的人，包括他们可能使用的搜索短语；如果无法从外部检测到，需注明。
记录——包含[K编号]、证据状态和可发现性；继续处理下一个keystone。

边处理边记录到文件中。在第一个确定的事件处创建

INCITING-EVENTS.md

；保持头部指针更新（“已处理的keystone：K1；当前处理：K2”）。文件是记录，而非聊天记录。

Phase C — Sweep and close

阶段C——检查与收尾

Coupling check — every event cites a keystone; every keystone has at least one event or an honest gap note ("no trigger known yet — ask the next five customers what prompted them").
Evidence audit — the batch press (delegated or self-run): no hypothesized event reads as fact; no observed event lacks its source; nothing generic survived.
Validation path — for the hypothesized events, note the question to ask customers ("what prompted you to start looking?") and when (right after purchase, while fresh). If a customer-interview process from this method's author is installed (its goal-setting skill is
```
asb-interview-goals
```
), name it as the systematic way to run that validation; otherwise describe it: ask new customers at onboarding, every time, and keep the answers.

Finalize (remove the header) and close with the handoff: the next step synthesizes everything — strengths, keystones, deal-breakers, and these events — into the ideal-customer definition; if a definition skill from this method's author is installed (for example Define Carol /

asb-carol-define

), name it: "when you're ready, run

asb-carol-define

on these files."

关联检查——每个事件都标注了keystone；每个keystone至少有一个事件或诚实的空白说明（“暂无已知触发因素——询问接下来的五位客户是什么促使他们购买”）。
证据审核——批量检查（委托或自行进行）：没有假设事件被当作事实；所有已观察事件都有来源；没有通用事件残留。
验证路径——对于假设事件，注明要询问客户的问题（“是什么促使你开始寻找产品？”）和询问时机（购买后立即询问，此时答案还清晰）。如果安装了同一作者开发的客户访谈流程技能（其目标设定技能为
```
asb-interview-goals
```
），提及它作为系统验证的方式；否则描述验证方法：每次在客户入职时询问新客户，并记录答案。

最终确定（移除头部）并移交：下一步是将所有内容——优势、keystone、deal-breakers和这些事件——整合为理想客户定义；如果安装了同一作者开发的定义技能（例如Define Carol /

asb-carol-define

），提及它：“准备就绪后，对这些文件运行

asb-carol-define

。”

The file structure

文件结构

markdown

undefined

markdown

undefined

Inciting events — <company / project name>

触发事件 — <公司/项目名称>

⚠️ IN PROGRESS — the walk is not complete. Keystones walked: <which>; currently on: <K-number>. If you are resuming, continue there. (This note is removed at finalization.)

⚠️ 进行中 — 处理尚未完成。已处理的keystone： <哪些>；当前处理：<K编号>。如果继续处理，请从此处开始。（最终确定时移除此注释。）

Inciting events

触发事件

E1. <The specific trigger moment, written vividly — what happened, what it cost, how it felt.> [K2] — OBSERVED Source: <where this story came from.> Findability: <how to detect/reach someone in this condition; likely search phrases in quotes.>

E2. <…> [K1] — HYPOTHESIZED (validate: ask new customers what prompted them to look) Findability: <…>

Gaps

<K-number> — no trigger known yet; <the question to ask the next customers>.

<K-number> — no trigger known yet; <the question to ask the next customers>.

Next steps


E-numbers are stable once written. Never renumber; an event whose
status changes (hypothesized → observed, once customers confirm it)
keeps its number and gains its source.


E-numbers are stable once written. Never renumber; an event whose
status changes (hypothesized → observed, once customers confirm it)
keeps its number and gains its source.

Refusal conditions

拒绝条件

No keystones. Triggers mapped without targets describe everyone's bad week. Offer the keystones step or the caveated quick capture.
Brainstorms dressed as evidence. A hypothesized event never loses its label because the user is sure. It converts to observed when a real customer account backs it — that's what the validation path is for.
Generic events, however insisted. "When they realize they need something better" is not recorded in any form; the specific moment behind a true trigger always exists, and pressing for it is the work.
Orphan events. An event coupled to no keystone is a flag — either off-target or a missing keystone worth taking back to that file — never an entry.
Writing the ads. The events are the raw material for advertising and positioning; writing the copy is downstream work with its own craft. Findability notes point at where and to whom; the words come later.
Inventing customer quotes. Observed means a real account from a real customer with a source. Fabricated color poisons the file's one advantage over guessing.

No keystones. Triggers mapped without targets describe everyone's bad week. Offer the keystones step or the caveated quick capture.
Brainstorms dressed as evidence. A hypothesized event never loses its label because the user is sure. It converts to observed when a real customer account backs it — that's what the validation path is for.
Generic events, however insisted. "When they realize they need something better" is not recorded in any form; the specific moment behind a true trigger always exists, and pressing for it is the work.
Orphan events. An event coupled to no keystone is a flag — either off-target or a missing keystone worth taking back to that file — never an entry.
Writing the ads. The events are the raw material for advertising and positioning; writing the copy is downstream work with its own craft. Findability notes point at where and to whom; the words come later.
Inventing customer quotes. Observed means a real account from a real customer with a source. Fabricated color poisons the file's one advantage over guessing.