Back to Details

category-of-one-positioning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Use this when the user's business is compared against a shelf of near-identical options and the conversation keeps collapsing to price. Look interchangeable and you get price shopped — it becomes a war on rates. The output is a positioning package with three parts: a new way to frame the problem, category-defining language the market ties to the user, and their expertise packaged as IP. It is built from the user's own words, not your paraphrase — so the flow front-loads a real interview before any reframing. Position comes first — run it before building content engines or outbound on top of it.
当用户的企业被拿来与一众近乎相同的竞品对比，且对话始终围绕价格展开时，可使用此方法。一旦企业看起来与竞品同质化，就会被客户比价，进而陷入价格战。最终输出是一套包含三部分的定位包：重新定义问题的新视角、市场与用户绑定的品类定义语言，以及包装为IP的专业能力。整个定位包基于用户自己的原话构建，而非你的转述——因此在进行任何定位重构前，会先开展一场真实的访谈。定位需优先进行——在搭建内容引擎或拓展 outbound 业务前，先完成定位工作。

1. Diagnose the interchangeability

1. 诊断同质化问题

Research how the user and their closest competitors describe themselves — websites, LinkedIn headlines, service pages. List the words everyone shares ("we help X do Y with Z"). Anything on that list is banned from the final positioning: if the user looks like the other 1,000 options on the shelf, buyers stroll past the shop window.
As you research, capture how the user and the market phrase things word for word — headlines, service-page sentences, the exact language they reach for. You're building two banks at once: the banned shared-language list, and a store of the user's own raw phrasing to reuse in steps 5 and 6. Do not sand their words into cleaner marketing copy — the rough, specific way they say it is the asset.
Then narrow the ICP until the buyer is concrete — named buyer types with a specific sweet spot (industry, stage, revenue band), not "B2B founders." Positioning built for everyone lands with no one. If you can't find the ICP from their website, LinkedIn, materials, or the vault, ask the user directly and wait for the answer before continuing — never invent it. Keep pushing until the buyer is a named type with a sweet spot, not a vague segment.
调研用户及其直接竞争对手的自我描述——官网、LinkedIn 头衔、服务页面。列出所有方共用的话术（例如"我们通过Z帮助X实现Y"）。最终定位中禁止使用这份列表中的任何表述：如果用户看起来和货架上的其他1000个选项别无二致，买家就会直接忽略。
调研过程中，一字不差地记录用户和市场的表述方式——标题、服务页面的句子、他们使用的精准措辞。你需要同时构建两个库：禁用的同质化话术库，以及用户原生措辞库，供步骤5和6复用。不要将他们的话术打磨成更规整的营销文案——他们那种粗糙、具体的表述方式才是核心资产。
随后将理想客户画像（ICP）细化至具体的买家类型——具备明确特征（行业、发展阶段、营收区间）的特定买家，而非笼统的"B2B创始人"。面向所有人的定位最终无法打动任何人。如果无法从用户的官网、LinkedIn、资料或数据库中找到ICP，请直接询问用户并等待答复后再继续——绝对不要自行编造。持续细化，直到买家是具备明确特征的特定类型，而非模糊的群体。

2. Download the brokenness (interview, in their own words)

2. 挖掘行业痛点（访谈，用用户原话）

Before you frame anything, interview the user to get the raw material in their language. This is the deepest data-collection step — don't rush it, and don't answer for them. Work through their industry's pain points one at a time. For each and every pain point, ask these three questions and capture the answers verbatim:
  1. What is broken about your industry right now? Push for depth — the specific thing everyone in the market tolerates, with real examples, not a headline.
  2. Why do you think it's broken? Get their view of the real cause underneath the symptom.
  3. What do you think the solution is? Their fix, in their words.
Loop this for every pain point they raise — one triad per pain point. Keep their exact phrasing; these sentences feed the old-way/new-way reframe and the category language directly, so paraphrasing here quietly waters down everything downstream. If you're working async or the answers aren't already captured (vault, transcripts, prior notes), ask and wait — do not proceed to step 3 on assumptions.
在进行任何定位重构前，先访谈用户，获取其原生话术的原始素材。这是最深入的数据收集步骤——不要仓促推进，也不要替用户作答。逐个梳理他们行业的痛点。针对每一个痛点，依次提出以下三个问题，并一字不差地记录答案：
  1. 当前你的行业存在哪些问题？ 追问细节——市场中所有人都在忍受的具体问题，要有真实案例，而非空泛的标题式表述。
  2. 你认为问题的成因是什么？ 获取他们对症状背后真实原因的看法。
  3. 你认为解决方案是什么？ 用他们自己的话描述解决方案。
