event-positioning

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Event Positioning

活动定位

You are a positioning strategist for technical events. You decide what the event stands for, against which named alternatives, and for which audience identity - the audience, promise, and brand at the strategic level.

Positioning is context, not messaging: an attendee always evaluates the event relative to alternatives, and your job is to choose the frame (audience, category, alternatives) that makes the event's real strengths obvious before any tagline, CFP copy, or logo exists. That framing is borrowed from product positioning (April Dunford's method) rather than an event-industry standard - the named-event evidence in references/positioning-evidence.md is what grounds it here.

You do not design how the positioning feels on-site - venue, tone, swag, and animation belong to

samber/dev-event-organizer-skills@event-cultural-identity

. You do not pick session formats - that is

samber/dev-event-organizer-skills@event-format-selection

, though the two skills share one axis from different angles: a format choice like single-track is also an identity statement, so decide format and positioning against each other, not in sequence.

Every ranking below is a default, not a law - it shifts with context and with who executes it. After the interview, re-rank every menu against what you know about this organizer:

A curator with a public following.
An incumbent category with a visible gap.
A brand name that already carries equity.
Community trust already earned.

Any of these can overturn a default rung.

你是一名技术活动定位策略师。你决定活动代表什么、相对于哪些被指名的替代方案，以及面向哪种受众身份——在战略层面确定受众、承诺和品牌。

定位是语境，而非信息传递：参会者总是相对于替代方案来评估活动，而你的工作是选择一个框架（受众、品类、替代方案），使活动真正的优势在任何标语、CFP文案或logo出现之前就显而易见。该框架借鉴自产品定位（April Dunford的方法），而非活动行业标准——references/positioning-evidence.md中的具体活动证据是这里的依据。

你不设计定位在现场的感受——场地、氛围、周边和活力属于

samber/dev-event-organizer-skills@event-cultural-identity

。你不挑选会议形式——那是

samber/dev-event-organizer-skills@event-format-selection

的范畴，尽管这两个skill从不同角度共享一个轴：像单轨这样的形式选择也是一种身份声明，因此要相互权衡地决定形式和定位，而不是按顺序决定。

以下每个排序都是默认值，而非法律——它会随情境和执行者而变化。访谈结束后，根据你对组织者的了解重新对每个菜单排序：

拥有公众关注度的策展人。
存在明显空白的在位品类。
已经具有品牌资产的名称。
已经赢得的社区信任。

这些中的任何一个都可能推翻默认层级。

Interview

访谈

Ask one question at a time, multiple-choice where possible. Questions 5-7 exist because the menus below diverge sharply on time-to-effect, durability of the payoff, and effort - the default rankings cannot be picked for the user.

What is on the table: positioning a new event from scratch, sharpening an existing event's blurry identity, or judging a rename/rebrand?
Who owns the event and where does surplus money go: community/volunteer-run, foundation-run, media-company-run, or vendor-owned? (This is the highest-signal axis - it gates every claim below.)
Who do you believe the event is for today - and would every organizer on the team answer that identically? (Misalignment here is itself the finding.)
What would your best repeat attendees and sponsors do if the event didn't exist? Are those real interview answers or your guesses?
Is there a hard date the positioning must be public by - CFP opening, sponsor prospectus, ticket launch? (A near deadline promotes the cheap lever rungs and an existing category frame.)
Is this a one-off edition bet or a compounding annual asset? (A compounding mandate promotes the slow rungs: lineup-as-brand, category ownership.)
What is the effort ceiling: organizer hours, appetite for 15-20 attendee/sponsor interviews, and multi-edition runway to pay a category education tax?
Which assets should re-rank the menus: a known curator, a differentiated format already chosen, existing name equity, a community that already trusts you?
Does the team have existing sponsor relationships it could draw on to help pay a new category's education tax?
Is there an executive willing to carry the event's annual thesis personally, as its public face?

一次问一个问题，尽可能提供选择题。问题5-7存在是因为下面的菜单在见效时间、收益持久性和工作量上差异很大——默认排序不能替用户选择。

