by , on 06 Sep 2010 01:07 pm

Daily Huddles

Popularity: 100% [?]

As and organization transitions to a Lean management system many of existing structures and practices change. Teams and individuals begin to work together in new, more disciplined and more effective ways. One of the most important changes early on in the transformation is the requirement that team member participate in a Daily Huddle. Having a Daily Huddle is a simple change, but for manage teams and managers it a profound change. Many of these team members have never been asked to do more then their daily work activities and many of these managers have never been asked to lead their team in daily improvement. Thus the Daily Huddle represents a new way of working which like all changes can be difficult to get started.


A Daily Huddle is time each day that the team comes together to work through the PDCA cycle. The team discusses the plan for the day and makes sure everyone is on the same page. Additionally the team checks the results from the previous day/week/month and problem solves what can be done more effectively. Finally, it is a chance for the team to make adjustments and improvements to their daily work practices including training on new processes, etc

When teams first get started Dailey Huddles are often awkward and teams don’t know what to do. My experience shows it often takes several months for teams to get engaged. The good news is that over time teams learn to become reliant on Huddles and most would tell you it is time well spent.

Below are a couple of tips to consider when you first get started:

  •  Make sure that the huddle topics are relevant to the team. This means that most of what is discussed needs to relate to the daily work. For example: who is here today, who called in sick, what is our expected demand, what problems came up yesterday, etc. Often managers spent too much time talking about improvement projects and teams lose interest.
  •  Reviewing visual systems is an important part of an effective Huddle. Often early on in the Lean transformation teams done have robust visual systems. Don’t dismay, having the huddle will provide a context for getting the team to take ownership for Visual Systems. Ask them what information they need to know to manage day to day and then incrementally improve the visuals.  
  • Keep the Huddles going, even if it is really busy. Often I see managers put a hold on Huddles when it gets busy. This sends a wrong message to the team. In fact, the busiest days should be the days that Huddles are the most important.  
  • Finally, as team members to rotate responsibility for leading the Huddle. It should not always fall to the manager. This helps teams begin to self manage.


Popularity: 100% [?]

4 Responses to “Daily Huddles”

  1. on 06 Sep 2010 at 4:30 pm 1.Wellesley Chapman said …

    Yes! Prior to starting huddles, our teams did not see the value, but now depend on them to help the day go smoothly. One area we’ve struggled with is bringing improvement work into this daily discussion. Teams prefer a longer format and tend to batch this work for weekly meetings. I suspect this is because we haven’t broken change into “bite size” pieces. Once we learn to think smaller, thinking daily will be easier. Stewarding this change in perspective is my job. I’m on it, and advice is welcome!

  2. on 08 Sep 2010 at 6:47 am 2.Mark Graban said …

    Thanks for sharing – I agree the meetings should be relevant and not led by a manager. Good points…. and the meeting should be short. Do you limit yours to 5 or 10 minutes?

    I’m curious – do you start each meeting with a safety discussion? This seems to be a a good habit that many factories embrace, in part of building a safety culture:

  3. on 12 Sep 2010 at 4:10 pm 3.Lee Fried said …

    Hi Mark,

    Thanks for the comment.

    Most of our huddles are between 5-10 minutes, although they can be longer if the team is doing some training like a new one point lesson.

    Its interesting that you brought up the idea of having a safety discussion at each huddle since we discussed this just last week at our Group Practice leadership meeting. Currently, we don’t currently have an organizational standard, but it would be a great improvement in my opinion.

    take care,


  4. on 17 Sep 2010 at 5:53 pm 4.Jason Yip said …

    More for the software development context but I wrote this a while back:

Trackback This Post | Subscribe to the comments through RSS Feed

Leave a Reply