Rules at the system's core
The person carrying out a fix cannot verify their own work. Domain rules are also reflected in database constraints.
03 / Web · Manufacturing
GembaFrom a finding to a verified fix.
Gemba grew out of my work with mLean in manufacturing. In it, I connect findings from workplace walks with corrective actions and checks that the problem has been resolved.
EXPERIENCE IN LEAN MANUFACTURING
From working with mLean to building Gemba.
Implementing and using mLean helped me understand what I needed from a digital Lean and kaizen tool. Some features were missing or did not suit the way I worked. That led me to create Gemba.
Someone records a problem and adds a photo or a note. An assignee takes ownership and provides evidence of corrective action; another person verifies the result. Walk schedules, work standards and operation measurements connect individual findings with everyday manufacturing work.
- 01
Record what is there
A nonconformity becomes a finding. A photograph or note adds detail about what was observed on site.
- 02
Take ownership and act
An assignee and a due date define the next step. The action needs supporting evidence.
- 03
Verify and follow up
Another person verifies the fix. Recurring and safety-related issues also need an effectiveness check.
BROWSER SIMULATION
From the queue to corrective action. Click through it.
Try selected workflows directly in your browser.
This is a separate simulation using fictional data.
GEMBA / INTERACTIVE DEMOSIMULATION · NO SIGN-IN
Loading the demo… A text overview is available below.
What you can try in this demo
- Queue and finding — Choose a demo plant, open the photographic evidence and work through a fix and independent verification.
- Schedule and audit — Open a sample walk and record an answer to an audit question.
- Documentation — Search a local copy of a sample work instruction.
- Plant overview — Browse the halls, open an operation measurement or visit administration.
TECHNICAL DECISIONS
A finding needs a next step.
An audit stays consistent when its template changes
An audit uses a frozen version of its template. Later changes must not overwrite that basis.
Built for the shop floor
Go, SQLite and HTML in one system. Core features and source retrieval do not depend on a language model.
Rules go beyond buttons
A rejected transition must neither change the state nor create a false audit event.
A walk is more than a form
Template versions, scoring schemes, recurring schedules and roles preserve the meaning of records over time.
AI is an addition
Documentation supports full-text search with citations even without a model. People record decisions and audit answers.
My contribution
Design and development of my own tool, drawing on my work with Lean methods and mLean. The focus is on connecting findings, responsibility, evidence and verification of corrective action.
Project and demo status
The project has a demonstration environment with five fictional plants. This website presents selected workflows from it. Finding counts and photos are demo content, not results from a customer deployment.
EVIDENCE AND LIMITS
The sources are the repository and a signed-in review of five demo plants on 18 October 2026. This web simulation uses selected text and generated photographs from fictional demo data. The displayed counts are not results from a customer deployment.