Skip to content

samber/dev-event-organizer-skills / skills/event-positioning

event-positioning

Verified

Define a technical event's positioning - what it stands for, against which alternatives, for which audience identity. Covers the governance axis (community-run, foundation, media-run, vendor-owned), competitive-alternative mapping, best-fit attendee and sponsor segments (and when a conference may serve several targets), the business-oriented layer sponsors buy, market-category strategy (head-to-head, subcategory, new category and its education tax), the positioning statement, contrast-not-attack anti-positioning, and the rebrand gate. Use whenever asked to position a conference, meetup or hackathon, differentiate it from neighboring events, decide who it is for, write a positioning statement, weigh a vendor-neutrality claim, or judge an event rename. Strategy only. Do NOT use for on-site embodiment - use samber/dev-event-organizer-skills@event-cultural-identity.

references/positioning-evidence.md

View on GitHub
# Named-event positioning evidence

Named examples and quotes underlying SKILL.md claims.

## The vendor pole: belonging language wrapping a launch purpose

Every major vendor conference states a commercial purpose (product launches, customer/partner alignment) but positions publicly in family/community/builder language - treat the move as deliberate and repeatable, not coincidence:

- **Salesforce Dreamforce** - built around "Ohana" (family), framed as uniting "employees, customers, partners, and members of the community"; the CEO has hosted the opening keynote every year since 2003, fusing the family framing to that edition's product announcements.
- **AWS re:Invent** - "for technical practitioners across every industry and experience level," with scale itself as identity: "five days in Las Vegas with 2,200+ sessions" and hands-on access to launches the day they're announced.
- **GitHub Universe** - "the world's fair of software," explicitly naming the hallway track as a value: "a hallway conversation that saves you a week of trial and error."
- **HashiConf** - "our flagship user conference," with explicit practitioner framing: "a great place to learn from the folks actually using [the] products in the real world." Its HashiDays spin-off borrows the "one-day, single-track, deeply technical, and community-focused" identity usually associated with independent events.
- **Google I/O** - "it's grown to be more than a developer conference," with keynote framing that centers the audience: "today's about you all, our developer community."

Lesson for the axis: warm language is _not_ evidence of community governance - both poles dress in it. Governance and money flow are the discriminating facts.

## The community pole: DevOpsDays

- Organizing rules state: "These events are not for individual or corporate profit." Surplus goes to the next event, other city events, or charity. The global core team explicitly cannot answer per-city sponsorship questions because organization is decentralized to local volunteer teams.
- Chapter-brand mechanic: a shared logo element carries global category trust while each city designs its own local variation around it (Cape Town's Table Mountain, Amsterdam's venue). For any chapter/franchise-style event, that is the strategic pattern: inherited trust without losing local identity. The visual execution belongs to `samber/dev-event-organizer-skills@event-cultural-identity`; the _reason_ to want it belongs here.

## The middle ground: foundation-run and media-run

- **CNCF / KubeCon** - "the open source, vendor-neutral hub of cloud native computing," repeated as a near-mantra; founding ED: the foundation "was formed to create a vendor-neutral home for Kubernetes." The neutrality claim is structural: no single company owns governance.
- **O'Reilly OSCON** - claimed the same neutrality ("no matter the origin or affiliation, a clear, vendor-neutral comparison") from a for-profit media company; real credibility (launch venue for OpenOffice.org and OpenStack) but not foundation-backed durability.
- **TechCrunch Disrupt** - the non-neutral media-run counterpart: claims no neutrality, positions on scale and access ("10,000+ founders, investors, and tech leaders").

Lesson: the same neutrality _claim_ is available at more than one point on the spectrum, but only governance structure makes it durable. State which kind of claim the organizer can actually back.

**Neutrality threshold**: a program over roughly 30-40% single-vendor product content forfeits a credible neutrality claim - rebalance the CFP or drop the claim.

## Anti-positioning catalog: contrast, not attack

Six events answering "why not attend X instead" in their own marketing - none names a specific rival; every contrast target is an archetype:

