--- title: The Challenge — two agile cells, live author: IBEAR 49 cohort cohort: IBEAR 49 language: en date: 2026-08-21 paths: [stayer, returner, pivoteer, climber] --- # The Challenge **The idea:** don't wait for the program to build what the cohort needs. Form a small cell, pick a real problem, run it like a product team. Two cells are live. There's room for more. Each cell runs the toolkit's own method: one prioritized list, 1–2 week blocks, a 2-minute check-in, a short retro. Roles rotate. Nobody is the boss. Announce, don't assign. --- ## Cell 1: Cohort Connect **Product Owner:** Debbie · **Scrum Master:** Jessie **The problem:** 38 people from 10 countries meet for one year, then scatter across the Pacific. The connective tissue — who knows whom, who's working on what, who can help — lives in a group chat that goes quiet by winter and dies at graduation. **The build:** a LinkedIn + Facebook hybrid for the cohort — professional profile *and* human connection in one place. Who you are, what you're building, what you need, what you can offer. Designed to extend to alumni from day one, because the network inside the program is what opens the network outside it. **The hand-over path:** same as this wiki — **plug-and-play for IBEAR Connect**. If the program adopts the model, the structure, profiles, and connections move into the official platform as its own. Build it where we can move fast; graduate it where it can live forever. --- ## Cell 2: The Potluck Kernel **Product Owner:** Chris · **Scrum Master:** Tariq **The problem:** every support system the cohort needs — housing tips, interview prep, intros, childcare during finals, a couch in Tokyo — keeps getting rebuilt as separate one-off asks. Each ask has friction; most never get made. **The exploration:** the potluck as a *kernel* — one pattern that generates many solutions. At a potluck nobody is the host and nobody arrives empty-handed: **each person brings what they have, and together the table covers everyone.** Applied beyond food: bring your industry knowledge, your spare monitor, your visa war story, your airport pickup — and draw from the table when you need. **The old name for this:** the Hanseatic League ran on it for four centuries — merchant cities cooperating without an emperor, each contributing ships, goods, and safe harbors, all gaining a network none could build alone. No central boss, strong shared norms, mutual benefit as the glue. A cohort where nobody wants to be managed by a peer is the same shape. The potluck is the smallest version of it; the cell is mapping which cohort problems the pattern can absorb. ### Seeds for the cell — questions, not answers **1. Golf is already working. Do you know why?** Golf already pulls two or three groups together in this cohort. Before expanding it, decode it. Golf has three properties almost nothing else has: it's **slow** (four-plus hours of unforced conversation), it's **handicapped** (a beginner and a lifer compete meaningfully — the equalizer is built into the rules), and it **ends at a table** (the 19th hole). Don't copy golf. Extract the kernel: *long + leveled + ends in food.* Now ask: what else in this cohort's cultures has all three? Hiking does. Mahjong does. Cooking a dish from scratch does. A karaoke room almost does. What's missing from each, and can you add it? **2. The handicap is the genius. Design one for everything.** The reason golf bridges is that unequal players can play *together* without anyone being humiliated or bored. Most activities die at the skill gap: the fluent dominate karaoke, the fit dominate the hike, the natives dominate the language. So the real design question for any activity you propose: **what is its handicap system?** What rule lets the beginner and the expert genuinely compete? Solve that, and any activity becomes a bridge. Fail it, and the activity silently re-sorts the cohort back into its groups. **3. Non-players are the expansion mechanism.** "How do we get everyone to golf?" is the wrong question — some people will never golf, and forcing it breaks the potluck rule (bring what you *have*). The right question: **what does a non-golfer bring to golf day?** Someone drives the carts. Someone runs the ridiculous side-bets. Someone cooks the 19th hole. Someone documents it so the group that missed it wants in next time. Every activity needs designed non-player roles — that's how two-or-three groups becomes everyone, without anyone pretending to like golf. **4. The festival calendar is your product roadmap — and it's already written.** Look at the next six months for *this* cohort: Obon is now. Mid-Autumn and Chuseok land in the **same week** — the Taiwan and Korea tables could host one night, two moons. Oktoberfest is late September. Diwali is October–November. Lunar New Year in late January belongs to half the room. You don't need to invent a single event; the calendar already scheduled them. The only question per festival: *who hosts, what's the dish, and what's the one thing the rest of us should know before we show up?* **5. Invert the hosting. The smallest delegation throws the biggest party.** Here's the counterintuitive one. When the largest group hosts its own festival, that's bonding — warm, easy, and it mostly connects people who already know each other. When the *only* German in the cohort hosts Oktoberfest for 37 people, or the one Peruvian runs the asado, that's bridging — the whole room shows up to something none of them knows, and one person becomes unforgettable. The calendar's own rule says it: *if you're the only person from your country, that's exactly the reason to host, not to skip it.* The solo delegations aren't the edge of this cohort's map. They're its highest-value squares. **6. Bonding fills the room; bridging is why you came.** Sociology has names for this: **bonding capital** (ties inside your group) and **bridging capital** (ties across groups) — Putnam's *Bowling Alone* is the classic study, and its title is literally about what happens to a community when shared activities die. Bonding happens by itself; every cohort naturally re-forms its language tables. Bridging is the thing that decays without design — and it's the entire reason people crossed an ocean for this program. So audit any week honestly: how many hours were bonding, how many were bridging? If the ratio embarrasses you, the potluck isn't working yet. **7. The ledger question — what keeps a potluck from becoming a buffet?** Every commons has the same failure mode: takers outnumber bringers, quietly, until the bringers stop. The Hansa never solved this with enforcement; it solved it with *visibility* — everyone knew who contributed what. So the minimal mechanism might just be a public table list: who brought what, this month. No points, no policing, no shame — just visible. Is visibility alone enough for 38 people who see each other daily? That's a real research question, and this cell is positioned to answer it with an experiment instead of an opinion. **The one-block challenge:** pick the nearest festival on the calendar. Run it as a full potluck experiment — inverted hosting, designed non-player roles, a visible table list. Retro afterward with one question: *did someone leave with a bridge they didn't arrive with?* Then write one page here about what actually happened. --- ## Why cells, not committees A committee discusses; a cell ships. Small (2–5 people), role-rotating, block-paced, and judged by one question at each retro: *did something real get built or learned this block?* The two cells are also each other's test: Cohort Connect builds the **map** (who has what), the Potluck Kernel builds the **exchange** (how it flows). If both work, the cohort has an economy, not just a chat. ## Start cell three **The door is open: [Start a Cell ✌️](start-a-cell.md)** — the 30-minute start, a menu of builds ready to claim, and the three rules. All you need is you plus one other person. Or use the announce format directly — post it where the cohort lives: ``` WHAT: [the problem you want a cell for] WHY: [one line — who hurts without it] ROLES: Product Owner + Scrum Master + 1-3 builders IF YOU'RE IN: [reply / react] BY WHEN: [date] ``` Then run the method: one list, short blocks, 2-minute check-ins, a retro. Report what you learn back here — one page, credited. --- **Status:** two cells live, IBEAR 49, August 2026. **Related:** announce-dont-assign, the toolkit's Method section, IBEAR Connect hand-over model.