Deployment — Getting Started with Obeyaka
There are two ways to bring Obeyaka into an organization. Neither is universally better — the right choice depends on context, urgency, and culture. Understanding the trade-offs is essential before starting.
Two Approaches
| Dimension | Downstream | Upstream |
|---|---|---|
| Starting point | Leadership defines the plan | A pilot team learns by doing |
| Speed of first results | Fast (weeks) | Medium (months) |
| Sustainability of results | Decreasing over time | Increasing over time |
| Cultural impact | Lower — adopted as process | Higher — adopted as mindset |
| Resistance to change | Higher — perceived as imposed | Lower — perceived as chosen |
| Initial investment | Higher — multiple teams at once | Lower — one team at a time |
| Key risk | Abandonment if sponsorship weakens | Stalling if pilot team fails |
| Best suited for | Urgency, compliance, turnaround | Cultural transformation, autonomy |
Hybrid Approach
In practice, many organizations blend both approaches. A common pattern is to start upstream with a pilot team, and once the model is proven, use downstream deployment to accelerate adoption across the rest of the organization. The pilot team's experience provides the credibility and practical knowledge that makes the downstream phase less fragile.
Phase 1 (Upstream): [Pilot Team] → learns → demonstrates results
Phase 2 (Transition): [Pilot Team] → coaches → [2-3 new teams]
Phase 3 (Downstream): [Leadership] → deploys → [remaining teams] with proven playbook
The key insight is that downstream without upstream tends to be mechanical, and upstream without downstream tends to be slow. The hybrid approach captures the cultural depth of upstream and the execution speed of downstream.