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/competitive-alternatives.md

View on GitHub
# Competitive alternatives for events

The "Obviously Awesome" alternatives taxonomy, restated for attendee/sponsor decisions - not event-industry authority. An event can't claim to be different until it names what it is different _from_, and most organizers under-scope that list to "the other conferences in our category."

## The five alternative types

| Type                         | Event meaning                                              | Example                                                                                                                                         |
| ---------------------------- | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Direct rival                 | A neighboring event in the same category/topic             | A rival platform-engineering conference in the same region and season                                                                           |
| Adjacent event               | A different category or format repurposed for the same job | A generalist cloud-vendor summit attended "well enough" instead of a topic-specific event; a meetup used as a lightweight conference substitute |
| Do the job without any event | Getting the learning/networking outcome eventless          | Watching the same speakers' talks on video after the fact; living in the topic's Slack/Discord community                                        |
| Delegate it                  | Paying someone else to capture the value                   | Sending one delegate to report back to the team; hiring a consultant instead of upskilling via talks                                            |
| Do nothing                   | Accepting the status quo                                   | Not engaging with the topic through any event at all - very frequently the largest true competitor                                              |

Classify rival events by ownership and money flow (the governance spectrum in SKILL.md), never by tone - a vendor event that sounds like a community is still a vendor event, and your attendees weigh it as one.

## Interview script

Interview 15-20 of the event's happiest, most successful _repeat_ attendees and sponsors - not prospects (no editions yet? interview the community members and sponsor contacts the concept targets, and label the answers as pre-launch signal, not behavior). Core questions:

- "Before you first attended [event], what did you use to get the same learning/networking/pipeline outcome?"
- "If [event] didn't run next year, what would you do instead?"
- "When you were deciding whether to attend, what other events or options did you seriously consider?"
- "Was there a way you thought about getting this that didn't involve attending any event at all?"
- "What's the biggest cost you weighed - travel, time away, ticket price - versus those alternatives?"

Probes:

- "tell me more about how you used [X] for this"
- "what specifically didn't work about [X]"
- "how long did you rely on [X] before switching to attending?"

## Cluster by segment, never blend

Different segments carry different primary alternatives: a first-time individual attendee's alternative is often "do nothing / watch the videos," while a sponsor's is "the rival vendor's summit" or "run our own private event." Rank alternatives by frequency _within_ each segment and keep the lists separate - the best-fit-segment choice in the canvas depends on knowing which alternative each segment is actually weighing.

## The do-nothing diagnostic

When "do nothing" dominates the answers, diagnose why before positioning against anything else:

- Low perceived cost of staying home (the videos come out anyway).
- No acute trigger (nothing at work forced the topic).
- High switching cost (travel, days away, ticket budget approval).
- Risk perception (fear the event won't be worth it - compounded for a first edition or a new category).
- Organizational inertia (a sponsor needing multi-stakeholder sign-off before committing budget).

Each cause implies a different positioning answer:

| Cause               | Positioning answer                                                  |
| ------------------- | ------------------------------------------------------------------- |
| Acute-trigger gap   | Sharper value themes tied to a real deadline in the attendee's work |
| Risk-perception gap | Proof points                                                        |
| Inertia gap         | Sponsor-side materials, not attendee copy                           |
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