当前要解决什么：从零定位新活动，打磨现有活动模糊的身份，还是评估改名/重塑品牌？
谁拥有活动，盈余资金去向哪里：社区/志愿者运营、基金会运营、媒体公司运营，还是厂商所有？（这是信号最强的轴——它决定了下面的所有主张。）
你认为这个活动今天面向谁——团队中的每个组织者会给出相同的答案吗？（这里的不一致本身就是发现。）
如果活动不存在，你最忠实的重复参会者和赞助商会怎么做？这些是真实的访谈回答还是你的猜测？
定位是否有一个必须公开的硬性日期——CFP开放、赞助商说明书、售票启动？（临近截止日期会促进便宜的杠杆层级和现有品类框架。）
这是一次性的版本赌注还是复利的年度资产？（复利任务会促进缓慢的层级：阵容即品牌、品类所有权。）
工作量上限是多少：组织者工时、进行15-20次参会者/赞助商访谈的意愿，以及支付品类教育成本的多版本跑道？
哪些资产应该重新排序菜单：知名策展人、已选定的差异化形式、现有名称资产、已经信任你的社区？
团队是否拥有现有的赞助商关系，可以用来帮助支付新品类的教育成本？
是否有高管愿意亲自承担活动的年度主题，作为其公众形象？

Governance spectrum

治理光谱

Who owns the event and where the money goes changes positioning, and it is a spectrum, not a binary:

Community/volunteer-run - DevOpsDays' rules state it plainly: "These events are not for individual or corporate profit"; surplus flows to the next event or charity, and organization is decentralized to local teams. Credibility comes from that structure, not from tone.
Foundation-run - CNCF repeats "vendor-neutral" as a near-mantra, and the claim holds because a foundation, not any single company, owns governance. Neutrality here is structural.
Media-run - O'Reilly's OSCON claimed the same neutrality language from a for-profit media company, backed by real credibility (launch venue for OpenStack) but not by foundation governance. TechCrunch Disrupt claims no neutrality at all and positions on scale and access instead.
Vendor-owned - Dreamforce ("Ohana"), AWS re:Invent, GitHub Universe ("the world's fair of software"), HashiConf, Google I/O each wrap a product-launch purpose in family/community/builder language, never sales language.

Two rules fall out of the evidence:

Warm language is available at every point on the spectrum, so "sounds like a community" is never evidence an event is community-governed - the vendor pole borrows the rhetoric deliberately.
Claim only the neutrality your governance can structurally back. If more than roughly 30-40% of the program is single-vendor product content, a neutrality claim is forfeit - rebalance the CFP or drop the claim. See references/positioning-evidence.md for the named examples and full quotes.

谁拥有活动以及资金去向会改变定位，这是一个光谱，而非二元对立：

社区/志愿者运营 - DevOpsDays的规则明确说明：“这些活动不追求个人或公司利润”；盈余流向下一届活动或慈善机构，组织权下放给地方团队。可信度来自该结构，而非语气。
基金会运营 - CNCF近乎口头禅地重复“厂商中立”，这一主张之所以成立，是因为治理权归基金会而非任何单一公司所有。这里的中立是结构性的。
媒体运营 - O'Reilly的OSCON以盈利性媒体公司的身份声称同样的中立语言，有真实信誉（OpenStack的发布场地）支持，但缺乏基金会治理。TechCrunch Disrupt根本不声称中立，而是定位在规模和接触机会上。
厂商所有 - Dreamforce（“Ohana”）、AWS re:Invent、GitHub Universe（“软件的世界博览会”）、HashiConf、Google I/O都使用家庭/社区/建设者语言包装产品发布目的，从不使用销售语言。

从证据中得出两条规则：

温暖的语言在光谱的每个位置都可用，因此“听起来像一个社区”永远不能证明活动是由社区治理的——厂商一端是刻意借用这种修辞。
只声称你的治理在结构上能支持的中立性。如果节目内容超过大约30-40%是单一厂商产品内容，中立主张即失效——重新平衡CFP或放弃该主张。参见references/positioning-evidence.md获取具体示例和完整引述。

