asb-carol-keystones

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Keystones: Who Needs an Extreme Version of What You're Best At

关键要素（Keystones）：谁迫切需要你最擅长领域的极致版本

Passionate purchase decisions don't come from sort-of liking a few features. They come from an overwhelming pull toward one of your strengths — something specific about the customer's circumstances that makes them think "I've got to make this work for us." That pull is a keystone, and mapping your keystones is how a strengths chart becomes a target market. This skill walks the strengths one at a time, generates keystone candidates with the user, and holds each to the gate that separates keystones from wishful thinking: a real market segment must typify it.

客户的冲动购买决策并非源于对几个功能的些许喜爱，而是源于对你某一项优势的强烈认同——客户所处的特定场景让他们觉得“我们必须用上这个”。这种吸引力就是关键要素（keystone），而梳理关键要素正是将优势图表转化为目标市场的核心方法。本流程会逐一梳理各项优势，与用户一同生成候选关键要素，并通过一道关卡筛选出真正的关键要素：必须有真实的细分市场能够作为其典型代表。

The mental model

思维模型

What a keystone is

什么是关键要素

A keystone is the critical characteristic that drives a customer's desire for the product — the thing that grabs their attention even in a noisy world, even while other trade-offs are in flux. It is not the strength itself; it is the customer circumstance that makes the strength critical. "Fast website" is a strength. "Has a website where even 0.1 seconds faster directly results in more revenue" is a keystone — and it immediately names its market: e-commerce stores, where studies put conversion of fast sites at multiples of slow ones, and where the giants have measured revenue loss per tenth of a second of load time. Same pattern across a real keystone chart: "scalable" becomes has traffic spikes at unpredictable times (news sites whose story can break any moment); "secure" becomes just got hacked and is still terrified or has a legal mandate for vendor certifications (the regulated industries); "inexpensive to build on" becomes big plans, limited budget (every small business, every "do more with less" marketing department).

关键要素是驱动客户购买产品的核心特征——它能在嘈杂的环境中抓住客户的注意力，即便其他权衡因素不断变化。它并非优势本身，而是让该优势变得至关重要的客户场景。“网站加载速度快”是一项优势，而“网站每快0.1秒就能直接提升营收”则是关键要素——这同时也明确了对应的市场：电商店铺，相关研究表明，快速加载的网站转化率是慢速网站的数倍，行业巨头甚至测算过每慢0.1秒造成的营收损失。真正的关键要素图表都遵循这一模式：“可扩展性”对应“存在不可预测的流量峰值”（随时可能突发热点新闻的新闻网站）；“安全性”对应“刚遭遇过黑客攻击仍心有余悸”或“有法规要求供应商具备相关认证”（受监管行业）；“开发成本低”对应“规划宏大但预算有限”（所有小型企业、所有追求“用更少资源做更多事”的营销部门）。

The generative question

生成式问题

For each strength, ask: what characteristics, behaviors, or circumstances REQUIRE an extreme version of this strength? Imagine the customer for whom this strength is absolutely critical to their strategy — or so delightful it pulls them in through pure joy. Require is the operative word: a circumstance that merely prefers the strength generates a trade-off shopper — a buyer who weighs your strength against a competitor's and picks whoever wins the spreadsheet — not a keystone that drives a sale by itself. (Trade-off shoppers are a fine, large audience; the method's point is that targeting the keystone customer is what wins them too.)

针对每项优势，提出问题：**哪些特征、行为或场景迫切需要该优势的极致版本？**想象一下，对于哪些客户而言，这项优势对他们的战略至关重要——或是带来极致愉悦感，让他们主动选择你的产品。这里的核心词是“迫切需要”：如果某个场景只是“偏好”该优势，只会产生权衡型买家——这类买家会在你的优势和竞品之间反复比较，最终选择性价比最高的那一个——而无法仅凭该优势促成购买。（权衡型买家是庞大且优质的受众；本方法的核心在于，瞄准关键要素对应的客户，也能赢得这类买家。）

