When should I use it

Gemba Flow is a good fit when three conditions hold at the same time: you are shipping to real users, the consequences of a bad deploy matter, and you want agents to carry out implementation work rather than just assist with it. When those conditions are absent, a lighter setup is probably the right call.

The fit conditions

Small team, real users, real consequences. Gemba Flow’s overhead — structured tickets, branch conventions, CI checks, PR review — is not free. It pays off when the cost of a bad deploy exceeds the cost of the process. A side project with no users, or a prototype you can throw away, does not clear that bar. A product with paying users or external commitments does.

You want agents to carry work, not assist with it. There is a difference between using Claude to autocomplete a function and using Claude to take a ticket from backlog to merged PR. Gemba Flow is built for the second mode. If you are primarily using AI as a writing aid inside your own editor, the framework adds structure you will not use.

You need human supervision to stay in the loop. Gemba Flow’s design assumption is that the human operator is a supervisor, not an implementor. If you want to write every line yourself and just get occasional help, the framework’s review gates and board workflow will feel like friction. If you want agents to implement while you walk the line and make go/no-go calls, the framework is designed for exactly that.

Decision tree

What “responsible human supervision” means here

The phrase comes from the design premise: when agents ship code at machine speed, the human’s job changes from implementor to supervisor. A supervisor who cannot observe the work cannot be responsible for it.

Gemba Flow keeps the observation cost low enough that supervision stays meaningful. Short branches, small PRs, structured commits, preview environments — each practice exists to keep one loop tight: can the human walking the work see what is actually happening?

If that question matters to you, Gemba Flow is for you. If it does not, the framework is solving a problem you do not have yet.