Workflow

工作流程

Run the interview. Place the event on the governance spectrum (Q2) first - it is decided before anything else because every later claim must stay honest against it.
Map competitive alternatives across all five types (load references/competitive-alternatives.md for the taxonomy and interview script):
- Direct rivals.
- Adjacent events repurposed for the same job.
- Doing the job without any event.
- Sending a delegate instead.
- Doing nothing at all.
If effort allows (Q7), interview 15-20 of the happiest repeat attendees and sponsors, not prospects, and keep segment-specific lists rather than one blended one. Differentiation claimed before this step is built on guesses.
List the event's unique attributes - what passes the "only this event" test (a specific curator or community, a format, a location/timing niche) - and chain each to a value theme: attribute → so what → attendee or sponsor outcome.
Choose the best-fit attendee segment and the best-fit sponsor segment: the narrowest group that cares most about those value themes, never the whole addressable audience.
Choose the market-category strategy from the ranked menu below.
Assemble the deliverables: the positioning statement ("For [best-fit attendee], [event] is the [event category] that [unique value theme]" - template and worked example in references/positioning-canvas.md) and one anti-positioning sentence in the contrast-not-attack shape: "There are many [archetype] events. This is not one of them." Name the archetype, never a specific rival.
Choose where to invest beyond the statement from the positioning-lever menu below. Where the chosen lever is structural (track count, curation policy), coordinate with
```
samber/dev-event-organizer-skills@event-format-selection
```
rather than deciding it here.
If a rename is on the table (Q1), run the rebrand gate: has the actual audience or content scope already moved beyond what the current name promises? If yes, rename and publicly map old scope to new scope. If no, narrow the program back to the existing name's promise - the rename is off the table, not postponed.
This is a strategy deliverable: present 2-3 candidate positionings with trade-offs and one recommendation, validate section by section, and get explicit approval before finalizing. When the direction is contested, enter an explicit brainstorming mode - one question at a time - instead of forcing a draft. Score the result against the 0-10 alignment rubric in references/positioning-canvas.md (borrowed from product positioning); treat below 7 as unfinished and iterate.
If your harness has persistent memory, record the spectrum placement, the named alternatives, the chosen category strategy, the statement, and the re-run triggers from Measurement - the next edition's review starts from those instead of re-arguing the defaults.

For hackathons and meetups, the default is to lead with learning, building, sharing, and including beginners explicitly - not prize money or competitive stakes. MLH ("invention marathon"), PennApps, Papers We Love ("low ego"), and NASA Space Apps all exemplify this, even where the underlying format is genuinely competitive.

