Adaptive organizations rely on teams that can continuously realign their work with a changing environment while preserving coherence with the wider system. At the team level, this requires more than conventional planning tools: it calls for shared understanding, explicit choices about focus, and a transparent view of how outcomes, enabling work, and operational obligations interact.
The Apple Tree method offers a simple yet powerful way to achieve this. By translating a team’s workload into a visual metaphor, it enables members to see what they are aiming to deliver, what must be in place to make that delivery possible, and how much capacity is already absorbed by business‑as‑usual.
Used on a regular cadence, it becomes a practical entry point for bottom‑up change within the Adaptive Organization framework, strengthening both local autonomy and systemic alignment.
1. AO at Team Level: A Bottom‑Up Practice
At team level, the Adaptive Organization (AO) approach can start with a simple but structured method to make work visible and foster shared ownership. The Apple Tree serves as a practical entry point for bottom‑up change.
2. The Apple Tree Method
Step 1 – Define the time horizon and purpose
- Agree on the time frame the Apple Tree will cover (e.g., the next three months).
- Clarify the purpose of the session: visualizing work, surfacing dependencies, enabling prioritization, and aligning with the AO roadmap.
- Invite all core team members and, where useful, a small number of key stakeholders as observers.
Step 2 – Introduce the metaphor and rules
Explain the three core elements:
- Fruits (apples): outcomes, deliverables, or goals the team intends to achieve within the chosen horizon.
- Roots (arrows): enabling work required to make the fruits possible (non‑functional work, authorizations, infrastructure, improvements, learning).
- Business‑as‑usual (white boxes): recurring or mandatory activities that consume capacity but are not directly tied to specific fruits (support, regulatory work, maintenance).
Clarify visualization rules (e.g., colors, shapes, naming conventions) so everyone uses the same language.
Step 3 – Elicit and place the fruits
- Ask the team to list all significant outcomes they are currently pursuing or planning.
- Classify them as:
- Big fruits: large initiatives (themes/epics) that will likely decompose into multiple smaller items.
- Regular fruits: smaller outcomes or features.
- Optionally, red fruits for attractive work and green fruits for less appealing but necessary work (e.g., compliance).
- Place the fruits in the tree canopy, distinguishing:
- Fruits in progress.
- Fruits planned but not started.
- Fruits “ready to harvest” (nearly done or ready for release).
Step 4 – Identify and connect the roots
- For each significant fruit, ask: “What must be true for us to deliver this?” and “What might prevent us from harvesting this fruit?”
- Capture the answers as roots:
- Non‑functional needs (performance, security, reliability).
- Authorizations and access.
- Technical or organizational improvements.
- Learning and experimentation.
- Draw arrows from roots to the fruits they enable, making dependencies explicit.
Step 5 – Map business‑as‑usual work
- List ongoing, recurring, or mandatory activities that consume capacity (e.g., “Conversion,” “Support,” “GDPR”).
- Represent these as white boxes separate from fruits and roots, but on the same canvas.
- Estimate the approximate capacity they require (e.g., percentage of time, number of people) and note it near each box.
Step 6 – Examine load and parallelization
- Step back and review the entire tree: number of fruits, density of roots, and volume of business‑as‑usual.
- Ask guiding questions:
- How many fruits are in progress at the same time?
- Where are we over‑committed?
- Which fruits are weakly supported by roots?
- How much capacity is effectively “locked” in business‑as‑usual?
- Identify clear signs of overload or fragmentation of focus.
Step 7 – Prioritize and decide limits
- As a team, prioritize fruits based on value, risk, and strategic relevance.
- Decide on explicit work‑in‑progress limits for fruits and, where relevant, for roots.
- Mark the highest‑priority fruits (e.g., with a symbol or color) and agree what to pause, stop, or defer.
- Capture any explicit decisions about business‑as‑usual (e.g., where it can be reduced, automated, or redistributed).
Step 8 – Connect to the AO roadmap and stakeholders
- Map prioritized fruits to higher‑level AO elements (e.g., outcomes or domains from the organizational roadmap).
- Verify that team‑level focus supports the current AO strategy.
- Share a digital version with the distributed team and place a physical poster in a visible location for stakeholders (e.g., the management floor).
- Use the tree to negotiate new requests: no additional fruits without removing or completing items already in progress.
Step 9 – Institutionalize the cadence
- Repeat the exercise on a regular cadence (e.g., quarterly), with lighter updates in between.
- At each review, discuss:
- Which fruits were harvested.
- Which roots proved critical or insufficient.
- How business‑as‑usual evolved.
- Adjust visualization rules and facilitation questions as the team matures.
3. Observed Effects in AO Adoption
From repeated use of the Apple Tree method, several patterns typically emerge:
- Strength: Teams develop a strong sense of ownership, and the complexity of their work becomes tangible rather than abstract.
- Weakness: The representation remains local and qualitative, making cross‑team comparison limited by design.
- Opportunity: The explicit structure greatly facilitates prioritization and negotiation of capacity, both within the team and with stakeholders.
- Threat: By revealing real constraints and overload, the method can challenge existing structures and expose tensions with PMOs or managers who attempt to introduce unplanned work.
In the broader AO context, the Apple Tree serves as a bottom‑up mechanism that makes local realities visible, and thus complements top‑down organizational design. Together, they enable teams to organize themselves more responsibly within a coherent adaptive framework.