Ecocycle Planning

1. What Is Ecocycle Planning?

Ecocycle Planning is a facilitation framework for examining a portfolio of activities as a living system rather than a static plan. It helps a team decide what should be nurtured, what should be scaled, what should be reinvented, and what should be stopped.

The framework is commonly used in strategy, innovation, transformation, and team-development settings. Consultants often use it with leadership teams because it makes one difficult issue visible very quickly: organizations rarely fail only because they lack ideas; they also fail because they hold on too long to activities that no longer create enough value.

In practical terms, Ecocycle Planning is a structured conversation tool. It gives a group a shared map for discussing products, projects, processes, customer segments, capabilities, or even relationships, and it is especially useful when priorities feel crowded and resources feel trapped.

2. Origin and Background

As a named facilitation method, Ecocycle Planning is most closely associated with Henri Lipmanowicz and Keith McCandless, the creators of Liberating Structures. It has been in use since at least the early 2010s and became widely known through Liberating Structures workshops, practice communities, and their 2014 book The Surprising Power of Liberating Structures.

The method draws on an older intellectual idea: the adaptive cycle in ecology and resilience theory, especially work associated with ecologist C.S. Holling. That ecological model describes how natural systems move through phases of growth, conservation, release, and reorganization. Ecocycle Planning translates that logic into a management and workshop format that leaders can apply to organizational activities.

That distinction matters. The ecological concept and the management workshop tool do not have identical origins, and descriptions of the framework sometimes blur the two. In business practice, however, most executives encounter Ecocycle Planning through the Liberating Structures approach, where it is used to improve planning, reflection, and collective decision making.

3. How Ecocycle Planning Works

The core logic is simple: every activity in an organization is at a different stage of development, and each stage requires a different managerial response. Some activities need protection and experimentation. Some need scale and discipline. Some need to be creatively destroyed so resources can be released. Others need to be reconfigured before they can create value again.

In a workshop, participants list the relevant activities and place each one on an ecocycle map. The discussion is not only about where an item sits today, but also whether it is flowing properly. The best insight often comes from items that are stuck rather than moving.

The four zones

The two traps

Ecocycle Planning is especially useful because it highlights two common traps. The poverty trap occurs when promising ideas remain underfunded or unsupported and never make the transition from experiment to scaled activity. The rigidity trap occurs when mature activities are protected long after their value has flattened or declined, preventing the organization from releasing resources.

The framework is not meant to force a perfect balance at all times. Its real purpose is to make resource flow visible. A healthy portfolio has movement: some items being born, some producing reliably, some being ended, and some being reinvented.

4. When to Use Ecocycle Planning

Ecocycle Planning is most helpful when the problem is not a lack of options but a lack of clarity about what to do with an overloaded set of activities. It is well suited to annual planning, transformation reviews, innovation portfolio discussions, product rationalization, team retrospectives, and post-merger integration work.

It is especially powerful when leaders suspect the system is clogged: legacy work dominates attention, experiments are starved, or teams are endlessly improving activities that should be retired. That is why it often appears in broader organization work, where the real issue is not just strategy formulation but the flow of priorities, roles, and resources.

The framework works best when the team can identify a clear set of items to map and bring at least some evidence on performance, effort, resource use, customer value, or strategic importance. It does not require perfect data, but it does require disciplined definitions. If one participant is mapping products, another is mapping capabilities, and a third is mapping initiatives, the conversation quickly becomes muddy.

It is not a good fit for every situation. If the decision is primarily a financial investment choice, a capacity model, or a market attractiveness analysis, other tools should lead. Ecocycle Planning can also mislead when politics make “creative destruction” taboo, when the organization treats the map as objective truth rather than a discussion aid, or when external forces matter more than internal portfolio flow.

Today, experienced practitioners usually use Ecocycle Planning as a workshop-based sense-making tool, not as a standalone strategic answer. In modern settings it is often combined with financial analysis, customer insight, prioritization, and governance design so the map leads to action rather than becoming an interesting poster.

5. How to Apply Ecocycle Planning: Step-by-Step

