Back to Details

asb-carol-dealbreakers

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Deal-Breakers: Who Will Never Buy, No Matter What

交易否决因素：无论如何都绝不会购买的群体

A buyer can have three keystones and still be disqualified: if they require SOC 2 and you don't have it, there is no deal — deal-breakers trump keystones, and purchasing committees lament it as often as vendors do. This skill maps those disqualifiers from the weaknesses chart, names the anti-market segments who live behind them, and then does the move that sharpens everything upstream: honing each keystone segment with the qualifiers the deal-breakers force.
即便买家符合三项核心要素，仍可能被淘汰：如果他们要求SOC 2认证但你方没有，那么交易直接告吹——交易否决因素的优先级高于核心要素，采购委员会和供应商对此都深感遗憾。本技能根据劣势图表梳理这些淘汰条件，明确背后对应的反市场细分群体，随后完成一项能优化上游所有环节的操作：用交易否决因素所要求的限定条件来打磨每个核心要素细分群体。

The mental model

思维模型

Weaknesses → deal-breakers → anti-market

劣势 → 交易否决因素 → 反市场

The procedure mirrors the keystones step exactly, on the other column: for each weakness, ask what circumstances make this weakness disqualifying — not annoying, not a negotiating point, but a hard no? Then name the real market segments that live in those circumstances. Those segments are the anti-market — beyond the edge of your possible market. From the canonical chart: "expensive" disqualifies anyone with a $5/mo website budget (personal projects; small businesses in markets where US pricing is unaffordable); "supports only WordPress" disqualifies everyone already built on something else; "requires design and build-out" disqualifies the person who needs a one-page site finished by tonight.
Not every weakness yields a deal-breaker. A weakness a third of the market dislikes but nobody refuses over is friction — it costs you points in comparisons, but it doesn't draw a boundary. Record the distinction: friction is for the product backlog; deal-breakers are for the market map.
该流程与核心要素步骤完全镜像，只是针对另一列内容：针对每个劣势，询问在什么情况下这个劣势会成为绝对否决项——不是令人不满，不是谈判筹码，而是直接拒绝？ 然后明确处于这些情况中的真实市场细分群体。这些群体就是反市场——超出你方潜在市场范围之外的群体。从标准图表来看：“价格高昂”会淘汰所有网站预算仅为每月5美元的用户（个人项目；美国定价在当地市场难以承受的小企业）；“仅支持WordPress”会淘汰所有已基于其他平台搭建的用户；“需要设计和搭建”会淘汰那些今晚就要完成单页网站的用户。
并非每个劣势都能转化为交易否决因素。如果三分之一的市场群体不喜某一劣势，但没人会因此拒绝购买，那么这只是摩擦点——会让你方在对比中失分，但不会划分市场边界。要明确区分：摩擦点应纳入产品待办事项；交易否决因素则用于市场地图。

Deal-breakers hone keystones

交易否决因素打磨核心要素

The most valuable output of this step is not the anti-market list — it's what the deal-breakers do to the keystone segments. "Has an e-commerce store where speed yields revenue" plus the "expensive" deal-breaker becomes "has an e-commerce store processing at least $5,000/mo" — stores below that can't afford the premium option, so they were never really in the segment. Add "supports only WordPress" and it becomes "…that is already built with WordPress." Every honed qualifier makes the keystone description more powerful: easier to target with advertising, easier for sales to qualify against, more relevant testimonials, clearer feature prioritization. The tighter the description, the closer it gets to the ideal customer.
本步骤最有价值的输出并非反市场列表——而是交易否决因素对核心要素细分群体的优化作用。“拥有能通过提升速度创造营收的电商店铺”加上“价格高昂”这一交易否决因素后，就变成了“拥有每月处理至少5000美元交易的电商店铺”——低于该额度的店铺无法承担溢价方案，所以他们从未真正属于该细分群体。再加上“仅支持WordPress”，则变为“……已基于WordPress搭建的电商店铺”。每一项打磨后的限定条件都会让核心要素描述更精准：广告定位更精准、销售筛选更高效、客户 testimonial更具相关性、功能优先级更清晰。描述越精准，就越接近理想客户。

Avoid the anti-market deliberately

主动避开反市场

