Skip to content

Failure Modes Memo — First-Timer Risks for This Group

Session: 3 (updated Session 9 — Failure Mode 9 added for new Luther site) Priority: High — specific to this group's backgrounds; reduces the most predictable mistakes


Purpose

This memo documents the failure modes most likely to affect this specific group based on their backgrounds. Generic first-timer mistakes are filtered for what actually applies to Amber, Matt, and Danny as a group.


Failure Mode 1: Water underplanning

Who is at risk: Everyone, but especially the group as a whole if Matt doesn't treat water as a primary planning item.

How it happens: - The calculation seems simple ("we'll bring a case of water bottles") - Nobody accounts for cooking, coffee, dishwashing, plus drinking in summer heat - By Day 3, the group is rationing or doing runs - There are no runs to make

How it specifically affects this group: Matt's festival logistics experience may not include water-carry planning since festivals have water stations. His default supply model needs explicit recalibration.

Prevention: - Calculate water before finalizing any packing plan: 1.5–2 gallons/person/day × full trip duration - Buy food-safe 5-gallon jugs, not individual bottles (easier to track volume) - Add 20% buffer for waste and guests

Detection signal: "We have enough" without an actual number. Replace with an actual number.


Failure Mode 2: Shade structure under-built or collapsed

Who is at risk: Everyone. This is the most common first-year camp infrastructure failure.

How it happens: - A standard canopy with clip-in stakes gets set up on flat ground - A weather front comes through with 30+ mph gusts (common in Michigan June) - The canopy collapses on gear, people, or both - Even if it doesn't collapse, an unstaked canopy becomes a hazard

How it specifically affects this group: Matt is the right person to own this — but only if he knows the standard EZ-up staking is insufficient for event conditions. He may bring his standard festival setup without adjusting for longer duration and weather exposure.

Prevention: - Heavy-duty stakes, minimum 12 inches - Guy lines on at least 4 corners - Consider ratchet straps to a vehicle or nearby anchor for storms - 10x10 EZ-up with solid side walls, not mesh — wind and rain blocking matters

Detection signal: Setup takes less than 20 minutes. A properly anchored shade structure takes longer.


Failure Mode 3: Sleep deprivation compounding

Who is at risk: Amber especially; potentially all three members.

How it happens: - Night 1: too stimulated to sleep well, or too worried about what's happening outside - Night 2: stayed out too late, slept light - By Night 3-4: cognitive function and emotional regulation are significantly degraded - Things that would be fine become irritating, things that are interesting become overwhelming

How it specifically affects this group: Amber's default orientation toward supporting others means she may prioritize group activity over personal sleep needs. She needs explicit permission to sleep when her body needs it, not when it seems socially optimal.

Prevention: - Earplugs and eye mask for everyone (not optional) - Establish personal sleep priority in the pre-event conversation: "your sleep is not negotiable for you" - No social pressure around sleep schedules - Tent positioned away from peak traffic areas if possible

Detection signal: "I'm tired but I don't want to miss anything." This is the exact moment to sleep.


Failure Mode 4: The supply-gap surprise

Who is at risk: Amber and Matt — both come from contexts where you can buy missing items.

How it happens: - Someone forgets something (sunscreen, a specific food, medication, a crucial piece of gear) - The reflex is "I'll just get it there" - There's nothing to get

How it specifically affects this group: Both Amber and Matt have festival and camping backgrounds where a store or vendor is accessible. The "I can get it there" reflex is deeply conditioned and will not disappear from habit alone.

Prevention: - Physical packing checklist, reviewed 48 hours before departure - Specific line items for: sunscreen, medication, earplugs, eye mask, electrolytes, chapstick, personal hygiene - Matt and Danny cross-check supply lists before final packing

Detection signal: A packing list that was written but not checked twice.


Failure Mode 5: Poor MOOP on departure day

Who is at risk: Everyone — strike day is when MOOP failures happen most.

How it happens: - Departure morning is chaotic: tired, behind schedule, emotionally processing the event ending - Small items get missed (zip ties, fabric strips, cigarette butts, food scraps) - The "good enough" threshold drops when people want to be done and driving home

How it specifically affects this group: Amber may not have MOOP framing from prior events. Matt may not have experienced an event where his camp's cleanup choices affect the event's future relationships with the land. Neither baseline includes "this matters beyond our immediate cleanup."

