Issues List Fatigue: Is a long Issues List stalling your Level 10 Meetings?

If your Issues List has grown out of control, you're not alone: EOS® Worldwide calls it "Issues List Fatigue". A healthy leadership team typically carries 10 to 25 issues at any given time. If yours is well above that, it's a sign the list is being used as a wish list rather than a working queue.

A too-long list is not only overwhelming, it's also a distraction. Real transformative issues can get lost in the noise, and smaller operational issues may take precedence because "they're easy." A clean list brings an immediate breath of fresh air into the room, freeing teams to solve root problems rather than manage a spreadsheet. In this guide, you'll learn:

• How to hold an honest, one-hour cleanup with your team
• How to isolate your top three priorities each week
• How to set rhythms that keep your short-term list sharp and actionable

Within the EOS framework, an "issue" isn't merely a negative breakdown or an operational fire: it is simply anything that stands between your company and its long-term vision.

That includes everyday hurdles and friction points, but it also captures promising new ideas, strategic opportunities, and pending decisions that need collective clarity. In a transparent leadership team, the Issues List works as an active holding space where these discussions wait until everyone has the time to address them with full focus.

To keep the team from mixing big-picture strategy with weekly firefighting, EOS draws a clear line between two lists:

• The short-term Issues List: built for your weekly Level 10 Meeting™, it gathers the tactical hurdles, team friction and immediate roadblocks that can (and should) be resolved within the current 90-day window.
• The long-term Issues List: reserved for your Quarterly and Annual planning sessions, it holds broader strategic questions, major structural changes and visionary initiatives that need deep deliberation rather than a quick weekly resolution.

When items reach the floor in a weekly meeting, the team works through them with IDS™ (Identify, Discuss, Solve), a process designed to cut through surface symptoms until the team produces a decisive To-Do with a single owner and a seven-day deadline. For a step-by-step breakdown of that flow, see our complete guide to the EOS IDS process in your L10.

A populated list is a reassuring sign of organizational maturity. The momentum only starts to drag when the team loses sight of the list's role, and what should be an agile, flowing queue slowly turns into a crowded digital attic.

When people care deeply about the business, items enter the system from every direction. Without a shared habit of pruning and filtering, that healthy input gradually builds up into visual noise, usually through three familiar habits.

A shared vocabulary is at the heart of EOS: it removes confusion and keeps everyone working toward the same goal. That doesn't mean every issue gets logged from the 50,000-foot business view. Sales logs that "leads are slow to follow up," Operations notes that "the handoff from sales is messy," and leadership adds that "deals keep dropping out during onboarding." On the screen it looks like three fires to fight, but in reality it's one process breakdown seen from three perspectives.

Issues are sometimes logged as reminders, and straightforward action items sneak into the queue disguised as strategic problems. An item like "call the property manager about lease terms" doesn't need five executive minds debating it for twenty minutes; it doesn't need discussion at all. It needs an owner and a deadline. Leaving these To-Dos on the Issues List means they might get picked because they are easy. It may feel good to mark them off, but they distract from the larger issues that do need a fuller discussion.

Big, open-ended questions often end up stranded on the weekly list. A 60-minute IDS block doesn't have the runway to unpack a major strategic initiative, so the team leaves it untouched and it keeps taking up prime mental space. If an issue is important enough to bring up, isn't a To-Do, and is too big to solve in 60 minutes, it belongs on the Quarterly agenda.

A packed Issues List is actually a good sign: an engaged leadership team that cares about the details and trusts each other enough to point out friction.

The challenge isn't that your team brings up too many topics. It's that an unfiltered list makes it hard to see where the real leverage is when the IDS timer starts. When weeks of quick hallway fixes, duplicate observations from different departments and small operational To-Dos pile up in one place, even the most focused leaders can end up picking the comfortable item rather than the most transformative one.

The fix? Do what EOS does best: IDS it. Dedicate an entire IDS block in your next L10 to cleaning up the list itself. It takes about an hour the first time. After that, keeping it clean takes a couple of minutes each week.

Start by reading the whole list out loud without stopping to solve anything. As you listen, group items that stem from the same root friction and replace them with one clear problem statement. Instead of carrying three separate complaints from Sales, Ops and Leadership, consolidate them into one line: "The sales-to-operations handoff lacks a clear process owner." This step alone often cuts an overwhelming list by nearly a third.

