The Polycrisis Playground: Finding Strategic Joy in Interlocking Doom Loops

We have all felt it: the news cycle delivers another collapse—a flood here, a tariff war there, a democratic norm eroding somewhere else. The temptation is to treat each crisis as a separate emergency, to triage and firefight until exhaustion sets in. But what if the crises are not separate? What if they are coupled, feeding back into one another, accelerating? That is the polycrisis hypothesis, and for governance professionals working in the Anthropocene, it is not a theoretical exercise—it is the operating environment. This guide is for those who already understand the basics of systems thinking and want a practical, joy-infused framework for acting effectively when everything seems to be breaking at once. We will argue that the polycrisis is not just a doom loop; it can be a playground for strategic intervention, if we know where to push.

Why This Topic Matters Now

The term 'polycrisis' has moved from academic circles into boardrooms and government briefings, but its implications are still poorly understood. A polycrisis is not merely a pile of simultaneous crises; it is a set of interlocking crises where each one worsens the others. For example, a drought reduces crop yields, which drives up food prices, which fuels social unrest, which distracts governments from climate adaptation, which leads to worse droughts next season. This coupling creates feedback loops that can overwhelm linear, siloed responses. The stakes for governance are immense: a single-agency approach to food security will fail if it ignores energy prices, supply chain logistics, and political stability. Practitioners who continue to operate in silos will find their efforts neutralized by forces outside their mandate. Yet the very complexity of the polycrisis also creates opportunities. Because the system is tightly coupled, a well-placed intervention in one node can ripple outward, producing benefits across multiple domains. The challenge is to find those nodes—the leverage points—and to act with precision rather than panic. This article provides a method for doing exactly that, grounded in complexity science and field-tested by teams working at the intersection of climate, economy, and society. We will show you how to map your own polycrisis landscape, identify strategic entry points, and sustain the energy needed for long-term engagement.

The Cost of Ignoring Interconnections

When we treat crises as independent, we waste resources on solutions that are undermined by unaddressed feedbacks. A classic example is building seawalls to protect against storm surges while simultaneously subsidizing fossil fuels that accelerate sea-level rise. The seawall investment is not wrong, but it is incomplete—and it can create a false sense of security. In governance, this pattern repeats across departments: agricultural policy ignores water scarcity, trade policy ignores labor rights, health policy ignores air pollution. The result is a series of expensive, fragile interventions that collapse under the weight of their own contradictions. Recognizing the polycrisis nature of our challenges is the first step toward designing interventions that are robust to surprise.

Why Joy Matters in a Crisis

Strategic joy is not about ignoring suffering or putting a positive spin on disaster. It is a deliberate emotional and cognitive stance that allows us to see possibility within constraint. When we are overwhelmed, our field of vision narrows; we focus on threats and lose sight of opportunities. Joy, in this context, is the capacity to remain curious, creative, and connected to purpose even when the system seems designed to defeat us. It is a professional skill, not a personality trait. Teams that cultivate strategic joy are more likely to experiment, learn from failure, and sustain their efforts over the long haul. They are also more fun to work with, which matters when collaboration is the only way through.

Core Idea in Plain Language

The core idea is simple: in a tightly coupled system, small pushes in the right places can produce large, positive cascades. Think of a playground seesaw: a child's slight shift in weight can lift a much heavier playmate. The polycrisis is full of such seesaws, but we have to learn to see them. The conventional approach to crisis management is to apply maximum force to the most visible symptom—send more food aid, build higher walls, pass stricter laws. But in a polycrisis, the most visible symptom is often not the best leverage point. The real leverage lies in the connections between crises: the feedback loops, the delays, the information flows. By intervening in those connections, we can change the behavior of the whole system without needing to control every part of it.

Leverage Points: Where to Push

Donella Meadows, a pioneer of systems thinking, identified a hierarchy of leverage points, from changing parameters (least effective) to changing the mindset or paradigm that shapes the system (most effective). In a polycrisis, we often default to the lowest leverage points—spending more money, hiring more staff, passing more regulations—because they are within our control. But the highest leverage points involve changing the rules of the game, the information flows, or the goals of the system itself. For example, instead of subsidizing disaster recovery after every flood, a community might change land-use rules to prevent building in floodplains. That is a rule change, and it has ripple effects across housing, insurance, and emergency services. Our method helps you identify which kind of leverage point is accessible in your context and how to push it without triggering backlash.

The Joy of Finding the Seesaw

There is a genuine intellectual pleasure in tracing a feedback loop and realizing that a small intervention could shift the entire dynamic. That pleasure is strategic joy. It is the opposite of the grim determination that often characterizes crisis work. When we find the seesaw, we feel a sense of agency and even playfulness. This is not frivolous; it is a survival mechanism. The polycrisis will not be solved by grimness alone. It will be solved by people who can see the system clearly, find the hidden levers, and pull them with precision and delight. That is the mindset we are building here.

