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-canvas.md

View on GitHub
# The positioning canvas, adapted for events

Everything in this file adapts April Dunford's "Obviously Awesome" positioning method, built for B2B products, to events. The adaptation holds because the underlying logic - a buyer evaluates relative to alternatives - applies to attendees and sponsors unchanged. It is not event-industry authority; the named-event evidence lives in the evidence reference.

## Five research fields, in order

Each field feeds the next; skipping one leaves the later ones guessing.

| Field                     | Event meaning                                                | Fill-in question                                                                                                                        |
| ------------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| Competitive alternatives  | What an attendee/sponsor would do if this event didn't exist | Use the five-type taxonomy in the alternatives reference - never just "the other conferences in our category"                           |
| Unique attributes         | What this event has that the alternatives don't              | A flagship curator or community, a format (single-track, unconference), a location/timing niche - must pass the "only this event" test  |
| Value themes              | The "so what?" chain from attribute to outcome               | "Single-track" → "everyone shares the same reference points" → "hallway conversations build on the talks instead of starting from zero" |
| Best-fit attendee/sponsor | The narrowest segment that cares most about that value       | "Senior platform engineers already running Kubernetes in production," not "anyone interested in cloud"                                  |
| Market category           | The event-type frame that makes the value obvious            | Head-to-head, subcategory, or new category - the ranked menu in SKILL.md                                                                |

## Five derived fields

Built from the research fields, never researched separately:

- Relevant trends, only where a trend connects to a real unique attribute.
- The positioning statement.
- Key proof points: past editions' speaker caliber, attendee testimonials, sponsor renewal.
- The CFP/sponsor narrative.
- Messaging, always last - writing it first is the most common ordering failure.

## Positioning statement template

**"For [best-fit attendee/sponsor], [event name] is the [event category] that [unique value theme]."**

Worked example (invented, for shape only): "For senior platform engineers running Kubernetes in production, ShipCon is the single-track conference where the hallway track builds on the talks - shared context, not FOMO."

Negative example (what not to write): "ShipCon is the premier conference for everyone passionate about cloud-native technology" - no best-fit segment, no category frame that shifts evaluation, a superlative instead of a value theme.

## Category naming patterns (subcategory rung)

| Pattern                              | Example                                          |
| ------------------------------------ | ------------------------------------------------ |
| [Topic conference] for [vertical]    | "Kubernetes conference for regulated industries" |
| [Format-modified] [topic] conference | "Single-track observability conference"          |
| [Audience]-first [topic] event       | "Practitioner-first MLOps summit"                |

Each modifier shifts what attendees expect to evaluate the event on - that shift, not the words, is the point.

## Signals the category choice is wrong

Re-run the category step at the next edition when any of these appears:

- Attendees or sponsors consistently misdescribe the event to colleagues.
- The event loses attendees/sponsors to events that aren't genuinely comparable.
- Ticket-sale or sponsor-close cycles run far longer than category peers'.
- Attendees arrive expecting something the event doesn't deliver, or use it for something the organizers didn't design.
- CFP submissions or sponsor pitches assume capabilities (expo hall, keynote slots) the event doesn't have.

## The 0-10 alignment rubric

Taken unchanged from the product original - swap "customers" for "attendees/sponsors." The ≥7 pass threshold is self-set for this skill.

| Band | Meaning                                                                        |
| ---- | ------------------------------------------------------------------------------ |
| 0-2  | No clear positioning; the event is described differently in every channel      |
| 3-4  | Vague; the audience is "everyone"                                              |
| 5-6  | Partial; organizers describe the event differently from each other             |
| 7-8  | Strong; all fields defined and the team describes the positioning identically  |
| 9-10 | Exceptional; new attendees immediately get what it is and why they should care |

## Common mistakes

| Mistake                            | Why it fails                                                                         |
| ---------------------------------- | ------------------------------------------------------------------------------------ |
| Positioning for everyone           | Dilutes every differentiation claim; the deleted non-option in SKILL.md              |
| Messaging before positioning       | Locks in a tagline the strategy then has to serve                                    |
| Listing formats instead of value   | Tracks and session types are attributes; attendees buy the outcome                   |
| Copying a neighbor's positioning   | Invites comparison on the incumbent's terms instead of building from own attributes  |
| Repositioning every edition        | Confuses returning attendees/sponsors and resets trust; commit for multiple editions |
| Premature new category             | Pays the education tax without the runway to survive it                              |
| Skipping the alternatives research | Differentiation claims built on guesses about what people would do instead           |

## Team workshop format

Run the five research fields as a 2-3 hour workshop with the organizing team's real functional split:

- Lead organizer(s) for vision.
- CFP/program chair for what unique content the event can attract.
- Sponsorship lead for the objections and alternatives sponsors actually raise.
- Marketing/comms for category and messaging.
- A returning-attendee or community-liaison voice for best-fit evidence, if editions exist.

- **Pre-work:** the alternatives interviews.
- **Post-work:** the written statement.

The output that matters most is alignment - every organizer describing the positioning identically is both the goal and the test (the rubric's 7-8 band).
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