Show Notes
The daily huddle and the visual management board are two of the most powerful, and most consistently wasted, tools on any operations floor. In this episode of Handled It, Joe Perkins, Brent Hillabrand, Ryan Tiller, and Ashley Watkins break down what separates a 10-minute meeting that transforms a shift from a mandatory gathering everyone dreads and nobody acts on.
From the football scoreboard analogy to why a board loses all its power the moment the data is wrong, the group gets specific on what great actually looks like: short, consistent huddles, associate ownership that drives behavior instead of just tracking it, and the counterintuitive truth that finding more problems means the system is working. Run with discipline, a huddle and a whiteboard become the operating system your floor actually runs on.
In this episode, you will learn:
- Why most shift meetings are expensive, habitual, and pointless- What a great huddle looks like: standing, under 15 minutes, ownership assigned
- Why a board loses all its integrity the moment the data is wrong
- How to run a huddle when you walk into a five-alarm fire
- Why finding more problems means the system is working
- How to hand the board to associates so it drives behavior, not just tracking
- Why "problems are good" and what hiding them really signals
Key Moments:
0:00 — Intro: Your Board is Lying to You
1:09 — Why Shift Meetings Break Down
2:59 — What a Great Huddle Looks Like
4:29 — Keeping the Scoreboard Honest
9:03 — Building Ownership and Accountability
14:45 — Questions That Drive the Right Behavior
19:00 — Handling Chaos and the Five-Alarm Fire
22:29 — From Task to Culture
24:38 — More Problems Isn't a Bad Thing
27:30 — Agree or Disagree Rapid Fire
31:41 — The Rant: Your Board Is Lying to You
Transcript
Daily huddles and visual management boards are two of the most powerful tools available to an operations team. They are also two of the most consistently wasted.
Neither tool requires advanced technology or a significant investment. At their simplest, they require a team, a few intentional questions, and a whiteboard.
But simply gathering employees and displaying numbers does not improve performance.
Without a clear purpose, accurate information, associate ownership, and follow-through, the huddle becomes an expensive ritual. The board becomes something people pass every day without noticing.
When used correctly, however, these tools give teams a shared understanding of where they stand, what is getting in their way, and what they need to do next.
When Meetings Become Rituals
Many daily huddles begin with good intentions.
A leader decides the team should meet before every shift because it is considered an operational best practice. The organization adopts a standard agenda and gathers everyone around a board.
But the team may never define what the meeting is supposed to accomplish.
Over time, the huddle becomes something employees attend because they are expected to, not because it helps them perform their work.
That creates an expensive habit. Multiple employees stop working to attend a meeting that may not produce a decision, resolve an obstacle, or change what happens during the shift.
A productive huddle should not exist simply to communicate information. It should help the team answer:
- What does winning look like today
- What is getting in our way?
- What requires immediate attention
- What are we going to do about it
- Who owns the next action?
If the meeting does not create clarity or action, its purpose needs to be reconsidered.
Focus on Today, Not Just Yesterday
Operational teams need to understand what happened during the previous shift, but a daily huddle should primarily prepare them for what is ahead.
The purpose is not to spend the meeting reliving yesterday’s problems. It is to use what the team learned to make better decisions today.
That means reviewing current production targets, customer expectations, safety concerns, quality issues, delivery requirements, and potential obstacles.
A strong huddle gives employees a clear picture of what good looks like for the shift.
The questions should be consistent. The meeting should begin and end on time. Employees should know what information they need to bring and what decisions need to be made.
That consistency turns the huddle from another meeting into part of the team’s operating rhythm.
The Board Is the Team’s Scoreboard
A visual management board should function like a scoreboard.
Imagine arriving at a football game and seeing that the scoreboard still displays the results from last week. No one would rely on it to understand what is happening in the current game.
The same is true on an operations floor.
A board displaying outdated safety information, old production numbers, incorrect quality data, or the wrong date cannot help employees understand current performance.
The board should allow the team to quickly answer:
- Are we winning or losing today?
- Where are we falling behind?
- What has changed since the last huddle?
- Did we complete what we said we would do?
- Where does the team need help?
The board is not the goal. It is a tool that informs the team’s decisions.
If it cannot accurately show what is happening, it no longer has operational value.
Your Board May Be Lying to You
An outdated board does more than communicate old information.
It signals to employees that the process is no longer important.
Leaders may continue walking past the board without addressing it, but associates notice when the information is weeks or months behind. They notice when the numbers are incorrect and when problems remain posted without any action.
The message becomes clear: leadership does not have time for this, the information does not matter, and employee participation is not important.
That may not be what leaders say, but it is what their actions communicate.
If an organization is not prepared to maintain the board, it may be better to remove it than allow it to become a visible example of inconsistency.
Incorrect Data Destroys Trust
An outdated board is a problem. An inaccurate board can be even more damaging.
When employees know that a defect was assigned to the wrong department, a quality issue was incorrectly categorized, or a production number does not reflect what happened, they begin questioning the entire process.
The board loses integrity.
Associates may stop contributing because they do not trust the information. Instead of creating accountability, the board creates defensiveness.
Accurate data should align with what employees are experiencing on the floor. When the numbers and reality do not match, leaders need to investigate the difference rather than dismiss the employees closest to the work.
A visual management system can only influence behavior when people believe what it is showing them.
Information Without Action Has Little Value
A board should do more than track problems.
Every issue displayed should lead to another question:
“What are we doing about it?”
Recording a recurring defect, supplier problem, missed delivery, or safety concern does not improve performance by itself. The team must determine what action is needed, who owns it, and when the group will revisit it.
Otherwise, the board becomes a place where problems are documented but accepted.
A strong board creates movement:
- Problems become visible.
- Priorities are established.
- Actions are assigned.
- Commitments are reviewed.
- Results are measured.
The board should drive performance, not simply describe it.
Ownership Creates Accountability
Leaders often introduce a new board, select the metrics, update the information, and lead every huddle.
That may be necessary at the beginning.
Teams need to see what a productive huddle looks like. Leaders may need to model how to discuss problems, ask questions, and turn information into action.
But the process should not remain dependent on the manager.
At some point, ownership must shift to the associates closest to the work. Employees can rotate responsibility for updating the board, leading the huddle, reporting results, and following up on commitments.
When associates own the process, the board becomes more relevant because it reflects their work and their challenges.
Ownership creates accountability because people naturally take better care of what they consider theirs.
The goal is not for leaders to disappear. It is for leaders to create a team capable of identifying and solving problems without waiting for management to direct every action.
What Belongs in a Daily Huddle
The exact content will vary by operation, but most huddles should focus on a few essential areas.
The first is employee well-being and safety. Teams should identify not only incidents that occurred, but also situations that could have become incidents.
The goal is to anticipate risk before someone is injured.
Once safety is addressed, the conversation can move toward quality and delivery:
- Are customers receiving what they expected?
- Is the work being completed correctly?
- Are orders being delivered when promised?
- What is preventing the team from meeting those expectations?
- Does the team need to adjust its plan?
The huddle can also begin with a recent win. Teams that only discuss obstacles may begin to view the meeting as a negative or critical experience.
Recognizing progress creates a more balanced conversation and reminds employees that the purpose is not simply to identify what went wrong. It is to help the team succeed.
Keep the Huddle Short and Consistent
A daily huddle should generally take fewer than 15 minutes.
The standing format helps reinforce that expectation. The team is not gathering for a lengthy discussion or a complete root-cause analysis. It is gathering to establish priorities and determine the next action.
When the operation is already facing a major disruption, the huddle may only require five minutes.
But the crisis should not automatically become a reason to cancel it.
When a football team is losing control of a game, it calls a timeout. The team briefly stops, evaluates what is happening, adjusts the plan, and returns to the field with greater clarity.
Operations teams need the same discipline.
Continuing to work inside the chaos without stopping to align will rarely resolve the situation. It may cause mistakes, confusion, and competing priorities to compound.
The more chaotic the shift becomes, the more important it is for the team to understand what matters most.
Prioritizing the Right Problems
Once teams begin identifying problems, they may discover far more than they can address at one time.
Not every issue has the same frequency, urgency, or operational impact.
Teams need a method for determining which problems deserve immediate attention. Tracking recurring issues can help reveal patterns and show which obstacles are creating the greatest disruption.
Some problems may require an immediate stop and response, even if they have only occurred once. Others may need to be documented and placed in a “parking lot” until the team has the capacity to address them.
The parking lot prevents lower-priority issues from disappearing without allowing them to distract the team from its current focus.
The goal is not to solve everything at once. It is to make intentional decisions about what the team will address now and what it will address next.
Huddles Can Break Down Silos
Many operational problems are created upstream but experienced downstream.
One team may live with the same recurring issue for years without realizing another department is contributing to it. The upstream team may have no idea how its process affects the rest of the operation.
Visual management creates shared visibility.
When information moves through different levels of huddles and boards, teams begin recognizing how their decisions affect quality, delivery, production, and customer experience elsewhere.
The conversation shifts from assigning blame to understanding impact.
Instead of saying, “You are the problem,” teams can say, “This is what the operation is experiencing, and this is what the data shows.”
That creates an opportunity for departments to solve problems together.
More Problems Can Mean the System Is Working
Organizations may introduce huddles and visual management, expecting their problems to disappear.
Instead, they often begin finding more.
That can make leaders believe the new process created additional problems. But those issues were usually already present. The organization is simply becoming more aware of them.
Problems may have been hidden, normalized, or accepted as part of the job. Associates may have learned to work around them rather than report them.
In some cultures, employees may even feel rewarded for hiding problems from leadership.
A strong visual management system changes that expectation.
It communicates that identifying a problem is not a failure. It is the first step toward understanding and correcting it.
An operation that reports no problems may not be performing perfectly. It may have created an environment where employees no longer feel comfortable raising them.
Healthy teams make problems visible.
Manual vs. Digital Boards
Organizations are often eager to automate visual management.
Digital dashboards, automated reports, spreadsheets, and live production displays can make information easier to distribute. But automation introduced too early can weaken ownership.
If associates cannot update the system themselves or do not understand where the information comes from, the board becomes something they observe rather than something they manage.
Manual boards can be especially effective while teams are developing the discipline of visual management.
Writing information down, updating results, and physically interacting with the board can strengthen the connection between the associate and the process.
Digital tools may become valuable once the team has established the right habits, ownership, and accountability.
Technology should support the process. It should not be used to avoid building the process.
Stop-the-Line Authority
Associate ownership must include the authority to act when something is wrong.
If an employee identifies a quality issue that could create a poor customer experience, that person should feel empowered to stop the process before the problem leaves the building.
Employees should not be expected to identify problems while being discouraged from responding to them.
That requires a culture where leaders thank associates for raising concerns instead of blaming them for slowing production.
The purpose of the board and huddle is not simply to make leadership more informed. It is to give the people closest to the work the information and authority needed to protect safety, quality, delivery, and the customer.
Final Takeaway
A daily huddle and visual management board should help an operations team understand reality and act on it.
The meeting should be short, consistent, and focused on today. The board should be current, accurate, and connected to the work employees are performing.
Leaders may establish the process, but associates must ultimately help own it.
Most importantly, the organization must create a culture where problems are surfaced rather than hidden. Finding more problems does not necessarily mean the operation is getting worse. It may mean the team is finally seeing clearly enough to improve.
A board that is accurate creates visibility.
A huddle that is intentional creates alignment.
Associate ownership creates accountability.
Together, they become more than a meeting and a whiteboard. They become the operating system the floor actually runs on.