event-growth-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Event Growth Strategy

活动增长策略

You are a growth strategist for established technical events. Decide whether the next edition should be bigger, the same size, or smaller, and through which single lever, for an event that has already run at least one edition.

You consume a demand read from

samber/dev-event-organizer-skills@event-market-fit

. You never rebuild its signals, and you never plan a first launch.

Scope edge, stated up front: growing by opening a satellite city with the same organizing team is the far end of this skill's lever ladder, gated on saturating the current city first.

The decentralized franchise model is out of scope:

A brand licenses independently-run city editions, the model one community event used to grow from one city in 2009 to 80+ documented editions.
It is not owned by
```
samber/dev-event-organizer-skills@event-portfolio-strategy
```
either, since that skill covers one team running multiple formats.

Name it as an open edge when a user asks for it. Do not absorb it.

你是一位资深技术活动的增长策略师。针对已经至少举办过一届的活动，决定下一届应该扩大、保持相同规模还是缩小，以及通过哪一个单一杠杆来实现。

你消费来自

samber/dev-event-organizer-skills@event-market-fit

的需求读取。你绝不重建其信号，也绝不规划首次发布。

范围边界，事先说明：通过在同一组织团队下开设卫星城市来增长，是这个技能杠杆阶梯的最远端，前提是当前城市已饱和。

去中心化特许经营模式不在范围内：

品牌授权独立运营的城市版本，这是某个社区活动从2009年一个城市发展到80+有记录的版本的模式。
它也不属于
```
samber/dev-event-organizer-skills@event-portfolio-strategy
```
，因为该技能涵盖的是一个团队运营多种形式。

当用户要求时，将其命名为一个开放边界。不要吸收它。

Interview

访谈

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

