EOS Q&A – Volume 2, February 2017

Question:

How and when can departments communicate pertinent information to each other if they have separate L10 meetings?

Answer 1: (From a leader with operations accountability and 2+ years working with EOS)
If something is big enough – or there is concern about it being communicated – we add it to our To-Do list in the executive L10. For example: “Controller will get input from HR on new direct hire policy and report back.”
The “cascading messages” part of the meeting is a good opportunity for these items to come up. We often say, “Hey, can we capture a to-do for that?” as part of our L10 meeting. If you’re disciplined in reviewing the To-Dos every meeting, this should be very successful.

Cascading is another good reason to have a daily ritual of huddles. As a manufacturing company, our teams need to be passing information through our organization daily to ensure clarity and focus shift to shift. If the issue is time sensitive and your team is huddling every day, you have the opportunity to follow-up. Once the structure is in place, people will know it’s going to come up – and they’ll want to have a positive answer.

Answer 2: (From a leader with operations accountability and 3+ years working with EOS)
That is a great question and something we struggled with for some time. We use email to send this out, but considered using our Sharepoint software.

We did an IDS session at the Leadership level since this was affecting multiple departments and we had everyone doing something different. We decided on a solution where a member in each L10 meeting is accountable to scribe and email out a running spreadsheet for all L10 meetings. This sheet has each department accounted for and funnels any cascading messages that are pertinent for other L10 leaders. This is emailed weekly to each team lead from the scribe of that meeting. The idea is the team lead is accountable to address the cascading message for his or her department at their weekly L10. It is the team lead’s responsibility to update any topics that need to be addressed in the IDS or headline section of your L10 meeting. So far this seems to work well for us in cascading important info between teams.

Here is a sample of what this communication would look like from an L10:

  • Engineering Operations
    • No cascading messages this week
  • Leadership
    • No cascading messages this week
  • Office Operations
    • No cascading messages this week
  • Onsite Engineering
    • No cascading messages this week
  • Project Management
    • No cascading messages this week
  • Remote Engineering
    • No cascading messages this week
  • Sales Management
    • No cascading messages this week
  • Technical Services
    • No cascading messages this week