Skip to main content

Downstream — Top-Down Deployment

The downstream approach starts from the top. Leadership defines a transformation plan, selects the improvement objectives, and creates Obeyaka teams to execute them. The direction is clear from day one: executives decide what to achieve and how much to achieve in the short term. The initiatives are already known; what is needed is structured execution.

How It Works​

  1. Leadership defines upper-level objectives and the transformation scope
  2. Obeyaka teams are created with assigned roles (Team Owners, Team Leaders, Team Members)
  3. Planning events are conducted to cascade objectives through Matrix catchball
  4. Teams execute the full Team cycle from the beginning — all events, all artefacts
  5. Scale events are introduced once multiple teams are operating

Characteristics​

  • Authoritative and planned — the organization commits resources and structure upfront
  • Lower cultural impact — the framework is adopted as a process, not as a shift in how people think about work
  • Fast but decreasing results — initial gains come from low-hanging fruit, but without cultural buy-in, improvements plateau
  • Higher resistance to change — teams may perceive the framework as imposed rather than chosen
  • Higher implementation cost — training, tooling, and dedicated time must be provisioned across all teams simultaneously

When to Choose Downstream​

  • The organization faces an urgent need for structured execution (turnaround, compliance, aggressive targets)
  • Leadership has strong alignment on objectives and is willing to sponsor the transformation
  • The culture already values process discipline, and what is missing is a coherent framework
  • There is budget and capacity to deploy across multiple teams at once

Risk​

If leadership sponsorship weakens or results plateau, the framework may be abandoned before it has time to create cultural roots. The downstream approach optimizes for speed but is fragile under organizational turbulence.

Anti-pattern: The Mandate Without Follow-Through​

Leadership announces the transformation, assigns roles, and expects results — but does not participate in Planning, does not attend Reviews, and does not adjust objectives based on feedback. The framework is imposed but not supported.

How to detect: Team Owners do not have access to upper-level objectives. Planning events happen without leadership input. The Matrix is built in isolation without catchball.

How to recover: Downstream requires active sponsorship, not passive authorization. The minimum commitment from leadership is: define clear objectives, participate in the first Planning, and attend every Review. If leadership cannot commit to this, the upstream approach is more appropriate.