event-learning-expedition-design

Event Learning Expedition Design

You take your own audience into somebody else's building, where that organization's working operation is the programme. Two decisions follow, and this skill owns nothing else: how much of your agenda depends on a host you cannot direct, and what the host lets your attendees see and repeat.

Read first: the scope is much narrower than the name

A "learning expedition" sounds like a whole event format. Inside this collection it is not, and pretending otherwise hands you advice a sibling skill gives better.

Most of what the format is taken to include already has an owner here, and each owner covers it in more depth than this skill can:

• Several sites in one agenda. Not a new mechanic. samber/dev-event-organizer-skills@event-venue-sourcing's reference file settles it: multi-venue events "inherit this whole sheet once per site, plus the transit time between them and a single named owner per site. That much is straightforward extension." Take the sheet from there.
• Transport and the headcount problem. samber/dev-event-organizer-skills@event-hospitality ranks an offsite excursion below doing nothing at all: "only one of them spends transport, a second building's own rules and insurance ask, and a headcount you cannot correct once the transport has left." That argument applies to you unchanged. One exception: a visit that is a social evening rather than the programme is that skill's subject, not this one's.
• Whether your policy reaches the coach and the host's floor. samber/dev-event-organizer-skills@event-code-of-conduct owns the scope clause. Its reference file records MLH covering "all hackathon venues, hackathon-related social events, hackathon-supplied transportation, and online interactions related to the event." and notes that "a shuttle is neither the venue nor a social event". Hand it the sites and the vehicles, and take back the clause.
• Catering on the move, and every supplier who moves with you. samber/dev-event-organizer-skills@event-hospitality for the service style, samber/dev-event-organizer-skills@event-vendor-sourcing for the contract.
• Who you invite and why. samber/dev-event-organizer-skills@business-event-formats. Its shape ladder ranks the account-depth family, and its compliance axis carries the mechanic people reach for here: "an accepted invitation cannot be withdrawn without insult, and it lands on the guest's own gift and anti-bribery policy before it lands on yours." A named guest with a protocol obligation is samber/dev-event-organizer-skills@event-vip-management; a journalist is samber/dev-event-organizer-skills@event-press-relations.
• Capturing the visit and publishing anything from it. samber/dev-event-organizer-skills@event-production through the master file, then samber/dev-event-organizer-skills@event-content-repurposing. Its rights gate governs you: "Silence is off-limits, not permission."
• Why the event exists, what it costs and how it is measured. samber/dev-event-organizer-skills@corporate-event-strategy. Perception shift and pipeline influence are that skill's goal-and-measurement vocabulary, not yours.

What is left is one structural fact, and it is real. Everywhere else in this collection, a third party supplies either the room or the content.

samber/dev-event-organizer-skills@event-venue-sourcing gets you a room you then fill. samber/dev-event-organizer-skills@event-side-event-coordination handles an event somebody else runs for their own reasons - "Where that skill's evening is the thing you provide, yours is the thing you permit."

Here the host supplies both. So a host who withdraws does not cost you a room you can re-book: it deletes the programme.

Nothing in the collection covers that. Nothing covers what a host organization - which is not a speaker, not a sponsor and not a vendor - permits your attendees to see and to repeat. The consent chain this collection runs on goes organizer to speaker, and it has no branch for the organization that opened its floor.

Route any question other than those two decisions to the owners above, and stop. This skill is short because those two decisions are all it owns.

Do not invent a number for any deliverable built from this skill. A site count, group size, briefing length, lead time, or host-approval turnaround is the host's to state, and an invented number outlives the caveat attached to it. Describe the constraint qualitatively and ask the host.

This skill states no legal threshold, jurisdiction, form, instrument name or monetary figure. That is the standing policy samber/dev-event-organizer-skills@event-side-event-coordination holds for liability and samber/dev-event-organizer-skills@hackathon-cash-prize holds for prize law. The access-posture rungs describe postures, not instruments, and any paper they need is counsel's to name.

