Tips for Generating a Great Issues List | EOS Tips

[@justindomino]

Do issues then either become Rocks or To-Do's? As we establish Rocks for each team member at the beginning of the quarter, doesn't the process of resolving issues just add more Rocks to everyone? If they're small things, they can be added to To-Do lists, but larger issues have to be tackled at the Rock level, correct? I foresee a problem being: each member starting with 4 Rocks, but by the end of the quarter, they have 15 Rocks.

[@trugroupscott]

Hey P - 99% of rocks for my clients come out of our quarterlies. We create an issues list first in the quarterly, review the VTO to generate any other issues, and then do rocks. Remember, the source of Rocks is generally: Goals (1 year), Issues, or Rocks that did not get completed the previous quarter. My teams find that most issues can get solved in an L10 with a good IDS topic and then a To Do(s) assigned to fix the issue. If the issue will take more than a week to solve, the choice is: 1) set the first To Do for the next week and then commit to any follow-up To Do after your report out the next L10 2) Create a Rock that will solve the issue in the next 30-90 days. From the feedback from my clients #2 is rarely used. Does that help? If not shoot me another message or maybe we can do a short call.

[@justindomino]

​@@trugroupscott that's very helpful, thank you! We're in the very beginning stages of Traction and just got through our first Issues List that involved 16 Issues. As we tackled it, some people had a lot of additions to their To-Do's and Rocks, while some didn't. As the Integrator, i'm trying to avoid overwhelming my team, especially in our beginning stages. Choice #1 is a great option.