task-ops
Shift changes at six. The board by the line has yesterday's numbers on it, three actions in the bottom right corner in marker pen, and one of them has a name next to it but no date. At some point in the next hour somebody wipes the top half to write the new figures, and by the end of the week two of those three actions have quietly ceased to exist. Nobody decided to drop them. The board simply ran out of room and the only record of them was the surface that got cleaned.
That is the problem a digital gemba board is being bought to solve, and it is worth being precise about it, because most of what gets sold under this heading solves a different problem: making the numbers prettier.
A gemba board exists so that a short conversation can happen in the place where the work happens, in front of information everybody can see at once. The information is a prompt. The conversation is the product.
That is why the board is on the floor and not in the office, and it is the thing most at risk when the board moves to a screen. A wall display that presents live figures beautifully can remove the reason to stand in front of it, because the figures are also on everybody's phone. The moment the team reads the numbers separately at their desks, the daily meeting becomes optional, and within a month it is a status email.
So the test for any digital version is not whether it displays more. It is whether the team still gathers, still points at something, and still leaves with actions that have owners. A board that makes the huddle better passes. A board that makes the huddle unnecessary has replaced a management practice with a screensaver.
Worth naming, because these are the requirements that get lost in a software selection.
Anybody can write on it, immediately, without a login. The whole team sees the same surface at the same moment, which is what makes disagreement visible. It is physically at the gemba, so standing in front of it means being where the work is. And it has a hard size limit, which forces the team to decide what matters rather than tracking everything.
A digital replacement that fails the first of those is the most common mistake. If updating a figure requires finding a supervisor with the right permissions on the right laptop, the board will be out of date by the second week.
There are only a few of these, and they are the whole case for digitising.
Continuity across shifts. This is the big one. A board has one surface and three shifts. Whatever the second shift needs to know from the first is either written somewhere that gets erased or communicated verbally at handover, which is when people are tired and leaving. Anything with a life longer than one shift, particularly open countermeasures, is at risk every time the marker comes out.
The trail behind a number. A whiteboard shows today. Whether today is normal, whether this is the fourth time this month, and what was tried the last three times are all absent. Teams compensate with paper logs in a folder under the board, which nobody reads during a ten minute huddle.
More than one place. Two sites cannot look at the same board. Neither can a supervisor at home, a quality engineer in another building, or a manager who covers four lines. Tiered escalation, where a line board feeds an area board which feeds a plant review, is possible on paper and laborious, because somebody transcribes at every level.
Actions that outlive the meeting. An action in marker pen has a name and, if the team is disciplined, a date. It has no history, no comment thread, no attachment and no reminder. When the walk moves on, the action has no existence outside that square of whiteboard.
These get discussed as one category and behave completely differently.
| Approach | What it is good at | Where it breaks |
|---|---|---|
| KPI dashboard on a wall display | Live figures pulled from machines or systems, no manual entry, looks credible to visitors | Read only. Actions and countermeasures have nowhere to live, so they go back on paper or into email |
| Spreadsheet or slide on a shared drive, shown on a screen | Free, familiar, anybody can lay it out however the team wants | One person edits at a time, no history of who changed what, and the file quietly becomes the property of whoever set it up |
| Board tool where each item is a card with an owner | Actions carry owners, dates, comments and attachments across shifts; the same items can be read on a wall display and on a phone | Numbers have to be entered by a person unless something feeds them in |
Most working setups end up as a combination of the first and the third rather than a single product. Machine data goes on a dashboard because nobody should type it. Actions, countermeasures, safety observations and anything that needs to survive a shift change go into a board where each one is an item with an owner and a due date.
The second row is where a surprising number of plants actually are, and it is not a foolish place to be. A spreadsheet on a screen is a real improvement on a wiped whiteboard because the previous weeks still exist. What it does not do is make an action findable by the person who owns it, which is the failure that matters most.
In most plants the board is not one board. A line has its own, an area has one that aggregates several lines, and a plant review looks across areas. On paper, each tier is maintained by transcription: somebody copies figures upward and carries decisions downward, usually once a day, usually into a different format.
That transcription is the clearest thing digitising removes. If an escalated item is the same item rather than a copy of it, the line board and the area board show one record, and the question of which version is current disappears. The supervisor who covers four lines reads four boards in the time it used to take to visit one.
The trap is to build the top tier first, because that is the tier a manager asked for. A plant level view assembled from lines that are not maintained is a confident picture of nothing. The order that works is the reverse: get one line's board genuinely current for a month, then add the second, then build the roll up once there is something to roll up.
One more detail matters here. Escalation needs a rule, not a judgement call. Something like a target missed twice in a week, or an action open past its date, moves up a tier automatically. Without a written rule, escalation depends on whoever runs the huddle that morning, and the tier above becomes a filtered view of what people were comfortable reporting.
Software selected from a conference room tends to fail on details that are obvious at the line.
Editing has to take seconds, standing up. A team leader with gloves on, in front of the board, with eleven people waiting, will not navigate three menus. If adding a countermeasure is slower than writing it in marker, marker wins and the digital board becomes a display of last week.
Shared terminals need an answer. One tablet by the line, used by forty people across three shifts, does not work with a personal login per person. Either there is a shared account for the board itself, with named ownership captured on the item rather than by the session, or somebody has to think carefully about how identity works there. This is the single most common reason a pilot dies in month two.
Two screen sizes, one source. The wall display and the phone are the same board. If the tool is only usable on one of them, half the value goes. Being able to read the board from home before a shift starts is what makes handover work.
Network is not guaranteed. Parts of a plant have poor coverage. A tool that shows an error when the connection drops during a huddle will be abandoned after that happens twice in front of the team.
Somebody has to own the layout. A physical board's format is enforced by the lines drawn on it. A digital board has to be configured to keep the same discipline, and if every team leader is free to restructure it, comparing two lines becomes impossible. Deciding the format once and locking it is part of the implementation, not an afterthought.
If only one thing is digitised, it should be this. Numbers on a wall display are the easy half; the actions are where the improvement either happens or does not.
The shape that works is unremarkable. Every action raised at the board becomes an item with an owner, a date and the reason it exists. Items are visible at the board during the huddle and reachable by the owner from a phone afterwards. Anything overdue is visible without anyone compiling a report, because the board itself shows it. A closed item stays searchable, so the fourth time the same fault appears, the previous three countermeasures can be read rather than reinvented.
That is a task board with a discipline applied to it, not a specialist manufacturing product, which is why plants of a certain size get a long way with a general tool. The features that matter are an owner and a date on every item, a comment thread, file attachments for a photo of the defect, and views that let the same items be shown as a board at the line and as a calendar or timeline to whoever is looking across weeks. Tools vary in whether all of that is available without moving up a tier, so it is worth checking which board types and fields a candidate includes and what the price is for the number of people who only read it before running a pilot, since on a factory floor most of the people who need to see the board will never edit it.
The walk itself. A gemba walk is going to the place and looking at the work, and no amount of instrumentation substitutes for that. A tablet with a checklist can record what was seen, but if the checklist becomes the point, the walk turns into data entry and stops surfacing the things nobody thought to ask about.
The handwriting, at first. Teams that keep the whiteboard and add a digital home for actions only tend to succeed more often than teams that remove the board on day one. Run both for a month, then drop whichever half nobody is using.
The judgement about what belongs on the board. Because a screen has no edge, it is tempting to add another metric, then another. The size limit on a whiteboard was a feature. Keeping the digital board to what fits on one screen at reading distance preserves it.
Take the actions off the whiteboard and give each one an owner and a date in something the owner can open from a phone, and leave the numbers exactly where they are for now. That single change is what stops items dying at shift handover, and a general board tool such as Pinateca is enough to do it before any specialist system is considered.
It can, and that is the main risk. If the board is only viewable at desks, the huddle at the line stops happening and the practice decays into reporting. The arrangement that avoids it is a display physically at the workplace, with phone access as a supplement for the owner of an action rather than a replacement for standing there.
Most plants use a fixed format so that boards can be compared, commonly safety, quality, delivery, inventory and productivity, or a local variant of that set. The important part is that each metric has a target, a visible status against it, and a place for the action raised when it is missed. A board with metrics and no actions has nothing to discuss.
Yes, and plenty of plants run this way. It keeps history, which a wiped whiteboard does not, and it costs nothing extra. The limits are that one person edits at a time, there is no reliable record of who changed what, and an action in a spreadsheet cell does not reach the person who owns it. That last point is usually what pushes teams to a board tool.
Carefully, or not at all. A personal login per operator does not work on a device used by three shifts, so most implementations use a single account for the board device and record ownership as a field on each item instead of relying on who is signed in. Deciding this before the pilot avoids the most common reason floor deployments are abandoned.
It depends on whether machine data has to flow in automatically. If the numbers are read from equipment, that is a job for a system built for it. If the numbers are entered by a person during the huddle and the real requirement is that actions survive shift changes, a general board tool with owners, dates and attachments covers it, and is considerably faster to pilot.