Interview

Ask one question at a time, multiple-choice where possible. Every condition on both menus names the question it is keyed to, so answer these before ranking anything.

1. Has a host organization agreed in writing to receive your audience, or is this a format idea with nobody's yes behind it? If there is a yes, was it conditioned on anything?
2. Why does the audience need to be physically there: is there a thing that cannot be shown on a slide - a floor, a hall, hardware, a scale, a failure - or is the draw the people and the conversation?
3. What is the audience's own question: a specific technical one they could push a named engineer on, or an experiential one about how an organization operates day to day?
4. Inside the host, who is the named counterpart, and can that person commit their colleagues' time, or only their own?
5. Has the host stated a restriction - an area, a customer name, a photography rule - and did that come from someone who speaks for the host, or from your own assumption about what they would want?
6. Is the attendee list bounded and known before the day, or open until the door?
7. Who, by name, would run a post-event clearance queue, and for how long after the event would they still be doing it?
8. What is the effort ceiling and the date: how many people can own this end to end, how much runway exists, and how survivable does a host's cancellation have to be?
9. What already exists that the default ordering assumes away: a standing relationship with a candidate host, an organizer employed by one, a prior edition's expedition, or an agreement already signed with any of them?

Both rankings below are defaults, not laws, and they shift with context and with who executes them. Re-rank against Q9 before recommending anything: an organizer who already works inside a candidate host turns a cold approach into a calendar invitation, and promotes that rung above whatever the default picked.

Workflow

1. Run the interview, Q1 first. If nobody has said yes, you are choosing a format rather than designing one, and samber/dev-event-organizer-skills@business-event-formats owns that choice.
2. Route out everything in the scope section above before going further. Most of what arrives as "design our learning expedition" leaves before either menu is reached.
3. Fix the value axis on the first menu from Q2 and Q3 before ranking it. This is the mechanic samber/dev-event-organizer-skills@business-event-formats uses for its own shape ladder - take it from there rather than re-deriving it.
4. Pick the host-dependency posture, applying its delete rules before ranking.
5. Pick the access-and-repeatability posture, applying its delete rules before ranking.
6. Write the host brief: what your audience is coming to understand, what you are asking their people to do, and what you have told your attendees they may repeat. Send it before the host's internal approvals start, not after.
7. Hand off, explicitly and by name:
   • Sites and vehicles to samber/dev-event-organizer-skills@event-code-of-conduct, for the scope clause.
   • The per-site requirements sheet to samber/dev-event-organizer-skills@event-venue-sourcing.
   • Transport, catering and the headcount to samber/dev-event-organizer-skills@event-hospitality and samber/dev-event-organizer-skills@event-vendor-sourcing.
   • Anything recorded to samber/dev-event-organizer-skills@event-production.
   • Goals and measurement to samber/dev-event-organizer-skills@corporate-event-strategy.
8. Present each decision for validation before anything is promised to a host or published to attendees. A host's approval process is the point of no return: once their people have blocked the time, a change costs their goodwill, not your calendar.

If your harness has persistent memory, record which host said yes and on what condition, the access posture agreed and who agreed it, and the restriction list. A host relationship is the only durable asset this format produces, and the one thing the next edition cannot rebuild from a document.

Host-dependency posture

How much of the agenda depends on an organization that has no obligation to you. Four rungs:

• Host representative in your own room: you invite their engineer to speak where you already control the room. No site.
• One host site, host-led: you go to them and they show what they show visitors.
• One host site, negotiated agenda: you specify what your audience needs to see and they build to it.
• Multi-host circuit: several host organizations in sequence.

Two value axes, and they genuinely disagree. That is why Q2 and Q3 have to be answered before this menu is ranked.