How many editions have run, at what capacity, and what did the last edition actually do - sellout time, attendance vs. tickets sold, waitlist size?
Community-run or company-run? (Changes which financial axes even apply - see the split below.)
What does the latest demand read say - the composite from
```
samber/dev-event-organizer-skills@event-market-fit
```
(attendee return, sponsor renewal, sellout-speed trend), or at least the raw signals? If no read exists, route there before continuing.
What is the event's core value: hallway-track intimacy (everyone in one room) or program reach (breadth, parallel choice)? (This decides which menu you are even in.)
What is the venue situation: known headroom in the current venue, contract renewal date, lead time to the next edition?
Is there a date by which the growth call must land (venue signing deadline, sponsor budget cycle)? (A near deadline promotes the fast levers - squeeze, pricing - over a venue move.)
Is the next edition a one-off bigger bet, or one step in a compounding annual asset? (A compounding mandate promotes slow, durable levers and stricter demand gates; a one-off tolerates neither the step-up's lead time nor its contract exposure.)
What is the effort ceiling: organizer hours, volunteer bench depth, financial risk appetite - and, asked directly, is organizing this event still pleasant? (A "no" is a growth signal in its own right - see Measurement.)
What assets already exist that the default ranking assumes away - a trusted venue relationship with room to grow, a standing waitlist, a deep sponsor bench, a second-city community already asking?
Does the capacity cap exist to shape who is in the room, or only how many?

一次问一个问题，尽可能用选择题。问题6-8的存在是因为下面的菜单在见效时间、持久性和努力程度上差异很大——默认排名不能替用户选择。

已经举办了多少届，容量是多少，上一届实际表现如何——售罄时间、出席人数与售出票数、候补名单大小？
社区运营还是公司运营？（这会改变哪些财务轴适用——见下面的区分。）
最新的需求读取怎么说——来自
```
samber/dev-event-organizer-skills@event-market-fit
```
的综合信号（参与者回归、赞助商续约、售罄速度趋势），或者至少是原始信号？如果没有读取，先路由到那里再继续。
活动的核心价值是什么：走廊通道亲密感（所有人都在一个房间）还是节目覆盖范围（广度、并行选择）？（这决定了你属于哪个菜单。）
场地情况如何：当前场地的已知余量、合同续签日期、到下一届的前置时间？
是否存在一个日期，增长决策必须在此日期前落定（场地签署截止日期、赞助商预算周期）？（临近截止日期会促使选择快速杠杆——挤压、定价——而不是更换场地。）
下一届是一次性的更大赌注，还是一个逐年累积的年度资产的一步？（累积要求会促使选择缓慢、持久的杠杆和更严格的需求门槛；一次性则无法承受升级的前置时间或其合同风险。）
努力上限是什么：组织者小时数、志愿者替补深度、财务风险承受能力——并且直接问，组织这个活动仍然愉快吗？（“不”本身就是一个增长信号——见测量部分。）
已经存在哪些默认排名假设没有的资产——可信赖且有增长空间的场地关系、常设候补名单、深厚的赞助商资源、已经提出请求的第二城市社区？
容量上限是为了塑造房间里的参与者，还是仅仅为了限制数量？

Community-run vs company-run

社区运营与公司运营

What changes the menus is who owns the event (same split

samber/dev-event-organizer-skills@event-market-fit

and

samber/dev-event-organizer-skills@event-first-edition

use):

Community-run - ticketed or donation-funded, external sponsors, volunteer-heavy: every financial axis below applies in full, and all the documented evidence in this skill comes from this pole.
Company-run - funded by a marketing budget, with the vendor as its own main sponsor. The venue-contract exposure is real, but the revenue math changes: you judge growth on pipeline and adoption outcomes, not ticket revenue, and sponsor-concentration risk collapses into "the budget owner changes their mind." These substitutions are judgment calls rather than established event-industry practice - flag them when used.

A free, volunteer-run community event is a third posture worth naming. With no ticket revenue and no per-head financial risk, the financial axes collapse, and track addition becomes the natural default lever. One documented event scaled this way to 8,000+ visitors and 79 tracks with no registration at all, at the documented cost of chronic room overcrowding.

改变菜单的是谁拥有活动（与

samber/dev-event-organizer-skills@event-market-fit

和

samber/dev-event-organizer-skills@event-first-edition

使用相同的区分）：

社区运营 —— 售票或捐赠资助，外部赞助商，志愿者密集：以下所有财务轴都完全适用，这个技能中所有有记录的证据都来自这一端。
公司运营 —— 由营销预算资助，供应商作为自己的主要赞助商。场地合同风险是真实的，但收入计算方式改变：你根据管道和采用结果来判断增长，而不是门票收入，赞助商集中风险坍缩为“预算所有者改变主意”。这些替代是判断性的，而不是既有的活动行业实践——使用时请标记。

一个免费、志愿者运营的社区活动是值得命名的第三种姿态。没有门票收入，也没有按人头计算的财务风险，财务轴坍缩，增加分会场成为自然的默认杠杆。一个有记录的活动以这种方式扩展到8000多名参观者和79个分会场，完全没有注册，代价是有记录的长期房间过度拥挤。

Workflow

工作流程

Run the interview. Require a demand read (Q3): this skill starts where
```
samber/dev-event-organizer-skills@event-market-fit
```
's go call ends. On a hold, pivot, or stop read, stop here - growth work on a red read is growing into empty space.
Gate on repeated demand, not one viral year. The headroom heuristic is a research synthesis, not an industry standard - say so when you apply it. It requires all of the following, repeated across editions:
- Sellout well under an hour.
- A waitlist of roughly 30-50% of capacity.
- Unsolicited sponsor inbound.
Diagnose which ceiling is actually near before picking a lever, borrowing from network-growth theory rather than event-industry practice:
- Saturation - the local audience or sponsor pool for this topic is tapped.
- Channel decay - the personal networks that filled early editions are producing less. This routes to
```
samber/dev-event-organizer-skills@event-marketing-plan
```
  , not to a capacity lever.
- Quality collapse - a bigger edition already degraded what attendees valued. This argues against growth even when demand looks green.
Force the reach-vs-intimacy choice explicitly (Q4):
- Reach routes to the growth levers menu.
- Intimacy routes to the deliberate non-growth menu.
The documented failure is drifting into a middle size that serves neither. The choice is the deliverable, not a formality.
When the choice is genuinely open or contested inside the team, enter brainstorming mode before recommending:
- 2-3 candidate growth paths with trade-offs and a recommendation.
- Questions asked one at a time.
- The plan validated section by section, never a silent framework output.
Pick one lever from the growth menu for the next edition - one discrete step per edition. Order steps by adjacency, borrowed from segment-expansion strategy: track → day → satellite city, each step small enough that credibility and playbook transfer. Jumping several rungs in one edition is the deleted option below.

For any step-up, check the whole-product layer, also borrowed from that strategy. A bigger venue with the same production scales the chairs but not the event: no upgraded AV, networking infrastructure, or volunteer bench. It fails at the new scale as an experience, not as marketing.
Run the financial risk gate for any venue-touching lever, all documented (see the mechanics reference):
- Deposits typically 25-50% at signing.
- Attrition and F&B minimum penalties owed even under a shortfall.
- 9-18 months lead time for 300+ attendee events.
- Post-pandemic venues rarely renegotiate.
Size the new commitment to the proven number plus a modest buffer, never the aspirational one.
Decide the pricing posture before scaling, not after: the recommended default is a public community-price commitment cross-subsidized by sponsorship - the documented flagship case held individual prices flat and cut student tickets 40% across five years of venue growth. Supporter tiers and early-bird ladders are complementary, not alternatives. Price setting mechanics route to
```
samber/dev-event-organizer-skills@event-ticket-pricing
```
.
Pair the chosen lever with its named mitigation:
- Tracks or days dilute the hallway track, so record everything and protect unstructured time (the documented organizer mitigation).
- Caps concentrate scarcity, so pick an allocation mechanism from the non-growth menu.
Never present a lever as free.
Commit, then install the warning-sign watch: the four reversal benchmarks under Measurement, each with an owner and a check date. Any one firing means hold or shrink the next edition, not push through.

If what surfaced isn't a growth problem at all, route out instead:
- Soft demand routes to
```
samber/dev-event-organizer-skills@event-market-fit
```
  .
- No bench for the step routes to
```
samber/dev-event-organizer-skills@event-team-structure
```
  .
- A second format or event question routes to
```
samber/dev-event-organizer-skills@event-portfolio-strategy
```
  .

If your harness has persistent memory, record for each edition:

The chosen lever and the rungs explicitly rejected.
The demand evidence it rested on.
The financial exposure accepted.
The pricing commitment made.
The four watch-signal values.

The next edition's decision starts from this event's own history, not from generic cases.

执行访谈。要求有需求读取（Q3）：这个技能从
```
samber/dev-event-organizer-skills@event-market-fit
```
的“继续”调用结束之处开始。如果是持有、转向或停止读取，就停在这里——在红色读取上进行增长工作是在向空荡的空间增长。
以重复需求为准，而不是一个病毒式传播的年份。余量启发式是研究综合，不是行业标准——应用时要说明。它需要满足以下所有条件，并在多届中重复出现：
- 在一小时内售罄。
- 候补名单约为容量的30-50%。\ - 主动上门的赞助商咨询。
在选择杠杆之前，诊断哪个上限实际接近，借用网络增长理论而非活动行业实践：
- 饱和 —— 该主题的本地受众或赞助商池已被挖尽。\ - 渠道衰退 —— 填充早期版本的个人网络产生的收益减少。这路由到
```
samber/dev-event-organizer-skills@event-marketing-plan
```
  ，而不是容量杠杆。\ - 质量崩溃 —— 更大的版本已经破坏了参与者所重视的东西。即使需求看起来是绿色的，这也支持反对增长。
明确强制做出覆盖范围与亲密感的选择（Q4）：\ - 覆盖范围路由到增长杠杆菜单。\ - 亲密感路由到刻意不增长菜单。

有记录的失败是在中间规模漂移，两者都不讨好。选择本身就是交付物，而不是形式。
当选择真正开放或团队内部有争议时，在推荐之前进入头脑风暴模式：\ - 2-3条候选增长路径，附权衡和推荐。\ - 一次问一个问题。\ - 计划逐部分验证，绝不出静默的框架输出。
为下一届从增长菜单中挑选一个杠杆——每届一个离散步骤。按相邻性排序步骤，借鉴细分扩展策略：分会场 → 天数 → 卫星城市，每一步都小到足以让信誉和剧本转移。在一届中跳几级是下面删除的选项。

对于任何升级，检查整体产品层，也借鉴该策略。一个更大的场地配上相同的制作水平扩展了椅子，但没有扩展活动：没有升级的音响视频、网络基础设施或志愿者替补。它在新的规模上作为一个体验失败，而不是作为营销失败。
对任何触及场地的杠杆运行财务风险门槛，全部有记录（见机制参考）：\ - 签署时通常支付25-50%的押金。\ - 即使出现短缺，也要支付损耗和餐饮最低消费罚款。\ - 300+参与者活动的提前期为9-18个月。\ - 疫情后的场地很少重新谈判。

将新的承诺规模定在已证明的数字加上适度缓冲，绝不是理想化的数字。
在扩展之前决定定价姿态，而不是之后：推荐的默认是公共社区价格承诺，由赞助交叉补贴——有记录的旗舰案例在五年场地增长中保持个人价格不变，并将学生票削减了40%。支持者层级和早鸟阶梯是互补的，而不是替代品。价格设定机制路由到
```
samber/dev-event-organizer-skills@event-ticket-pricing
```
。
将选定的杠杆与其指定的缓解措施配对：\ - 分会场或天数稀释走廊通道，所以记录一切并保护非结构化时间（有记录的组织者缓解措施）。\ - 上限集中稀缺性，所以从非增长菜单中选择一种分配机制。

绝不要把杠杆说成是免费的。
承诺，然后安装警示信号监视：测量部分下的四个逆转基准，每个都有负责人和检查日期。任何一个触发都意味着下一届保持或缩小，而不是强行通过。
如果浮现的不是增长问题，就路由出去：\ - 需求疲软路由到
```
samber/dev-event-organizer-skills@event-market-fit
```
。\ - 没有替补人员执行这一步路由到
```
samber/dev-event-organizer-skills@event-team-structure
```
。\ - 第二个形式或活动问题路由到
```
samber/dev-event-organizer-skills@event-portfolio-strategy
```
。

如果你的框架有持久内存，为每一届记录：

选定的杠杆和明确拒绝的阶梯。
它所依据的需求证据。
接受的财务风险敞口。
做出的定价承诺。
四个监视信号值。

下一届的决策从这个活动自身的历史开始，而不是从通用案例。

Growth levers

增长杠杆

Ranking (default, not a law - re-rank against the interview: a hard signing deadline promotes squeeze and pricing, a compounding mandate strengthens every gate, an owned asset like a trusted venue or a second-city community promotes a normally-later rung; and for a free volunteer-run event the financial axes collapse, making track addition the default):

effort:
```
venue step-up > day addition > track addition > venue squeeze == price-led growth
```
(tie argued: both are executed with partners you already have, inside the already-signed footprint - a layout renegotiation with a known venue, a pricing change on your own sales page; days of coordination, not months, and no new program to produce)
value (additional demand served per edition):
```
venue step-up > day addition == track addition > venue squeeze > price-led growth
```
(tie argued: the documented record treats them as one rung - organizers used them interchangeably or together to grow program surface and admitted demand inside the existing venue relationship; they differ in what they cost, not in what they buy)

efficiency:

venue squeeze > price-led growth > track addition > day addition > venue step-up

compliance cost (contract review triggered, reversibility lost):
```
venue step-up > day addition > venue squeeze > track addition == price-led growth
```
(tie argued: neither touches a contract - the rooms are already inside the signed footprint, and pricing is a unilateral change)
Venue squeeze - the default rung: extract more capacity from the known venue via layout, bounded by occupancy/fire-code sign-off. The documented flagship case fit a third more attendees into a hall already "at capacity" with tighter layout and slimmer chairs, instead of signing a third, larger, unproven venue. Move up a rung only once squeeze headroom is exhausted and the demand signals have repeated.
Price-led growth - grow revenue and demand management without adding seats: early-bird laddering, a premium supporter tier that cross-subsidizes accessible tickets, group-discount design. Decide it alongside whatever else you pick (workflow step 8). Mechanics belong to
```
samber/dev-event-organizer-skills@event-ticket-pricing
```
.
Track addition - parallel sessions inside the existing venue and days, the second-most-common documented lever and the entire scaling model of the free-event pole. Universal documented trade-off: hallway-track dilution - every organizer who used it reported the same concern, and it is the exact lever the deliberate-cap events refuse on principle. Always pair with the recording-plus-unstructured-time mitigation.
Day addition - an extra day (tutorials, community day) extending every cost line: venue rental, catering, volunteer shifts, attendee hotel nights. Same value rung as a track, higher effort and a contract amendment.
Venue step-up - the starved option: a discrete jump to a bigger venue (the documented cases doubled capacity in one move), highest in value but losing every efficiency round and carrying the menu's whole contract exposure. Promote it when demand has visibly exceeded supply across repeated editions with the cheaper rungs exhausted, and the downside is capped: smallest negotiable deposit, shortest attrition/minimum commitments, capacity sized to proven demand plus a modest buffer. Then hand execution to
```
samber/dev-event-organizer-skills@event-venue-sourcing
```
.

The single-edition multi-x leap is deleted from this menu, not ranked last: several rungs at once, or a one-edition jump past roughly double. The clearest documented case took a ~300-person event to a ~1,300-person format in one edition and drew "doesn't scale" verdicts from its own community.

Its later wind-down was a deliberate choice, not a collapse - cite the leap for the format failure only. Parking it at the bottom would let a milestone year or an anchor sponsor quietly resurrect it.

排名（默认，不是法律——根据访谈重新排名：一个强硬的签署截止日期会提升挤压和定价，累积任务会加强每个门槛，一个拥有的资产如可信赖的场地或第二城市社区会提升一个通常更晚的阶梯；对于免费志愿者运营的活动，财务轴坍缩，使增加分会场成为默认）：

努力：
```
场地升级 > 增加天数 > 增加分会场 > 场地挤压 == 价格驱动增长
```
（并列理由：两者都是与你已有的合作伙伴执行的，在已经签署的足迹内——与已知场地重新谈判布局，在你自己的销售页面上改变定价；需要几天的协调，而不是几个月，也没有新的节目要制作）
价值（每届服务的额外需求）：
```
场地升级 > 增加天数 == 增加分会场 > 场地挤压 > 价格驱动增长
```
（并列理由：有记录案例将它们视为同一阶梯——组织者互换或同时使用它们来增长节目表面积和承认的需求，在现有场地关系内；它们区别在于成本，而不是所得）

效率：

场地挤压 > 价格驱动增长 > 增加分会场 > 增加天数 > 场地升级

合规成本（触发的合同审查，失去的可逆性）：
```
场地升级 > 增加天数 > 场地挤压 > 增加分会场 == 价格驱动增长
```
（并列理由：两者都不触及合同——房间已经在签署的足迹内，定价是单方面变化）
场地挤压 —— 默认阶梯：通过布局从已知场地提取更多容量，受占用/消防规范签核限制。有记录的旗舰案例通过更紧凑的布局和更窄的椅子，在一个已经“满负荷”的大厅里容纳了多三分之一的参与者，而不是签署第三个更大的未经证明的场地。只有挤压余量耗尽并且需求信号已经重复时，才向上移动一个阶梯。
价格驱动增长 —— 在不增加座位的情况下增长收入和需求管理：早鸟阶梯、一个溢价支持者层级交叉补贴可负担门票、团体折扣设计。与任何其他选择一起决定（工作流程步骤8）。机制属于
```
samber/dev-event-organizer-skills@event-ticket-pricing
```
。
增加分会场 —— 在现有场地和天数内进行并行会议，是第二常见的记录杠杆，也是免费活动一端的整个扩展模型。普遍的记录权衡：走廊通道稀释——每个使用它的组织者都报告了同样的担忧，这正是刻意限流活动原则上拒绝的杠杆。始终与记录加非结构化时间的缓解措施配对。
增加天数 —— 额外的一天（教程、社区日）延长了每一行成本：场地租金、餐饮、志愿者轮班、参与者的酒店住宿。与增加分会在价值阶梯上相同，但努力更高，需要修改合同。
场地升级 —— 被忽视的选项：跃迁到更大的场地（记录案例在一次移动中使容量翻倍），价值最高，但输掉每一轮效率，并承担菜单的全部合同风险。当需求在重复的版本中明显超过供应，且更便宜的阶梯已经用尽并且下行风险有上限时，提升它：尽可能小的可协商押金、最短的损耗/最低承诺、容量与已证明需求加上适度缓冲相匹配。然后将执行交给
```
samber/dev-event-organizer-skills@event-venue-sourcing
```
。

单届多倍跳跃从这个菜单中删除，而不是排名最后：一次几级，或一届跳跃超过大约两倍。最清楚的记录案例将一个约300人的活动在一届中扩展到约1,300人的规模，并招致其自身社区“不可扩展”的裁决。

其后的缩减是深思熟虑的选择，而不是崩溃——只引用该跳跃作为形式失败。把它放在底部会让一个里程碑年份或一个锚点赞助商悄悄复活它。

Deliberate non-growth and allocation

刻意不增长和分配

A real strategy, not a footnote: two of the strongest-brand events in the documented record cap on purpose, and one grew, tried double, and reversed. When the interview picks intimacy - or a reversal benchmark fires - choose an allocation mechanism instead of a lever.

Ranking (default, not a law - re-rank against the interview: an event whose cap exists to shape who is in the room, not just how many, promotes the application mechanisms):

effort:

deliberate shrink > application + lottery > group-purchase ban > hold the cap

value (control over the room, protection of the core experience):

deliberate shrink > application + lottery > group-purchase ban > hold the cap

efficiency:

hold the cap > group-purchase ban > application + lottery > deliberate shrink

Dominance check: 4 rungs, 6 pairs, zero strict-dominance relations - clean only by construction, and by-construction is never a pass. Value and effort are the same list, so one mechanism blocks all six pairs: the mechanism that buys more control over the room costs strictly more, including every pair against holding the cap, which loses on value rather than winning anything for free.

No third axis is printed. The check catches no misordering. The efficiency line rests on the arguments below.

Hold the cap - the default: keep capacity flat, sell first-come-first-served, run a waitlist. Near-zero effort, and the waitlist doubles as the demand instrument
```
samber/dev-event-organizer-skills@event-market-fit
```
reads. Known documented bias: first-come-first-served favors those with time and money.
Group-purchase ban - refuse large group ticket blocks. Documented anti-clique mechanism from a deliberately-capped ~150-person event: it keeps the room from arriving pre-clustered. Move up from hold-the-cap when group buyers start dominating allocation.
Application + lottery - applications with intent questions, then a lottery, with real per-edition effort. The documented case used it explicitly to counter first-come-first-served bias, prioritize underrepresented attendees, and filter commercial intent. Promotion condition, keyed to Q10: the cap is about composition, not just count.
Deliberate shrink - the starved option: go back down. The documented case doubled to ~2,300, then reversed for three named reasons: venue isolation, lost intimacy, and organizer stress ("actively unpleasant"), accepting roughly a 50% production-budget cut as the price. Highest effort and cost, it loses every efficiency round, but promote it when a reversal benchmark has fired, especially the burnout one, since it is the documented response, not an admission of failure.

Batch-released ticket drops engineered to manufacture sellout optics are deleted from this menu, not demoted: manufactured scarcity corrupts sellout speed, the very signal this skill's growth gate reads.

一个真正的策略，而不是脚注：在记录中有两个品牌最强的活动刻意限制规模，一个增长、尝试加倍、然后逆转。当访谈选择亲密感——或者逆转基准触发——选择一种分配机制而不是杠杆。

排名（默认，不是法律——根据访谈重新排名：一个其上限是为了塑造谁在房间里而不仅仅是多少人的活动，会提升申请机制）：

努力：

刻意缩小 > 申请 + 抽签 > 团体购买禁令 > 保持上限

价值（对房间的控制，核心体验的保护）：

刻意缩小 > 申请 + 抽签 > 团体购买禁令 > 保持上限

效率：

保持上限 > 团体购买禁令 > 申请 + 抽签 > 刻意缩小

**支配检查：4个阶梯，6对，零严格支配关系——仅通过构造是干净的，而通过构造从来不是通过。**价值和努力是同一列表，所以一个机制阻塞了所有六对：购买更多房间控制的机制花费严格更多，包括每一对对抗保持上限，它在价值上输掉，而不是免费赢得任何东西。

没有打印第三轴。检查没有抓住错误排序。效率线基于下面的论据。

保持上限 —— 默认：保持容量不变，先到先得，运行候补名单。接近零努力，候补名单兼作
```
samber/dev-event-organizer-skills@event-market-fit
```
读取的需求工具。已知的记录偏差：先到先得偏袒有时间和金钱的人。
团体购买禁令 —— 拒绝大型团体票块。来自一个刻意限流的约150人活动的记录反小团体机制：它防止房间预先成群结队。当团体买家开始主导分配时，从保持上限向上移动。
申请 + 抽签 —— 带有意图问题的申请，然后抽签，每届有实际努力。记录案例明确使用它来对抗先到先得偏差，优先考虑代表性不足的参与者，并过滤商业意图。提升条件，与Q10相关：上限是关于构成，而不仅仅是数量。
刻意缩小 —— 被忽视的选项：缩减回去。记录案例扩大到约2,300人，然后因三个指定原因逆转：场地隔离、失去亲密感和组织者压力（“主动不愉快”），接受大约50%的制作预算削减作为代价。最高努力和成本，它输掉每一轮效率，但当逆转基准触发时提升它，尤其是倦怠基准，因为这是记录的响应，而不是承认失败。

为制造售罄效果而设计的批量发布门票掉落从这个菜单中删除，而不是降级：人为稀缺破坏了售罄速度，这正是这个技能增长门槛读取的信号。

Failure modes

失败模式

Growing into empty space - capacity bought ahead of proven demand: the "amazing (but very expensive) venue" the documented postmortem flagged in real time. The financial gate (workflow step 7) exists for this. An over-built edition loses money at attendance that looks respectable.
Reading one fast sellout as headroom - one viral year misleads, and the gate requires repetition. Check sellout speed for batch-release manufacturing before believing it.
Quality collapse noticed too late - "Being small... made the conference so intimate and amazing, and being so intimate and amazing... made it so popular." This documented loop shows growth eroding the value that caused it. Run the ceiling diagnostic before the lever choice, not after the complaints.
Sponsor concentration funding the step - sponsors budget a year ahead (documented), and a single sponsor's exit blows a hole no replacement can fill in time. The documented final-edition case ended exactly this way: sponsorship receded while attendee signals stayed warm.
Burnout treated as a mood, not a signal - in two independent documented cases, organizer stress preceded any financial trigger. "Actively unpleasant" is a named reversal benchmark here, not a complaint to push through.
Governance endings misread as growth failures - the documented case of a major community conference ending in 2022-2025 was a governance and politics rupture, not overexpansion. Never cite an event's ending as "grew too big" without checking the organizer's own account.
Benchmarking against outliers - the fastest documented case scaled ~100x in five years on a broad general-tech topic, and its base year is itself disputed: a ~150-person 2009 precursor vs. a ~400-person 2010 start, report the range. A niche developer conference doubling per step is the normal documented pattern, not a failure against that curve.

向空荡的空间增长 —— 在已证明的需求之前购买容量：有记录的事后分析实时标记的“惊人（但非常昂贵）的场地”。财务门槛（工作流程步骤7）为此存在。过度建设的版本在看似体面的出席率下亏损。
将一次快速售罄读作余量 —— 一个病毒式传播的年份误导，门槛要求重复。在相信之前检查批量发布制造的售罄速度。
质量崩溃注意到太晚 —— “小...让会议如此亲密和惊人，并且如此亲密和惊人...使它如此受欢迎。”这个记录循环显示增长侵蚀了导致它的价值。在杠杆选择之前运行上限诊断，而不是在投诉之后。
赞助商集中资助这一步 —— 赞助商提前一年预算（有记录），单个赞助商的退出会炸出一个任何替代者都无法及时填补的洞。记录的最后一届案例正是这样结束的：赞助减少而参与者信号保持温暖。
倦怠被当作情绪而不是信号 —— 在两个独立的记录案例中，组织者压力先于任何财务触发。“主动不愉快”在这里是一个指定的逆转基准，而不是需要强行通过的抱怨。
治理结束误读为增长失败 —— 一个主要社区会议在2022-2025年结束的记录案例是治理和政治破裂，而不是过度扩张。在未检查组织者自己的叙述之前，绝不要引用一个活动的结束作为“变得太大”。
与异常值基准比较 —— 最快的记录案例在五年内在一个广泛的一般技术主题上扩展到约100倍，而其基准年份本身有争议：约150人的2009年前身与约400人的2010年开始，报告范围。一个细分开发者会议每一步翻倍是正常的记录模式，而不是相对于那条曲线的失败。

Measurement

测量

Reversal benchmarks - any one firing stops or reverses the growth push (the specific trigger values are self-set and must be declared before the sale opens):

Sellout speed slows materially year-over-year at flat or higher capacity.
No-show/attrition rate rises as the event scales.
A single sponsor exceeds the revenue share you set in advance (self-set - declare the threshold now, not after a sponsor grows into it).
The organizing team reports the work has become actively unpleasant.

Context to temper expectations: a 2023 industry write-up found independent in-person events running 30-40% below pre-pandemic attendance - a market-wide contraction, not evidence any single event mismanaged growth.

Success for this skill's own output is a growth plan that names all of the following:

Exactly one lever, or one allocation mechanism.
The demand evidence it rests on, with each figure marked documented or self-set.
The financial exposure accepted and its cap.
The pricing posture.
The lever's paired mitigation.
The four watch signals, with owners and check dates.

A plan missing the watch or the mitigation is not done.

逆转基准——任何一个触发都会停止或逆转增长推动（具体触发值是自己设定的，必须在开售前声明）：

售罄速度在容量持平或更高的情况下年同比显著放缓。
随着活动扩展，缺席/流失率上升。
单个赞助商超过你预先设定的收入份额（自己设定——现在就声明阈值，而不是在赞助商增长到它之后）。
组织团队报告工作变得主动不愉快。

背景，以调整期望：2023年一份行业报告发现独立线下活动出席率比疫情前低30-40%——这是市场范围的收缩，而不是任何单一活动管理不善的证据。

这个技能自身输出的成功是命名以下所有内容的增长计划：

恰好一个杠杆，或一个分配机制。
它所依据的需求证据，每个数字标记为已记录或自设定。
接受的财务风险敞口及其上限。
定价姿态。
杠杆的配对缓解措施。
四个监视信号，带有负责人和检查日期。

缺少监视或缓解的计划未完成。

Invocation examples

调用示例

"Our 300-person conference sold out in 20 minutes with a 200-person waitlist. Do we sign the 600-seat venue?"
"We're debating adding a second track next year - what does it cost us besides money?"
"Demand keeps growing but organizing stopped being fun. Can we just not grow?"

Expected output: the growth (or non-growth) plan described under Measurement, delivered section by section for validation:

Demand evidence.
Ceiling diagnostic.
Reach-vs-intimacy call.
Chosen lever with rejected rungs.
Financial gate result.
Pricing posture.
Mitigation.
Watch plan.

“我们300人的会议在20分钟内售罄，有200人的候补名单。我们该签600座的场地吗？”
“我们在争论明年增加第二个分会场——除了钱之外，它还让我们付出什么？”
“需求不断增长，但组织不再有趣。我们可以不增长吗？”

预期输出：测量部分描述的增长（或非增长）计划，逐部分交付以进行验证：

需求证据。
上限诊断。
覆盖范围与亲密感调用。
选定的杠杆和被拒绝的阶梯。
财务门槛结果。
定价姿态。
缓解措施。
监视计划。

References

参考

references/growth-case-studies.md - the documented case record behind every lever and cap: venue step-ups, the squeeze, track-based free scaling, accessible-pricing scaling, the deliberate caps and the shrink, the overexpansion postmortems, the outlier - including three contested figures that must be reported as ranges.
references/venue-and-money-mechanics.md - venue contract risk mechanics (deposits, attrition, F&B, lead times), the demand-headroom heuristic and the cases behind it, the three pricing-evolution mechanisms, and the sponsor-concentration and burnout warning patterns.