The anti-market isn't a sad byproduct; it's an instruction. Exclude those segments intentionally from marketing, sales, and feature development:
  • In advertising, use language that appeals to the target AND actively dissuades the anti-market from clicking — "for the most demanding websites" tells the $5/mo shopper to keep scrolling, which is precisely the point: every unqualified click costs money and every unqualified trial costs support time.
  • In product, don't build features that appeal to the anti-market, even though those requests WILL arrive, loudly. They come from the unprofitable tail of the customer base, not from the customers the strategy is built on.
反市场并非令人遗憾的副产品，而是行动指引。要刻意将这些群体排除在营销、销售和功能开发之外：
  • 营销层面：使用既能吸引目标群体又能主动劝退反市场群体的语言——“专为高要求网站打造”会让每月预算5美元的用户继续浏览，这正是目的所在：每一次不合格的点击都会耗费成本，每一次不合格的试用都会占用支持时间。
  • 产品层面：不要为了吸引反市场群体而开发功能，即便这类需求会频繁且强烈地出现。这些需求来自客户群体中无利可图的尾部，而非战略所聚焦的核心客户。

Sell what's on the truck

立足现有产品进行定位

You will be tempted, at every deal-breaker, to say "but we could add a feature that fixes that." Maybe you should — someday, as a deliberate strategy decision, because addressing a new market takes more than one feature. Today's job is describing the market you can win as you are. The fix-it idea gets parked, on the record, as strategy input; the deal-breaker stands, and the honing proceeds from the product that exists.
在梳理每个交易否决因素时，你可能会忍不住想说“但我们可以添加一个功能来解决这个问题”。也许未来应该这么做——但这需要经过深思熟虑的战略决策，因为开拓新市场远不止开发一个功能那么简单。当前的任务是描述你方凭借现有产品就能赢得的市场。“修复劣势”的想法可以记录下来作为战略输入；而交易否决因素依然有效，打磨流程基于现有产品推进。

Vocabulary

术语定义

  • Deal-breaker (D1, D2, …) — a circumstance under which a weakness disqualifies the product outright; cites its [W-number].
  • Anti-market — the real segments living in those circumstances; deliberately excluded from marketing, sales, and product decisions.
  • Friction — a weakness that costs points but disqualifies no one; recorded as such, no deal-breaker derived.
  • Honing — appending deal-breaker-forced qualifiers to keystone segment descriptions, editing the keystones file under its frozen numbers.
  • 交易否决因素（D1、D2……）：指某一劣势直接导致产品被淘汰的情况；标注对应的[W编号]。
  • 反市场：处于上述情况中的真实细分群体；刻意被排除在营销、销售和产品决策之外。
  • 摩擦点：会导致失分但不会淘汰任何用户的劣势；需如实记录，不转化为交易否决因素。
  • 打磨（Honing）：将交易否决因素要求的限定条件添加到核心要素细分群体描述中，在核心要素文件中保留原有K编号并进行编辑。

The refiner'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——职业生涯与网站成败息息相关的所有者”）。仅标注代号对于数小时或数天前看过定义的人来说难以理解：代号用于追溯，补充说明用于理解。保留代号以确保准确性；务必添加补充说明。

Mirror the keystone discipline

遵循核心要素流程的严谨性

Generate deal-breaker candidates freely — yours and the user's — and gate each visibly: does the circumstance truly disqualify (not merely annoy), and can a real anti-market segment be named? Press vague segments into circumstance and behavior, exactly as targets were pressed. 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 deal-breakers — find every one that's actually just friction nobody refuses over, every anti-market segment too vague to exclude deliberately, and every honing qualifier that dodges instead of bites. Don't accept wishful or defensive answers. 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
），可以用以下指令对草稿进行质疑：攻击这些交易否决因素——找出所有实际只是不会被拒绝的摩擦点、所有模糊到无法刻意排除的反市场细分群体，以及所有回避实质问题的打磨限定条件。不接受一厢情愿或防御性的回答。 如果没有此类技能，请自行进行上述质疑，全程透明：候选项列在文中，最后统一进行全面审查。

The user owns the market; the mechanics are fixed

用户掌握市场信息；流程规则固定

