systems-thinking

Awe Practice

Also known as:

Deliberately seek and cultivate experiences of awe—through nature, art, cosmos, or human excellence—as a regular practice for perspective and wellbeing.

Deliberately seek and cultivate experiences of awe—through nature, art, cosmos, or human excellence—as a regular practice for perspective and wellbeing.

[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Dacher Keltner / Positive Psychology.

Section 1: Context

Systems at scale—whether corporate hierarchies, government bureaucracies, activist collectives, or tech teams—tend toward fragmentation of attention and contraction of perspective. The work becomes granular: KPIs, policy cycles, campaign metrics, sprint goals. The horizon collapses. People live in their tasks, their silos, their echo chambers. Meanwhile, the commons they are stewarding—the living systems they depend on—continue their own cycles: seasons turn, species migrate, beauty persists, human excellence emerges in unexpected places.

This pattern arises in organisations that recognise a creeping cost: cognitive rigidity, burnout, loss of adaptive capacity, and erosion of the moral intuition that makes collaborative stewardship possible. When awe is systematically absent from a system’s rhythm, people stop perceiving the larger patterns they are part of. They lose the felt sense of scale that makes sacrifice, generosity, and long-term thinking rational.

The conditions are ripe for this pattern in systems where stakeholders experience:

  • Chronic task saturation and deadline pressure
  • Spatial isolation from nature, beauty, or works of excellence
  • Governance structures that treat perspective-renewal as optional rather than structural
  • Team cultures that valorise busyness over presence

In these contexts, awe practice becomes a deliberate counter-current—a way to restore the perceptual flexibility and moral clarity that resilient commons need.

Section 2: Problem

The core conflict is Awe vs. Practice.

The tension runs like this:

Awe’s demand: Stop. Look up. Feel the vastness. Recognise what is larger than your concern. This requires genuine discontinuity—a break from productivity logic, a surrender of control, a willingness to be small.

Practice’s demand: Show up. Do the work. Build the system. Tend the commons through consistent action, habit, and incremental improvement. This requires discipline, focus, measurement, and the relentless prioritisation of what moves the needle.

These two logics seem to oppose each other. Many practitioners experience them as zero-sum: time spent in awe is time away from the work. A team that pauses to watch a sunset together is a team not shipping. A government body that funds arts access is a body making a luxury choice when urgent needs remain unmet.

The unresolved tension shows up as:

  • Instrumentalised awe: People take “wellness retreats” but return to unchanged systems, awe treated as a reset button rather than a structural input.
  • Awe avoidance: High-performing teams aggressively optimise for productivity and treat expanded perspective as distraction or self-indulgence.
  • Guilt cycles: Individual practitioners squeeze in personal awe-seeking (hikes, museums) but carry shame that they are not fully present to “the work,” creating additional stress rather than relief.

The break comes when practitioners realise awe is not a luxury amenity but a cognitive technology: it restores the perceptual bandwidth and emotional resilience required for sustained, intelligent collaboration. It is part of the work itself.

Section 3: Solution

Therefore, establish awe cultivation as a non-negotiable rhythm within the system—structured time and explicit permission for stakeholders to seek and share experiences of vastness, beauty, or excellence—integrated into governance cycles and team practice rather than marginalised as individual wellness.

This pattern works by reframing awe from escape to infrastructure.

When awe is deliberately scheduled and collectively witnessed, it functions as a restorative rhythm that prevents cognitive calcification. Keltner’s research shows that awe experiences expand time perception, reduce ego-driven anxiety, and increase prosocial behaviour and generosity—all capacities the commons requires. But these effects depend on regularity and on genuine exposure to something experienced as vast, complex, or humbling.

The mechanism is simple: awe interrupts the narrative loop of task-identity. When you stand before a starfield, or witness a performance of human excellence, or move through a landscape larger than your immediate concerns, the brain’s default mode network shifts. The constant production of self-reference—worry about status, performance, rightness—quiets. In that gap, perspective re-enters.

For a commons to integrate this, it must be planted into the system’s tissue: not as an optional add-on but as a structural beat. A governance board schedules quarterly visits to a natural site or artwork. An activist cell begins meetings with five minutes of collective silence before a video of human courage. A tech team blocks time for what one engineer called “awe sprints”—dedicated exploration of scale problems their software touches.

The vitality that emerges is not new adaptive capacity but the renewal of existing capacity that atrophies under pressure. Like root systems that thicken in winter dormancy, awe practice deepens the capacity to think clearly and act generously when the system returns to its ordinary work. It is metabolic—a system that does not rest cannot sustain high function indefinitely.

Section 4: Implementation

For corporate/wonder-based culture: Create a “Awe Hours” budget in team calendars—two hours per quarter that each person and team must spend deliberately seeking awe, then share a single sentence or image in a dedicated Slack channel. Make it visible on the same dashboard as OKRs. One financial services firm embedded this as a “perspective session” before annual strategy sessions: teams spend 90 minutes at a natural history museum or botanical garden before entering strategic planning. The outcome shift was measurable—conversations shifted from quarterly competition to longer-term stewardship questions.

For government/arts & nature access policy: Establish public awe infrastructure as a budget line. Fund free or low-cost access to natural sites, artworks, and performances with transport included for underserved areas. Staff working on policy should be required to spend time in these spaces monthly. One city planning department required all zoning staff to visit a different neighbourhood park quarterly and report what they felt and noticed. This simple practice changed how they approached green-space allocation—no longer as amenity but as commons essential to cognitive health.

For activist/awe-inspired activism: Begin every organising meeting with a five-minute shared experience of beauty or courage: a short video of non-violent resistance, a photograph of a thriving ecosystem, a moment of silence in nature. Document and share stories of why certain activists chose their work—many arose from moments of awe. One climate justice group built “witnessing walks” into their practice: activists spend time at sites facing destruction before launching campaigns there. The awe and grief together fuel sustained action.

For tech/awe opportunity AI finder: Build tools that surface awe: dashboards that show the scale and complexity of problems your code touches (population served, environmental impact, lives affected). Create API integrations that surface cosmic data, biodiversity information, or human excellence records in team communication channels. One ML team set their Slack background to daily updates from the James Webb Space Telescope. More pointedly: develop AI tools that help workers find awe experiences near them—nature walks, art events, performances—and build them into scheduling.

General steps all contexts:

  1. Audit awe absence: Measure current time stakeholders spend in genuine awe-seeking (not productivity-framed “wellness”). Be honest.
  2. Designate stewards: Assign 1–2 people (rotated annually) to curate and schedule awe experiences for the system. Make it a real role.
  3. Create permission structures: Explicit language in governance documents that time spent in awe-seeking is work, not theft from work. Remove the guilt.
  4. Make it collective: Do not allow awe to be purely individual. Create shared experiences—team visits, group moments of silence, collective witnessing. This plants awe into the commons’ shared memory.
  5. Anchor in meaning: Connect awe experiences back to the system’s purpose. After a nature visit, name explicitly: “This ecosystem we just walked through is what we are stewarding with our code/policy/campaign.”

Section 5: Consequences

What flourishes:

Stakeholders develop what Keltner calls “moral clarity”—the intuitive sense of what matters and why. Decision-making becomes less reactive, more grounded in values beyond quarterly performance. Teams report reduced burnout and higher retention because the work is recontextualised as part of something larger. Creativity increases: the expanded time perception awe creates allows for novel pattern-matching. Trust deepens in teams that witness awe together—there is something about shared wonder that dissolves posturing.

Resilience to setbacks improves. Systems that practice awe tend to reframe failure not as identity threat but as part of larger cycles. One board member in a struggling non-profit described returning from an awe practice at a canyon: “Our fundraising failure seemed enormous. Then I remembered the canyon has been working for 300 million years. We have time.”

What risks emerge:

The pattern carries real failure modes. Awe can become routinised hollow practice—teams check the box, visit a museum, feel nothing, return unchanged. This happens when awe is forced or when the chosen experience does not genuinely trigger the expansive response. Watch for teams that describe awe sessions as “nice breaks” but show no shift in thinking or collaboration.

Awe can become escapism: When the system is fundamentally broken, awe can become a palliative that delays necessary change. A toxic workplace that offers quarterly nature trips to workers is using awe as sedation, not medicine.

Awe can increase guilt: If only some stakeholders have access to nature or art, awe practices can deepen inequality rather than heal it. A team that takes a retreat to a beautiful location while remote workers are excluded has weaponised awe.

Governance and resilience risks: This pattern scores 3.0 on stakeholder architecture and resilience. Awe is not a substitute for structural fairness or clear decision-making processes. If a system uses awe language (“we are all part of something larger”) to justify hierarchy or inequitable burden-sharing, it becomes corrosive. The pattern requires alignment with genuine co-ownership.

Section 6: Known Uses

Story 1: The Climate Leadership Council (Policy/Government) A state environmental agency with chronic conflict between conservation and development interests began a practice called “Sacred Site Visits.” Quarterly, the full council—developers, conservationists, staff, tribal representatives—travelled together to a landscape of significance. They spent time in silence, then shared without agenda. Over two years, decisions shifted. A developer who had fought wildfire protection spoke about standing in a forest after hearing a wildlife biologist’s awe story. He stopped opposing a conservation easement. The practice did not create agreement on every issue, but it restored stakeholders’ ability to see each other as part of the same living system rather than opponents. The Commons assessment would call this improved ownership—people began co-stewarding rather than competing.

Story 2: The Mozilla Fellowship (Tech) Early in the AI ethics fellowship, participants reported burnout and moral numbness despite working on important problems. The programme director integrated “cosmos hours”: structured time to engage with scale—watching documentaries on deep time, reading astronomy, visiting planetariums. Fellows report this practice renewed their commitment. One fellow who was about to quit the programme said: “I spent three hours understanding that our solar system is part of a galaxy with 200 billion stars, and our code is part of something affecting billions of people. Suddenly the work felt rational again, not futile.”

Story 3: The Mutual Aid Network (Activist) An activist collective working on housing justice built “witnessing” into organising. Before launching campaigns, members visited neighbourhoods facing displacement. Standing in someone’s home, listening to their story, seeing the street—this created awe at the stakes and at human resilience. One organiser described the shift: “We went from talking about eviction statistics to feeling the weight of lives. Our work became less angry and more grounded. We could think longer-term because we had actually met the people we were fighting for.” This practice increased both retention and strategic clarity.

Section 7: Cognitive Era

AI and distributed intelligence reshape awe practice in two directions.

New leverage: AI tools can surface awe at scale. Dashboards that show real-time impact (how many people are using the code you built, what ecosystem depends on the policy you crafted) become awe generators. Recommendation systems trained to surface beauty, cosmic data, or human excellence records can democratise access to awe-triggers for workers without privilege to travel or leisure. AI can identify which awe experiences resonate with which team members, personalising the practice while keeping it collective.

New risks: AI also accelerates the conditions that make awe practice necessary—task saturation, attention fragmentation, algorithmic capture of perspective. If awe-seeking itself becomes quantified, gamified, or optimised for engagement, it hollows. A team using an “awe app” that serves algorithmic recommendations of beautiful images may feel awe-adjacent but not the genuine vastness that requires surrender and risk.

More subtly: as AI systems become more capable and autonomous, human workers face a particular kind of vertigo—wondering whether their skills matter, whether they are obsolete. This can trigger false awe: dread masked as wonder. The pattern’s viability depends on practitioners distinguishing genuine awe (expansive, clarifying, pro-social) from awe-turned-to-anxiety (contractive, identity-threatening, paralyzing). Systems need explicit reflection on this.

The tech context translation (Awe Opportunity AI Finder) points to a key leverage point: build AI tools that help workers perceive the actual scale and complexity of the systems they are stewarding. An engineer working on a recommendation algorithm might be served daily data on how that algorithm shapes behaviour, culture, and attention—not as guilt-inducing metrics but as awe-generating perspective. “You shaped 500 million feeds today. You are part of the attention infrastructure of human consciousness. Act accordingly.”

Section 8: Vitality

Signs of life:

  • Stakeholders describe genuine shifts in how they perceive the system’s purpose and their role in it. Language moves from task-completion to stewardship. (“We are not shipping a feature; we are stewarding infrastructure that shapes how 10 million people spend their time.”)
  • Decision-making shows longer time horizons. Conversations reference the future, the ecosystem, the next generation without prompting.
  • Psychological safety increases. Teams report feeling more willing to voice doubt, ask “dumb” questions, and challenge groupthink after awe practices. The ego contraction awe brings seems to make hierarchy lighter.
  • Retention improves, particularly for high-performing people who have other options. They report the work feels meaningful again.

Signs of decay:

  • Awe sessions become rote. Teams attend but report no genuine feeling. Language is passive: “It was nice.” No shift in behaviour or conversation follows.
  • The practice becomes isolated from the rest of the system’s work. Awe happens in a designated box—a quarterly retreat—and the system returns to its baseline logic immediately after.
  • Equity problems emerge. Some stakeholders have consistent access to awe experiences (downtown workers can visit museums; remote workers cannot). The practice begins to sort rather than unite.
  • Guilt increases rather than clarity. Stakeholders feel they “should” be awestruck or that time spent in awe is selfish. The practice becomes another source of moral taxation rather than renewal.
  • Executives use awe language (“we are all part of something larger”) to avoid accountability or justify inequality. Awe becomes a tool of manipulation.

When to replant:

If the pattern has decayed into routine emptiness, redesign the awe triggers rather than abandon the practice. Rotate sites, invite new artists or speakers, change the timing. If equity problems have emerged, address them structurally: fund transport, include remote workers, audit whose awe experiences get centred. If the practice has become isolated, reintegrate it: reference awe moments in strategic decisions, weave them into onboarding, anchor them to the system’s stated purpose.

The right moment to restart or intensify awe practice is when you notice stakeholders defaulting to short-term thinking, when cynicism is rising, when the work feels like grinding rather than stewarding. That is the signal that the commons’ perceptual system has contracted. Awe practice, planted with intention and protected from instrumentalisation, is how the system learns to see again.