- **Strange Loop**: "There are many fine speakers, topics, and conferences in the process area. This is not one of them."
- **DevOpsDays**: profit "is forbidden for devopsdays events" - against for-profit and single-vendor conferences at once.
- **OSCON**: "no matter the origin or affiliation, rather than focus on a single language or aspect" - against single-vendor events.
- **XOXO**: "eschewed the corporate nature of other conferences," with a lottery entry system screening out attendees "focused on marketing to other attendees."
- **Papers We Love**: "just come, listen, and discuss in a low ego, friendly environment."
- **MLH**: the hackathon as "invention marathon" - "you don't have to be a programmer."

An archetype contrast doesn't age out when a rival changes strategy and can't be read as an attack inviting rebuttal - that is why it is the required shape.

## Single-track as identity claim

- **Scott Berkun on Webstock**: "Single track events force quality, placing big bets on who they invite, investing heavily in a singular, crafted, shared experience."
- **Jeremy Keith on FF Conf**: "multi-track events are a terrible waste of time for attendees"; a curated lineup is "a snapshot of [the curator's] brain."
- **Jeffrey Zeldman**: "the ideal conference offers a single track, so that all attendees (and all speakers) share the same intense experience."
- **XOXO**: single-track solo talks plus an admission lottery - one move that curates content _and_ self-selects the audience; final 2024 edition capped at 1,000 via lottery.

The format mechanics live in `samber/dev-event-organizer-skills@event-format-selection`; what belongs here is the public identity claim: "we are the kind of event that bets everything on curation" is a positioning statement made before a single talk is announced.

## Keynote and lineup as the brand carrier

- Vendor events: the CEO keynote _is_ the edition's positioning statement - Benioff every year since 2003, Pichai opening I/O, re:Invent structured around live launches.
- Curated events: the lineup does that work instead - "The speakers make up the bulk of the content of your conference and no amount of surrounding local cultural events can save a poor performing lineup. They're your ambassadors and your performers" (Michael Flarup).
- Benchmark question: can attendees say why these specific speakers are together? A shrug means the lineup isn't doing positioning work, regardless of individual speaker quality.
- **Caveat**: claims that a top headliner "lifts early registrations" circulate from speaker-bureau and PR sources - self-interested advocacy, not verified data. Never cite them as evidence.

## Rebrand evidence: scope moves first, the name follows

- **HubSpot INBOUND → UNBOUND (2026)** - the cleanest tech case. Stated rationale: "growth no longer fits within a single framework or function. UNBOUND reflects that expanded reality." The event's audience and content had already outgrown the name before the rename; the announcement mapped old scope to new scope explicitly.
- Adjacent corroboration (non-developer events, weaker as precedent) - every case frames the rename as documenting change that already happened:
  - ISTE→ISTE+ASCD ("shifting to a name that describes why we do it")
  - Wireless Technology Forum→Atlanta Innovation Forum
  - Fibre Council Europe→Fibre Horizons

The rule: rename only when the audience/scope has already moved beyond the name's promise, and map old→new publicly. A rename that promises change instead of recording it reads as churn.

## Hackathons and meetups: learn/build/share over prizes

- **MLH**: "every student on the planet should have access to high quality events where they can learn, build, and share"; the hackathon reframed as an "invention marathon" welcoming non-programmers - while still running genuinely competitive formats underneath.
- **PennApps**:
  - "the nation's first student-run college hackathon"
  - "many times the most important aspect of a hackathon is the community it generates"
  - "we love first-time hackers."
- **Papers We Love**: intellectual, non-commercial, low-ego framing.
- **NASA Space Apps** - the largest annual global hackathon (93,520 registrants, 163 countries, 2024): "you join a community that shares a desire to propel humanity forward"; collaboration explicitly subordinates competition.

Convergent pattern across all four: foreground learning/building/sharing and beginner inclusion; none leads with prize money - which is why prize-led positioning is a failure mode, not a differentiator.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall