Gemba Walk

It is 6:45 AM at the Braine-l'Alleud sterile fill-finish facility. The Site Director puts on her cleanroom gown, taps the ProBeya app on her tablet, and opens the "Building C — Aseptic Suite Morning Walk" route. As she moves through the gowning corridor, the Grade B prep area, and into the Grade A filling suite, she records observations at each checkpoint: PPE compliance verified, environmental monitoring plates correctly positioned, visual management board updated with overnight differential pressure data. At Station 3, she notices a cracked seal on the pass-through hatch — she photographs it, classifies it as a Concern, and with one tap generates a tracked action assigned to the Maintenance Lead with a 24-hour due date.

By the time she reaches the TIER 2 meeting at 8:00 AM, the observation is already in the system, the action is assigned, and the maintenance team has received a push notification. This is what Taiichi Ohno meant when he said "go and see for yourself" — except now the seeing is recorded, the acting is tracked, and the loop is closed.

Why Gemba Walks Matter in Pharma

"Gemba" (現場) means "the real place" in Japanese — the actual location where value is created. In pharma manufacturing, the gemba is the production floor, the QC laboratory, the warehouse, the packaging line. The gemba walk is the practice of leaders going to the real place, observing the real work, and engaging with the real people.

FDA's current Good Manufacturing Practice guidance emphasizes management oversight of manufacturing operations. EU GMP Chapter 1 requires that senior management "ensure that an effective pharmaceutical quality system is in place." Gemba walks operationalize these requirements: they transform "management oversight" from an abstract audit finding into a concrete, recurring practice with documented evidence.

More importantly, gemba walks build trust. When a Site Director regularly walks the floor and listens to operators, two things happen: problems surface earlier (because people speak up), and solutions stick (because people feel heard).

For Senior Leaders

The gemba walk is not an inspection. You are not there to find fault. You are there to understand reality. Ask open-ended questions: "What is making your job harder today?" "Is there anything you need that you do not have?" The observations you record should reflect what you learned, not what you judged.

Walk Route Templates

A walk route defines the physical path through the facility, organized as a sequence of areas with specific checkpoints at each stop.

Creating a Walk Route

1. Navigate to a board and open the Gemba Walk tab
2. Click + New Walk Route
3. Enter a name (e.g., "Weekly VP Walk — Building A Manufacturing")
4. Add areas in the order they should be visited:

Field	Description	Example
Area Name	Physical location to visit	"Grade B Prep Room 2.04"
Checkpoints	Specific items to observe (at least 1 required)	"Differential pressure reading within spec", "Gowning procedure followed correctly"

5. Click Save

Designing Effective Routes for Pharma Facilities

The route design should reflect the natural flow of the facility and the walk's purpose:

Safety-focused walk:

1. Emergency exits and eye wash stations → 2. Chemical storage areas → 3. High-traffic intersections → 4. Equipment with moving parts → 5. Waste handling stations

Quality-focused walk:

1. Incoming materials staging → 2. Dispensing/weighing rooms → 3. Manufacturing suites → 4. In-process testing stations → 5. Packaging lines → 6. Finished goods warehouse

GMP compliance walk:

1. Gowning areas → 2. Environmental monitoring points → 3. Logbook stations → 4. Cleaning status tags → 5. Equipment calibration labels

Route Design

Order areas to minimize backtracking and reduce gowning/de-gowning cycles. In a classified environment, plan the route from higher to lower classification grades. Include checkpoints that are specific and observable — "Check everything" is not a checkpoint. "Verify that DP gauge in Room 2.04 reads ≥15 Pa" is a checkpoint.

Conducting a Walk

Recording Observations

While following the walk route, the walker records observations in real time:

1. Open a walk route from the Gemba Walk tab
2. For each area/checkpoint, click + Add Observation
3. Fill in the observation details:

Field	Description	Required
Area Name	Where the observation was made	Yes
Checkpoint	Specific checkpoint (auto-populated from route)	No
Type	Classification of the observation	Yes
Description	Detailed description of what was observed	Yes
Photo	Photo evidence (uploaded to S3 storage)	No

Observation Types

Type	Purpose	Pharma Example
Positive	Recognize good practices and improvements	"Operator proactively flagged borderline DP reading before it went out of spec — excellent vigilance"
Concern	Flag safety, quality, or compliance issues	"Pass-through hatch seal cracked in Room 2.07 — contamination risk to Grade A area"
Improvement	Identify opportunities for waste reduction or process enhancement	"Operators walking 40m to retrieve printouts — relocating printer to suite would save 12 min/batch"