• effort (securing a host with no reason to say yes, briefing their staff, transit between sites, a headcount fixed before departure, an escort per site, and the rebuild when one host withdraws): multi-host circuit > one host site, negotiated agenda > one host site, host-led > host representative in your own room
• value, place - what the audience sees on site that no talk reproduces: multi-host circuit > one host site, negotiated agenda == one host site, host-led > host representative in your own room
• value, fit - the audience's own question gets answered, in their vocabulary, by someone they can push: one host site, negotiated agenda > host representative in your own room > one host site, host-led == multi-host circuit
• compliance cost, as the review it triggers on the host's side - visitor screening, site safety induction, their own confidentiality and customer-data rules - and what stops being reversible once your audience is standing in their building: multi-host circuit > one host site, negotiated agenda > one host site, host-led > host representative in your own room
• efficiency, place per unit effort, the line to use when Q2 names a physical thing: one host site, host-led > one host site, negotiated agenda > multi-host circuit > host representative in your own room
• efficiency, fit per unit effort, the line to use when Q3 names a specific technical question: host representative in your own room > one host site, negotiated agenda > one host site, host-led > multi-host circuit

The place == is argued: a host-led visit and a negotiated one both put the audience inside one real building, and the building is what the axis measures. They differ in what is shown there, which is the other axis's job.

The fit == is argued too, and at the same level rather than at zero: a host-led agenda is a host-led agenda whether the audience sees one of them or a sequence of them, so a circuit multiplies places without improving the answer to anybody's question. That tie does not survive division: equal fit at strictly higher effort is strictly worse fit-efficiency. That is why the circuit sits last on that line rather than level with the host-led rung.

Compliance tracks effort rung for rung here. Admit that rather than presenting it as a second signal: both scale with how far inside somebody else's organization you go, and with how many organizations that is. The axis stays because the exposure is real - a host's screening and induction requirements are theirs to set and you cannot negotiate them down - but it discriminates nothing the effort axis did not already say.

Dominance check: 4 rungs, 6 pairs, zero strict-dominance relations. Covering all six takes two mechanisms, and one alone would cover only half:

• Blocked by opposed value axes (3 pairs): own-room against host-led, own-room against the circuit, negotiated against the circuit. In each, whichever rung leads on place trails on fit.
• Blocked by cost alone (3 pairs): own-room against negotiated, host-led against negotiated, host-led against the circuit. In each, the rung ahead leads on both value axes (tying one of them in the last two) and still costs strictly more on effort and on compliance.

That accounts for all six.

The two value axes are not exact inverses of each other. They tie in different places, so this check carries real information rather than being clean by construction.

• One host site, host-led - the default. It buys the whole "they were actually there" effect for the least coordination, and it is the rung a host can say yes to without convening anybody. Promote it to the negotiated agenda when Q3 says the audience's question is specific and Q4 names a counterpart who can commit their colleagues' time. Both, not either: a specific question with nobody inside to route it produces a standard tour with your hopes attached.

• Host representative in your own room. Tops the fit-efficiency line and costs almost nothing. When Q3 says the question is technical and specific, this is the honest recommendation: say so plainly and close this skill rather than designing travel around a conversation that fits in a session. Delete it, from this menu and from every axis line above, when Q2 names a physical thing that cannot be shown on a slide. A talk is not a smaller version of standing on the floor, and a deleted rung left at the bottom returns later as a cost saving.

• One host site, negotiated agenda. The rung that answers a specific question, at the price of an internal owner inside the host. Delete it, from this menu and from every axis line above, when Q4 finds no counterpart who can commit colleagues' time. Without one it is not a cheaper negotiated agenda. It is the host-led rung plus meetings, which is the worst cell on this menu.

• Multi-host circuit - the starved rung. Tops place, tops both cost axes, and neither efficiency line ever picks it. Promotion conditions are keyed to Q9 and Q8, each carrying its own weight:

  • Q9: standing relationships with more than one candidate host, so each additional site is a call rather than a cold approach.
  • Q8: enough runway that one host withdrawing does not collapse the day.

  Both conditions apply together, not either alone - a circuit built on cold approaches with n

...