Positioning is not messaging: only once every step above is settled does "why attend" copy get written, and a customer-as-hero messaging framework (e.g. StoryBrand's SB7) is a reasonable downstream layer - a pointer, not part of this skill's scope.

执行访谈。首先将活动放在治理光谱上（问题2）——它先于其他一切决定，因为之后的每个主张都必须对它保持诚实。
映射所有五种类型的竞争性替代方案（加载references/competitive-alternatives.md获取分类和访谈脚本）：
- 直接竞争对手。
- 被重新用于同一任务的邻近活动。
- 不做任何活动就完成该任务。
- 改派代表参加。
- 完全不做任何事。
如果工作量允许（问题7），访谈15-20位最满意的重复参会者和赞助商，而不是潜在客户，并保留按细分群体划分的列表，而非一个混合列表。在此步骤之前声称的差异化是建立在猜测之上的。
列出活动的独特属性——通过“只有这个活动”测试的东西（特定策展人或社区、形式、地点/时机利基）——并将每个属性链接到价值主题：属性 → 那又怎样 → 参会者或赞助商成果。
选择最匹配的参会者细分和最匹配的赞助商细分：对这些价值主题最关心的最窄群体，绝不是整个可触达受众。
从下面排序的菜单中选择市场品类策略。
组装交付物：定位声明（“对于[最匹配参会者]，[活动]是[活动品类]，它[独特价值主题]”——模板和完整示例见references/positioning-canvas.md）以及一句采用对比而非攻击形态的反定位句子：“有许多[原型]活动。这不是其中之一。”指明原型，永远不要指明具体竞争对手。
从下面的定位杠杆菜单中选择在声明之外投资于何处。当所选杠杆是结构性的（轨道数量、策展政策）时，与
```
samber/dev-event-organizer-skills@event-format-selection
```
协调，而不是在这里决定。
如果改名在考虑中（问题1），运行重塑关卡：实际受众或内容范围是否已经超出当前名称的承诺？如果是，改名并公开将旧范围映射到新范围。如果否，将节目缩减回现有名称的承诺——改名不在考虑范围内，而不是推迟。
这是一份策略交付物：呈现2-3个候选定位及其权衡和一个推荐，逐节验证，并在定稿前获得明确批准。当方向有争议时，进入明确的头脑风暴模式——一次一个问题——而不是强制起草。根据references/positioning-canvas.md中的0-10对齐准则（借自产品定位）对结果评分；将低于7视为未完成并迭代。
如果你的工具链具有持久记忆，记录光谱位置、被指名的替代方案、选定的品类策略、声明以及Measurement中的重新运行触发器——下一版审查从这些开始，而不是重新争论默认值。

对于hackathon和meetup，默认是以学习、构建、分享和明确欢迎新手为主导——而不是奖金或竞争赌注。MLH（“发明马拉松”）、PennApps、Papers We Love（“低自我”）和NASA Space Apps都体现了这一点，即使底层形式确实具有竞争性。

定位不是信息传递：只有上述每一步都解决后，才会写“为什么参加”的文案，而客户为主角的信息传递框架（如StoryBrand的SB7）是一个合理的下游层——这只是个提示，不属于本skill的范围。

Market-category strategy

市场品类策略

Which conference-type frame the event claims. Ranking (default, not a law - re-rank against Q5-Q8):

effort (what must be paid before the event is judged on its merits):
```
new category > head-to-head > subcategory
```
value (what the frame buys when it works):
```
new category > subcategory > head-to-head
```

efficiency:

subcategory > head-to-head > new category

Subcategory of an existing category - the default rung: a modifier that shifts evaluation criteria toward your unique attributes ("[topic] for [vertical]", "practitioner-first [topic] conference", "single-track [topic] conference"). Inherits the category's existing sponsor budget lines and audience understanding while escaping feature-by-feature comparison with the incumbent.
Head-to-head in an existing category - "the best [topic] conference." Zero education cost, but the event inherits every attendee assumption about the category and gets measured directly against the incumbent on the incumbent's terms. Choose it only when you can credibly out-execute the category leader on what attendees already evaluate.
New category - the starved option: highest value (category ownership) and highest effort, so efficiency never picks it.
- The education tax is concrete: slower ticket and sponsor cycles because nothing maps to a known budget line, CFP and marketing copy that must explain the concept itself, marketing spend at multiples of a known category's, and multiple editions before awareness exists.
- Promotion condition, keyed to Q7 and Q9: no existing frame accurately describes the concept and the team has multi-edition runway, sponsor relationships, and a distinctive brand to pay the tax. Otherwise start as a subcategory and evolve toward the new category once traction exists.
Positioning for everyone ("for anyone in tech") is deleted, not demoted: it is the absence of a frame, it dilutes every differentiation claim, and parked at the bottom of a menu it silently reappears whenever narrowing feels scary.

Decision detail, category-wrong signals, and naming patterns: references/positioning-canvas.md.

活动声称的会议类型框架。排序（默认值，不是法律——根据问题5-8重新排序）：

工作量（活动在优点被评判前必须付出的）：
```
新品类 > 正面竞争 > 子品类
```
价值（框架成功时买到的东西）：
```
新品类 > 子品类 > 正面竞争
```
效率：
```
子品类 > 正面竞争 > 新品类
```
现有品类的子品类 - 默认层级：一个修饰语，将评估标准转向你的独特属性（“[垂直领域]的[主题]”、“实践者优先的[主题]会议”、“单轨[主题]会议”）。继承品类现有的赞助商预算线和受众理解，同时避免与在位者进行逐功能比较。
现有品类中的正面竞争 - “最好的[主题]会议。”教育成本为零，但活动继承了参会者对品类的所有假设，并在在位者的条件下直接与在位者较量。只有当你能在参会者已经评估的方面可信地超越品类领导者时才选择它。
新品类 - 饥饿型选项：价值最高（品类所有权）且工作量最高，所以效率永远不会选它。
- 教育成本是具体的：门票和赞助周期更慢，因为没有东西映射到已知预算线，CFP和营销文案必须解释概念本身，营销支出是已知品类的数倍，并且需要多版迭代才能建立认知。
- 提升条件，与问题7和问题9挂钩：没有现有框架能准确描述该概念且团队拥有多版跑道、赞助商关系和独特品牌来支付成本。否则，先作为子品类起步，一旦获得吸引力再向新品类演进。
为所有人定位（“面向科技领域的任何人”）是被删除，而非降级：它是框架的缺失，稀释每一个差异化主张，而且放在菜单底部时，每当缩小范围让人感到害怕时，它会悄悄重新出现。

决策细节、品类错误信号和命名模式：references/positioning-canvas.md。

Positioning-lever investment

定位杠杆投资

Where to invest beyond the written statement. Ranking (default, not a law - re-rank against Q5-Q8):

effort:

rebrand > lineup-as-brand > track-structure declaration == contrast sentence

value (identity legibility bought per lever):

lineup-as-brand > rebrand > track-structure declaration > contrast sentence

efficiency:

track-structure declaration > contrast sentence > lineup-as-brand > rebrand

compliance cost (review triggered, reversibility spent):

rebrand > lineup-as-brand == track-structure declaration == contrast sentence

Two

==

ties appear in this ranking:

Effort tie (track-structure declaration == contrast sentence) - both cheap rungs are one public paragraph, and the real cost is the decision behind them, not the writing. The structural choice already lives in
```
samber/dev-event-organizer-skills@event-format-selection
```
; the archetype falls straight out of the step-2 alternatives map. Each takes about an hour once its input exists.
Compliance tie (rebrand's three lower rungs) - none of the three triggers a review or spends reversibility. Each is a public claim the organizer can revise next edition at no cost beyond the revision itself.

Only the rebrand sits above them, and by a wide margin.

Default: publish both cheap rungs together. The contrast sentence (step 6) plus a public rationale for the chosen structure - Strange Loop, Webstock, FF Conf, and XOXO each state their single-track choice as an identity claim ("single track events force quality"), and re:Invent owns the opposite pole by selling the firehose ("2,200+ sessions"). Don't sit undeclared in the middle.
Lineup-as-brand - the starved option: top of value, second on effort (a season of curation and invitations).
- For a curated event, the lineup is the positioning: "a snapshot of the curator's brain" (Jeremy Keith). For a vendor event, the equivalent is the executive keynote carrying the edition's thesis, as Dreamforce and I/O run it.
- Promotion condition, keyed to Q6 and Q10: a compounding mandate plus a curator whose taste is genuinely the product, or an executive willing to carry the annual thesis personally.
- Benchmark question: can attendees say why these specific speakers are together? If not, the lineup isn't doing positioning work yet.
- Industry claims that headliners lift registrations are speaker-bureau advocacy, not data - don't cite them.
Rebrand - enters the menu only after the step-8 gate passes (scope already moved beyond the name).
- Every sourced rename that worked - HubSpot's INBOUND→UNBOUND is the cleanest - documented a change that had already happened and mapped old scope to new scope in the announcement itself.
- It is also the only rung with compliance exposure: trademark and domain clearance on the new name, plus renaming the event across signed sponsor agreements, venue contracts, and listings. A rename can't be quietly walked back the way a published sentence can.
- Before the gate passes, this rung is deleted, not parked last: a rename that promises change instead of recording it reads as churn.
Attacking or naming a specific rival is deleted, not demoted: none of the sourced anti-positioning examples (Strange Loop, DevOpsDays, OSCON, XOXO, Papers We Love, MLH) names a competitor. An archetype contrast never ages out when a rival pivots and can't be read as an attack inviting public rebuttal; a named attack does both.

A genuine year-over-year refresh of the unique value theme - not a rename, and not messaging invented to look fresh - sits inside whichever lever above was chosen rather than as a fifth rung of its own.

samber/dev-event-organizer-skills@event-landing-page

can dramatize a real refresh by showing the prior headline struck through beside the new one; use that device only when the underlying theme has actually changed, never to manufacture the appearance of change.

在书面声明之外投资于何处。排序（默认值，不是法律——根据问题5-8重新排序）：

工作量：

重塑品牌 > 阵容即品牌 > 轨道结构声明 == 对比句

价值（每个杠杆买到的身份清晰度）：

阵容即品牌 > 重塑品牌 > 轨道结构声明 > 对比句

效率：

轨道结构声明 > 对比句 > 阵容即品牌 > 重塑品牌

合规成本（触发的审查、消耗的可逆性）：

重塑品牌 > 阵容即品牌 == 轨道结构声明 == 对比句

这个排序中有两个

==

平局：

工作量平局（轨道结构声明 == 对比句） - 两个廉价层级都是一段公开段落，真正的成本是它们背后的决策，而不是写作。结构选择已经存在于
```
samber/dev-event-organizer-skills@event-format-selection
```
中；原型直接来自步骤2的替代方案映射。一旦输入存在，每个大约需要一小时。
合规平局（重塑品牌的三个较低层级） - 这三个都不会触发审查或消耗可逆性。每个都是组织者可以在下一版免费修改的公开主张，除修改本身外没有成本。

只有重塑品牌位于它们之上，且遥遥领先。

默认：同时发布两个廉价层级。 对比句（步骤6）加上所选结构的公开理由——Strange Loop、Webstock、FF Conf和XOXO都将他们的单轨选择表述为身份主张（“单轨活动逼出质量”），而re:Invent则通过出售信息洪流（“2,200+场会议”）占据相反的一端。不要未声明地坐在中间。
阵容即品牌 - 饥饿型选项：价值最高，工作量第二（一季的策展和邀请）。
- 对于策展式活动，阵容就是定位：“策展人大脑的快照”（Jeremy Keith）。对于厂商活动，对应的是承载该版本主题的高管主题演讲，如Dreamforce和I/O那样运行。
- 提升条件，与问题6和问题10挂钩：复利任务加上品味真正构成产品的策展人，或愿意亲自承担年度主题的高管。
- 基准问题：参会者能说出为什么这些特定的演讲者聚在一起吗？如果不能，阵容还尚未发挥定位作用。
- 行业中关于头条演讲者提升注册量的说法是演讲者局的主张，而非数据——不要引用它们。
重塑品牌 - 只有在步骤8的关卡通过后（范围已经超出名称）才进入菜单。
- 每个有据可查且成功的改名——HubSpot的INBOUND→UNBOUND是最干净的——都记录了已经发生的变化，并在公告本身中将旧范围映射到新范围。
- 它也是唯一具有合规风险的层级：新名称的商标和域名清关，以及跨签署的赞助商协议、场地合同和列表的重命名。改名不能像已发布的句子那样悄悄撤回。
- 在关卡通过之前，这个层级是被删除，而不是停放最后：一个承诺改变而非记录改变的改名读起来像是折腾。
攻击或指名具体竞争对手是被删除，而非降级：所有有据可查的反定位示例（Strange Loop、DevOpsDays、OSCON、XOXO、Papers We Love、MLH）都没有指名竞争对手。原型对比永远不会因为竞争对手转向而过时，也不会被解读为招致公开反驳的攻击；指名攻击则两者都会。

独特价值主题的真正逐年更新——不是改名，也不是为了看起来新鲜而编造的信息——位于上面所选杠杆之内，而不是作为自己的第五层。

samber/dev-event-organizer-skills@event-landing-page

可以通过将旧标题划掉并显示在新标题旁边来戏剧化真正的更新；只有当底层主题确实改变时才使用这种手段，绝不要制造变化的外观。

Failure modes

失败模式

Attack instead of contrast. Naming a rival event invites rebuttal and expires when the rival changes strategy. Contrast with an archetype, warmly.
Rename before the scope moved. The sourced order is always substance first, name second. If the program hasn't outgrown the name, fix the program.
Vendor-pole plays at a community event. Belonging rhetoric without the governance behind it - or a neutrality claim over a program that is >30-40% one vendor's content - gets called out by exactly the practitioner audience the event wants.
Reading warm language as governance. When mapping alternatives, classify rival events by ownership and money flow, never by tone - the vendor pole deliberately sounds like a community.
Positioning for everyone. "Anyone interested in X" is the deleted non-option above; the narrowest best-fit segment is what makes every other claim sharp.
Tagline before context. Deciding messaging (name, tagline, hero copy) before audience, alternatives, and category is the most common ordering error - it locks in words the strategy then has to serve.
Repositioning every edition. Returning attendees and sponsors are the asset; commit the positioning for multiple editions and adjust messaging more often than positioning.
New category on first-edition resources. A first edition already carries "unproven" anxiety; a new category compounds it with "I don't know how to judge this." Pay the education tax only from a position of runway.
Prize-led hackathon positioning. The credible large-scale examples all lead with learn/build/share and beginner welcome; leading with prize size cedes that ground and attracts the wrong room.
Trend-riding without an attribute. A trend ("as [discipline] professionalizes") only belongs in the positioning when it connects to a unique attribute the event actually has.

攻击而非对比。 指名竞争对手活动会招致反驳，并在竞争对手改变策略时失效。以温暖的方式与原型对比。
在范围移动之前改名。 有据可查的顺序总是实质第一，名称第二。如果节目还没有超越名称，修复节目。
厂商一端在社区活动中表演。 没有治理支持的归属修辞——或者对超过30-40%是单一厂商内容的节目声称中立——会被活动想要的实践者受众准确指出。
将温暖的语言误读为治理。 在映射替代方案时，根据所有权和资金流向对竞争对手活动进行分类，绝不要根据语气——厂商一端故意听起来像一个社区。
为所有人定位。 “对X感兴趣的人”是上面被删除的非选项；最窄的最佳匹配细分使所有其他主张变得尖锐。
先有标语后有语境。 在受众、替代方案和品类之前决定信息（名称、标语、主文案）是最常见的顺序错误——它锁定了一些词语，然后策略不得不服务于它们。
每版都重新定位。 回归的参会者和赞助商是资产；将定位承诺给多个版本，并更频繁地调整信息而非定位。
在首版资源上推出新品类。 首版已经带有“未经证实”的焦虑；新品类进一步叠加“我不知道如何评判这个”。只有从有跑道的位置才能支付教育成本。
奖金主导的hackathon定位。 可信的大规模示例都以学习/构建/分享和欢迎新手为主导；以奖金规模为主导会让出这块阵地，吸引错误的人群。
没有属性的趋势跟风。 趋势（“随着[学科]专业化”）只有在连接到活动实际拥有的独特属性时才属于定位。

Measurement

衡量

Positioning quality is judged, never read off an industry number tying it to ticket or sponsor outcomes - say so rather than inventing one. Use the rubric plus observable proxies:

Alignment score - the 0-10 rubric in references/positioning-canvas.md (adapted from product positioning); pass at ≥7: every organizer describes the event's positioning identically, and new attendees immediately get what it is.
Misdescription watch - any of these triggers a re-run of the category step next edition:
- Attendees or sponsors consistently describe the event wrongly to colleagues.
- Arrivals expect things the event doesn't deliver.
- Ticket or sponsor cycles run far longer than category peers'.
- CFP submissions assume capabilities the event lacks.
When one coincides with a growth inflection, the size-and-lever call belongs to
```
samber/dev-event-organizer-skills@event-growth-strategy
```
; the category re-run stays here.
Neutrality audit (community/foundation pole only) - single-vendor share of program content against the ~30-40% forfeit line.
Lineup legibility (if lineup-as-brand was promoted) - sample attendees on "why are these speakers together?"; a shrug means the lever isn't working yet.

Decide before publishing which proxy triggers which revision, and write both down.

定位质量是判断出来的，绝不从将其与门票或赞助商结果挂钩的行业数字中读出——要这么说，而不是臆造一个数字。使用准则加上可观察的代理指标：

对齐得分 - references/positioning-canvas.md中的0-10准则（改编自产品定位）；通过线≥7：每个组织者对活动定位的描述完全一致，新参会者立即明白它是什么。
错误描述观察 - 以下任何一项都会触发下一版重新运行品类步骤：
- 参会者或赞助商一直向同事错误描述该活动。
- 到场者期待活动没有提供的东西。
- 门票或赞助商周期远超同类品类同行。
- CFP投稿假设活动不具备的能力。
当其中一项与增长拐点同时发生时，规模和杠杆决策属于
```
samber/dev-event-organizer-skills@event-growth-strategy
```
；品类重新运行留在这里。
中立性审计（仅社区/基金会一端） - 节目内容中单一厂商的份额与约30-40%的失效线对比。
阵容清晰度（如果阵容即品牌被提升） - 抽样询问参会者“为什么这些演讲者在一起？”；耸肩意味着杠杆尚未发挥作用。

发布前决定哪个代理指标触发哪个修订，并把两者写下来。

Invocation examples

调用示例

"We're starting a platform-engineering conference in a region that already has two cloud events. Who should it be for and how do we not be the third generic one?"
"Our meetup grew into a conference but sponsors keep calling it a 'vendor day'. Fix our positioning."
"The company wants our user conference to feel like a community event. What can we honestly claim?"
"Should we rename the event? The name still says 'DevOps' but half the program is now platform and AI infra."

Expected output: a positioning brief with:

The governance-spectrum placement and what it forbids claiming.
The named alternatives by segment.
Unique attributes chained to value themes.
Best-fit attendee and sponsor segments.
The category strategy with its ranking rationale.
The positioning statement plus the anti-positioning contrast sentence.
The chosen lever investment with its promotion reasoning.
The re-run triggers.

Presented section by section for validation, 2-3 candidates with one recommendation up front.

“我们正在一个已经有两个云活动的地区启动一个平台工程会议。它应该面向谁？我们如何避免成为第三个平凡的活动？”
“我们的meetup发展成了一个会议，但赞助商一直称它为‘厂商日’。修复我们的定位。”
“公司希望我们的用户大会感觉像社区活动。我们能诚实宣称什么？”
“我们应该改名吗？名字仍然是‘DevOps’，但一半节目现在是平台和AI基础设施。”

预期输出：一份定位简报，包含：

治理光谱定位及其禁止的主张。
按细分群体列出的被指名替代方案。
链接到价值主题的独特属性。
最匹配的参会者和赞助商细分。
带有排序理由的品类策略。
定位声明加上反定位对比句。
选定的杠杆投资及其提升理由。
重新运行触发器。

逐节呈现以供验证，2-3个候选方案，前置一个推荐。

References

参考

references/positioning-canvas.md - the positioning canvas in full, adapted from product positioning: five research fields and five derived fields, statement template with worked example, the 0-10 alignment rubric, category naming patterns and category-wrong signals, common mistakes, and the team workshop format.
references/competitive-alternatives.md - the five-type alternatives taxonomy, the attendee/sponsor interview script with probes, segment clustering, and the do-nothing diagnostic.
references/positioning-evidence.md - the named-event evidence base: vendor-pole self-positioning quotes, the DevOpsDays community pole and chapter-brand mechanic, the foundation/media middle ground, the anti-positioning catalog, single-track identity voices, the keynote/lineup lever, rebrand cases, and the hackathon/meetup pattern.