Whether a segment truly refuses, whether an anti-market is real — the user's market knowledge rules, after one honest press. What their call can't change: a deal-breaker with no refusing segment is friction, not a deal-breaker; honing edits keep the keystone file's K-numbers frozen and leave a change-log line; and "we'll fix that weakness soon" doesn't soften today's map.
某个细分群体是否真的会拒绝购买、反市场是否真实——用户的市场知识是最终判断依据，但前提是经过一次坦诚的验证。用户的判断无法改变的规则是：没有对应拒绝群体的交易否决因素只是摩擦点，而非交易否决因素；打磨编辑需保留核心要素文件的K编号并添加变更日志；“我们很快会修复这个劣势”不会改变当前的市场地图。

Honing is proposed, never imposed

打磨仅为提议，绝不强制

Each honing edit is one proposal: the keystone's current segment line, the deal-breaker that intersects it, the qualified rewrite — before/after — and the user decides. Some keystone segments are untouched by any deal-breaker; say so and move on rather than inventing qualifiers. Where a qualifier guts a keystone (the honed segment is now nearly empty), that's a finding to surface plainly: this keystone's market may be smaller than it looked.
每一项打磨编辑都是一个提议：核心要素当前的细分群体描述、与之相关的交易否决因素、修改后的限定版本——提供前后对比，由用户决定。有些核心要素细分群体不会受到任何交易否决因素的影响；此时应如实说明并继续推进，而非编造限定条件。如果某一限定条件导致核心要素细分群体几乎消失，需明确指出这一发现：该核心要素对应的市场可能比看起来小得多。

One item per exchange

每次交流处理一项内容

One weakness per exchange in the mapping walk; one keystone per exchange in the honing walk. Small opening move; compress ceremony on request, never structure.
梳理反市场时，每次交流处理一个劣势；打磨核心要素时，每次交流处理一个核心要素。从小步骤开始；可根据用户要求简化流程，但绝不改变结构。

How to use this skill

如何使用本技能

Phase A — Ingest

阶段A — 导入

Read the weaknesses (from 
STRENGTHS-WEAKNESSES.md
, default in the current directory; both-classified attributes participate here on their weakness reading) and the keystones file (
KEYSTONES.md
). If the keystones file carries a Verdict section (one or zero keystones survived), surface it before honing — mapping the anti-market of a not-yet-compelling product may be premature, and the user should say whether to proceed. Missing keystones file: the mapping walk can proceed, but the honing half can't — say what's lost, and name the keystones step invoke-if-installed style (for example Keystones / 
asb-carol-keystones
) as the way to produce it. Missing weaknesses (e.g., the keystones step ran from a quick capture): capture a defensible weakness list in chat now — same mini genericness press, W-numbers as they settle, recorded in the DEALBREAKERS.md preamble — with the caveat that unvetted weaknesses yield unvetted deal-breakers. If a DEALBREAKERS.md already exists: in-progress header means resume; complete means ask whether to revise.
Output: 
DEALBREAKERS.md
in the same directory; honing edits go directly into 
KEYSTONES.md
. 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.
读取劣势信息（来自当前目录默认的
STRENGTHS-WEAKNESSES.md
；已分类的属性在此处按劣势解读）和核心要素文件（
KEYSTONES.md
）。如果核心要素文件包含Verdict部分（仅保留了0个或1个核心要素），在打磨前需向用户说明——为尚未具备吸引力的产品绘制反市场可能为时过早，需由用户决定是否继续。 如果缺少核心要素文件：可以继续梳理反市场，但无法进行打磨操作——需说明缺失的内容，并告知用户可调用核心要素步骤的技能（例如Keystones / 
asb-carol-keystones
）来生成该文件。如果缺少劣势信息（例如核心要素步骤仅基于快速收集的信息完成）：立即在聊天中收集可靠的劣势列表——同样进行模糊性验证，确定后标注W编号，记录在DEALBREAKERS.md的前言中——同时提醒用户，未经验证的劣势会导致未经验证的交易否决因素。如果DEALBREAKERS.md已存在：如果文件头部标注“进行中”则继续；如果标注“已完成”则询问用户是否需要修订。
输出结果：在同一目录生成
DEALBREAKERS.md
；打磨编辑直接写入
KEYSTONES.md
。如果输入内容是粘贴的且未知路径，需先询问用户方法文件应存储在何处（默认：当前目录）——切勿静默分散文件。

