A145 | The Whiteboard We Keep Adding To — How One Internal Habit Changed the Way We Solve Problems

There is a whiteboard in the room we use for production meetings that has been in continuous use for about three years. It started as a temporary fixture — someone needed to draw a diagram to explain a loom tension problem and the meeting ran long, so the diagram stayed up. By the next week, someone else had added something next to it. Three years later, the board is covered in a sedimentary record of problems we have encountered and things we have figured out, written in at least six different people's handwriting with markers in three colours.

We tried to erase it once. The production manager said leave it, he would deal with it later. Later never came, and over time we stopped thinking of it as clutter and started thinking of it as a working document. This is the story of how that happened and what it taught us about the way problems actually get solved in a manufacturing environment.

What the Whiteboard Contains

If you looked at it today, you would see several distinct layers. The oldest content — nearly illegible under later additions — includes notes from a dye consistency issue we had in the spring of 2023: the specific batch numbers affected, the dye lot codes, the adjustment we made to the temperature hold time that fixed it. We do not have the same problem anymore. We could probably erase those notes. We have not, partly because no one is sure whether they might become relevant again, and partly because the production manager says seeing them reminds him of something he learned that winter about the relationship between ambient temperature and dye uptake that he still applies.

Layered over those are notes from a jacquard setup problem that occupied two weeks in late 2024 — thread tension specifications for a particular metallic yarn that turned out to be thinner than labelled. There is a small diagram of the loom configuration that eventually worked, with an annotation in red saying "only for this specific spool type." We lost almost a full week of production to that problem before we found the fix. The diagram on the whiteboard is why we will not lose another week if we encounter the same yarn again.

The most recent additions are from this month: a note about the timing of a customer's approval cycle that affects how we schedule production in September, and a short list of questions that came up in a planning conversation that no one had time to answer on the spot but that needed to stay visible rather than disappearing into someone's notebook.

What We Think the Whiteboard Is Actually Doing

A factory's institutional memory lives in three places: written procedures, the heads of experienced staff, and whatever informal records accumulate in the environment. The first category is carefully maintained. The second is valuable but fragile — it walks out the door when someone leaves or retires. The third is usually underestimated.

The whiteboard is the third category made slightly more durable. It is not a substitute for written procedures, which need to be searchable and structured and version-controlled. It is not a substitute for the kind of deep experience that Master Huang has about the tension rollers in cold weather. It is the in-between thing: the notes from a problem that has not been fully absorbed into official procedure yet, the diagram that explains something faster than any text could, the list of open questions that someone needs to see every day until they get answered.

What Happened When We Tried to Digitalise It

About eighteen months ago, a staff member suggested we move the whiteboard content into a shared document — a living knowledge base that everyone could access from their phones. The suggestion was well-intentioned and probably right in principle. We tried it for about ten weeks.

What happened was: people added things to the document for the first three weeks, while the initiative was fresh. Then additions slowed. By week eight, the document was being read but not written to. By week ten, it had effectively stopped growing. The whiteboard, meanwhile, continued accumulating content as it always had.

We spent some time thinking about why. The most honest explanation we arrived at is this: writing something on a whiteboard in a room where a problem is being discussed is the natural continuation of the discussion. Opening a phone, navigating to a shared document, and typing a structured entry is a separate task that requires a separate decision. In a busy production environment, the separate task loses to everything else that is also waiting.

The digital knowledge base is still there and still accessible. It is useful for things that need to be found by people who were not in the original conversation. The whiteboard is useful for things that need to stay visible to the people who are in the room every day. Both have their place. We stopped thinking of them as competing and started treating them as different tools for different jobs.

The Rule We Eventually Made

The one formal rule we introduced, about a year into the whiteboard's continuous-use period, is that the production manager has to photograph it at the end of every month and store the photograph. This was prompted by a specific incident: a note about a customer's packaging specification got partially erased during a session when someone needed more space, and we could not fully reconstruct what it said. The monthly photograph does not replace the whiteboard — it creates a record of what was on it in case something important gets lost in the same way.

It is a small, low-friction habit. It takes about thirty seconds. It has already paid for itself once, when a photograph from February contained a note about a thread specification that became relevant again in June and that no one clearly remembered the details of. The photograph had the details.

We are not claiming the whiteboard is a system. It is not. It is a whiteboard in a meeting room that has been in use long enough to become something worth paying attention to. The lesson, if there is one, is that the informal knowledge-keeping habits of a team often contain more value than they appear to, and that the right response to noticing that value is usually not to replace the habit with something more formal — it is to add the smallest possible structure that prevents the value from getting lost.