Task A1.1: Sketch some Recursions

What is Task A1.1?

Task A1.1 is part of the "Observe" phase in the Viability Canvas methodology, specifically within the "Define the System-in-Focus" step (Step A1). This task instructs you to "Sketch some Recursions" to help identify the appropriate level of analysis for your VSM application.

Purpose of Sketching Recursions

The purpose of this task is to map the nested hierarchical levels of your organization to understand how different organizational units relate to each other. This serves several important functions:

1. Establishing context: Understanding how units are embedded within larger systems
2. Clarifying boundaries: Defining where one system ends and another begins
3. Exploring alternatives: Considering different potential systems-in-focus
4. Visualizing recursion: Making the fractal nature of organizations concrete
5. Preparing for focus: Creating the foundation for selecting your system-in-focus

By sketching recursions, you create a visual representation of the organizational hierarchy that helps you select the most appropriate level for your VSM analysis.

How to Complete Task A1.1

To sketch recursions effectively:

1. Start with a candidate unit of interest:
   • Draw or write the name of this unit (e.g., "Bike Repairs")
   • Use sticky notes for easier rearrangement if needed
2. Identify the next higher level that contains this unit:
   • Draw a larger shape around your candidate unit
   • Label this with the name of the higher-level system (e.g., "Bike Shop")
   • Continue this process upward until you reach the organizational boundary
3. Identify peer units at the same level:
   • For each level, identify other units that operate at the same level of recursion
   • For example, "Bike Sales" and "Parts Store" might be peer units to "Bike Repairs"
4. Consider lower levels if appropriate:
   • If your candidate unit contains subsystems, identify these as well
   • Draw them as smaller units contained within your candidate unit
5. Review and refine your recursion diagram:
   • Ensure the hierarchical relationships are accurately represented
   • Verify that all relevant organizational units are included

Example Application

In a retail organization example:

• You might start with "Bike Repairs" as your candidate unit
• This is contained within the "Bike Shop" at the next level up
• The "Bike Shop" might be part of "The Sports Mall" at the next level
• At the same level as "Bike Repairs," you might have "Bike Sales" and "Parts Store"

By creating this visual representation, you can clearly see how different organizational units nest within each other, providing crucial context for selecting your system-in-focus in the next step.

Why This Approach Works

Sketching recursions works well because:

1. It makes relationships visible: The hierarchical structure becomes explicit and clear
2. It's flexible: Using sticky notes allows for easy reorganization as understanding evolves
3. It facilitates discussion: The visual representation serves as a focal point for team conversations
4. It prevents confusion: Having a clear map prevents mixing different recursion levels in the analysis
5. It supports the fractal nature of VSM: Reinforcing that the same VSM principles apply at each level

When implementing this step for your own organization, ensure you capture both formal and informal organizational structures that might be relevant to your analysis.