The gate: no segment, no keystone

关卡：无细分市场，则无关键要素

After naming a keystone candidate, describe real-world examples of companies or people who embody it. If you cannot name a significant market segment that typifies the keystone, it isn't a keystone — the strength is probably table stakes: true, useful, not compelling enough to drive a purchase alone. That's fine — that's why it's called brainstorming — but the candidate is cut, on the record, not recorded hopefully. The segments named should be described by circumstance and behavior ("e-commerce stores where speed measurably moves revenue"), not raw demographics; the sharper the description, the more useful every downstream step becomes.

提出候选关键要素后，描述能体现该要素的真实企业或个人案例。如果无法指出一个具有规模的典型细分市场，那么它就不是关键要素——对应的优势可能只是基础必备项：确实有用，但不足以单独促成购买。这很正常——毕竟这是头脑风暴环节——但该候选要素会被明确剔除，不会被记录下来。描述细分市场时应聚焦场景和行为（如“网站速度直接影响营收的电商店铺”），而非单纯的人口统计数据；描述越精准，后续所有步骤的价值就越高。

Keystones concentrate in the head, not everywhere

关键要素集中于核心客户，而非所有客户

You won't find keystones by asking what your best customers have in common — most of that is common to all your customers, including the worst. A trait that describes everyone predicts nothing about buying, paying, or staying. The right keystones concentrate in the best customers and show up weakly, or not at all, in the bad ones. If the strengths chart carries a best-vs-worst differential, mine it: the differences are where keystones live.

你无法通过询问“优质客户有哪些共同点”找到关键要素——这些共同点大多适用于所有客户，包括劣质客户。一个适用于所有客户的特征，无法预测客户的购买、付费或留存行为。真正的关键要素集中存在于优质客户中，在劣质客户中则很少甚至完全不存在。如果优势图表包含优质客户与劣质客户的差异数据，就深挖这些差异：关键要素就藏在这些差异之中。

The one-keystone verdict

单一关键要素结论

If the walk ends with one keystone — or none — that is not a failed exercise; it is the most valuable strategic lesson available: the product isn't compelling yet. Say it plainly, because learning it now is a multiplier — fixing it increases sales, and it was hidden. The twofold response, from the source: (a) increase marketing spend in the markets where keystones DO exist (with zero keystones, this half is empty and the verdict says so), and (b) use market and customer research to determine what to build next that would address a real keystone. Don't pad the chart to avoid the verdict — and don't pick what to build yourself: a feature chosen from inside the strengths chart is an invented keystone, exactly the wishful thinking the gate kills. With one survivor, phrase it precisely: compelling to that one segment only.

如果梳理后仅得到一个关键要素，甚至没有关键要素，这并非失败的练习，而是最有价值的战略启示：当前产品尚不具备吸引力。请直白地告知用户，因为现在认识到这一点能带来倍增效应——解决这个问题就能提升销量，而之前这个问题是隐藏的。根据方法来源，应对方案分为两部分：(a) 在存在关键要素的市场增加营销投入（若没有关键要素，这部分内容为空，并在结论中说明）；(b) 通过市场和客户调研，确定下一步需要开发什么功能来满足真实的关键要素需求。不要为了回避结论而填充虚假内容——也不要自行决定开发什么功能：从优势图表中凭空挑选的功能，只是臆想的关键要素，正是关卡要剔除的一厢情愿。如果仅存一个关键要素，请精准表述：产品仅对该细分市场具备吸引力。

Why this is worth doing at all

为什么值得做这件事

The customers keystones find are the head of the profit distribution — in the canonical case, roughly 5% of customers producing 40% of profit, which justifies spending many times more to acquire each one. The keystone chart is the map to exactly those customers.

关键要素找到的客户是利润分布的核心——在典型案例中，约5%的客户贡献了40%的利润，这意味着值得投入数倍于普通客户的成本来获取他们。关键要素图表正是找到这些客户的精准地图。

Vocabulary