The Power of Positive Observations

In behavioral science, recognition of desired behaviors is 3-5x more effective at sustaining improvement than correction of undesired behaviors. Aim for a 3:1 ratio of positive to concern observations. This is not about being soft — it is about being effective. When operators see that good work is noticed and recorded, they maintain higher standards even when no one is watching.

From Observation to Action: Closing the Loop

The critical step that separates a digital gemba walk from a paper clipboard is the automatic conversion of observations to tracked actions.

Generating an Action

1. Open a completed observation
2. Click Create Action
3. Fill in the action details:

Field	Description	Default
Title	Action title	Pre-filled from observation description
Priority	Critical, High, Medium, or Low	Medium
Responsible	User assigned to resolve the issue	(empty)
Due Date	Target completion date	(empty)
Tier Level	TIER level for escalation tracking	1

The action is created with source = "gemba" and automatically linked to the originating observation. This creates bidirectional traceability:

• From the observation, you can navigate to the follow-up action
• From the action, you can trace back to the original gemba observation, including the photo evidence

One Observation, One Action

Each observation can only generate one action. If an observation already has a linked action, the Create Action button is disabled to prevent duplicates. If the action was closed prematurely, reopen it rather than creating a new one from the same observation.

Worked Example: Cracked Seal to Corrective Action

Step	Time	What Happens
Observation logged	06:52	Site Director photographs cracked seal, classifies as Concern
Action created	06:53	"Replace pass-through hatch seal — Room 2.07" — Priority: High, Due: 24h
Notification sent	06:53	Maintenance Lead receives push notification
Discussed at TIER 1	07:15	Morning standup — team confirms maintenance scheduled for afternoon
Action completed	14:30	Maintenance Lead marks action as Done, attaches work order reference
Verified at next walk	06:48 (next day)	Site Director confirms seal replaced during next morning walk

Total elapsed time from observation to verified closure: 24 hours. On paper, this same cycle typically takes 5-10 business days.

Walk Statistics and Analytics

Each walk route displays summary statistics that help track gemba walk effectiveness:

• Total observations made across all sessions
• Breakdown by type (positive / concern / improvement)
• Actions generated from observations
• Open actions still pending resolution

For OpEx Coordinators

Track gemba walk frequency as a KPI on your SQCDP boards. The target is not "more walks" — it is "consistent walks at the right cadence." For a pharma manufacturing site, recommended cadences are:

Role	Recommended Cadence
Team Lead / Supervisor	Daily (focused, 10-15 min)
Department Manager	2-3x per week (thematic, 20-30 min)
Site Director / VP	Weekly (broad, 30-45 min)
Quality Head	Weekly (GMP-focused, 30 min)

Regulatory Context

Gemba walk records in ProBeya serve multiple regulatory purposes:

• FDA Process Validation Stage 3 (Continued Process Verification): documented evidence that manufacturing leadership regularly reviews process performance at the point of manufacture
• EU GMP Chapter 1.4(viii): evidence of "periodic management review of the pharmaceutical quality system" at the operational level
• ISO 13485:2016 Section 5.6: management review input that includes "data from production and service provision"
• 21 CFR Part 211.180(e): records showing that "at least annually" (and preferably much more frequently) written procedures are evaluated and updated based on real observations

The photo evidence capability is particularly valuable during regulatory inspections. When an FDA investigator asks "How does site management maintain awareness of shop floor conditions?" the answer is not a policy document — it is a searchable history of dated, geotagged observations with photographic evidence and linked corrective actions.

Permissions

Action	Required Role
View walk routes and observations	Any board member
Create/edit walk routes	Board admin or workspace admin
Conduct walks and add observations	Any board member with write access
Create actions from observations	Any board member with write access

Related Features

• Action Log — Track and resolve actions generated from gemba observations
• 5S Audit — Combine gemba walks with formal 5S audits for comprehensive workplace assessments
• KPI Boards — Track gemba walk frequency and observation counts as People or Quality KPIs
• Escalation Engine — Escalate critical observations through the TIER hierarchy
• Routines — The Gemba Walk preset in the routine library provides a structured 15-step walk template