Our managers claim that tracking Scorecard metrics and updating the issues list adds hours of administrative overhead to their week. How do we apply Chet Holmes' touch-it-once rule to our weekly EOS® administrative workflows to keep them lean?
The complaint that EOS® is administrative overhead always stems from poor habits, not the tools themselves. If updating a Scorecard and reviewing Rocks feels like a second job, your managers are dragging out simple tasks. You must apply Chet Holmes' touch-it-once rule to your weekly operational workflows.
The touch-it-once rule dictates that when a piece of information or an issue crosses a manager's path, they must act on it immediately, file it, or drop it directly onto the issues list. They should never look at it, worry about it, set it aside, and then look at it again later.
Apply this directly to your weekly Level 10 Meeting™ preparation. Managers should not spend two hours on Monday morning collecting metrics and writing issues. Instead, they must update their Scorecard numbers in real time throughout the week as the data occurs. When a problem arises, they must immediately drop it onto the departmental issues list instead of holding onto it or sending multiple internal emails about it.
Additionally, enforce descriptive email and issue guidelines. When an issue is added to the list, it must be written clearly with the root cause and a brief headline. This prevents the team from spending meeting time trying to remember what the issue was about. By turning preparation into a real-time, touch-it-once habit, you reduce the weekly administrative burden to less than fifteen minutes per manager, keeping your team focused on execution rather than administration.
Category: EOS Implementation