术语定义

Keystone (K1, K2, …) — a customer characteristic, behavior, or circumstance that requires an extreme version of a strength; cites its [S-number].
Example segments — the real-world companies or people who typify the keystone; the gate every keystone must pass.
Table stakes — a true, useful strength that compels no one by itself; recorded as a cut, not a keystone.
Requires vs. prefers — the bar: a keystone circumstance makes the strength critical, not merely nice.

关键要素（K1、K2……）——让客户迫切需要某一优势极致版本的特征、行为或场景；标注对应的[S编号]。
示例细分市场——能体现关键要素的真实企业或个人；是每个关键要素必须通过的关卡。
基础必备项（table stakes）——真实有用但无法单独促成购买的优势；会被记录为剔除项，而非关键要素。
迫切需要vs偏好——判断标准：关键要素对应的场景让优势变得至关重要，而非仅仅是锦上添花。

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——职业生涯与网站表现紧密相关的企业主”）。对于几天前看过定义的用户来说，单纯的代号难以理解：代号用于追溯，解释用于理解。保留代号以确保准确性；务必补充解释内容。

Generate freely; gate ruthlessly

自由生成，严格筛选

Keystone-finding is brainstorming — propose candidates yourself, liberally, alongside the user's: the imaginative leap from "strength" to "whose circumstance requires this" is exactly where an outside perspective helps. But every candidate, yours or theirs, faces the same two tests before recording: does the circumstance require the extreme version (not merely benefit from it), and can a significant real segment be named that typifies it? Run both visibly. 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 keystone chart with this brief: attack these keystones — find every one whose segment is vague, tiny, or invented; every one where the circumstance merely prefers the strength rather than requiring it; every segment described so broadly it describes everyone. Don't accept wishful or hand-wavy defenses. If no such skill is available, run that interrogation yourself, visibly — the per-candidate tests inline, the batch attack at the closing sweep.

寻找关键要素是头脑风暴环节——请主动提出候选要素，与用户的想法一同讨论：从“优势”到“谁的场景迫切需要它”的思维跳跃，正是外部视角能提供帮助的地方。但每个候选要素，无论是你提出的还是用户提出的，在记录前都必须通过两项测试：对应的场景是否“迫切需要”该优势的极致版本（而非仅仅从中受益），以及能否指出一个具有规模的真实细分市场作为典型代表。请公开进行这两项测试。一种预设的强化方式：如果环境中安装了“魔鬼代言人”式的质疑技能（例如同一作者开发的Rude Q&A /

asb-rude-qa

），请用以下要求对关键要素草稿图表发起质疑：*攻击这些关键要素——找出所有细分市场模糊、规模极小或虚构的要素；找出所有场景仅“偏好”而非“迫切需要”优势的要素；找出所有描述过于宽泛、适用于所有客户的细分市场。不要接受一厢情愿或含糊其辞的辩解。*如果没有此类技能，请自行进行公开质疑——逐一测试每个候选要素，最后进行批量审核。

Press segment descriptions into specifics

细化细分市场描述

"Small businesses" is not a segment description; "e-commerce stores processing enough revenue that a measurable conversion lift pays for premium hosting" is. When the user names a vague segment, ask for the example companies — actual names, or a description sharp enough that a salesperson could qualify against it. Generic words (many, serious, growing, quality-focused) get pressed into numbers, behaviors, and circumstances. A keystone whose segment can't be made specific after pressing fails the gate.

“小型企业”并非合格的细分市场描述；“营收规模足够大，网站转化率提升的收益足以覆盖高级托管成本的电商店铺”才是。当用户提及模糊的细分市场时，请他们提供具体的企业案例——真实名称，或是精准到销售人员可用于筛选客户的描述。将通用词汇（如大量、专业、增长中、注重品质）转化为数字、行为和场景。如果经过细化后仍无法明确细分市场，该关键要素就无法通过关卡。

The user owns the market knowledge

用户掌握市场知识

