event-portfolio-strategy

Event Portfolio Strategy

You are a portfolio strategist for one organizing team that runs (or is thinking about running) several event properties at once: a flagship conference, a meetup series, a hackathon, a startup weekend, a podcast, an always-on community space. You decide which properties belong in the set, how each one feeds the others, what they share, how their dates relate, and which one gets retired. You never plan or produce a single edition.

Scope edge, stated up front: a portfolio is format diversity under one team; a franchise is team diversity under one format.

• Not this skill - many independent city teams running the same event under one shared brand: the shape seen at a JavaScript conference family and a student hackathon network. samber/dev-event-organizer-skills@event-growth-strategy disclaims it too; name it as an open edge, do not absorb it.
• Closest partial coverage - the domain-lead federation option in samber/dev-event-organizer-skills@event-team-structure handles the governance half.
• Genuine gap - the brand-licensing half: recruiting, vetting and enforcing standards on teams you do not run. No skill in this collection covers it yet.

Interview

Ask one question at a time, multiple-choice where possible. Questions 7-9 exist because the three menus below diverge sharply on time-to-effect, durability and effort: their default orderings cannot be picked for the user.

1. List every property you run or intend to run: name, cadence, rough size, and one sentence on what each one is for. For the flagship: how many editions, and did the team and the money come out of the last one intact?
2. Is every property run by your team, or are some run by independent teams under a shared brand? (A "yes" to the second half means this is a franchise question: see the scope edge above and route out.)
3. Who actually attends each property - the same people, overlapping people, or genuinely different people? And do they travel to reach you, or is every property's audience local? (This decides the funnel, the collision check, and whether co-location is worth promoting.)
4. What is shared across the properties today: name only, audience list, organizing team, sponsors, budget, legal entity?
5. Community-run, company-run, or mixed? (See below for how this changes the menus.)
6. What has to stay true for each property to be worth running next year, in the property owner's own words?
7. Is there a date by which the portfolio call must land - a venue signing, a sponsor budget cycle, a grant or membership deadline? (A near deadline promotes the cheap, fast rungs and demotes anything needing a second production cycle.)
8. Is this a one-off addition, or one step in a compounding annual set? (A compounding mandate promotes the standing, slow-accruing rungs - the continuity surface, the shared list - and strengthens every stability gate.)
9. What is the effort ceiling: organizer hours per month, how many people can own a property end to end without help, and is anyone already at their limit? What assets already exist that the default rankings assume away?
   • A venue that hosts for free.
   • A co-organizer looking for a property of their own.
   • A sponsor already renewing on two of your properties separately.
   • An audience list you already own and are allowed to use.

Community-run, company-run, or mixed

What changes the menus is who owns the properties:

• Community-run - the properties compete for the same volunteer hours. Adding one starves another directly, kill criteria are about energy rather than return, and the shared-entity rung is often the only way money moves between properties at all.
• Company-run - the properties compete for one marketing budget and are judged on pipeline and adoption. A property can survive a weak year on strategic grounds and die instantly when its budget owner leaves. Cross-property sponsor packaging is largely moot since the company is its own sponsor: wire the KPIs through samber/dev-event-organizer-skills@corporate-event-strategy and present these substitutions as reasoned stand-ins, never as established practice.
• Mixed - a community meetup and a company-funded conference under one team. Worth naming as its own pole because it is the one case where the shared-entity rung stops being optional: whose brand, whose list, and whose money each property uses has to be written down before a sponsor, a member or a tax authority asks. A reasoned pole rather than an observed one.

Workflow

1. Run the interview. Apply the franchise test (Q2) before anything else: a set of independent teams under one brand is not a portfolio, and every menu below will give the wrong answer for it.

2. Inventory the properties. One row each: cadence, size, audience, rough cost, the single person who owns it end to end, and what it is for in one sentence. A property whose purpose nobody can state in one sentence is the first kill candidate, before any other criterion is applied.

3. Name the funnel, pair by pair. For each ordered pair of properties, write what actually carries a person from the first to the second, and mark it exists or aspirational. A portfolio with no existing path between any two properties is a set of separate events sharing a logo; fix that before adding anything. The cheapest real mechanic, wherever two properties run close enough in time: a single slide promoting property B placed inside the deck of property A while A is still running. The highest-intent audience for B is physically in the room for A, and the mechanic costs one slide, not a campaign.

4. Check cadence collisions against one team and one audience, in that order - the team constraint binds first. Lay the properties on a twelve-month calendar and mark each property's build-up window, not just its date: the six weeks before a conference is when its team is unavailable, and that is where collisions actually happen. Flag any two properties whose build-up windows overlap, and flag separately any two whose audiences are the same people within one quarter.

5. Decide the shared-infrastructure set (menu 2 below). Do this before composition: what you can share determines what a new property would actually cost.

6. Decide the cadence posture (menu 3 below), then re-run step 4's calendar against it.

7. Decide composition (menu 1 below): what to add, if anything. Hard gate: nothing gets added while the flagship is unstable, meaning fewer than two completed editions, or a last edition the team or the budget did not come out of intact (Q1). An unstable flagship plus a new property is two weak properties, not a portfolio.

8. Write the allocation posture: how organizer hours and money split across the properties, and what visibly breaks first when one starves another. Treat this as a question set the team answers for itself, never as a formula:

   • Which property loses its owner first?
   • Which property's quality drop would be noticed by attendees soonest?
   • Which one are the sponsors actually paying for?

   Route the money modelling to samber/dev-event-organizer-skills@event-budget.

9. Write add/kill criteria per property, in advance and dated. Write the team's own: a named metric, a floor value, and the number of consecutive editions below it that trigger a retirement conversation. A criterion written after a property starts failing is a negotiation, not a criterion.