How It Works Under the Hood

Our method has three phases: mapping, prioritizing, and acting. Each phase is iterative and collaborative, designed to be used by a team or a network of stakeholders. We will describe each phase in detail, along with common pitfalls and how to avoid them.

Phase 1: Map the System

Start by identifying the key crises that affect your domain. Do not try to map everything; focus on the ones that interact. For each crisis, list its drivers, its impacts, and its feedback loops with other crises. Use a whiteboard or collaborative software to draw causal loop diagrams. Look for reinforcing loops (where A makes B worse, which makes A worse) and balancing loops (where the system self-corrects). The goal is not a perfect map but a shared understanding of the most important connections. A typical map might include 10 to 15 nodes and 20 to 30 links. Resist the urge to add more; simplicity is a feature, not a bug. A common mistake is to include every possible factor, which leads to analysis paralysis. Instead, ask: which connections, if changed, would most alter the system's behavior?

Phase 2: Prioritize Leverage Points

Once you have a map, look for nodes that appear in multiple feedback loops—these are potential leverage points. Also look for delays: places where an intervention now could have a big effect later, or where a current trend is about to tip. Prioritize interventions that are feasible, have low downside risk, and could produce cascading benefits. For example, investing in decentralized renewable energy might simultaneously reduce emissions, create local jobs, and increase energy security—a triple win. But beware of interventions that look good on paper but require perfect implementation; in a messy world, robustness matters more than optimization. Use a simple matrix: impact (high/medium/low) vs. feasibility (high/medium/low). Focus on the high-impact, high-feasibility quadrant, but also keep an eye on high-impact, low-feasibility items that might become feasible with coalition-building.

Phase 3: Act and Adapt

Choose one or two priority interventions and design a small, reversible experiment. The polycrisis is too complex for large, irreversible bets. Instead, test your hypothesis with a pilot project that can be scaled if it works and abandoned if it does not. Measure not just the direct outcome but also the ripple effects—did the intervention create unexpected benefits or harms? Use those observations to update your map and adjust your strategy. This phase requires humility: you will be wrong about some things, and that is okay as long as you learn quickly. The key is to maintain strategic joy by celebrating small wins and treating failures as data, not as personal defeats.

Worked Example: A Regional Food System Under Stress

Let us apply the method to a composite scenario: a mid-sized agricultural region facing drought, rising fertilizer costs, and labor shortages. The local government wants to ensure food security, but each crisis is managed by a different department—water, agriculture, and labor—with little coordination. Using our method, a cross-departmental team maps the system. They find a reinforcing loop: drought reduces crop yields, which reduces farm income, which reduces investment in irrigation, which makes the next drought worse. They also find a balancing loop: high food prices attract new farmers, which increases supply and lowers prices, but this loop is weak because new farmers lack access to land and capital. The team identifies a leverage point: creating a community-managed water cooperative that pools resources for efficient irrigation. This intervention addresses water scarcity directly, but it also stabilizes farm incomes (by reducing water costs) and creates a platform for collective investment in drought-resistant crops. It is feasible because it builds on existing farmer networks and requires only modest startup funding. The team launches a pilot in one watershed, with clear metrics for water use, crop yields, and farmer satisfaction. After one season, they find that water use dropped 20% while yields remained stable, and farmers reported higher confidence in their ability to weather future droughts. The cooperative model is now being scaled to adjacent watersheds, and the team is exploring how to use it as a platform for other interventions, such as bulk purchasing of inputs and shared labor pools. This example shows how a single, well-chosen intervention can ripple across multiple crises, creating strategic joy in the process.

What Made This Work

The success hinged on three factors: the team took time to map the system before acting; they chose a leverage point that was both high-impact and feasible; and they designed a small experiment that allowed for learning. They also maintained strategic joy by celebrating the pilot's success and using it to build momentum. Without the map, they might have invested in a desalination plant (expensive, slow, and disconnected from the social dynamics) or a labor recruitment campaign (which would have failed without addressing water and income). The map revealed the hidden seesaw.

Edge Cases and Exceptions

No method works in all situations. Here are some edge cases where our approach may need adjustment.

When the System Is Too Tightly Coupled

In some polycrises, the feedback loops are so fast and so strong that any intervention is immediately overwhelmed. For example, a financial panic can cascade through global markets in hours, leaving no time for mapping and deliberation. In such cases, the priority is to stabilize the system first—through emergency measures like liquidity injections or moratoriums—and then apply the method once the system has settled. Our approach is for chronic, compounding crises, not acute emergencies.

