Go to the gemba
Understanding happens at the source. Conference rooms come second.
About
The real place, then the software.
Gemba Tech started from a plain observation: technology projects fail when they are designed away from the work they are supposed to support.
We are based in Coeur d'Alene, Idaho. The name is the method. Gemba is the Japanese word for the real place — the floor, the route, the counter — where value is created or lost.
The practice comes from manufacturing and from years of watching lean habits change operations that software, alone, had only documented. Understand the work. Then improve it. Then write the code that makes the improvement stick.
Every feature has to earn its place. If it does not remove waste or create a result someone can name, it waits.
What we will not compromise
Respect the people doing the job
The best system makes their judgment faster. It does not replace it with a form.
Eliminate waste
If a feature does not change an outcome, it does not ship.
Quality is built in
We would rather release a smaller thing that holds than a large thing we have to apologize for.
Improve in public
Every cycle should teach the team something they can use on the next one.
Think past the launch
Short-term demos are easy. We stay interested in what is still true six months later.