For every lingering item, run a simple test: "If this vanished from the screen right now, would anyone genuinely push to bring it back?" If the honest answer is no, give yourselves permission to drop it. Priorities shift quickly, and trusting that genuinely critical challenges will resurface takes away the anxiety of letting minor items go.

Filter out the entries that are tasks masquerading as discussions. If an item only needs one person to take one action (like approving an invoice or calling a vendor), it doesn't need team debate. Give it an owner and a seven-day due date, move it to your weekly To-Do List, and clear it off the Issues List.

Look at each remaining item through a 90-day lens. A major software migration, a new office location or next year's hiring strategy can't be unpacked in a weekly IDS block. Move these broader topics to your long-term Issues List so they get the deep, uninterrupted focus they deserve at your next Quarterly. For a blueprint, see our guide to preparing and running an effective EOS Quarterly meeting.

Vague, one-word topics like "Hiring" or "Website" slow the room down, because the team first has to work out what the topic actually is. Rewrite each remaining item as a specific sentence with the name of the person who raised it. For example: "Mark: Inbound website leads are failing to sync into the CRM." When the friction is obvious, the room can go straight to solving it.

By the end of the hour, your short-term list should settle into a focused queue of roughly five to a dozen meaningful items that the whole room can scan in under a minute.

A clean list is only half of the fix. The other half is how the team uses it in the meeting.

When the L10 reaches IDS, the team reads the list quickly and picks the three most important issues. Not the easiest, not the newest: the most important. Number them one, two and three, and start with number one.

Solve one issue completely before you move to the next. If the team solves all three, pick the next three. If time runs out after one, that's fine. Solving the most important issue is a better use of the hour than touching five issues and solving none.

A few questions help the team choose:

• Which issue, if solved, would make the most other issues go away?
• Which issue is blocking a Rock or a number on the Scorecard?
• Which issue have we been avoiding?

The last question is the uncomfortable one, and it is often where the most value is. If the same issue keeps being skipped week after week, that is a signal it needs to be number one.

For the full meeting structure and timing, our guide on how to run a Level 10 Meeting (L10) that actually works walks through each section.

Here is what a cleanup can look like for a 40-person services company. Before, the leadership team's short-term list had 23 items. Some of them:

• "Hiring"
• "Project managers are overloaded"
• "Too many projects running late"
• "Clients complain about missed deadlines"
• "Call the accountant about Q3 numbers"
• "Should we add a second office?"
• "New CRM?"
• "Website contact form leads not reaching sales"

After the cleanup:

• Merged: "Project managers are overloaded," "Too many projects running late" and "Clients complain about missed deadlines" became one issue: "Project load per PM is too high to deliver on time."
• Converted to a To-Do: "Call the accountant about Q3 numbers" went to the finance lead's To-Do List.
• Moved to long-term: "Should we add a second office?" and "New CRM?" went to the Quarterly.
• Rewritten: "Hiring" became "No plan to fill the open senior designer seat," which ties it to the Accountability Chart.
• Dropped: four items nobody could explain anymore.

The short-term list ended with nine items. The next L10 solved the project load issue first, and two other items on the list turned out to be symptoms of it.

The same pattern works for other teams:

• A sales team might merge "low close rate," "long sales cycle" and "pricing objections" into one issue about the discovery call, and move "should we sell in a new region?" to long-term.
• An operations team might turn "order the new scanners" into a To-Do and rewrite "warehouse" as "picking errors on the late shift are above target."
• A small business of 10 people often finds that half its list is To-Dos, because the owner uses the Issues List as a personal reminder list.

In Success.co, short-term and long-term issues live on separate tabs, both on the Issues page and inside the L10 meeting itself. That separation mirrors the EOS distinction between the weekly L10 Issues List and the V/TO™ Issues List, so the weekly IDS block stays focused on tactical problems while strategic conversations wait on the Long term tab until the Quarterly.

When you open an issue, you can switch its type from Short term to Long term with a single click, which is exactly what step 4 of this cleanup asks you to do. Issues that belong on the V/TO move over without being lost, and they also appear in the Long-term Issues section of your V/TO page.

When IDS produces an action, you can add a To-Do straight from the issue: it gets an owner and shows up in the next L10's To-Do review. That closes the loop that usually makes lists grow: the issue comes off the list, and the action is tracked where the team already looks every week.

Every issue also has an activity log showing who created it and when, so during a cleanup, items that have sat untouched for weeks are easy to spot and either solve, move or drop.