We have a leadership team member who brings the exact same operational issue back to our Level 10 Meeting Issues List week after week, even though the team already debated and solved it. They keep resurrecting it because they do not agree with the majority decision. How do we prevent this issue recycling and make our weekly decisions stick?

Question

Tyler Smith · Accepted Answer

When a leadership team member continuously resurrects an issue that has already been solved, it is a clear sign of a deeper alignment problem. This behavior typically means the team member did not actually buy into the decided solution during the original IDS segment, or they are practicing passive resistance. It drains your team's energy and grinds your operational momentum to a halt.

To fix this, you must enforce the EOS rule of agree and commit. During the original IDS discussion, every team member has the opportunity to voice their perspective, debate the options, and push back. However, once a decision is made, everyone must align and support the execution.

The next time this recycled issue is added to the list, the facilitator must address it immediately during the prioritization phase.
- State clearly that this issue was solved on a previous date and read the recorded solution from your meeting archives.
- Ask the team member if there is genuinely new, critical information that was unavailable during the original discussion.
- If no new information exists, remove the item from the list immediately and refuse to open it for debate.

If the team member still refuses to execute, this is no longer an operational issue; it is a people issue. You must address this offline as a GWC or core values misalignment. Your weekly meeting cannot be held hostage by a leader who refuses to align with the collective decisions of the leadership team.