--- title: The bigger table — every Marshall population, reverse-engineered author: IBEAR Toolkit cohort: IBEAR 49 onward language: en date: 2026-08-22 paths: [stayer, returner, pivoteer, climber] --- # The Bigger Table **The question:** IBEAR is 38 people. Marshall is thousands — undergrads, five MBA formats, specialized masters, PhDs, faculty, staff, and a global alumni network. How does one cohort's potluck plug into all of that? **The method:** don't design it from scratch. Reverse-engineer what has *already* connected organically, extract the pattern, and point it at each population. --- ## What we've already watched work Four connectors, all observed in the wild this year — none of them invented: 1. **The staff broker.** One career-services introduction crossed three populations in two emails: an alum, a student from a *different* MBA program, and the staff member who saw the match. Staff see every population at once; students and alumni see only their own. **Staff already act as the routers of the Trojan network** — one intro at a time. If a conversation ever opens, the cell menu is sitting here ready; that's an offer, not an assignment. 2. **The panel that leaked.** The July alumni panel wasn't IBEAR-pure: four IBEAR generations *plus a Marshall MBA from another program* shared one stage — and the panelists reconnected with each other as much as with the students. An event built for one population organically becomes an exchange between several, plus an alumni reunion nobody scheduled. Events leak on purpose. 3. **The leveled activity.** Golf already bridges groups inside the cohort because it's long, handicapped, and ends at a table. Nothing about that kernel is cohort-specific — a leveled activity bridges *populations* exactly as well as it bridges *countries*. 4. **The concrete ask.** What actually traveled across program lines was never "let's connect" — it was *"confirm narrative and suggested next steps."* Specific, bounded, answerable. The vaguer the ask, the shorter the distance it travels. A concrete ask crosses the whole school. **The extracted kernel:** every population has a surplus and a deficit. A bridge forms when a broker, an event, an activity, or a concrete ask lets one population's surplus meet another's deficit — and the cell (PO + SM + developers + AI) is the vehicle that makes the exchange repeatable instead of lucky. --- ## The population map — who brings what, who needs what | Population | Their surplus (what they bring) | Their deficit (what they need) | Natural cell seat | |------------|--------------------------------|-------------------------------|-------------------| | **Undergrads** | Hands, code, time, native-platform energy — they can *build* | Executive exposure, war stories, references, resume lines | **Developers.** The flagship trade: an IBEAR PO brings 13 years of judgment, an undergrad brings the build. Mentorship flows down, velocity flows up — both leave richer. | | **Full-Time MBA (2-yr)** | Club infrastructure, recruiting-cycle knowledge, two years of runway | International perspective, executive peers to learn from | **Scrum Masters & co-builders** — they know how student organizations actually run here | | **EMBA / PM MBA** | Seniority, US-local networks, hiring power | Fresh narratives, AI fluency, energy — reverse-mentoring | **Advisors** — one conversation per block, not a seat at every standup | | **Specialized masters** (MSBA, MSF, supply chain…) | Deep single-skill firepower: analytics, finance models, ops | Business context, cross-functional teams for their portfolios | **Specialist developers** — the ledger experiment needs exactly one MSBA student | | **PhD students** | Research methods, rigor, publication instinct | Field sites, real data, live experiments | **The observers.** The Hansa ledger question is literally a research question — a cell is a lab that builds itself | | **Faculty** | Legitimacy, classroom vehicles, credit-bearing projects | Living cases, engaged practitioners | **Sponsors** — one cell adopted per course beats ten guest lectures | | **Staff** (career services, program offices) | Sight across all populations, the event calendar, the rolodex | Signal about what students actually need | **The routers** — they already broker intros; the cell menu is here if they ever want it | | **Alumni** (all programs, all decades) | Hindsight, doors, one-answer generosity | A low-cost way to help that isn't "be a mentor forever" | **The razor suppliers** — one credited page, one answered question, one panel seat | | **Corporate partners** | Real problems, sponsorship, hiring intent | Early access to talent that can already ship | **The clients** — a cell's block output is a live audition | --- ## The channels that already exist (use, don't build) No new platform needed — each population already reads a channel: - **Undergrads:** student org fairs, case competitions, the CS/business double-majors hunting for real projects. One announce posted where builders hang out: *"IBEAR cell seeks two developers. Real product, real credit, executives on the team."* That sentence recruits itself. - **Other MBAs:** shared electives, club events, and the staff brokers who serve several programs at once. - **PhDs & faculty:** one email to the relevant department — *"we're running a live commons experiment with 38 executives; want to measure it?"* is catnip to the right researcher. - **Alumni:** the panels that already happen (capture pipeline), IBEAR Connect, and the one-answer inbox. - **Everyone at once:** the courtyard. The physical potluck — a festival from the calendar with the doors deliberately left open to other programs — is the only channel that reaches every population in a single afternoon. Food remains the most portable protocol Marshall has. --- ## The one-block experiments Three cheap tests, each one block long, each answerable with a yes or no: 1. **The undergrad trade:** one cell posts one announce in one undergrad channel offering two developer seats. Did builders show up? Did the mentorship-for-velocity trade hold? 2. **The open festival:** the next calendar festival invites one other Marshall population explicitly. Did anyone cross? Did a bridge survive two weeks past the event? 3. **The router test:** if a staff conversation opens naturally, mention the cell menu. Did an intro find its way to a cell within a block? Each experiment ships its one page here — what happened, credited. Three yeses and the bigger table isn't a theory; it's a roster. --- **The compressed version:** *Marshall's populations are shelves of surpluses that never meet. The cell is the table. The announce is the invitation. Staff are the routers, events leak on purpose, and food reaches everyone. Undergrads are the developers the cells are missing — and the cells are the executive rooms the undergrads can't otherwise enter.* **Related:** the-challenge, start-a-cell, alumni-panel razors, the calendar.