TL;DR: Lean daily management is the system that makes improvement happen between the projects — visual boards, huddles, gemba walks, leader standard work, and strategy alignment working together. The boards don't do the work. The leadership behaviors do.
Most Lean improvement efforts follow a recognizable pattern. A team runs a kaizen event or maps a value stream. Results improve. People feel energized. And then, gradually, things drift back.
Not all at once — it's rarely dramatic.
The old workarounds return. The new process gets modified by someone who wasn't in the room. Six months later, the gains are mostly gone, and the next improvement project starts from roughly where the last one did.
If that sounds familiar, it's not because your people lack discipline. It's because there's nothing between the projects. No structure for surfacing problems as they emerge. No rhythm that keeps improvement happening on a Tuesday afternoon, not just during a scheduled event. No way for a frontline staff member's observation to reach someone who can actually do something about it.
That gap — between project-based improvement and daily work — is where many Lean efforts quietly stall. Leaders stay busy, but they're reacting to whatever hits them first rather than working on anything systematically. Staff stop raising issues because the last few went nowhere. Strategy lives in a slide deck that nobody on the floor has ever seen.
This is what organizations lose when they don't have a daily management system: not a dramatic failure, but a slow erosion of the gains they worked hard to create — and a growing sense among frontline staff that improvement is something that happens to them, not with them.
Lean daily management is what fills that gap.
What Is Lean Daily Management?
Lean daily management is a structured approach to managing and improving work at every level of an organization, every day. It typically includes several interconnected components:
- Visual boards that display key metrics and the status of improvement efforts
- Daily huddles (brief stand-up meetings) where teams review performance and surface problems
- Leader standard work that defines how leaders spend their time, including gemba walks
- An escalation path (often called tiered huddles) so that problems that can't be solved locally move to the right level quickly
- A connection to strategy deployment (hoshin kanri) so that local improvement aligns with organizational priorities
ThedaCare, a health system in Appleton, Wisconsin, was among the early adopters in healthcare. They defined their “Business Performance System” as interconnected components: daily status sheets, daily huddles, monthly scorecards, monthly performance reviews, A3 thinking and countermeasures, leader standard work, and visual management. The key word there is “interconnected.” Picking one or two components without the others tends to have limited effect or sustainability. And, there's a risk that it goes away when there's a leadership change.
The University of Michigan Health System calls their approach “Lean in Daily Work,” which includes key visual metrics, daily team huddles, daily problem solving through their “Everyday Lean Idea” process, and leadership gemba walks. One of their stated goals is to “redirect reactive firefighting to a systemic, proactive process.” That's a good way to describe the intent.
Visual Boards and Metrics: Making Performance Visible
In many departments, people have no idea how their team is performing in any quantitative way. Metrics either aren't tracked, aren't shared, or are buried in a monthly report that arrives weeks after the fact. When people can't see how things are going, they can't improve how things are going. That's not a motivation problem. It's an information problem.
Lean daily management changes that. Metrics are posted in high-visibility locations where teams can see them during their work — not behind a manager's desk. In a Lean environment, we focus on more than just cost. The mantra is typically SQDCM — safety, quality, delivery, cost, and morale. That order matters. Safety comes first, always. If safety, quality, and delivery are improved, cost tends to follow.
Each metric should come with a brief explanation of why it matters. In one hospital lab I worked with, where teams measured “percentage of tests resulted before 7 a.m.,” the metrics sheet explained: “This is a key measure that physicians use to judge lab effectiveness. Physicians get dissatisfied if results are not on the patient chart when they do morning rounding, and this can delay patient care decisions or discharges.” Even experienced employees often don't fully understand the impact of certain measures on their patients or internal customers. Making that connection visible changes how people relate to the number.
One thing worth flagging: I've seen organizations focus too narrowly on a single dimension. One hospital lab tracked only turnaround time, and after a few weeks an employee asked if management was saying quality didn't matter. Some staff worried that competitive personalities might cut corners to look good on the TAT metric. A balanced set of metrics protects against that kind of dysfunction. The absence of a metric sends a message too.
And a caution about the boards themselves. At ThedaCare, Theresa Moore said the teams had experimented with their “tracking center” board format and that there was “not a published standard.” She explained:
“More important is the coaching approach more so than the board itself.”
I've seen organizations spend a lot of time designing a board that was perfectly identical in each unit, or that literally copied one they saw at ThedaCare. More often than not, those boards end up unused. It would be better to see a board that's slightly different and even messy, as long as it's being used and helping a team improve their performance. A beautiful board that nobody touches is just wallpaper.
Related post: What Is SQDCM? The Lean Framework for Safety, Quality, Delivery, Cost, and Morale
Daily Huddles: Brief, Focused, at the Board
Without a daily huddle, the most common pattern is this: problems accumulate silently, get discussed in hallways or over email (if they get discussed at all), and eventually surface in a monthly meeting where it's too late to do much about them. The huddle exists to shorten that feedback loop from weeks to hours.
Daily huddles are brief stand-up meetings — typically 5 to 10 minutes — held in front of the visual board where metrics, process audits, and improvement ideas are posted. Standing up keeps things short. Staying close to the workspace keeps the team grounded in the real work.
Here's a sample huddle agenda, drawn from what I've seen work well across multiple health systems:
- Safety reminder or review of safety issues and risks
- Immediate problems to be aware of (equipment down, staffing gaps)
- Review of yesterday's metrics and trends
- New employee ideas or suggestions; updates on previous ideas
- Share any positive feedback or recognition
That's it. In 5 to 10 minutes, you can't discuss every issue or do complex problem solving, and you shouldn't try. The intent is quick communication, prioritized around immediate needs. As problems or suggestions come up, they get captured on the board or in a kaizen tracking system for more detailed follow-up later. If six or seven people are in a huddle but only two need to investigate a particular root cause, the full group meeting stays short and those two stay behind.
At New London Medical Center, they experimented with the order and found it was better to start with celebrations rather than ending with them. That's the kind of small adjustment that reflects a team learning what works for them — which is itself a form of kaizen.
One pitfall worth mentioning: at one hospital, managers stopped holding regular huddles because corporate was inadvertently punishing them for it. The time staff spent in huddles was counted against the department's productivity metrics. Managers became reluctant to pull frontline staff away from direct patient care. That's a system problem, not a people problem, and it's the kind of thing that leaders at the next level up need to catch and fix. When your measurement system discourages the very behaviors you're trying to build, the measurement system needs to change.
Related post: Daily Huddle Best Practices in Healthcare: Lessons from the Everett Clinic
Tiered Huddles: Connecting the Frontline to the Organization
One of the most common frustrations in any organization is that problems get documented but don't go anywhere. Frontline staff fill out forms, submit tickets, raise concerns — and nothing happens. After enough repetitions, people stop raising issues altogether. The problem isn't apathy. It's a rational response to a broken escalation path.
At Baylor Scott & White Health, daily huddles take place at every level of the organization, starting with frontline teams and ending with the executive staff. Through these “tiered huddles,” important information about immediate risks or challenges can flow up within a few hours. Important updates can likewise flow back down to frontline staff and middle managers by the next day.
This is what makes lean daily management a system rather than a collection of department-level meetings. Tier 1 is the frontline team huddle. Problems that can be solved locally stay there. Problems that need resources, authority, or cross-departmental coordination escalate to Tier 2 (department or value stream leadership) and, if needed, Tier 3 (senior leadership). The structure ensures that problems don't just get documented — they move to the level where they can actually be resolved.
That escalation path also connects daily management to strategy deployment, or hoshin kanri. Senior leaders set the “true north” direction and high-level objectives. Those cascade down so that each level of the organization has local metrics aligned with the larger goals. Frontline managers and staff in a mature strategy deployment setting can explain how their local metrics contribute to organizational priorities. They can point to specific kaizen efforts that are improving those metrics. That alignment is what turns a huddle from a status update into a vehicle for executing strategy.
At ThedaCare, the true north objectives came from the question “What are the most important problems and opportunities?” and included safety and quality, people, customer satisfaction, and financial stewardship — each with specific high-level measures. A medical-surgical unit might track patient falls as a safety metric, while an outpatient clinic might measure employee strains. Different measures, same direction.
Larry Culp, CEO of GE Aerospace and a deeply committed Lean practitioner, described this connection well. GE's proprietary Lean operating model, which they call FLIGHT DECK, includes standard work, daily and visual management, value stream management, operating cadences, and strategy through hoshin kanri. Culp put it this way:
Hoshin kanri is “the piece of the operating model that allows us to identify, through our strategic planning process, the breakthroughs that we need to strengthen our competitive advantage and then operationalize them… to not only TALK strategy, but to DELIVER it.”
Without that connection, strategy stays abstract. With it, the person drawing blood at 5 a.m. can explain how their work connects to organizational priorities. That's not a small thing.
Related post: How Cleveland Clinic Uses Daily Tiered Huddles to Drive Lean, Accountability, and Learning
Leader Standard Work: Structuring the Leader's Day
Here's a pattern that plays out in a lot of organizations: leaders say they want more improvement, more problem solving, more coaching — but their calendars are full of meetings, emails, and whatever crisis surfaced that morning. They're not opposed to spending time at the gemba. They just never get there.
Leader standard work addresses this directly. It documents what leaders do to ensure their processes run as designed, and then improve them. It doesn't mean a minute-by-minute script. A top leader may have only a quarter of their typical week defined by leader standard work, while vice presidents and directors might have half their time structured, and frontline supervisors really need to have most of their day and week scripted.
Baylor Scott & White has introduced leader standard work through every level, including hospital CEOs. As their system explains:
“After following leader standard work for a few weeks, a subtle shift will occur. You will get your day back… you will have time to lead continuous improvement in your areas… the most important job of a leader.”
Some organizations, including ThedaCare, institute “no meeting zones” for the first two hours of the day, creating protected time for leaders to do structured rounding or gemba walks. Supervisors and leaders carry checklists and standardized work documents that prompt how they spend their time and which questions they ask. Even vice presidents carry a standardized “stat sheet” that reminds them to start team discussions with employee and patient safety, among other standard topics.
As with standardized work for any role, the goal isn't to be restrictive or to reduce leadership to check-the-box activity. Leader standard work provides helpful structure, planning those management tasks that can be standardized while freeing mental bandwidth for times when creativity and judgment are needed. Without it, the urgent always crowds out the important.
Related post: Leader Standard Work Is About Behavior, Not Just Your Calendar
Gemba Walks: Going to See, Not to Judge
A “gemba walk” is the practice of leaders going to the actual place where work happens — the gemba — to observe, ask questions, and engage with teams. The term comes from the Japanese genchi genbutsu, which means “go and see for yourself to thoroughly understand the situation.”
This sounds simple, but the details matter enormously — because a gemba walk done poorly can do more damage than no gemba walk at all. If a leader shows up, asks a question that feels like an interrogation, and then disappears without following up, they've just demonstrated that leadership visits are performative. Staff will learn to manage appearances during the walk and go back to work as soon as it's over.
A gemba walk is not an inspection. It's not an audit designed to catch people doing something wrong. And it's not a casual walk-through where a leader waves hello and goes back to their office. Done right, a gemba walk is a learning activity for the leader and a coaching opportunity for the team.
The questions a leader asks during a gemba walk shape the culture more than any poster or mission statement. Questions like “What's going well?” and “What's getting in the way of your work?” and “What have you improved recently?” signal that leadership is interested in understanding and helping, not judging.
Jeff Liker, who studied Toyota for decades, taught an important principle about gemba walks that I think gets overlooked. At Toyota, he observed, leaders are expected to “not skip hats.” If a senior manager goes to the floor and starts asking a team member detailed questions about why they made a certain decision, they're bypassing the team leader and group leader. They won't have the context those leaders have. They may jump to conclusions. And they unintentionally undermine the authority of the people in between.
As Liker put it, when leaders go to the gemba, the purpose is to observe and reflect, not to be the one solving problems. The senior leader's job is to coach and develop the next level down, who coaches the level below them. It's a bottom-up chain of support, not a top-down chain of command.
Some practical tips I've seen work: If the physical layout puts executive offices far from patient care areas, work to change that — or at least change the routine. Bill Schmidt, CEO of New London Family Medical Center, intentionally parks so that he walks through the emergency department and inpatient units on his way to his office. “Leadership is very visible,” he says.
In the NHS Releasing Time to Care program, the hospital CEO visits each ward on a monthly basis, signing a board to indicate the visit and that the CEO is checking that lower-level leaders have completed their own checks. That creates a visible hierarchy of accountability without micromanagement.
Related post: Gemba Walks, Daily Improvement, and the Leadership Behaviors That Make Kaizen Possible
Daily Kaizen: The Improvement Engine
All of these components — boards, huddles, leader standard work, gemba walks — exist to support one thing: daily problem solving and continuous improvement by the people closest to the work.
Without a daily management system, improvement tends to be episodic. Problems pile up between projects. Good ideas sit in people's heads because there's no mechanism to capture or act on them. Organizations end up dependent on a small group of specialists or consultants to drive change, while the people who know the work best watch from the sidelines.
In a mature lean daily management system, improvement isn't a separate activity. It's embedded in the daily rhythm. A problem surfaces during a huddle. It gets posted on the board. A frontline staff member and their supervisor discuss it, test a change, and document the result. If it works, the standardized work gets updated. If it doesn't, they try something else. That's PDSA at the speed of daily work.
As I wrote about in my kaizen post, the visual tracking boards many organizations use have four columns:
- Done
- New ideas
- To do
- Doing
As people walk by, they read the cards, add their thoughts, or take an idea to their own part of the workplace. Leaders, during their gemba walks, can see whether ideas are being submitted and acted on — or whether they're piling up in the “To do” column, which signals a system problem worth investigating.
The real measure of a lean daily management system isn't how pretty the boards look or how faithfully the huddle agenda is followed. It's whether problems are being identified, escalated when needed, and resolved — and whether frontline staff feel that their ideas and observations matter.
What Makes It Work — and What Makes It Stall
I've seen lean daily management transform how organizations operate, and I've seen it become another set of motions that people go through without much conviction. The difference almost always comes down to a few things.
Leaders who participate, not just sponsor. When a CEO or vice president shows up at a gemba, asks thoughtful questions, and follows up on what they hear, it sends a message that no memo can replicate. When they delegate daily management to the “Lean department,” the message is equally clear.
Coaching over compliance. The purpose of auditing standardized work is not to catch people doing something wrong. Didier Rabino, a HealthEast vice president, described what happens when a kamishibai card turns red because standardized work wasn't being followed: “supportive leadership is provided.” That phrase is worth sitting with. Supportive leadership. Not a write-up. Not a lecture. Organizations that treat daily management as a compliance mechanism tend to get compliance behavior in return — people who perform the motions without the thinking.
Starting with the problem, not the template. Before copying what you see at ThedaCare or Baylor or Virginia Mason, define your own problem statements. ThedaCare defined problems such as “Teams were not positioned to see, prioritize, and pursue thousands of identified improvement opportunities” and “Unit leaders had significant variations in management styles with no structured management reporting system.” Your problems may be different. The system you build should respond to them.
Patience with the messiness. The early months will be imperfect. Huddles will run long. Boards will be half-empty. Some leaders will resist. That's normal. Use PDSA on your own management system — plan your approach, try it, study what's working, and adjust. It would be ironic to roll out a daily management system without applying the improvement principles it's supposed to enable.
Getting Started
If you're considering lean daily management, here's what I'd suggest based on what I've seen work.
Pick one or two areas to pilot. Don't launch across the entire organization at once. Choose areas with willing leaders and frontline teams who are open to trying something new.
Start with the huddle and the board. These are the most visible and immediately practical components. A simple board with SQDCM categories, a huddle agenda, and a place to capture ideas is enough to start. You can refine the board design over time based on what the team actually needs.
Define leader standard work for frontline supervisors first. What should they be checking? When should they be rounding? What questions should they ask? Then build upward through the leadership levels.
Connect to your strategy. Even a simple version of strategy deployment helps. If the organization's priorities are clear — patient safety, employee engagement, financial sustainability — make sure local metrics link to them. People want to know that their daily work connects to something bigger.
And above all, focus on the behaviors, not the artifacts. The boards, the stat sheets, the kamishibai cards — these are useful tools. But the tools don't create the system. The system is what happens when a leader shows up, asks a genuine question, listens to the answer, and helps remove an obstacle.
What has your experience been with daily management systems? I'd be curious to hear what's worked, what hasn't, and what you've learned along the way.
Related Posts:
- Setting Lean Goals That Matter: An Introduction to SQDCM
- What Is Kaizen? Meaning, Principles, and Examples
- Larry Culp's 2024 Letter to Stakeholders and GE Aerospace's FLIGHT DECK
- Engaging Staff as Problem Solvers at Allina Health
Books Referenced:
- Lean Hospitals: Improving Quality, Patient Safety, and Employee Engagement (3rd Edition) by Mark Graban
- Healthcare Kaizen by Mark Graban and Joe Swartz
- The Executive Guide to Healthcare Kaizen by Mark Graban and Joe Swartz
- Measures of Success: React Less, Lead Better, Improve More by Mark Graban
- The Toyota Way by Jeffrey Liker
Frequently Asked Questions About Lean Daily Management
Lean daily management is a structured set of interconnected practices — including visual boards, daily huddles, leader standard work, gemba walks, and escalation through tiered meetings — that help teams manage and improve their work every day. It connects frontline problem-solving to organizational strategy and creates a rhythm where improvement is embedded in daily work rather than limited to periodic projects.
A lean huddle board is a visual display, typically posted in a team's work area, that shows key performance metrics organized around categories like safety, quality, delivery, cost, and morale (SQDCM). It also tracks improvement ideas and their status. Teams gather around the board for brief daily stand-up meetings to review performance, surface problems, and discuss improvement efforts.
Leader standard work documents the recurring activities that leaders at each level should perform to ensure processes run as designed and to support continuous improvement. For frontline supervisors, this might cover most of the day — including gemba walks, process checks, and huddle facilitation. For senior leaders, it might define a quarter of the week. The purpose is to create helpful structure, not a rigid script.
A gemba walk is the practice of leaders going to the place where work actually happens to observe, ask questions, and understand the current situation. The purpose is learning and coaching, not inspecting or judging. Questions like “What's going well?” and “What's getting in the way?” help leaders understand real conditions and support frontline teams in solving problems.
Strategy deployment (hoshin kanri) sets an organization's “true north” direction and high-level objectives. Lean daily management is how those priorities come to life at every level. Through tiered huddles, local team metrics align with organizational goals, and problems that need cross-departmental support escalate upward. The frontline team's daily improvement work becomes the execution mechanism for organizational strategy.