Prevention: - Danny owns the departure-day sweep protocol (see LNT memo) - Assign specific sweep roles before departure morning — not "everyone look around" but "you sweep the east side, I'll do west" - Pre-agreement: nothing is packed until the sweep is done

Detection signal: "I think we got everything" without a structured sweep.


Failure Mode 6: Gray water neglect

Who is at risk: Everyone — this doesn't exist in prior experience for anyone except possibly Danny.

How it happens: - Gray water bucket fills up but no one checks it - Someone dumps it on the ground, which violates LNT and may violate site rules - Or it overflows and becomes a smell and hygiene problem

How it specifically affects this group: Nobody in the group has prior gray water management experience at this type of event. This is a new system with no existing habit to draw on.

Prevention: - Danny designs and sets up the gray water system on arrival (see LNT memo + INFRA checklist) - Designate the gray water check as a named daily task — not assumed - Trough-style evaporation setup minimizes management burden if site rules allow it

Detection signal: The gray water container is never checked until there's a problem.


Failure Mode 7: Over-schedule, under-wander

Who is at risk: Amber (activities-coordinator reflex toward scheduling) and Danny (experienced, may have specific things they want to return to).

How it happens: - The group builds a mental schedule of things to see and do - The schedule becomes a source of stress when spontaneous things happen - The group misses genuinely good unplanned moments because they're "supposed to be somewhere"

How it specifically affects this group: Amber's professional instinct is to fill time with planned activities. The event rewards the opposite.

Prevention: - Pre-event conversation: "we have anchors (meals, check-ins), not a schedule" - Acknowledge that wandering and not knowing what's next is the design, not a failure - Accept that you will miss things. That is fine.

Detection signal: A group member saying "we need to be at X at Y time" more than once a day.


Failure Mode 8: Group member goes missing (socially or literally)

Who is at risk: Amber — unfamiliar site, potentially overwhelmed, may wander and lose orientation.

How it happens: - Someone wanders the event and loses track of time and location - Cell service is spotty - They're not in immediate danger but nobody knows where they are for 4+ hours

How it specifically affects this group: First-time attendees often underestimate how disorienting the site becomes after dark, when tired, or after consuming substances.

Prevention: - Camp landmark visible from distance (flag, light string, distinctive marker) - Pre-agreed meeting location that doesn't require phones - Daily check-in agreement (see PSYCH-PREP memo) - Each person does at least one daytime orientation walk to memorize camp location from multiple directions

Detection signal: "We'll just find each other using our phones." Cell service is unreliable. This is not a sufficient plan.


Failure Mode 9: New site terrain and insect exposure

Who is at risk: All three members — nobody has been to the Luther site before.

How it happens: - The group arrives expecting something like an established campground or prior LoF layout - The Luther site is 80 acres of raw land with rolling hills, cedar swamps, and a winding creek - Camping in a low-lying area near the swamp or creek leads to standing water after rain - Evening sitting in the meadow without bug spray leads to significant mosquito exposure - Uneven terrain (roots, rocks, soft ground near swamp) leads to ankle issues if navigated in sandals or at night without proper footwear - Stakes can't be hand-pushed into rocky or root-dense Michigan woods soil

How it specifically affects this group: None of the three have been to this site. Prior LoF experience (Danny) was at the Mecosta County site. Maps and campsite advice will not fully transfer. The undeveloped terrain is a genuine unknown for the first arrival.

Prevention: - Insect repellent (DEET or picaridin) for everyone — non-optional for this site - Closed-toe shoes with grip as dedicated camp shoes — not sandals - Rubber mallet for stakes — bring it, do not assume hand-driving works - Campsite selection away from cedar swamp areas and creek-adjacent low ground - Danny does Day 1 walkthrough to understand actual terrain before group commits to campsite

Detection signal: Arriving without insect repellent, or setting up camp in a low, shaded, swampy-looking area because "it looked nice and shady."


Decision memo

  • Keep: This failure mode list as a pre-event group read — especially for Amber and Matt
  • Standardize: Packing checklist must be physical and reviewed 48 hours before departure
  • Assign: Matt owns water volume calculation; Danny owns departure sweep protocol; Danny designs gray water
  • Reject: "I think we got everything" as a departure standard
  • Test: Visual camp landmark (flag + LED string) for nighttime navigation — this memo makes the case for it
  • Add (Session 9): Failure Mode 9 — new site terrain and mosquito exposure at Luther MI
  • Revisit: After the event, identify which failure modes actually appeared and update for next year