Phase B — Map the deal-breakers

阶段B — 梳理交易否决因素

Open small: what you read, which weaknesses look disqualifying vs. friction-shaped, then the first weakness. Per weakness:
  1. Ask the mirror question — under what circumstances is this a hard no? Offer candidates alongside the user's.
  2. Gate each candidate: disqualifies-not-annoys, then the anti-market segment named sharply enough to deliberately exclude.
  3. Record deal-breakers with [W-numbers] and anti-market segments; record friction verdicts with one line of reasoning.
  4. Park every "we could fix that" in a strategy-input list — the idea survives, the map doesn't wait for it.
Record to the file as you go. Create 
DEALBREAKERS.md
at the first settled item (or at ingest, when weaknesses were quick-captured — the capture itself is worth preserving); keep the header pointer current. The file is the memory, not the chat.
从小处着手：说明你读取的内容、哪些劣势看起来可能成为否决项或摩擦点，然后开始处理第一个劣势。针对每个劣势：
  1. 提出镜像问题——在什么情况下这会成为绝对拒绝项？在用户提出的候选项之外，补充你提出的候选项。
  2. 验证每个候选项：确认是“淘汰”而非“不满”，且反市场细分群体足够明确，可以刻意排除。
  3. 记录标注[W编号]的交易否决因素及对应的反市场细分群体；记录摩擦点判定及一句理由。
  4. 将所有“我们可以修复这个问题”的想法存入战略输入列表——想法保留，但市场地图不会等待修复完成。
随时记录到文件中。 在第一个确定的项目出现时创建
DEALBREAKERS.md
（或在导入阶段快速收集劣势时创建——收集的内容本身就值得保留）；保持头部指针更新。文件是记录载体，而非聊天记录。

Phase C — Hone the keystones

阶段C — 打磨核心要素

Walk the keystones file one keystone per exchange. For each:
  1. Name which deal-breakers intersect its segment (often none — say so and move on).
  2. Propose the qualified segment line — before/after — with the [D-number] driving each qualifier.
  3. On agreement, edit KEYSTONES.md: the segment line under its frozen K-number, plus one dated change-log line at the bottom of that file ("2026-07-09: K1 segment honed — added 'processing ≥$5k/mo' [D1] and 'already built on X' [D2]") — create the change log section on first use, and apply edit + log line + header pointer as one move, so a died session never has an agreed change missing from disk. Never renumber; never touch keystone wording beyond the segment lines without the user asking. Keystones the check leaves untouched may be reviewed several per exchange (no decision is being asked), and get one collective change-log line ("K2, K4 reviewed — untouched by any deal-breaker") so the finalized files certify the whole walk happened.
  4. Where the honed segment collapses to nearly nobody, surface the finding plainly — a keystone whose honest market is tiny is strategy input, not a thing to hide with a looser qualifier.
逐一处理核心要素文件中的每个核心要素，每次交流处理一个。针对每个核心要素：
  1. 说明哪些交易否决因素与其细分群体相关（通常没有——如实说明并继续）。
  2. 提出修改后的细分群体描述——提供前后对比，并标注驱动每项限定条件的[D编号]。
  3. 获得同意后，编辑KEYSTONES.md：保留原有K编号下的细分群体描述，在文件底部添加一条带日期的变更日志（例如“2026-07-09：打磨K1细分群体——添加‘每月处理≥5000美元交易’[D1]和‘已基于X搭建’[D2]”）——首次使用时创建变更日志部分，同时完成编辑、添加日志和更新头部指针三个操作，避免会话中断后已确认的修改未保存到磁盘。绝不重新编号；未经用户请求，绝不修改核心要素描述中除细分群体行之外的内容。未被打磨影响的核心要素可以批量审查（无需用户决策），并添加一条汇总变更日志（“K2、K4已审查——未受任何交易否决因素影响”），以便最终文件能证明整个打磨流程已完成。
  4. 如果打磨后的细分群体几乎无人符合，需明确指出这一发现——真实市场极小的核心要素是战略输入，不应通过放宽限定条件来掩盖。