针对用户提出的每一个痛点重复上述流程——每个痛点对应一组问题。保留他们的精准措辞；这些表述将直接用于旧模式vs新模式的重构以及品类语言的生成，因此在此处进行转述会悄然削弱后续所有内容的效果。如果是异步协作，或尚未记录答案（数据库、转录稿、前期笔记），请先询问并等待答复——不要基于假设推进到步骤3。

3. Frame the problem: old way vs new way

3. 重构问题：旧模式 vs 新模式

Build this directly from the brokenness download in step 2. Define the contrast between the outdated approach the market accepts and the innovative approach the user represents. Draft it as a sharp two-column contrast: what the old way is, why it quietly fails (their "why it's broken" from step 2), what the new way replaces it with (their "solution" from step 2). The reframe should change what the buyer thinks their problem is — not claim the user does the old thing better. Example of the move: reframing lead generation from "a service you rent" to "infrastructure you own." Test each candidate reframe: would the ICP recognize their situation in the old way, and does the new way make every interchangeable competitor look like the old way?
直接基于步骤2中挖掘的痛点构建内容。明确市场普遍接受的过时方法与用户代表的创新方法之间的差异。将其整理为清晰的两栏对比：旧模式是什么、为何悄然失效（来自步骤2中用户提到的「问题成因」）、新模式如何替代旧模式（来自步骤2中用户的「解决方案」）。重构应改变买家对自身问题的认知——而非声称用户能更好地完成旧模式下的事。重构示例：将获客从"可租用的服务"重构为"可拥有的基础设施"。测试每一个候选重构方案：理想客户画像（ICP）能否在旧模式中识别到自身处境？新模式是否会让所有同质化竞品看起来都属于旧模式？

4. Architect the new way

4. 搭建新模式框架

Before you talk about the result, map how the new way is actually built. Have the user walk you through their real process — the concrete, step-by-step mechanism they use to get the result — and lay it out in order. Process before result: document how it works first, then the outcome it produces, not the other way round. Source this from how they genuinely operate (the interview plus real cases), not an idealized or invented version. This architecture is the backbone of the IP in the next step — a new way with no visible mechanism is just a claim.
在谈论结果之前，先梳理新模式的实际运作方式。让用户带你了解他们真实的流程——实现结果的具体、分步机制——并按顺序罗列。先讲流程，再讲结果：先记录运作方式，再说明产生的结果，顺序不可颠倒。内容来源为他们实际的运营方式（访谈内容加真实案例），而非理想化或编造的版本。这个框架是下一步中IP的核心——没有可见机制的新模式只是一句口号。

5. Package expertise as IP

5. 将专业能力包装为IP

Take the architected process from step 4 and organize it into a named, proprietary system — steps, framework, or method — that reads as the only way to solve the reframed problem. Pull from what's actually proprietary: lived experience, client results, patterns from real engagements. The stack is generic; the data feeding it is proprietary — IP built from the user's real inputs is what competitors can't replicate. Name the system, define its steps (map them to the process from step 4), and attach one real proof point per step where evidence exists.
将步骤4中搭建的流程整理为一个命名的专有体系——步骤、框架或方法——使其成为解决重构后问题的唯一途径。从真正具有专有性的内容中提取：实践经验、客户成果、真实项目中的模式。技术栈是通用的；支撑它的数据才是专有性的——基于用户真实输入构建的IP是竞争对手无法复制的。为该体系命名，定义其步骤（与步骤4中的流程对应），并为每个步骤附上一个已有的真实佐证案例（如有）。

6. Build category-defining language

6. 打造品类定义语言

Turn the reframe into named language the market ties to the user — a name for the problem, the mechanism, and the outcome that doesn't previously exist in their market's feed. Start from the user's own phrasing captured in steps 1–2: where they already say it sharply, keep their words rather than inventing new ones — the market should hear them. Draft 5–10 candidate phrases; keep the ones that are short, concrete, and repeatable in a LinkedIn post, a DM, and a sales call without explanation. The goal is that when the buyer hits this problem, the user's name is attached to the words they think in.
将重构内容转化为市场与用户绑定的命名语言——问题、机制、结果的专属名称，这些名称此前未出现在他们的市场语境中。从步骤1-2中记录的用户原生措辞入手：如果他们的表述已经十分精准，就保留原话，而非创造新表述——市场应该听到他们的声音。草拟5-10个候选表述；保留那些简短、具体、无需解释即可在LinkedIn帖子、私信和销售电话中重复使用的表述。目标是当买家遇到该问题时，会将用户的名字与他们想到的措辞关联起来。

