Strategy Model
      Back to home
      1. Help Center
      2. Customize
      3. Strategy Model

      Understanding the Cascade Strategy Model

      Estimated reading time: 3 minutes

      The Cascade Strategy Model is the foundation of strategy execution in your organization as you translate it into Cascade. It defines the language, structures your platform, and —when set up well—ensures Cascade integrates seamlessly into your organization, from setting goals to tracking progress and managing planning cycles.

      This article explains the 4 key strategy layers and provides best practices to translate your Strategic Plan within Cascade.

      Why it Matters -  A strong strategy model:
           • Clarifies strategy: Translates high-level goals into actionable tasks.
           • Connects teams: Aligns leadership vision with frontline execution
           •       Streamlines management: Simplifies tracking and reporting at every level.

      The Four Typical Layers of Strategy

      When setting up your strategy in Cascade, most organizations' strategies follow these 4 common layers:

      image (1)-1

      1. Corporate (Executive Leadership)

        High-level goals and the organizational vision.

        • Example: “Increase market share by 15% over the next 5 years.”

      2. Business Units or Regions

        Priorities for divisions or regions that align with corporate strategy.

        • Example: “Launch 2 new product lines to drive regional growth.”

      3. Functional Departments

        Tactical plans created by departments like marketing, finance, or HR.

        • Example: “Develop a go-to-market strategy for new product launches.”

      4. Teams or Squads

        Day-to-day deliverables that execute departmental plans.

        • Example: “Run customer feedback sessions to refine product features by Q1.”

      Breaking Down Layers in Cascade

      Here's how to align your organization's strategy with these layers.

      Note: Your organization may have more or fewer layers—this represents a typical structure:

      1. Define the Layers

        Map your organisational structure:

        • Corporate: Vision and long-term objectives.
        • Business Units: Regional or divisional priorities.
        • Departments: Functional initiatives.
        • Teams: Tactical deliverables.

      2. Identify Goal Types

        Assign specific goal types to each layer:

        • Corporate: High-level objectives.
        • Business Units: Objectives and strategic initiatives.
        • Departments: Projects and success measures.
        • Teams: Tactical actions.

      3. Scope Goal Types to Plans

        Keep plans focused by scoping relevant goal types:

        • Corporate plans focus on long-term goals.
        • Departmental plans detail projects and success measures.
        • Team plans target tactical actions.

      Best Practices:

           • Simplify: Keep the model intuitive and easy for teams to follow.
           • Standardize: Use consistent goal types across all layers.
           • Filter: Add tags for regions or priorities to refine reports without over-complicating.

      Example: A retailer aligned their corporate vision of “increasing global customer satisfaction” with regional strategies, department initiatives, and team actions to improve customer service and drive growth.

      Final Takeaway

      By structuring your strategy into Corporate, Business Units, Functional Departments, and Teams, you create a clear and actionable pathway. Cascade streamlines this alignment, enabling efficient strategy execution and better results.

      Next Step: Learn how to configure your strategy model in Cascade by exploring Strategy Elements alongside  Using types to structure your strategy

      Summary of Key Takeaways
           •       Master the 4 layers of strategy: Corporate, Business Units, Functional Departments, Teams.
           •       Use Cascade to align your strategy model with your organizational structure.
           •       Prioritize clarity, alignment, and execution to drive results.

       

      FAQ


      Can I enforce which types can contribute to others across plan boundaries.

      No, goals and projects should be able to contribute where they need to across the business irrespective of where they belong.

      What happens when a type is moved to a plan it doesn’t belong on.

      We don’t prevent types from being moved to plans they aren’t intended to belong to. Ultimately we want to ensure your teams have the easiest experience possible building out goals and collaborating with team-mates.

      Can I share a goal onto a plan that doesn’t support that type of goal

      Yes, we allow existing goals to contribute to plans that don’t allow creation of that goal type to ensure teams have the easiest possible experience collaborating with one another.

      Can I rename the parts of the Strategy Model?

      Yes. We're providing you with a more flexible strategy model - example measure can be changed to key performance indicator for the most streamlined strategy. 

      Where can I enter the mission statement and values?
       Navigate to Plans and select the plan of your choice, click the "Plan Settings" and add the vision, mission and values in the description. 

      Are plans time-bound?

      No, there's no timelines on a plan. Once created, it'll stay forever in your workspace unless you delete them. Only objectives and its associated success criteria (actions, projects, measures) are time-bound.