Physical improvement boards work. That's the starting point of this session, not its rejection.
A well-designed huddle board with the right team gathered around it remains one of the most powerful artifacts in continuous improvement. Visual management is foundational to Lean, and the daily practice of a team aligning around a physical board has been producing results for decades.
The question this webinar asks is what happens when that practice runs into scale. When the team is distributed across multiple sites. When improvements that worked in one department need to spread to twenty others. When a continuous improvement coach is responsible for supporting ninety boards and can only physically visit two per day. When the board is in one room, the people who need to see it are in another room, and the person who could improve it is in another time zone.
Mark Graban and Greg Jacobson walk through what physical boards do well, where they hit structural limitations, and what changes when visual management moves to digital infrastructure. The argument isn't that digital boards replace the Lean practices that physical boards support. The argument is that digital infrastructure removes the constraints that physical media impose, so the practices can scale.
Mark Graban is Senior Advisor at KaiNexus and the author of Lean Hospitals, Healthcare Kaizen, and The Mistakes That Make Us. Greg Jacobson, MD is co-founder and CEO of KaiNexus and a practicing emergency physician.
Before getting to where boards struggle, it's worth being explicit about what they do well -- because the goal isn't to abandon what works.
A huddle board in a hospital unit shows the team's staffing, census, safety concerns, and improvement work for the day. The team stands at the board for ten minutes, reviews the metrics, surfaces issues, and walks away aligned. The board is the anchor for a daily practice that's been refined across thousands of organizations.
A metrics board with red-yellow-green color coding shows performance against target at a glance. A status board in a manufacturing cell shows production goals and current state. A kaizen board shows ideas in different stages of evaluation and implementation. An SQDC board (Safety, Quality, Delivery, Cost) gives leaders and frontline staff a shared frame for reviewing performance.
Toyota's term for these boards is FMDS -- Floor Management Development System. The name is worth noticing. The purpose of the board isn't just to drive results. It's also to develop managers and staff. The visual artifact creates the occasion for the leadership behaviors -- the questions, the coaching, the problem-solving conversations -- that develop people over time.
This is what physical boards do well: they create alignment, they make problems visible, they anchor daily practices, and they develop the people who use them. None of this is going away. The question is what happens at the boundaries -- when the board needs to be visible to people who can't physically stand in front of it, when the work needs to scale beyond what one team can see, when the improvements need to travel.
Mark works through several patterns where physical boards run into limitations that aren't easily solved within the physical medium.
The cluttered bulletin board. A board that started as a useful artifact becomes corporate wallpaper over time. New announcements pile on top of old ones. Nothing gets taken down. By the time anyone needs the urgent information, it's buried under months of accumulated content. This is a failure mode of any board that doesn't have a discipline around what stays and what leaves.
The empty showcase board. The opposite failure mode. An organization visits a Lean leader (often a healthcare system that's traveled the journey), comes back, copies the board format exactly, hangs it on a wall, and never populates it. The board is pristine. It's also useless. The board itself was never the point. The methodology and the leadership behaviors that produce the board's contents are the point. Without them, the board is an empty container.
The visibility ceiling. A physical board can only be seen by people who can physically be near it. For a single-team huddle in a single location, this is fine. For an organization with multiple departments, multiple sites, or multiple time zones, the constraint becomes binding. A manager responsible for two facilities can't be at both boards simultaneously. A continuous improvement coach responsible for ninety boards across an enterprise can visit a handful per day at most. The work happening on those boards is invisible to anyone who can't be physically present.
The duplication tax. When the same improvement affects three departments, the team running the work has to update three different physical boards. The information lives in three places, gets maintained by three different people, and inevitably falls out of sync. The duplication tax is silent but expensive.
The history problem. When an improvement is completed and moved off the board, where does it go? In practice, it usually goes into a folder that nobody ever opens again. The institutional learning that the completed improvement represents -- what was tried, what worked, what the team learned -- is functionally lost. The next team that encounters the same problem starts from scratch.
The Kaizen motion waste. Greg's observation lands sharply: when the only place to capture an idea is a physical board in a specific location, the people whose ideas matter most often don't capture them. The ideas occur in the cafeteria, the parking lot, the drive home. By the time the person is near the board again, the idea is gone. The improvement opportunities that physical boards don't capture are silent losses -- never visible because they never made it to the artifact.
Space constraints. A physical board can only display so many improvements before it becomes unreadable. An active department running fifty improvements at any given time can't fit them all on one wall. Teams that want comprehensive visibility into their improvement portfolio run out of physical real estate before they run out of work to track.
Greg organizes the digital board case around five categories. The structure is useful because it separates the different benefits rather than treating "digital" as a single undifferentiated upgrade.
Collaboration. The most visible change. When boards are digital, teams that can't physically stand in front of the same wall can still align around the same artifact. A team distributed across three cities can review the same board in real time. An international company with operations on different continents can coordinate improvement work across time zones. A practicing physician finishing a shift at 3am can review and update the board before signing out.
This isn't a substitute for face-to-face problem-solving. Greg is explicit that going to the gemba and working through problems in person remains the gold standard. The digital board augments that practice -- bringing into the conversation the people who couldn't otherwise have been part of it, without displacing the work that genuinely benefits from being done together in person.
The reframe Mark offers: twenty years ago in manufacturing, his world was limited to the people he could walk to. There was no email, no public internet, no way to learn from peers at other facilities. Today, the expectation is that professional collaboration crosses geographic boundaries by default. The visual management practices that emerged in that earlier era can usefully evolve to match the connectivity that the rest of work has already adopted.
Standardization. When boards are templated digitally, the cognitive load of designing each new board is dramatically reduced. A new department adopting visual management doesn't have to spend weeks debating layout, sizing, color choices, and content categories. The standard formats are available. The team picks the one that fits their workflow and starts.
Standardization in this context doesn't mean uniformity. Greg shows examples of three boards that share underlying structure but are customized for their specific workflows. The standard provides scaffolding. The customization happens within it. Teams aren't forced into identical boards -- they're freed from rebuilding the wheel every time they want a new board.
The contrast with the physical equivalent is worth naming. Greg recalls customers who spent six months designing a board, then ordered two hundred of them at $100,000, then couldn't change the design afterward because the cost of redoing the print run was prohibitive. The physical artifact locks in design decisions in ways that the digital equivalent doesn't.
Visibility. The category Greg places at the center of the framework because it's the most fundamental. If you can't see a board, the board can't help you. A board hidden in a back conference room serves no one beyond the people who happen to walk past it.
What digital infrastructure enables is the ability to see every board across the organization at any time. A leader responsible for a region can look at every department's huddle board in their territory. A CI coach can scan ninety boards in a morning, identify the three that need their attention today, and spend their time on the highest-leverage coaching opportunity. A new manager joining the organization can see what active improvement work is happening everywhere, not just in their immediate area.
This level of visibility is structurally impossible with physical boards. It's not that the visibility is somewhat better -- it's that the relationship between observer and artifact changes entirely.
Impact. Greg's framing is sharp: the impact of improvement work should be front and center, not buried in a quarterly report. The reason most organizations struggle to articulate the impact of their CI program is that the administrative burden of aggregating impact data manually is too high. The CI coach who tries to roll up impact across thirty departments using spreadsheets and email finds that the work takes longer than the next monthly cycle allows, so it doesn't get done -- or it gets done with significant lag and questionable accuracy.
When the work happens in a platform that captures impact automatically, the aggregation is a side effect rather than a separate activity. Total impact across the organization, impact by department, impact by category, impact over time -- all of it is available without anyone having to assemble it.
The basketball analogy Greg uses is useful. Watching a basketball game without seeing the score is a completely different experience than watching one where the score is visible. Improvement work without visible impact tracking is structurally similar -- the same activity, much harder to engage with because the consequences aren't visible.
Knowledge repository. The final and probably most underappreciated benefit. When completed improvements live in a searchable digital system rather than in folders, they become a permanent institutional asset.
The example Greg uses: a team about to start work on a problem can search the platform for the term "PowerPoint presentation" and see every improvement ever attempted on related issues, in any department, anywhere in the organization. The platform also surfaces duplicate work in progress -- when someone starts entering an improvement, the system shows related improvements already underway, so the new team can join the existing effort rather than running a parallel one.
This isn't just convenience. It changes the cost structure of organizational learning. The institutional memory that physical-board organizations lose every time a completed improvement is filed away becomes a permanent resource that compounds over time.
Greg is explicit on this point and it's worth amplifying. The digital board isn't replacing Lean behaviors. It's removing the constraints that prevent Lean behaviors from scaling.
Teams still huddle. The huddle happens around a screen instead of a paper artifact, but the practice -- the daily review, the discussion, the surfacing of issues, the coaching conversation -- is the same.
Leaders still go to the gemba. Walking the floor, talking to frontline staff, observing the work firsthand -- none of this is displaced by digital infrastructure. If anything, the digital boards make leaders' time at the gemba more productive, because they can prepare for the visit by reviewing what's been happening and arrive informed rather than blank.
Improvements still follow PDSA cycles. The methodology is the methodology, regardless of whether the cycle is documented on paper or in a platform.
Coaches still coach. The leader-coaches-frontline relationship that's central to Lean culture is supported by digital boards, not replaced. The coach can see more of what's happening, but the coaching conversation still happens person-to-person.
The change is in what scales. Lean practices that work beautifully for one team in one room can now work across distributed organizations without losing the visibility, alignment, and institutional memory that physical artifacts couldn't carry.
A few specific patterns from the session are worth pulling out because they're immediately useful.
Boards on big screens. The most common question about digital boards is whether they sacrifice the always-visible character of physical boards. The practical answer is that customers project digital boards onto wall-mounted flat-screen TVs or use inexpensive devices like a Chromecast plugged into a large display. The boards live on the wall the same way physical boards do, with the added benefits of being updatable, searchable, and shareable.
Default board per user. Different roles need to see different things first. A frontline employee defaults to their team's huddle board. A mid-level manager defaults to their department dashboard. A CI coach defaults to a view that surfaces bottlenecks across the boards they support. A senior leader defaults to a strategy deployment view. The same underlying system serves all four through configurable defaults.
Bottleneck boards. A CI team responsible for fifty departments needs a way to see where improvement work is stalled across all of them simultaneously. Bottleneck boards filter for improvements that have been in a particular status too long -- in "new" for more than 72 hours, in "approval pending" for more than seven days, overdue by more than thirty days. The coach reviews the bottleneck board, sees where leadership attention is most needed, and goes to those specific places to coach. The work of finding the bottlenecks moves from manual investigation to automated surfacing.
Wallboard mode for huddles. When a team is huddling at a screen, the board switches into wallboard mode -- a clean display optimized for group viewing. When the huddle ends, the board switches back to interactive mode so anyone can update it. The same underlying board serves both display and interaction purposes.
Embedded media. Digital boards can include content that paper can't. A team announcement board can embed a video. A strategy deployment board can include linked references to source documents. An idea board can include images of the current state alongside the description of the problem.
This session is unusually direct about platform capabilities because the topic itself is digital infrastructure. A few elements are worth naming explicitly.
The board configuration system supports any of the major board types -- huddle boards, metric boards, kaizen boards, strategy deployment boards, announcement boards, bottleneck boards -- with the same underlying architecture. Teams pick the columns and cards that fit their workflow. The cards can be lists of improvements, charts, reports, custom content blocks, or X-matrix views.
The reporting library aggregates impact, engagement, and activity across all the boards in the organization. The reports that show up on individual boards pull from the same underlying data that drives organization-wide rollups. The CI coach reviewing a bottleneck board sees the same data the CEO sees in the executive dashboard -- just filtered and displayed differently for the audience.
The notification and workflow system routes improvement work between collaborators automatically. When an improvement affects three departments, all three are notified, all three see the work on their boards, and all three see updates in real time. The duplication tax that physical boards impose disappears.
The search and knowledge repository functionality makes completed improvements permanently discoverable across the organization. A team starting work on a problem can find every related improvement ever attempted, anywhere in the organization, in seconds.
The cross-board visibility lets leaders, coaches, and managers see every board they're authorized to see from a single interface. The choice of which board to focus on becomes the leader's decision rather than a function of where they happen to be physically standing.
None of this substitutes for the leadership practices and Lean disciplines that produce real improvement. The platform amplifies the practice; it doesn't replace it. But for organizations whose improvement work has outgrown what physical infrastructure can support, the digital equivalent removes the constraints without sacrificing what physical boards do well.
Mark Graban is Senior Advisor at KaiNexus and a recognized voice in Lean management and continuous improvement. He is the author of Lean Hospitals, co-author of Healthcare Kaizen, and author of The Mistakes That Make Us. Mark has worked with organizations across healthcare, manufacturing, and service industries to build cultures of continuous improvement grounded in respect for people.
Greg Jacobson, MD is co-founder and CEO of KaiNexus and a practicing emergency physician. Inspired by Kaizen principles in his clinical work, he founded KaiNexus to help organizations engage frontline staff in meaningful improvement and to scale continuous improvement through digital infrastructure.
Do digital improvement boards replace physical huddles and gemba walks?
No. Digital boards remove the constraints that physical media impose on visual management, but they don't replace the underlying Lean practices. Teams still huddle. Leaders still go to the gemba. Coaches still coach. The huddle happens around a screen instead of a paper artifact, but the practice -- the daily review, the discussion, the surfacing of issues, the coaching conversation -- is the same. What changes is what scales: practices that work beautifully for one team in one room can now work across distributed organizations without losing the visibility and alignment that physical artifacts couldn't carry.
What problems do digital boards solve that physical boards can't?
Several structural limitations of physical media. Visibility across multiple sites or time zones -- a physical board can only be seen by people physically near it. Collaboration across departments on improvements that affect multiple teams. The duplication tax of maintaining the same information in three places. The history problem of completed improvements disappearing into folders that nobody opens again. The Kaizen motion waste of ideas that don't get captured because the person isn't near a board when they have the idea. Space constraints that limit how many active improvements can be displayed at once. None of these are failures of the physical board itself -- they're limits of the medium that digital infrastructure can move past.
How do digital boards stay visible without forcing people to log in?
Most organizations using digital boards display them on wall-mounted flat-screen TVs or projector setups in the same locations where physical boards used to live. Inexpensive devices like a Chromecast can turn any television into an internet-connected display running the board software. The board stays visible the same way physical boards do, with the added benefit that the content updates automatically and the display can switch to interactive mode during huddles.
What is a "bottleneck board" and why does it matter?
A board that surfaces improvements stuck in any particular status across the organization. The CI coach responsible for fifty departments needs to see where work is stalled across all of them simultaneously -- improvements that have been in "new" for more than 72 hours, in "approval pending" for more than a week, overdue by more than thirty days. Without an automated view, finding the bottlenecks requires manual investigation across every department, which doesn't scale. The bottleneck board surfaces the patterns automatically so the coach can spend their time on the highest-leverage coaching opportunities rather than on hunting for problems.
How does a digital board help share improvements across departments and sites?
Through visibility, search, and notification. When an improvement is completed, it's visible to every other team in the organization that has access to that part of the system. Teams searching for solutions to similar problems find the original improvement automatically. Notifications can route relevant work to leaders in other departments who might benefit. The result is that successful improvements travel through the organization rather than staying local. A health system with ten hospitals can find that an improvement worth $85,000 at one site multiplies to over $700,000 in cumulative impact when the other nine hospitals adopt it -- but only if the other nine know it exists. Digital boards make that visibility automatic.
What changes about the role of the continuous improvement coach when boards go digital?
The work shifts from administrative coordination to higher-leverage coaching. A coach responsible for ninety boards across an enterprise can scan all of them digitally in a morning, identify the handful that need attention today, and spend the rest of the day on substantive coaching at those boards. The alternative -- physically visiting two boards a day, four days a week -- means most boards never get coaching attention, and the boards that do get attention often don't need it as urgently as the ones the coach didn't reach. The digital infrastructure makes the coach's time productive rather than absorbed by the logistics of finding problems to coach.
.svg)
Copyright © 2026
Privacy Policy