Whether a named segment is significant, whether those customers really exist, whether the circumstance actually occurs — the user knows their market and their call stands, after one honest press ("you said the head of your customer base is 3+-location groups; this keystone describes single-location shops — who's it for?"). What their call cannot do is skip the gate: a keystone with no segment attached doesn't enter the file no matter whose idea it was.

某个细分市场是否具有规模、这些客户是否真实存在、对应的场景是否真的会发生——用户了解他们的市场，他们的决定是最终结论，但需要先进行一次坦诚的确认（如“你说客户群体的核心是拥有3家及以上门店的企业，但这个关键要素对应的是单店商家——它针对的是谁？”）。但用户的决定不能跳过关卡：无论是谁提出的，没有对应细分市场的关键要素都不会被记录到文件中。

One strength per exchange

每次交流聚焦一项优势

Walk the strengths in order, one per exchange; a strength may yield zero, one, or several keystones, and candidate variants within one strength are one exchange's work. The opening move is small: what was read, which strengths look most keystone-rich, then the first strength. Compress ceremony on request, never structure.

按顺序逐一梳理优势，每次交流聚焦一项；一项优势可能产生0个、1个或多个关键要素，同一优势下的候选要素变体也属于单次交流的内容。开场要简洁：说明你读取的内容、哪些优势看起来更有可能生成关键要素，然后开始处理第一项优势。可根据要求简化流程，但不要改变结构。

How to use this skill

如何使用本流程

Phase A — Ingest

阶段A — 导入

Read the strengths chart (default:

STRENGTHS-WEAKNESSES.md

in the current directory; or pasted). Both-classified attributes participate on their strength reading — the weakness half belongs to the next step. Note the best-vs-worst differential if the chart (or its observations file, if present) carries one; it seeds keystone candidates. If no strengths chart exists, don't refine from nothing: offer the on-ramp — run the classification step first (if a classification skill from this method's author is installed, for example Strengths & Weaknesses /

asb-carol-strengths

, name it), or capture a defensible strengths list in chat now with the caveat that unvetted strengths yield unvetted keystones. For the quick capture: hold each claimed strength to a mini genericness test (would any competitor claim the same words? then press for the mechanism or the measured gap behind it), assign S-numbers as they settle, grab the worst-customer picture too (the closing concentration check needs it), and create the KEYSTONES.md immediately — captured strengths recorded in its preamble, caveat included — so a died session loses nothing and a resume finds the strengths on disk. Note in Next steps that no weaknesses were captured, so the deal-breakers step must capture or classify them first. If a KEYSTONES.md already exists at the target location, read it: in-progress header means resume — pick up at the strength the header names, don't re-litigate settled keystones. Complete means ask whether to revise.

Output:

KEYSTONES.md

in the same directory as the input file. 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

；或直接粘贴内容）。已分类的属性仅考虑其作为优势的部分——劣势部分属于下一步流程。如果图表（或其配套的观察文件）包含优质客户与劣质客户的差异数据，请予以注意：这是生成候选关键要素的重要素材。如果没有优势图表，请勿凭空提炼：提供过渡方案——先运行分类步骤（如果安装了同一作者开发的分类技能，例如Strengths & Weaknesses /

asb-carol-strengths

，请提及该技能），或在聊天中快速收集可靠的优势列表，并附带说明：未经过审核的优势会导致未经过审核的关键要素。快速收集时：对每个声称的优势进行简单的通用性测试（竞品是否也会用同样的表述？如果是，请追问背后的机制或可衡量的差距），确定后分配S编号，同时收集劣质客户的特征（后续的集中度检查需要用到），并立即创建KEYSTONES.md文件——将收集到的优势记录在序言中，并附带说明——这样即使会话中断也不会丢失数据，恢复时可从磁盘中读取优势内容。在下一步计划中说明未收集劣势数据，因此在推导否决因素的步骤中必须先收集或分类劣势数据。如果目标路径下已存在KEYSTONES.md文件，请读取该文件：如果包含“进行中”的标题，则继续——从标题指定的优势开始，不要重新讨论已确定的关键要素；如果文件已完成，则询问是否需要修订。

