Go see the work. Keep the follow-through connected.
A walk should not end as another checklist no one revisits. Digital Gemba Walks keeps observations with the people, place, and improvement records they came from, so recurring problems have a clear next step.
Development preview on Lite and above.
When walks live in paper notes or disconnected forms, an observation can lose its owner, its location, and its connection to the improvement work already underway.
Start with the work that is getting stuck
An existing site, department, team, work area, walk templates, assigned people, and relevant KPIs or Andon locations.
Keep the next step visible
Choose one of eight built-in templates or create versioned questions. Assign the walk to a person or team and work area, then share a QR route that still requires sign-in. Review context before starting; capture answers, observations, and private photos; save a draft and resume it later. Every walk keeps its assigned template version even if that template is later archived.
See what moved and what needs attention
A scoped walk record, explicit observation classifications, source links to existing CI work, and reports that distinguish completed walks and closed follow-through from open or unrecorded work.
A learning cycle
An idea should have somewhere to go next.
A proposal becomes useful when the team can test it, check what changed, and decide what to keep.
Plan
Name the problem, owner, expected change, and measure.
Do
Try the change on a scale the team can review.
Check
Compare what happened with the expectation and evidence.
Act: standardize or adjust
Make the agreed method clear when the test holds. If it does not, adapt the change and test again.
Keep what was seen at the work, then connect the next step to the improvement system the team already uses.
Start with a real walk, not a blank form
Use eight built-in templates for general Gemba, safety, quality, 5S, process and waste, people and culture, customer experience, and leadership—or create a versioned template with your own questions. Before starting, check assignment and work-area context. A QR destination can open the assigned walk, but still requires login.
Capture what happened where it happened
Answer the walk questions, record an observation at its scoped site, department, and work area, and attach private photos. Drafts can be resumed; completing a walk is an explicit action. The captured development workspace is empty, so it does not imply any customer records or outcomes.
Make the follow-through an explicit decision
Classify a finding as Observation Only, Action, Andon, Improvement Idea, or Existing Improvement. An Action requires an existing improvement, owner, and due date; Andon uses an existing scoped point and reason; an Improvement Idea creates a linked idea, while Existing Improvement links a chosen record. Fishbone / 5 Whys and A3 investigations, KPI context, huddle views, and reports remain linked to their source records.
Review recurrence from source evidence
Inspect 14- and 30-day recurrence from recorded evidence and open its source locations. Smart Gemba may suggest a question, but it does not invent counts or change a template automatically: approve a reviewed question explicitly, or dismiss or snooze it. Reports separate actual completed walks and closed Action follow-through from open records.
Digital Gemba Walks keeps the observation connected to the place it came from and the CI work the team chooses to do next.