Being with Dying

Supporting someone through dying is one of the most profound forms of care available — and most people approach it without preparation, guidance, or a community of practice.

[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Palliative Care / Contemplative Practice.

---

Section 1: Context

Most organizations, movements, and systems treat endings as failures rather than thresholds. When someone is dying—whether a person, a team member, a department, or a product line—the surrounding ecosystem defaults to denial, acceleration, or managed abandonment. The commons becomes fragmented: some stakeholders want to fix or extend; others want to move on quickly; still others become paralyzed. In corporate settings, dying employees are often managed through HR protocols that prioritize liability over presence. In activism, dying movements or leaders are rarely honored; energy shifts to the next campaign. In government, dying programs persist as zombies rather than being consciously released. In tech, dying products receive no graceful sunsetting—they vanish or are killed. Across all domains, the system lacks a coherent practice for what comes at the end: a way of being that neither denies the ending nor abandons those in it. This pattern emerges from the recognition that dying—whether literal or metaphorical—is not a failure of the commons but a natural season, and that how we accompany each other through it determines whether the system remains resilient, trustworthy, and alive.

---

Section 2: Problem

The core conflict is Being vs. Dying.

On one side: Being—the impulse to maintain, fix, extend, control, and deny loss. This force says: “We can solve this, reverse this, optimize our way through.” It generates urgency, action, problem-solving energy. Without it, systems don’t persist.

On the other side: Dying—the ecological reality of endings, decay, release, and transformation. This force says: “This season is finishing; the energy belongs elsewhere now.” It asks for acceptance, witnessing, and letting go. Without it, systems become toxic, hoarding resources and attention meant for new growth.

When the two forces misalign, the commons breaks. The dying person or initiative is abandoned by those still in “being” mode—treated as already gone while still present. Alternatively, “being” mode dominates so completely that dying is medicalized, pathologized, or simply denied, creating invisible suffering and robbing the system of closure and learning. The stakeholder architecture fragments: some stewards want resurrection; others want erasure; few want genuine accompaniment.

The real cost: the system loses trust. People learn that vulnerability—admitting you are diminishing—means being left alone or aggressively “fixed.” Movements lose their elder wisdom because dying leaders have no honored way to pass it on. Products die without teaching what they revealed. Teams lose cohesion when one member’s decline is treated as a management problem, not a communal moment. The commons atrophies because no one knows how to be present to its actual ecology.

---

Section 3: Solution

Therefore, cultivate a rooted practice of showing up without agenda: maintaining steady presence, learning the actual contours of what is ending, and creating deliberate space for the dying person or process to teach what only they can teach.

This pattern shifts the locus of power from the dying toward the accompanier’s capacity to witness without fixing, protect without controlling, and grieve without collapsing. In palliative care traditions, this appears as “bearing witness”—a discipline of presence that honors the patient’s own authority over their dying, not the clinician’s capacity to reverse it.

The mechanism works through a series of small, recursive acts: stabilizing your own ground so you don’t project your fear onto the dying person; asking questions that follow their lead rather than imposing a timeline or narrative; sustaining presence across discomfort—staying in the room when it would be easier to leave; creating ritual containers that mark the threshold and give meaning to the passage. Each act rebuilds trust: the dying person experiences themselves as valuable exactly as they are—not as a problem to solve. The system around them begins to normalize endings instead of hiding them.

The living systems shift: energy that was locked in denial, denial-resistance, and frantic action becomes available for actual learning, connection, and transformation. The “being” energy and the “dying” energy stop colliding and start informing each other. Those in early seasons of growth learn from those at the boundary. The commons develops adaptive capacity—not because we create new programs, but because we restore honest relationship with our own temporality.

This is ecological commons engineering: aligning human rhythm with the actual life cycle of systems, so vitality can flow cleanly through growth, stability, and release.

---

Section 4: Implementation

Establish the threshold literacy. Before you encounter active dying, build collective knowledge of what dying actually looks and feels like—not as medical stages, but as ecological transitions. Host a community circle where those with experience (hospice workers, longtime activists, people who have sat vigil) share what happens in the last months, weeks, days. Name the phases: the active, relational phase (still lucid, still teaching); the liminal phase (consciousness flickering, very little verbal communication); the final dissolution. This grounds people in reality instead of fantasy. Corporate translation: Host an “end of service” ritual before someone leaves due to terminal illness, retirement, or departure. Invite them to name what they’ve learned; ask the team explicitly what they want to receive from this person before they go. Government translation: Create a formal “program sunsetting” protocol that includes knowledge transfer sessions, not just budget closure. Activist translation: Establish an “elder council” where dying or exiting activists mentor newer people explicitly, with scheduled time and recognition. Tech translation: Document the “product autopsy”—why is this product dying, what did it teach, what do we preserve, who do we thank?

Prepare yourself, not the dying person. The dying person does not need to comfort you. Your job is to stabilize your own nervous system so your presence is useful, not draining. Practice: sitting in silence without needing to fill it. Noticing your urge to fix or flee. Breathing through your own grief. If you are religious or contemplative, anchor in your own practice. This is not self-care performance; it is the hygiene required to show up. Meet with one trusted peer weekly to process what you are witnessing. You will need help carrying this.

Follow their agenda, not the hospital’s or the organization’s. Ask: “What matters most to you right now?” and listen to the answer. It might be finishing a conversation, hearing forgiveness, planning a meal, or sitting in silence. Let go of the timeline. Corporate: If someone is dying while still employed, ask them what they want their last weeks at work to include, not what the department needs from them. Government: Exempt dying colleagues from standard exit interviews; instead, offer “legacy conversations” on their terms. Activist: Ask the dying movement organizer what they want documented, who they want to mentor, what story they want told. Tech: Ask the product team and early users: “What should we preserve? What should we release? How do we honor what it taught us?”

Create bounded ritual containers. Dying needs a frame. Without one, time becomes shapeless and the commons doesn’t know how to be with it. This might be: a weekly visiting circle; a meal shared together; a designated quiet hour; a recording session where the dying person tells their story. The ritual says: You matter. We are showing up. This is sacred time. Corporate: Schedule recurring “legacy lunches” where a dying colleague tells their work story and the team listens. Government: Establish a “service reflection” ritual: the dying public servant meets with their direct report and their peers; they share one lesson they’ll carry forward from this person. Activist: Host monthly “elder teachings” where the dying activist receives the full attention of the movement for as long as they want to speak. Tech: Create a “project retrospective” that becomes ceremony—not a meeting. The product team gathers to honor what was built, what broke, what was learned, what gets carried forward.

Document the ordinary. Later, people will want to know not just the grand story but the small ones. What did this person say? What made them laugh? What did they reach for first in the morning? Keep a simple record—written, audio, video—of presence. Not sanitized. Include the difficulty. Corporate: Record a 15-minute video where the dying employee answers: “What do you want people to know?” Government: Photograph the office, the daily routine, the rituals of work. Activist: Record conversations—full sentences, not summaries. Tech: Screenshot the product interface, user feedback, the evolution of the design. These become seeds for meaning-making later.

---

Section 5: Consequences

What flourishes:

The commons regenerates trust in honest endings. When people experience dying as witnessed rather than abandoned, they become willing to admit vulnerability earlier in other cycles. Teams become more permeable—people can take time to grieve without losing their place. Organizations develop institutional memory that survives turnover because knowledge was deliberately passed on. Movements learn to honor their own evolution instead of burning out founders. Products are retired with gratitude rather than deleted. Most importantly: people learn they are valued for who they are, not what they produce, because they encounter that valuation at the moment of least productivity. This ripples backward, changing how the whole system relates to care, time, and belonging. The commons becomes less extractive.

What risks emerge:

The pattern assumes sufficient time for accompaniment—yet dying can be sudden. If implementation becomes performative (rituals without presence, documentation without genuine witness), it creates a hollow theater that can harm more than help. Those doing the accompanying risk burnout if they don’t truly stabilize their own ground; the pattern can become a coercive expectation rather than a capacity. Most critically: at resilience 3.0, this pattern sustains existing vitality but doesn’t generate adaptive capacity. If the organization relies on “Being with Dying” without simultaneously investing in regeneration, succession, and new growth, the system can become a well-lit hospice rather than a living commons. Watch for: rituals that become habit without heart; documentation that becomes voyeurism; “honoring” that masks unwillingness to grieve and move on. The pattern works only if it genuinely opens the next season.

---

Section 6: Known Uses

Dame Cicely Saunders, founding Modern Hospice (1960s): Saunders was a nurse, social worker, and contemplative who recognized that dying patients were being medicalized out of human presence. She established St. Christopher’s Hospice with an explicit practice: patients were not projects to fix but people to accompany. Staff sat with patients, learned their stories, asked what mattered. Family was included. Pain was managed not for the system’s convenience but for the person’s peace. The “being with dying” became the treatment itself. Visitors to the hospice remarked that it felt alive, not deadening. Decades later, this practice seeded the modern palliative care movement. The mechanism: presence without agenda fundamentally changed what was possible in the final weeks. Commons signal: When accompaniment is the core intervention, the system doesn’t collapse under the weight of dying—it becomes stronger.

Zulu Ubuntu Funeral Practices, South Africa: In traditional Zulu culture, dying and death are not private medical events but communal thresholds. When someone is dying, the extended family gathers. They maintain presence—cooking, sitting, singing, telling stories—not to change the outcome but to ensure the person is never alone and the community’s bonds are reinforced precisely at the moment of rupture. The dying person’s last words are remembered and repeated. The funeral is not a separate event but the continuation of accompaniment. Years later, the stories are invoked to teach the young. The pattern sustains the commons across generations because knowledge, relationship, and identity flow through the threshold rather than terminating at it. Commons signal: When dying is communal and ritually held, the system’s coherence survives the individual loss.

Activist Lineage Practice, US Black Radical Tradition: In movements led by Black organizers, dying elders (whether literally or from burnout) have been held in explicit “passing the torch” ceremonies. Ella Baker, Fannie Lou Hamer, and many unnamed organizers invested in mentoring younger people not as a side project but as core work. Younger organizers sat with elders, asked their questions, recorded their thinking, and were explicitly told: “This is what I learned. Take it. Change it. Make it yours.” The rituals were often informal—sitting on porches, riding in cars—but intentional. The result: the movement didn’t lose its wisdom when key people stepped back. Newer generations could access the full depth of strategic thinking and moral clarity because it was transmitted, not abandoned. Commons signal: When dying (or transition) is treated as a teaching moment, the commons doesn’t fragment—it deepens.

---

Section 7: Cognitive Era

In a world of AI, distributed systems, and algorithmic decision-making, “Being with Dying” becomes both more necessary and more complex.

New necessity: As organizations increasingly offshore decisions to AI systems, the human capacity for presence and meaning-making at boundaries becomes rarer and more valuable. If a product is “dying” because an algorithm has determined it’s unprofitable, the workers, users, and communities depending on it experience abandonment. A human being with that ending—asking what the algorithm cannot ask, creating space for grief and learning—becomes an act of radical care. Similarly, as work becomes more distributed and asynchronous, the threshold moments when people leave or step back are easier to ignore entirely. Intentional rituals for dying become more necessary, not less, because the default is isolation.

New risks: AI creates pressure toward speed. Sunsetting a product takes weeks; a new algorithm can replace it in hours. Dying can be accelerated, rationalized, made invisible beneath layers of technical process. There’s risk that “Being with Dying” becomes another box to check—a HR module, a product retrospective checklist—without genuine presence. The pattern also creates vulnerability: if accompaniment is expected, but the organization is unwilling to truly slow down and resource it, the disappointment is worse than if the ending had been quick and honest.

New leverage: Distributed communities can hold dying differently. A product used globally can have simultaneous goodbye rituals across time zones. An open-source project can invite the broader community into the sunsetting conversation, not just the core team. An activist network can document and transmit dying elder wisdom at scale, in multiple languages and formats. AI itself can assist: transcribing stories, detecting when someone might benefit from particular care, matching mentors to learners. But only if the humans remain in charge of the meaning—the algorithm is a tool, not the source.

Tech translation specificity: When a tech product is dying, the pattern asks: Can we gather the users and builders in real time? Can we record what was learned? Can we explicitly ask: “What should we preserve? What should we release?” This turns product death from a business event into a commons event. The data itself becomes more trustworthy because it was generated with intention, not extracted from a corpse.

---

Section 8: Vitality

Signs of life:

1. People voluntarily show up. When a colleague is dying or leaving, people make time. They don’t have to be asked twice. This signals that the practice feels meaningful, not obligatory—the commons recognizes genuine care is happening.

2. Stories get told and remembered. Months or years later, the dying person’s wisdom circulates. Someone says, “My mentor taught me…” or “The product taught us…” The knowledge became heritable because it was consciously transmitted, not lost.

3. New people feel safe admitting vulnerability. After experiencing the commons hold someone through decline with dignity, newer members ask for support earlier—during their struggles, not only at their endings. The system becomes more permeable because trust is proven.

4. Rituals evolve without losing their spine. The specific form changes (video instead of in-person, async instead of gathered), but the core act—witness without agenda—persists. The pattern is living, not fossilized.

Signs of decay:

1. Rituals become performance. The dying person or exiting leader describes the ceremonies as “nice but hollow.” Presence is checked off but not felt. The camera is on, but nobody is really here.

2. The same people always do the work. One person or small group becomes the designated “death doula” while others disappear. Accompaniment becomes specialist labor instead of communal practice. Burnout follows quickly.

3. Knowledge doesn’t transfer. Documentation happens but nobody reads it. Stories are recorded but filed away. The apprentices don’t actually learn; the elders feel unheard. The ritual satisfied the observer, not the dying person.

4. The organization speeds up right after. The person or product is honored in a ceremony, then instantly forgotten as the system pivots to the next priority. The ending becomes a pause, not a threshold. The commons didn’t actually shift.

When to replant:

If you notice decay, pause the current ritual entirely rather than perfecting it. Ask: “What would it look like if this person/process actually felt honored by us, not by the ritual?” Often, you need to start smaller—one genuine conversation instead of a gathered ceremony; one person truly present instead of a room full of half-present people. The pattern regenerates when you return to the root: showing up without agenda, asking “What do you need right now?”, and being willing to be changed by what you witness. Replant when the commons is ready to admit that endings are not failures but the ground where renewal grows.