Phase D — Sweep and close

阶段D — 全面审查与收尾

  • Trump check — read the deal-breakers against the keystone segments once more: any keystone segment that still contains people a deal-breaker excludes needs another qualifier — OR the deal-breaker's anti-market wording was over-broad and gets tightened instead ("single-location" becomes "single-location without admin staff"). Either resolution is legitimate; the evidence says which.
  • Anti-market statement — one short paragraph in DEALBREAKERS.md: who is deliberately excluded, with the standing instructions (dissuasive ad language; no anti-market features, however loud the requests).
  • Friction list — confirm it reads as product-backlog input, not market boundaries.
Finalize both files: remove the in-progress header; update the keystones preamble's "pre-honing" sentence to "segments honed — see change log"; confirm the change log (canonical header: 
## Change log
) in KEYSTONES.md tells the honing story. Close with the handoff: the next step finds the inciting events — what moves a perfect-fit customer from could-buy to buying-today; if an inciting-events skill from this method's author is installed (for example Inciting Events / 
asb-carol-inciting-events
), name it: "when you're ready, run 
asb-carol-inciting-events
on these files."
  • 优先级检查——再次对照核心要素细分群体审查交易否决因素：如果某个核心要素细分群体仍包含被交易否决因素淘汰的用户，需添加新的限定条件——或者收紧交易否决因素的反市场描述（例如“单店”改为“无管理员的单店”）。两种解决方案均合理，需根据实际情况判断。
  • 反市场声明——在DEALBREAKERS.md中添加一段简短的段落：说明刻意排除的群体，以及相关指导原则（使用劝退性广告语言；即便有需求，也不为反市场群体开发功能）。
  • 摩擦点列表——确认其作为产品待办事项输入的定位，而非市场边界。
最终确定两个文件：移除“进行中”头部标注；将核心要素前言中的“打磨前”语句更新为“已打磨细分群体——详见变更日志”；确认KEYSTONES.md中的变更日志（标准标题：
## Change log
）完整记录了打磨过程。收尾时告知用户下一步：寻找触发事件——即促使完全符合核心要素的客户从“可能购买”转向“立即购买”的具体时刻；如果已安装同一作者开发的触发事件技能（例如Inciting Events / 
asb-carol-inciting-events
），告知用户：“准备就绪后，可对这些文件运行
asb-carol-inciting-events
。”

The file structure

文件结构

markdown
undefined
markdown
undefined

Deal-breakers — <company / project name>

交易否决因素 — <公司/项目名称>

⚠️ IN PROGRESS — the walk is not complete. Weaknesses walked: <which W-numbers>; honing: <not started / K-numbers done>. If you are resuming, continue there. (This note is removed at finalization.)
<Two or three lines: which files this works from (name them), and the company context. Deal-breakers disqualify outright and trump keystones; the anti-market is deliberately excluded. Friction items cost points but disqualify no one — they're backlog input, not boundaries.>
⚠️ 进行中——流程尚未完成。已梳理的劣势： <对应的W编号>；打磨进度：<未开始 / 已完成的K编号>。如果继续，请从此处开始。（最终确定时移除本提示。）
<2-3行文字：说明本文件基于哪些文件（列出文件名），以及公司背景。交易否决因素直接淘汰用户，优先级高于核心要素；反市场群体被刻意排除。摩擦点会导致失分但不会淘汰用户——属于待办事项输入，而非市场边界。>

Deal-breakers

交易否决因素

D1. <The disqualifying circumstance.> [W2] Anti-market segments: <who lives there — sharp enough to deliberately exclude in ad targeting and sales qualification.>
D2. <…> [W1]
D1. <淘汰条件。> [W2] 反市场细分群体：<对应的群体——需足够明确，以便在广告定位和销售筛选中刻意排除。>
D2. <……> [W1]

Friction (costs points; disqualifies no one)

摩擦点（导致失分；不淘汰用户）

  • <Weakness> — <one line: who dislikes it, why nobody refuses over it>. [W3]
  • <劣势> — <一句话说明：哪些群体不喜该劣势，以及为何没人会因此拒绝购买。> [W3]

Anti-market statement

反市场声明