1. Clarify the decision and scope. Define what the team is trying to decide. Are you reviewing products, initiatives, customer segments, processes, or capabilities? Set the time horizon and state what is inside and outside scope.

2. Gather the required inputs. Build a simple fact base before the session: current activity list, spend or effort levels, performance trends, customer feedback, operational pain points, and strategic objectives. Interviews with key leaders are often enough to expose where the portfolio already feels stuck.

3. Define the units of analysis. Be precise about what each sticky note or item represents. The framework works only when like is compared with like. If necessary, run separate maps for different categories such as products, internal initiatives, and capabilities.

4. Construct the ecocycle map. Draw the four zones and explain them in plain language. Have participants place each item where it currently sits, not where they wish it sat. Encourage debate, because disagreement often reveals different assumptions about value, maturity, or ownership.

5. Analyze the pattern, not just the items. Look for clusters, empty zones, and bottlenecks. Are there too many mature activities? Too little renewal? A pile of experiments with no path to scale? Pay special attention to items trapped in poverty or rigidity.

6. Translate the map into actions. For each item, decide whether to invest, scale, redesign, harvest, or stop. The discussion should end with named moves, owners, and timelines. In many companies, this is the point where a workshop becomes a coordinated change program rather than a one-off reflection exercise.

7. Test sensitivities and assumptions. Revisit contentious placements and ask what assumptions would move an item to a different zone. This is particularly important for mature businesses with declining economics and for renewal efforts that may really need closure instead.

8. Align governance and follow-through. Review what decisions require executive approval, budget release, role changes, or communication to the broader organization. When the number of moves is large, a lightweight transformation office can help track closures, reinvestment, and the transition of work between zones.

6. Example: Ecocycle Planning in Action

Situation

A $450 million B2B software company had accumulated too many priorities. It supported three legacy product lines, five newer modules, a services business, and more than 20 internal initiatives. Revenue was still growing, but release quality was slipping, product teams were overextended, and executives could not agree on what to stop.

Why the company chose Ecocycle Planning

The CEO did not need another strategy presentation; she needed a shared view of where the business was stuck. Ecocycle Planning was chosen because it could bring the executive team, product leaders, and customer success heads into one room and force explicit discussion of scale, reinvention, and exit.

How the framework was applied

The team mapped products, major initiatives, and a small number of enabling capabilities on separate ecocycle charts. They used revenue trends, gross margin, customer retention, implementation effort, and qualitative customer feedback as inputs. In discussion, several activities initially described as “core” turned out to be mature but declining offerings that consumed disproportionate engineering time.

Insights and actions

The maps showed a classic rigidity trap: legacy modules were being defended because a few large clients still used them, even though they constrained investment in the fastest-growing workflow products. They also showed a poverty trap: two promising AI-enabled features had strong customer interest but no dedicated funding path to scale.

The leadership team decided to sunset one legacy module, limit custom enhancements on another, and redirect engineers into the newer workflow products. The exercise also revealed that accountabilities were organized around old product silos rather than target customer journeys, which led to a focused organizational redesign in product management and customer success.

7. Strengths and Limitations

Strengths

• Makes trade-offs visible. It forces teams to discuss stopping work, not just starting more.
• Handles complexity simply. A large, messy portfolio becomes easier to discuss without pretending to have perfect precision.
• Creates shared language. Birth, maturity, destruction, and renewal are intuitive and memorable categories.
• Surfaces blocked resource flow. The poverty and rigidity traps are often immediately recognizable to executives.
• Works well in group settings. It is highly effective in workshops, offsites, and cross-functional reviews where alignment matters as much as analysis.

Limitations

• It is inherently subjective. Placement depends on judgment, and different leaders may interpret the same item differently.
• It can oversimplify. Some activities span multiple zones or behave differently across regions, products, or customer segments.
• It is not a financial model. The framework does not replace market analysis, valuation, scenario modeling, or business-case work.
• It may underweight external context. Competitive moves, regulation, and technology shifts can matter more than internal lifecycle stage.
• It can stall at insight. Without decisions, governance, and follow-through, the workshop creates awareness but not change.

8. Common Pitfalls and How to Avoid Them