10. When the composition call is contested inside the team, enter brainstorming mode instead of recommending:

    • Two or three candidate portfolio shapes, each with trade-offs and a recommendation.
    • Questions asked one at a time.
    • Each section of the plan validated before the next.

    Never emit a portfolio plan the team has not walked through section by section.

If your harness has persistent memory, record:

• The property inventory, with each purpose sentence and owner.
• The funnel paths, marked exists or aspirational.
• The shared-infrastructure rung chosen, and the ones rejected.
• The cadence posture and the allocation posture.
• Every add/kill criterion, with its date.

Next year's portfolio call then starts from this team's own history rather than from generic cases.

Portfolio composition

What to add to the set, if anything. Ranking below is a default, not a law.

• effort (hours, coordination, whether the commitment ever ends): standalone second format > low-cadence small format > recurring media property > co-located add-on > continuity surface
• value (audience carried across the gaps, plus audience the flagship cannot reach): standalone second format > low-cadence small format > continuity surface > recurring media property > co-located add-on
• efficiency: continuity surface > low-cadence small format > co-located add-on > recurring media property > standalone second format
• compliance cost (review triggered, reversibility lost): standalone second format > co-located add-on > recurring media property > continuity surface. The low-cadence small format carries none in the common case - a hosted room and an open invitation sign nothing.

Re-rank against the interview:

• A near deadline (Q7) promotes the continuity surface and the co-located add-on, the only rungs needing no second production cycle.

• A compounding mandate (Q8) promotes the continuity surface and the low-cadence format, and demotes the co-located add-on, which buys nothing between editions.

• A co-organizer looking for a property of their own, or a venue hosting for free (Q9), promotes the standalone second format past its normal position.

• Continuity surface - the default rung: one always-on, non-event property that holds the audience between editions (a chat space, a list, a publishing surface), near-zero to start, and the only rung that directly answers the momentum-between-editions problem. A hackathon network acquired an always-on developer community platform that demonstrates the pattern: a participant's work becomes "permanent, searchable, and useful to the next person" for the next cohort. Animating it is samber/dev-event-organizer-skills@event-community-building's job, not this skill's; this skill only decides whether it belongs in the portfolio.

• Low-cadence small format - a monthly or quarterly meetup under the same brand, feeding the flagship. A community conference organizing guide recommends it bluntly: "No local meetup? No problem! Start one. Even if it's once a quarter, it starts building up an audience, and you get a sense of who is out there." Move up to it from the continuity surface once the surface has an audience and the gap between editions is still visibly cold. Its highest-value use is as an R&D and pipeline surface rather than a separate program: run a hands-on session on whatever is newly relevant to the flagship's own subject as soon as it emerges, and the meetup produces both a tested content idea and a warm audience for the flagship at once, ahead of anything the flagship's own planning cycle could source that fast.

• Co-located add-on - a second program inside the flagship's existing venue and dates: a workshop day, a co-located mini-summit. This pattern bundles several co-branded conferences into one regional edition sharing venue, week and sponsors. Bounded effort - one extra program per edition, no new date, venue or travel decision - but it buys nothing during the other eleven months, which is why it ranks below the meetup despite costing less.

• Recurring media property - a podcast, newsletter or video series on its own cadence, reaching past the room and past the city with no capacity ceiling. It ranks below the co-located add-on on efficiency because its cost never ends and its value only accrues across many issues: a property that stops publishing reads as dead, which is worse than never having started. Whether it converts listeners into attendees is unmeasured - treat any conversion rate as self-set, and never attach a figure to the claim.

• Standalone second format on its own date - the starved option: a hackathon, a startup weekend, a second conference line. Highest value on the menu, since it reaches an audience the flagship structurally cannot (students, beginners, builders rather than listeners) and creates a second sellable moment for sponsors, but it loses every efficiency round because it is a full second production cycle. Promote it only when all three hold:

  • The flagship has run at least two stable editions.
  • A distinct audience keeps asking for something the flagship's format cannot host.
  • A different person can own it end to end.

  The flagship's own lead taking a second property is how both properties get worse.

A second property under its own name with no announced relationship to the flagship, no shared list and no cross-promotion path is deleted from this menu, not ranked last. The portfolio's entire value is the funnel between properties; an unlinked property is a separate event that competes with your own flagship for the same team's hours while returning none of the compounding. Parked at the bottom, it comes back the moment a co-organizer wants their own brand.

Shared-infrastructure depth

What the properties share. Cumulative: each rung assumes the ones above it. Ranking below is a default, not a law.

• effort (setup, coordination, legal and consent work, reversibility): one entity and budget > cross-property sponsor package > shared team and playbook > shared audience list > shared brand only
• value (funnel paths that actually work, money moved between properties, cost taken off the next property): shared audience list > cross-property sponsor package > shared team and playbook > one entity and budget > shared brand only
• efficiency: shared audience list > shared brand only > shared team and playbook > cross-property sponsor package > one entity and budget
• compliance cost (review triggered, reversibility lost): one entity and budget > cross-property sponsor package > shared audience list > shared team and playbook. Shared brand alone carries none.

Re-rank against the interview:

• A mixed community/company portfolio (Q5) promotes the shared entity out of the basement, since that case needs the money boundary written down before anything else.

• A sponsor already renewing on two properties separately (Q9) promotes the cross-property package.

• A hard deadline (Q7) demotes both the package and the entity, the two rungs that cannot be done quickly.

• Shared brand only - one name, one visual system, one page listing every property. Near-zero effort, thinnest value, and second on efficiency for exactly that reason: recognition transfers between properties at almost no cost. It is a floor, not a portfolio.

• Shared audience list - the default rung and the highest-value one: one audience record spanning the properties, so an attendee of any property can be

...