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.