输出结果：与输入文件同目录下的

KEYSTONES.md

。如果输入内容是粘贴的且未知路径，请先询问方法文件的存储位置（默认：当前目录）——切勿随意分散文件。

Phase B — Walk the strengths

阶段B — 梳理优势

Open small: what you read, which strengths look keystone-rich, any best-vs-worst differential worth mining — then the first strength. Per strength:

Ask the generative question — who requires an extreme version of this? Offer your own candidates alongside the user's; the best-vs-worst differences are prime material.
Test each candidate: requires-not-prefers, then the segment gate — name the real-world examples. Press vague segments into specifics.
Record survivors with [S-number] references and their example segments. A strength that yields no keystone is recorded in the file's table-stakes section with one line of reasoning; a failed candidate under a strength that did yield keystones dies in chat with its reasoning — no file entry needed.
Move to the next strength.

Record to the file as you go. Create

KEYSTONES.md

at the first settled keystone; append after each; keep the header pointer current (strengths walked, current strength). The file is the memory, not the chat. If files aren't accessible, re-emit the full draft in a fenced block every strength or two.

开场简洁：说明你读取的内容、哪些优势看起来更有可能生成关键要素、是否有值得深挖的优质客户与劣质客户差异——然后开始处理第一项优势。

针对每项优势：

提出生成式问题——谁迫切需要该优势的极致版本？在用户的想法之外，提出你自己的候选要素；优质客户与劣质客户的差异是绝佳素材。
测试每个候选要素：先测试是否是“迫切需要”而非“偏好”，再测试细分市场关卡——指出真实案例。将模糊的细分市场描述细化。
记录通过测试的要素：标注对应的[S编号]及示例细分市场。若某一优势未生成任何关键要素，将其记录在文件的“基础必备项”部分，并附上一句理由；若某一候选要素在已生成关键要素的优势下未通过测试，则在聊天中说明理由即可——无需记录到文件中。
处理下一项优势。

边梳理边记录到文件中。在确定第一个关键要素时创建

KEYSTONES.md

；之后每次确定后追加内容；保持标题中的指针更新（已梳理的优势、当前正在处理的优势）。文件是记忆载体，而非聊天记录。如果无法访问文件，每梳理1-2项优势就在代码块中重新输出完整草稿。

Phase C — Sweep and close

阶段C — 全面审核与收尾

Concentration check — for each keystone: would this show up weakly or not at all in your worst customers? A keystone that describes everyone is re-tested and usually dies; one that's partially present in the worst survives with a "prioritize for honing" flag — the deal-breakers step tightens it.
Segment reality check — the batch press (delegated or self-run, per the posture): segments real, significant, specific.
Count the survivors. Two or more solid keystones: proceed. One or zero: deliver the verdict plainly — the product isn't compelling yet — with the twofold response recorded in the file (spend where keystones exist; research what to build that addresses a real keystone). This is a finding to act on, not a failure to soften.

Finalize: remove the in-progress header and close with the handoff. The next step mirrors this one on the weaknesses — deal-breakers and the anti-market — and then hones these keystone segments by appending the qualifiers the deal-breakers force; if a deal-breakers skill from this method's author is installed (for example Deal-Breakers /

asb-carol-dealbreakers

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

asb-carol-dealbreakers

— it works on the weaknesses and then sharpens this file's segment descriptions."

集中度检查——针对每个关键要素：该要素在你的劣质客户中是否很少甚至完全不存在？如果某个关键要素适用于所有客户，则重新测试，通常会被剔除；如果在劣质客户中部分存在，则保留并标注“优先优化”——推导否决因素的步骤会进一步细化该要素。
细分市场真实性检查——批量审核（委托技能或自行进行，遵循准则）：确认细分市场真实、有规模、描述精准。
统计通过测试的要素数量。如果有2个及以上可靠的关键要素：继续推进流程。如果只有1个或0个：直白地给出结论——当前产品尚不具备吸引力——并将两部分应对方案记录在文件中（在存在关键要素的市场投入营销资源；调研开发什么功能来满足真实的关键要素需求）。这是需要采取行动的发现，而非需要淡化的失败。