• Mixing different item types. Teams put products, people issues, and projects on one map, making comparisons meaningless. Avoid this by defining one unit of analysis per map.
• Avoiding creative destruction. Participants politely agree that everything is still important. This matters because no resources are actually freed. Counter it by asking what would happen if nothing were stopped.
• Using vague evidence. Items are placed based on seniority or narrative rather than data. Even a light fact base improves the quality of judgment.
• Confusing maturity with success. Mature activities may still be valuable, but maturity does not mean they deserve indefinite protection. Separate current cash generation from future strategic role.
• Assuming renewal is always better than exit. Some activities should be redesigned; others should simply be shut down. Make that distinction explicit.
• Stopping at the map. The exercise becomes a workshop artifact with no owners or deadlines. Close with concrete actions, named accountabilities, and a review cadence.

9. How Ecocycle Planning Relates to Other Frameworks

Ecocycle Planning and Three Horizons

These frameworks are related but not identical. Three Horizons helps leaders balance investment across the core business, emerging adjacencies, and longer-term bets. Ecocycle Planning focuses less on time horizon and more on lifecycle stage and blocked flow. A team might use Three Horizons to shape investment ambition, then use Ecocycle Planning to decide what in the current portfolio should be scaled, renewed, or stopped.

Ecocycle Planning and the Product Life Cycle

The product life cycle is primarily a market-facing concept about introduction, growth, maturity, and decline. Ecocycle Planning is broader and more managerial. It can be applied to internal initiatives, capabilities, customer relationships, or organizational practices, and it places much more emphasis on deliberate ending and reinvention.

Ecocycle Planning and prioritization frameworks

Ecocycle Planning is excellent for diagnosing flow and surfacing bottlenecks, but it is less precise for sequencing decisions. After the map is built, many teams use a prioritization matrix, business-case analysis, or an OKR-style planning process to decide which moves happen first, who owns them, and how resources will shift.

Ecocycle Planning and diagnostic strategy tools

Frameworks such as SWOT or Porter’s Five Forces diagnose the environment and competitive position. Ecocycle Planning does something different: it helps leaders act on that diagnosis by reshaping the portfolio of work inside the organization. Used together, the tools answer both “What is happening around us?” and “What should we now start, scale, renew, or stop?”

10. Key Takeaways

• Ecocycle Planning is a facilitated way to map activities across birth, maturity, creative destruction, and renewal.
• Its main value is making blocked resource flow visible, especially poverty traps and rigidity traps.
• It is most useful when an organization has too many priorities and not enough clarity on what to stop.
• The framework works best with a clear unit of analysis, a light fact base, and candid discussion.
• It should be treated as a thinking and alignment tool, not as a standalone answer.
• The biggest failure mode is insight without follow-through.

11. FAQs About Ecocycle Planning

Is Ecocycle Planning still relevant today?

Yes. It remains highly relevant because most organizations still struggle more with overload and inertia than with a shortage of initiatives. What has changed is how it is used: experienced practitioners now combine it with portfolio, financial, and governance tools so the workshop leads to action.

What is the difference between Ecocycle Planning and Three Horizons?

Three Horizons is mainly about balancing investments across different future time frames. Ecocycle Planning is about the current lifecycle stage of activities and the need to start, scale, renew, or stop them. Three Horizons is more investment-oriented; Ecocycle Planning is more flow- and portfolio-oriented.

Can small or early-stage companies use Ecocycle Planning?

Absolutely. Smaller companies often benefit because they have limited capacity and cannot afford to keep too many side projects alive. The process can be very lightweight: one leadership session, a short activity list, and clear choices about what to double down on and what to drop.

How long does it typically take to apply Ecocycle Planning in a real project?

A simple team session can be done in 60 to 90 minutes. A more robust application, with interviews, fact gathering, multiple maps, and executive decision making, usually takes a few days to a few weeks depending on scope and stakes.

What data is needed to use Ecocycle Planning?

The minimum useful input is a defined list of activities and informed judgment from people close to the work. The analysis improves materially when you add performance trends, resource consumption, customer or stakeholder feedback, and a clear view of strategic priorities.