<One short paragraph: who is deliberately excluded and the standing instructions — ad language that dissuades them from clicking, and no features built for them, even though they'll ask.>
<一段简短的段落：说明刻意排除的群体及指导原则——使用劝退性广告语言，即便有需求也不为其开发功能。>

Strategy-input list (fix-it ideas parked during the walk)

战略输入列表（流程中记录的“修复”想法）

  • <"We could add X to remove D2" — parked; addressing a new market is a strategy decision, not a qualifier dodge.>
  • <“我们可以添加X来消除D2”——暂存；开拓新市场是战略决策，而非回避限定条件的借口。>

Next steps

下一步

<Two or three sentences of prose: find the inciting events — the specific trigger moments that move a keystone-fit customer from could-buy to buying-today; each couples to a keystone. That's the next step of the method, and it works from the honed KEYSTONES.md; this file's deal-breakers and anti-market feed the final definition step.>

D-numbers are stable once written; descriptions may be sharpened at
any sweep under their frozen numbers (note a post-honing tightening
in the honing keystone's change-log line, since honed qualifiers may
reference it). The KEYSTONES.md edits live under its K-numbers with
change-log lines — a fresh session reads both files and the change
log tells it exactly how far the honing got (a useful header form:
"honing: K1 done — resume at K2").
<2-3行文字：寻找触发事件——即促使符合核心要素的客户从“可能购买”转向“立即购买”的具体触发时刻；每个触发事件对应一个核心要素。这是该方法的下一步，基于已打磨的KEYSTONES.md进行；本文件中的交易否决因素和反市场信息将用于最终定义步骤。>

D编号一旦确定即保持稳定；描述内容可在任何审查阶段进行优化（在核心要素的变更日志中注明打磨后的调整，因为打磨后的限定条件可能会引用该描述）。KEYSTONES.md的编辑内容保留原有K编号并附带变更日志——新会话读取两个文件时，变更日志会明确显示打磨进度（一种实用的头部格式：“打磨进度：已完成K1——从K2开始”）。

Refusal conditions

拒绝执行的情况

  • No weaknesses at all. Deal-breakers derived from vibes exclude the wrong people. Offer the classification step or the caveated quick capture.
  • "We'll fix that weakness, so skip the deal-breaker." Sell what's on the truck: the map describes today; the fix is parked as strategy input. A deal-breaker only leaves the map when the fix has shipped.
  • Friction promoted to deal-breaker for drama (or deal-breaker demoted to friction for comfort). The gate is refusal evidence: someone must actually be disqualified, or nobody actually is. Press once, then record what the evidence supports.
  • Honing qualifiers that dodge. "Serious customers" is not a qualifier; "processing at least $5,000/mo" is. Vague qualifiers get pressed or dropped — a keystone honed with mush is honed with nothing.
  • Building for the anti-market. If the user starts planning features for excluded segments mid-session, name the rule — those requests come from the tail — and park it.
  • Choosing the target segment or writing the definition. Later steps. This one maps the boundary and sharpens the targets.
  • 完全没有劣势信息。 仅凭感觉推导的交易否决因素会错误排除用户。建议执行分类步骤或进行带说明的快速收集。
  • “我们会修复这个劣势，所以跳过该交易否决因素。” 立足现有产品进行定位：市场地图描述的是当前情况；修复想法暂存为战略输入。只有当修复功能上线后，交易否决因素才会从地图中移除。
  • 为了制造戏剧效果将摩擦点提升为交易否决因素（或为了自我安慰将交易否决因素降为摩擦点）。 判断标准是拒绝证据：必须确实存在被淘汰的用户，或者确实没有。验证一次后，根据证据记录结果。
  • 回避实质问题的打磨限定条件。 “优质客户”不是有效的限定条件；“每月处理至少5000美元交易”才是。模糊的限定条件需被验证或删除——用模糊内容打磨的核心要素等同于未打磨。
  • 为反市场群体开发功能。 如果用户在会话中开始计划为被排除群体开发功能，需明确规则——这些需求来自尾部客户群体——并将想法暂存。
  • 选择目标细分群体或撰写最终定义。 这些是后续步骤的内容。本步骤仅用于划分市场边界和优化目标群体。