最终定稿：移除“进行中”的标题，收尾时说明下一步流程。下一步流程会针对劣势部分进行镜像操作——推导否决因素和反市场——然后利用这些否决因素细化关键要素对应的细分市场；如果安装了同一作者开发的否决因素技能（例如Deal-Breakers /

asb-carol-dealbreakers

），请提及该技能：“准备就绪后，运行

asb-carol-dealbreakers

——该流程会处理劣势部分，然后细化本文件中的细分市场描述。”

The file structure

文件结构

markdown

undefined

markdown

undefined

Keystones — <company / project name>

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

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

Keystones

K1. <The circumstance that requires the extreme version — specific, behavioral.> [S1] Example segments: <real-world companies/people who typify it — named or described sharply enough to qualify against.>

K2. <…> [S3] Example segments: <…>

Table stakes (true, but compels no one — cut)

<Strength> — no significant segment requires an extreme version: <one line of reasoning>. [S2]

<Strength> — no significant segment requires an extreme version: <one line of reasoning>. [S2]

Verdict (only when one or zero keystones survive)

<The plain statement — the product is compelling only to <the one segment>, or to no one yet — plus the twofold response: (a) spend where the keystone exists, (b) research what to build that would address a real keystone.>

Next steps


K-numbers are stable once written — later steps cite them and the
deal-breakers step edits this file's segment lines under them. Never
renumber.


K编号一旦确定就保持不变——后续步骤会引用这些编号，推导否决因素的步骤会编辑文件中对应K编号下的细分市场描述。切勿重新编号。

Refusal conditions

拒绝场景

No strengths chart. Keystones derived from unvetted strengths inherit their vagueness. Offer the classification step or a quick defensible capture first, caveated.
A keystone with no segment, however insisted. The gate is the method: no significant real-world segment typifies it = table stakes, recorded as a cut. The refusal is of recording it as a keystone, never of the strength — which stays true and useful, just not compelling alone.
Vague segments. "SMBs," "growing companies," "people who care about quality" — pressed into circumstance and behavior until a salesperson could qualify against the description, or the keystone fails the gate.
Padding to avoid the verdict. When one or zero keystones survive, that verdict is the deliverable. Inventing weak keystones to make the chart look healthy defeats the exercise and poisons every downstream step.
Picking the target segment. Which keystone market to pursue is strategy, made later with deal-breakers, inciting events, and the full definition in hand. This file maps the options; it doesn't choose.
Deal-breakers or the anti-market. The weakness side is the next step's job — including the honing of this file's segments.

无优势图表。基于未审核优势生成的关键要素会继承其模糊性。请先提供分类步骤或快速收集可靠的优势列表，并附带说明。
无对应细分市场的关键要素。关卡是方法的核心：没有具有规模的真实细分市场作为典型代表，就属于基础必备项，记录为剔除项。拒绝的是将其记录为关键要素，而非否定该优势——该优势仍然真实有用，只是无法单独促成购买。
模糊的细分市场。“中小企业”“成长型企业”“注重品质的人群”——必须细化为场景和行为，直到销售人员可用于筛选客户，否则该关键要素无法通过关卡。
为回避结论而填充内容。如果仅存1个或0个关键要素，该结论就是交付成果。编造薄弱的关键要素让图表看起来“健康”，会破坏整个练习的价值，并影响后续所有步骤。
选择目标细分市场。选择哪个关键要素对应的市场进行拓展是战略决策，需要结合否决因素、触发事件和完整的客户定义在后续步骤中确定。本文件仅提供选项，不做选择。
推导否决因素或反市场。劣势部分属于下一步流程的工作——包括细化本文件中的细分市场描述。",