Why Analog First: Building Data Credibility
Digital ERP data is distrusted on most shop floors. The distrust is often rational: the data was loaded years ago, never validated, and does not reflect current reality (see Guide 08). Operators know the numbers are wrong. Supervisors know the numbers are wrong. When management makes decisions based on those numbers, the floor loses confidence in the entire data system.
The Pitch Board is an analog reset. It starts fresh, with data collected by the people who do the work, at the point where the work happens, in real time. There is no system lag, no data entry delay, no translation error. The board is right there on the wall, updated every hour, visible to everyone. When it says “missed target — reason: missing P/N 4567-2,” everyone can see it, and everyone can verify it.
Within four weeks of consistent use, a Pitch Board produces better actionable data than most ERP systems. Not because the ERP is bad technology — but because the Pitch Board’s data is honest, operator-generated, and immediately verifiable.
What a Pitch Board Looks Like
A Pitch Board is a whiteboard (or laminated poster) mounted at the production cell with the following structure:
| Time Period | Target | Actual | Cumulative +/– | Reason Code (if miss) |
|---|---|---|---|---|
| 7:00–8:00 | 3 units | 3 | 0 | — |
| 8:00–9:00 | 3 units | 2 | –1 | M-02: Missing P/N 4567-2 from kit |
| 9:00–10:00 | 3 units | 3 | –1 | — |
| 10:00–11:00 | 3 units | 1 | –3 | E-01: Work instruction Rev C, current is Rev E |
| 11:00–12:00 | 3 units | 3 | –3 | — |
| 12:30–1:30 | 3 units | 3 | –3 | — |
| 1:30–2:30 | 3 units | 2 | –4 | Q-03: Rework from upstream sealant defect |
| 2:30–3:30 | 3 units | 3 | –4 | — |
At the end of each hour, the line lead updates the board. It takes 30–60 seconds. The cumulative column makes the day’s trajectory visible at a glance — anyone walking past can see whether the cell is on target, ahead, or behind, and exactly why.
⚠️ If the Pitch Board Is Used to Discipline Operators, It Will Be Falsified Within Two Weeks
The Pitch Board does not measure operator performance — it measures system performance. When the reason code says “missing part from kit,” that is a logistics failure. When it says “work instruction outdated,” that is an engineering failure. The operator is the reporter, not the subject. The moment a supervisor uses Pitch Board data to blame an operator, every operator on the floor learns to write “on target” regardless of reality, and the board becomes theater.
Designing the Reason Code Taxonomy
| Category | Code | Description |
|---|---|---|
| Material (M) | M-01 | Kit incomplete — part not delivered to station |
| M-02 | Wrong part in kit (P/N mismatch) | |
| M-03 | Damaged part requiring replacement | |
| M-04 | Consumable depleted (fasteners, sealant, safety wire) | |
| Quality (Q) | Q-01 | Rework from upstream quality escape |
| Q-02 | Awaiting inspector buy-off (inspector unavailable) | |
| Q-03 | Discrepancy disposition pending (MRB hold) | |
| Equipment (X) | X-01 | Tool unavailable or out of calibration |
| X-02 | Fixture/jig malfunction | |
| X-03 | Crane/support equipment unavailable | |
| Engineering (E) | E-01 | Work instruction outdated or missing steps |
| E-02 | Engineering change (ECN) mid-flow | |
| E-03 | Drawing discrepancy or ambiguity | |
| Logistics (L) | L-01 | Predecessor work not complete (upstream delay) |
| L-02 | Waiting for crane access or material movement | |
| L-03 | Waiting for shared tooling from another station | |
| Other (O) | O-01 | Training activity (new hire, cross-training) |
| O-02 | Other (write in) |
Design principles:
- Specific enough to drive action: “M-01: Kit incomplete” tells the IE exactly where to look. “Material issue” does not.
- Simple enough to record in 10 seconds: the line lead should be able to glance at the code list and pick the right code immediately
- 15–20 codes maximum to start. Expand only when “Other” is used more than 10% of the time.
Weekly Pareto Analysis: Turning Data into Engineering Action
Scenario: After four weeks of Pitch Board data collection, the IE tallies all reason codes:
| Code | Description | Occurrences | Lost Hours | Cumulative % |
|---|---|---|---|---|
| M-01 | Kit incomplete | 38 | 76 hrs | 31% |
| L-01 | Predecessor work not complete | 27 | 54 hrs | 53% |
| Q-02 | Awaiting inspector buy-off | 19 | 38 hrs | 69% |
| E-01 | Work instruction outdated | 14 | 28 hrs | 80% |
| X-01 | Tool unavailable | 9 | 18 hrs | 87% |
| Q-01 | Upstream quality escape | 8 | 16 hrs | 94% |
| All other | Various | 7 | 14 hrs | 100% |
Pareto interpretation: Four root causes (M-01, L-01, Q-02, E-01) account for 80% of all lost production hours. These are the “vital few.”
Engineering response priority:
- M-01 (Kit incomplete): Implement Water Spider delivery and kit verification process. Target: reduce from 38 to <10 occurrences in the next 4 weeks.
- L-01 (Predecessor delay): Investigate upstream constraint — likely a bottleneck or schedule sequencing issue.
- Q-02 (Inspector availability): Stagger inspector assignments to match Takt periods; implement self-inspection for non-critical attributes.
- E-01 (Outdated instructions): Priority update of work instructions at this cell — ERP data correction project (Guide 08).
The result after 4 more weeks: If the top 2 causes are addressed, lost hours drop by ~53% (from 244 hrs to ~115 hrs per month). That is 129 hours of recovered production capacity per month — without adding headcount, overtime, or equipment.
Closing the Loop: Making Operators Believe the Data Matters
💡 Operators Who Trust the System Give You Better Data
Operators who trust that their Pitch Board data results in engineering action will give you more honest data than any digital system ever will. The feedback loop is simple: operator reports problem → engineer fixes problem → operator sees the fix → operator reports the next problem with more detail and more willingness. This virtuous cycle produces exponentially better data over time. Break it once (ignore a report, blame the operator, fail to follow up), and it takes months to rebuild.
The action loop:
captures miss
analysis
ticket created
visibly
The “visibly” part is crucial. When the Water Spider system launches because of Pitch Board data showing 38 kit-incomplete events per month, post a note on the Pitch Board: “Your M-01 data drove this change. Thank you.” This closes the loop. The operators see that their data produced a concrete engineering action. They will give you better data next month.
🎯 The Bottom Line
The Pitch Board does not improve performance by itself — it makes the system’s failures visible so engineers can eliminate them. It is the foundation of a data-driven improvement culture: honest data from the floor, weekly Pareto analysis by the IE, engineering action on the vital few, and visible feedback to the operators who reported the problems. When this loop runs consistently, it produces more sustainable improvement than any consultant engagement or Kaizen event. Next: Standard Work & TWI — documenting the improved methods so they can be trained and sustained.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.