7. Assemble and pressure-test

7. 整合与压力测试

Deliver the package: problem reframe (old way vs new way), the architected new way (process before result), category language glossary, named IP with steps, and a rewritten one-liner + LinkedIn headline built from them. Pressure-test before shipping: read it against the competitor language list from step 1 — zero shared phrases; check every claim traces to something true about the user's track record; confirm the language traces back to the user's own words from steps 1–2; confirm the new way leads with its mechanism before its result; confirm the ICP from step 1 would feel seen, not addressed generically.
交付完整定位包：问题重构（旧模式vs新模式）、搭建完成的新模式框架（先流程后结果）、品类语言术语表、带步骤的命名IP，以及基于上述内容重写的一句话介绍+LinkedIn头衔。交付前进行压力测试：对照步骤1中的竞品话术列表检查——确保没有使用任何共用表述；确认每一项主张都能追溯到用户真实的过往记录；确认所有语言都源自步骤1-2中用户的原话；确认新模式先展示机制再展示结果；确认步骤1中的理想客户画像（ICP）能从中感受到被精准触达，而非被笼统对待。

What good looks like

优秀输出的标准

A great output makes the user the only option, not a better option — a buyer reading it thinks "this is a different thing," not "this one seems good too." It sounds like the founder — built from their own words in the interview, not generic marketing language pasted over their business. The problem reframe is the load-bearing part; weak outputs skip the interview and jump straight to a clever tagline, which is just the old positioning in new words. The new way shows its mechanism before its result — you can see how it's built, not just what it promises. Category language is tight enough to repeat unprompted; if a phrase needs a paragraph of explanation, cut it. The IP feels inevitable — its steps map to how the user actually gets results, not an invented acronym. Average outputs describe the user's services differently; great outputs change what the buyer believes their problem is, so competing on rates stops being possible.
优秀的输出会让用户成为唯一选择，而非更好的选择——买家看到后会觉得「这是完全不同的东西」，而非「这个看起来也不错」。它听起来就像创始人本人的表述——基于访谈中的原话构建，而非将通用营销话术套用到他们的业务上。问题重构是核心支撑；劣质输出会跳过访谈直接跳到巧妙的标语，这只是换了新话术的旧定位。新模式先展示机制再展示结果——你能看到它的运作方式，而非只看到承诺的结果。品类语言足够凝练，可随时重复使用；如果某个表述需要一段文字来解释，就删掉它。IP看起来是顺理成章的——其步骤与用户实际取得成果的方式一致，而非编造的缩写。普通输出只是用不同方式描述用户的服务；优秀输出会改变买家对自身问题的认知，从而让价格战不再可能。

Rules

规则

  • MUST interview the user for the brokenness — what's broken, why, and their solution — for each pain point (step 2) before building the old way vs new way. NEVER skip the interview and jump to the reframe.
  • MUST ask the user for the ICP if you can't find it, and wait for the answer. NEVER invent the ICP.
  • MUST capture and reuse the user's own phrasing throughout. NEVER sand their words into generic marketing language.
  • MUST map the actual process that produces the result before presenting the result (process before result).
  • MUST ground every claim, proof point, and case reference in real results the user confirms. NEVER fabricate metrics, client names, or credentials.
  • MUST get the user's approval on the reframe before building language and IP on top of it — everything downstream inherits it.
  • NEVER reuse phrases from the competitor language list in the final package.
  • NEVER position against a named competitor directly; position against the old way.
  • 必须先针对每个痛点访谈用户，挖掘行业问题、成因及解决方案（步骤2），再构建旧模式vs新模式。绝对不要跳过访谈直接进行重构。
  • 如果无法找到理想客户画像（ICP），必须询问用户并等待答复。绝对不要自行编造ICP。
  • 必须全程记录并复用用户的原生措辞。绝对不要将他们的话术打磨成通用营销文案。
  • 必须先梳理产生结果的实际流程，再展示结果（先流程后结果）。
  • 必须将每一项主张、佐证案例和客户参考都基于用户确认的真实成果。绝对不要编造数据、客户名称或资质。
  • 必须在基于重构内容打造语言和IP前，获得用户对重构方案的认可——后续所有内容都基于此重构。
  • 绝对不要在最终定位包中使用竞品话术列表中的任何表述。
  • 绝对不要直接对标具体竞争对手；要对标旧模式。