Team — The First Team of Progress
Obeyaka Team is the framework for a single team. It defines the minimum structure a team needs to set direction, improve continuously, and sustain its gains.
Pains
Every team faces recurring dysfunctions that erode progress. Obeyaka Team identifies three and provides a specific moment to counteract each one.
Lack of Focus — Objectives and priorities are unclear or not defined. The team works hard but in scattered directions. Energy is spent without convergence. People finish tasks that do not connect to a shared goal, and at the end of the cycle no one can articulate what the team actually achieved.
Execution Drift — The team starts with a clear direction but gradually deviates. Follow-through weakens as daily urgencies take over. The gap between what was planned and what is actually happening grows silently until it becomes too large to correct within the cycle.
Lack of Discipline — Improvements happen but do not stick. The team solves a problem, celebrates the result, and then reverts to the previous way of working. There is no mechanism to lock in gains, so the same problems resurface cycle after cycle.
Moments
A team of progress operates through three moments — specific points where management action counteracts a recurring pain:
Set — Counteracts: Lack of Focus. Define the target condition. Like a ship establishing its destination before sailing, the team must know where it is going before it can move. The Team Owner leads this moment.
Improve — Counteracts: Execution Drift. Close the gap between current and target conditions. The team measures where it stands, compares it to where it wants to be, and adjusts course. The Team Leader leads this moment.
Sustain — Counteracts: Lack of Discipline. Lock in the gains. Once an improvement is confirmed, it becomes the new standard — a new starting point, not a ceiling. Team Members lead this moment.
| Moment | Description | Role | Event | Artefact |
|---|---|---|---|---|
| Set | Define direction and priorities for the cycle | Team Owner | Planning · Review | Matrix |
| Improve | Close the gap between current and target conditions | Team Leader | Briefing · Debriefing | Board |
| Sustain | Lock in gains as new standards | Team Member | Circle | Story |
Flow
| Step | Layer | PDCA | Event | Description |
|---|---|---|---|---|
| T1.1 | Strategic | Plan | Planning | Team Owners transform upper-level objectives into team-level objectives using the Matrix |
| T1.2 | Strategic | Do | Planning | Team Owners perform catchball with Team Leaders, negotiating and committing team-level matrices |
| T1.3 | Strategic | Check | Review | Each Team Owner verifies results per objective and reviews improvement opportunities in progress |
| T1.4 | Strategic | Act | Review | Team Owners detect strategic-level improvement opportunities and adjust objectives and priorities |
| T2.1 | Tactical | Plan | Briefing | Team Leader reads team Matrix objectives to the team and sets the improvement direction |
| T2.2 | Tactical | Do | Briefing | Team Leader assigns tasks per objective on the Board |
| T2.3 | Tactical | Check | Debriefing | Team detects and presents improvement opportunities from execution results |
| T2.4 | Tactical | Act | Debriefing | Team implements improvements and adjusts action plans accordingly |
| T3.1 | Operational | Plan | Circle | Team Members identify an improvement opportunity and estimate its potential value capture |
| T3.2 | Operational | Do | Circle | Team Members implement improvements periodically using Stories |
| T3.3 | Operational | Check | Circle | Team Members verify results against expected value and identify new potential opportunities |
| T3.4 | Operational | Act | Circle | Team Members adjust action plans and/or realize captured value into new standards |
PDCA Cycle
Role
Routine
Board
Internal Connections
- Planning to Briefing (T1.2 → T2.1) — Catchball output becomes briefing input (the negotiated Matrix arrives at the team)
- Briefing to Circle (T2.2 → T3.1) — Assigned tasks surface improvement needs (the Board feeds the Circle)
- Circle to Debriefing (T3.4 → T2.3) — Realized improvements surface in debriefing (the Circle reports back to the team)
- Debriefing to Review (T2.4 → T1.3) — Adjusted plans inform strategic review (the team's learning reaches the Owner)
Anti-patterns
The Improvement Theater
The team runs all events, fills all artefacts, and reports improvements — but nothing changes in how work is actually done. The framework becomes a performance layer on top of business as usual.
How to detect: Metrics improve on paper but team members' daily experience does not change. Improvement Stories document cosmetic changes. The framework is discussed in meetings but not referenced in daily decisions.
How to recover: Go to the Gemba. Observe the work as it actually happens. Ask team members: "What changed for you in the last cycle?" If they cannot answer, the improvement is theater.
The Disconnected Layers
Strategic, tactical, and operational layers run independently. Planning produces a Matrix that Briefing ignores. Briefing assigns tasks that do not connect to Circle improvements. The PDCA cycle runs at each layer but the layers do not talk to each other.
How to detect: The Matrix objectives do not appear on the Board. Board tasks do not generate improvement opportunities for the Circle. Circle results do not inform the Review.
How to recover: Trace the connections explicitly: T1.2 → T2.1 → T3.1 → T3.4 → T2.3 → T1.3. If any link is broken, the information does not flow. Fix the broken link before adding more events or artefacts.