When Stakeholders Are Hostile

Mapping and collaboration require trust. If key stakeholders are actively opposed to change—for example, a powerful industry that benefits from the status quo—your map may be incomplete or your interventions blocked. In such cases, you may need to work covertly or build a coalition of smaller actors before engaging the powerful. Strategic joy can help here: finding pleasure in outmaneuvering opposition rather than confronting it head-on.

When Data Is Scarce

Our method relies on qualitative mapping, which is robust to data gaps. But if you have no information at all about a critical connection, your map may be misleading. In such cases, invest in rapid data collection—surveys, interviews, or sensor networks—before committing to an intervention. Alternatively, design your experiment to test the connection itself. For example, if you are unsure whether a new irrigation technology will reduce water use, pilot it in a small area and measure.

Limits of the Approach

We must be honest about what this method cannot do. It is not a guarantee of success; the polycrisis is inherently unpredictable, and even the best-laid plans can fail. It is also not a substitute for political action or resource mobilization; a leverage point is useless if you lack the power or funds to push it. Furthermore, the method can be gamed: if powerful actors use it to identify leverage points for their own benefit, they could make the polycrisis worse. We assume good-faith actors working for the common good, but that is not always the reality. Another limit is the risk of 'toxic positivity'—using strategic joy as a way to dismiss legitimate grief, anger, or fear. Joy is a tool, not a mask. Teams must create space for difficult emotions while still moving forward. Finally, the method requires time and cognitive effort, which are scarce in crisis conditions. Leaders must decide when to invest in this approach and when to fall back on simpler heuristics. There is no shame in using a fire extinguisher when the house is burning; the method is for when you have a moment to think.

When Not to Use This Method

Do not use this method when immediate action is needed to prevent loss of life—evacuate first, map later. Do not use it when you lack the authority or resources to act on the insights; you will only create frustration. And do not use it as a way to avoid making hard decisions; the method is meant to inform decisions, not replace them. If you find yourself mapping endlessly without acting, you have fallen into analysis paralysis—a common trap. Set a time limit for each phase and stick to it.

Reader FAQ

Isn't 'strategic joy' just a fancy term for denial?

No. Denial ignores problems; strategic joy acknowledges them fully while choosing to focus on what can be changed. It is a discipline, not a delusion. Practitioners report that it actually increases their capacity to face hard truths because they are not drained by hopelessness.

How do I convince my boss or team to try this approach?

Start small. Use the method on a single, low-stakes problem and show results. Share the worked example above as a concrete illustration. Emphasize that this is not a radical departure but a structured way to do what good practitioners already do intuitively—connect dots and act on insights.

What if our organization is too siloed to map across departments?

That is a common barrier. Begin by mapping within your own silo, then invite one or two allies from other departments to co-create a partial map. Even a two-department map can reveal surprising connections. Use those insights to build a case for broader collaboration. Sometimes the map itself becomes a boundary object that helps break down silos.

Can this method be used by an individual, or does it require a team?

It works best with a team, but an individual can do a rough version. The risk is that your map will reflect your own blind spots. If you work alone, seek feedback from diverse stakeholders to challenge your assumptions. The joy part is harder alone, too—find at least one collaborator to share the process.

How do I maintain strategic joy when things go wrong?

Expect setbacks. When an intervention fails, treat it as data: what did we learn about the system? Celebrate the learning itself. Also, build joy practices into your team's routine: start meetings with a good news round, take breaks to reflect on what is working, and acknowledge effort regardless of outcome. Joy is a habit, not a feeling.

Practical Takeaways

We have covered a lot of ground. Here are the specific actions you can take starting today:

• Map one interconnected crisis in your domain this week. Use a whiteboard or a simple digital tool. Identify at least three feedback loops. Share the map with a colleague and ask what you missed.
• Identify one leverage point that is both high-impact and feasible. Design a small experiment to test it. Set a three-month timeline and clear success metrics.
• Schedule a 30-minute 'joy check' with your team each week. Ask: what went well? What did we learn? What are we curious about? Keep the tone light and forward-looking.
• Read one book or article on systems thinking or complexity theory. We recommend Donella Meadows's 'Thinking in Systems' or the 'Stockholm Resilience Centre' primer on planetary boundaries. Apply one concept to your current work.
• Share your findings with a wider network. Write a short post, give a brown-bag talk, or start a community of practice. The polycrisis is too big for any one team; we need collective intelligence to find the seesaws.

The polycrisis is real, and it is daunting. But it is also a playground—a space where strategic joy can guide us to interventions that matter. The alternative is burnout and cynicism. We choose joy, not because it is easy, but because it works.