Commensality as Commons
Also known as:
Eating together (commensality) is ancient practice of creating bonds across difference and building shared belonging. Commons that prioritize shared meals as ritual strengthen the commons itself.
Eating together is an ancient practice of creating bonds across difference and building shared belonging.
[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Commensality studies.
Section 1: Context
In organisations, movements, public agencies, and product teams, silos deepen. People eat alone at desks, in isolated breakrooms, or skip meals entirely in pursuit of individual productivity. When they do gather, meals are transactional—catering at meetings, fuel between tasks, not ritual. The commons itself fragments: stakeholders cease knowing one another as whole humans; trust exists only in formal channels; knowledge flows downward or sideways but rarely becomes truly shared. In activist spaces, shared meals once anchored collective action; now many organising happens in async spaces, diluting the embodied knowing that sustains long campaigns. In product teams, shipping velocity is rewarded; the time cost of eating together registers as waste. Government services operate on scarcity logic: meal breaks are efficiency losses, not system-building. Across all these domains, a common pattern emerges—the system is functioning, meetings are held, work moves forward—but it is not alive. Relationships remain instrumental. New members do not feel they belong. Decisions that require genuine collective wisdom default to hierarchy because there is no embodied trust to draw on. The commons is hollow because the practices that make it real—the ones that convert strangers into stewards—have been optimised away.
Section 2: Problem
The core conflict is Commensality vs. Commons.
Commensality—the practice of eating together—carries ancient power: it breaks hierarchy, creates vulnerability, establishes obligation across difference. Yet commons engineering often treats eating as separate from “real work,” a personal wellness issue or a scheduling hassle. The tension is not whether meals matter; it is whether they matter to the commons itself.
One force says: meals are private, personal, best left to individuals. Time spent eating together is time not spent producing. Efficiency demands we optimise away ritual. This view treats the commons as a coordination mechanism, not a living culture. Decisions can be made in writing. Trust can be codified in contracts.
The other force knows: you cannot steward what you do not love, and you do not love what you do not know. Commensality creates the conditions for recognition—seeing the human across from you, understanding their constraints and gifts, making eye contact during disagreement. Without it, the commons becomes a set of rules enforced by strangers. Governance becomes punishment. Resilience collapses because no one has skin in the game beyond their paycheck or ideology.
When the tension is unresolved, the commons degrades in a specific way: it remains functional but loses vitality. Rules exist; people follow them or do not. Belonging does not form. New entrants remain outsiders. When crisis comes—funding loss, conflict, burnout—there is no web of mutual obligation to pull the system back together. The commons survives as an empty shell.
Section 3: Solution
Therefore, establish shared meals as a non-negotiable ritual stewarded by rotating members, where the act of cooking and eating together becomes a deliberate practice of building co-ownership.
This pattern works by shifting commensality from personal choice into commons infrastructure. When eating together becomes ritual—scheduled, expected, resourced—it is no longer something individuals must carve out time for. It becomes the Commons doing its own maintenance work.
The mechanism is this: shared meals create what anthropologists call “commensality bonds”—relationships forged through the vulnerability of hunger and satiation, the negotiation of taste and dietary need, the economics of who brings what, who cooks, who cleans. These bonds are not sentimental; they are structural. They create channels through which tacit knowledge flows. A newer member learns from an elder not through a training program but through conversation while chopping vegetables. A conflict between departments does not escalate through formal grievance channels—it surfaces over bread, where tone and body language make the real disagreement visible.
More specifically, this pattern works through rotation. When different members take turns stewarding the meal—buying, cooking, hosting—the commons becomes consciously maintained by its members rather than delegated to staff or assumed to happen naturally. This rotation makes co-ownership visible and practiced. Each person tastes what it means to feed others; each person receives food they did not have to produce themselves. The economics of care become tangible.
In living systems terms, shared meals are the rhizome of a commons—the root network that connects surface parts. You can have excellent governance (formal structures) and active collaboration (explicit projects), but without the rhizome, when stress comes, the system shatters. Commensality rebuilds that root network by creating repeated, embodied exposure to interdependence. The commons does not just work together; it becomes a body.
Section 4: Implementation
In corporate intrapreneurship, establish a “Commons Kitchen” ritual: one hour, weekly, at the same time. Rotate who cooks—including leaders and individual contributors in the same pool. Require attendance for core team members; make it optional for guests to allow porous boundaries. Do not use this time for meetings. Conversation flows naturally or does not. The steward for that week owns sourcing, cooking, and deciding what gets eaten—creating real decision-making power, not theatre. Track this in your calendar the same way you track board meetings. When a project ships or a conflict resolves, the first recognition happens over a meal someone made. This transforms the commons from a Slack channel into a place.
In government service, pilot “Commensality Hours” in public-facing teams—tax offices, welfare intake, licensing bureaus. Once weekly, team members eat together before a shift where they serve the public. The meal is not efficiency; it is deliberate preparation for encountering citizens as whole humans. Staff rotation ensures the meal changes: sometimes the director cooks, sometimes the newest hire. This breaks the hierarchy that makes public service rigid. Teams that do this report higher stress tolerance, fewer errors in processing, and better handling of angry constituents—because they have just spent an hour in mutual vulnerability with colleagues. The commons they steward (public trust) cannot be separated from the commons they live in.
In activist movements, revive the “Supper Council” model: a weekly meal where all roles are dissolved for the duration. Organisers, strategists, frontline folks, funders—they eat at the same table, and decisions about campaign direction surface naturally through conversation, not hierarchy. Cook from scratch; source from members’ networks and gardens where possible. This rebuilds the gift economy that sustains movements beyond funding cycles. When collective action requires months of sacrifice, the commensality bond is what holds people when morale falls. Movements that have lost this practice often experience sudden collapse; movements that maintain it survive splits.
In product teams, establish “Ship Meals”—a celebration that happens every time a feature launches, not annually. The person or pair who shipped decides what gets cooked and who cooks with them. This is non-negotiable time away from the backlog. Over time, this builds a culture where velocity is not the goal; sustainable co-creation is. Teams report fewer burnout cycles and more retention of people with deep product knowledge. It also changes how design decisions get debated—when you know the engineers you disagreed with are going to cook for you next week, disagreement becomes workable.
In all contexts: resource the meal financially (do not ask members to subsidise commons maintenance), rotate stewarding roles quarterly (to prevent one person becoming the designated cook), and track participation as a commons health metric alongside traditional KPIs.
Section 5: Consequences
What flourishes:
New members integrate faster because they arrive into an already-existing web of relationships, not a task list. Trust compounds—small repeated exposures to vulnerability create robust bonds that survive disagreement. Tacit knowledge spreads through conversation during meals, reducing training time and institutional forgetting. Decisions that emerge from commensality bonds carry legitimacy because they were forged in a context where all parties saw each other’s humanity. The commons develops what we might call “metabolic resilience”—the capacity to absorb shock because there is real care underneath formal structure. People stay longer. They show up differently in conflicts because they have already survived small vulnerabilities together. Creativity rises because people feel safe enough to think out loud. The commons becomes generative, not just coordinative.
What risks emerge:
This pattern sits at a vitality score of 3.5 because it is fundamentally maintenance-oriented—it sustains existing health but can calcify into empty ritual. When commensality becomes routine without intention, it becomes just another meeting. The vulnerability evaporates; people show up, eat, check the box. This hollow commensality is worse than no commensality because it creates the appearance of belonging without the substance. Watch for this when attendance becomes mandatory-but-resentful, or when the meal itself becomes a performance (Instagram-worthy rather than nourishing).
Resilience and ownership both score at 3.0 because commensality alone cannot create adaptive capacity—the commons must also have clear decision-making structures and ways to learn from failure. A team with beautiful meals but no feedback loops will decay. Autonomy also requires protection: this pattern can become a tool for cultural conformity if it is weaponised to police who “fits” the culture. Finally, commensality is vulnerable to scaling—a meal that bonds twelve people may fracture at fifty. Sector-based meals or rotating subgroup meals become necessary, risking fragmentation of the commons.
Section 6: Known Uses
The Slow Food movement’s regional Convivia: Founded in Italy in 1989, Slow Food created “Convivia”—local chapters organised around commensality. Members gather monthly to share meals sourced from their region, learning food history and building governance capacity around food systems. Over thirty years, these meals have created real commons—members have launched local seed banks, founded farmer-led networks, and developed shared land stewardship. What matters: the meal is not incidental to the political work; it is the political work. Members say they trust each other because they have stood in each other’s kitchens, argued about sourcing, and eaten failures together (a bad harvest, an overcooked dish). The Convivia model spreads across ninety countries because the practice is transferable: anywhere you gather people around food, you can build a commons.
Highlander Research and Education Center’s communal dining: Operating in Tennessee since 1932, Highlander trained civil rights organisers, environmental activists, and labour leaders. Every person at Highlander—staff, workshop leaders, participants—eats the same meal in the same dining hall, served family style. This destroyed hierarchy in a segregated era: activists across race, class, and geography broke bread together. Participants report that the commensality created the conditions for the hard conversations that followed. When Walter Brueggemann and other theologians later studied Highlander, they identified commensality as the “hidden curriculum”—the practice that made formal education stick. Highlander still operates this way; the meal is their commons.
Gitlab’s “All-Hands Dinners” (transformed): GitLab was a fully distributed product team with no physical office. In 2015, to address team fragmentation, they instituted quarterly global gatherings where all members flew in for a week. Early attempts at trust-building through workshops failed until someone insisted on commensality: every evening was a shared meal, rotating who cooked and who cleaned. These were not team-building exercises; they were necessity. Distributed teams who had only ever Zoomed suddenly experienced each other as bodies with dietary needs, cooking preferences, table habits. The meals became the hinge point: virtual collaboration suddenly felt less lonely because it was tethered to lived relationship. Teams that participated in the dinners had higher retention; teams that skipped them atrophied.
Section 7: Cognitive Era
In an era where AI handles coordination and async communication replaces meetings, commensality becomes more radical, not less. When a machine can schedule tasks and route messages, the only irreducible reason to gather is the one that machines cannot replicate: embodied presence. This upgrades commensality from “nice to have” to “core commons infrastructure.”
AI introduces new risks. Distributed teams mediated entirely through language models and collaborative documents will lose the non-verbal channels that commensality repairs. Product teams building AI systems for users will become increasingly isolated from each other unless commensality is explicit. The default is acceleration and isolation; commensality becomes the circuit-breaker.
But there is also new leverage. AI can handle meal logistics better than humans—coordinating dietary needs, finding local sourcing, even assisting with recipe planning—freeing human creativity for the actual work of cooking together and building relationship. Some teams are experimenting with AI-assisted “commensality scheduling”: systems that learn preferences, rotate roles, and surface cross-team meals that would otherwise never happen. This is not replacing the meal; it is removing friction from showing up.
The tech translation deepens here: in product teams building AI-mediated commons (platforms, tools, networks), the team itself must experience commensality deliberately. You cannot design for belonging in systems you do not know how to create for yourself. Teams that eat together design products that create genuine connection; teams that are isolated design machines that optimise for engagement metrics instead.
Section 8: Vitality
Signs of life:
The meal happens regularly and people show up with their whole selves—not checking phones, contributing to conversation, asking questions about each other’s lives that extend beyond work. New members report feeling part of the commons within weeks, not months. Decisions that require genuine collective wisdom surface first over a meal, then get formalised in writing—not the reverse. Conflict gets addressed before formal grievance because someone says “we need to talk about this” while washing dishes. Rotation of cooking duties is actual—the rotation is not always the same person, and it is not always the “designated nurturers.” The meal is resourced; no one is using their own money to feed the commons. Attendance is expected but not forced; absences are noticed and checked on. When someone leaves the commons, the meal is where goodbye rituals happen.
Signs of decay:
The meal becomes optional, then sporadic, then optional again—a nice idea that never quite happens. When it does happen, people eat in separate clusters, or they attend but stay silent. The same person cooks every time, or it gets catered, removing the act of care from members’ hands. Conversation stays at the surface—no real exchange about conflicts, dreams, or vulnerabilities. New members feel like outsiders even after attending several meals; belonging is not forming. The meal becomes a performance—Instagram-worthy, curated, extractive—rather than nourishing. Attendance drops, especially from those who are busiest or most stressed. The commons starts saying “we should really do meals again” the way it says “we should exercise more”—as something acknowledged but not prioritised. When conflict arrives, the meal cannot hold it because there is no trust stored in the relationship bank.
When to replant:
If commensality has decayed into ritual without substance, pause. Do not force meals; instead, invite one person to cook for five, with no agenda. Let that small group rebuild the practice before scaling. If the commons is growing faster than commensality can reach—new members arriving before old relationships are secured—create sector-based meals (by role, by project, by tenure) and rebuild the commons as nested convivia. The right moment to restart is when people say “I miss eating together” or when you notice conflict hardening into silence—that is the signal that the rhizome needs tending.