Skip to main content

Upstream — Bottom-Up Evangelization

The upstream approach starts with a single pilot team. This team learns Obeyaka by practicing it — running the events, building the artefacts, solving real problems through Circles. As the team becomes more productive, their results become visible, and other teams begin to ask "what are they doing differently?" The change spreads through demonstration, not mandate.

How It Works​

  1. A single team is selected as the pilot — ideally one with a motivated Team Leader and visible, measurable work
  2. The pilot team adopts the Team cycle: Planning, Briefing, Debriefing, Circle, and Review
  3. Leaders (supervisors, managers) participate actively — they do not delegate the transformation, they lead it alongside their team
  4. As the pilot team demonstrates results, adjacent teams are invited to observe and adopt
  5. Each new team adapts the framework to their context, guided by the pilot team's experience
  6. Scale events emerge naturally when multiple teams need coordination

Characteristics​

  • Progressive and pilot-driven — the organization learns by doing, one team at a time
  • Higher cultural impact — team members internalize the framework because they chose it and shaped it to their reality
  • Medium-term but increasing results — early cycles are slower as the team learns, but each cycle builds on the previous one
  • Lower resistance to change — the framework is adopted because it works, not because it was mandated
  • Lower initial cost — only one team needs support at the start; investment scales with adoption

When to Choose Upstream​

  • The organization values autonomy and wants change to emerge from the teams themselves
  • There is no immediate crisis requiring broad transformation
  • Leadership wants deep cultural change, not just process improvement
  • There is a strong candidate for the pilot team (motivated leader, measurable work, visible to other teams)

Risk​

If the pilot team fails or its results are not visible, the approach may stall. The upstream approach optimizes for sustainability but requires patience and a strong initial team.

Anti-pattern: The Invisible Pilot​

The pilot team runs Obeyaka successfully but no one outside the team knows. Results are not shared. Other teams are not invited to observe. The pilot becomes an island of improvement in a sea of business as usual.

How to detect: After two full cycles, no other team has expressed interest in adopting the framework. The pilot team's improvements are not referenced in organizational meetings. Leadership is unaware of the pilot's results.

How to recover: The pilot team must make its results visible — through internal presentations, open Circle sessions, or shared metrics. The Team Owner plays a key role here: they are the bridge between the pilot team and the rest of the organization. If results are real but invisible, the approach will stall regardless of quality.