🔍Issues List

Solve Problems Systematically
Before They Become Crises

Stop letting problems fester. GoalCadence's Issues List helps you identify, prioritize, and solve problems systematically with your team.

Issues List (IDS)

12 Open
Customer support response time
Process•Sarah•in-progress
high
Sales pipeline conversion dropping
Sales•Jane•open
high
Office space for growth
Operations•Mike•researching
medium
Product roadmap alignment
Product•John•open
medium
Team communication gaps
People•HR•open
low
Next IDS Session: Tomorrow 2 PM
📋

Capture Everything

Never lose track of issues that need attention

🎯

Prioritize Smartly

Focus on what matters most for your business

✅

Solve & Track

Assign owners and track resolution progress

Everything You Need for Your Issues List

GoalCadence combines proven Issues List methodology with modern technology to help you solve problems systematically.

Issue Tracking

Capture and categorize issues as they arise. Never let important problems slip through the cracks.

Priority Management

Rank issues by impact and urgency. Focus your team's energy on what matters most.

Root Cause Analysis

Use proven frameworks to identify the real cause of problems, not just the symptoms.

Action Planning

Create clear action plans with owners, deadlines, and success metrics for each issue.

Team Collaboration

Enable team members to contribute to issue resolution with comments and updates.

Resolution Tracking

Monitor progress and celebrate wins as issues are resolved. Keep your team motivated.

How to Use the Issues List

Follow these proven steps to identify, prioritize, and solve problems systematically.

1

Identify Issues

Capture issues as they arise. Don't try to solve them immediately - just get them on the list.

GoalCadence Enhancement:

Quick issue capture with templates and categorization tools.

2

Prioritize Issues

Rank issues by impact and urgency. Focus on the most important problems that affect your business.

GoalCadence Enhancement:

AI-powered prioritization and impact assessment tools.

3

Analyze Root Cause

Use the "5 Whys" or other frameworks to identify the real cause, not just the symptoms.

GoalCadence Enhancement:

Guided root cause analysis with proven frameworks.

4

Create Action Plan

Develop specific, measurable actions with clear owners and deadlines to resolve the issue.

GoalCadence Enhancement:

Action plan templates and automated deadline tracking.

5

Execute and Monitor

Take action and track progress. Update the team on status and celebrate wins as issues are resolved.

GoalCadence Enhancement:

Progress tracking and automated status updates.

6

Review and Learn

After resolution, review what worked and what didn't. Document lessons learned for future issues.

GoalCadence Enhancement:

Knowledge capture and learning documentation tools.

💡Pro Tip: Review your Issues List weekly in structured meetings

The best teams solve problems systematically. Regular review keeps issues from becoming crises and builds a culture of continuous improvement.

What the Issues List is and why it matters

In EOS®, an issue is anything that stands between your team and its goals: a problem, an obstacle, an idea, an opportunity, or simply something that needs a decision. The Issues List is where those things are written down so they can be dealt with on purpose instead of nagging at people in hallways and inboxes.

The idea sounds simple, and it is. The value comes from the habit it creates. When every leader knows there is one trusted place to put an issue, and that issues on that list really do get solved, people stop carrying problems around in their heads. They stop raising them at random moments, and they stop letting them fester because there never seems to be a good time to bring them up.

EOS treats issues as a normal and healthy part of running a business. A long list is not a sign of failure. It usually means people feel safe saying what is wrong, which is exactly what you want.

The two kinds of issues lists

EOS uses issues lists at two time horizons, and keeping them separate is one of the most useful things a team can do.

Weekly (short-term) issues listLong-term Issues List
Time horizonCan be solved within the next week or soNeeds to be addressed this quarter or later
Where it is workedIDS in the weekly Level 10 Meeting™Quarterly and annual planning sessions
Typical examplesA late customer delivery, a vacant role causing overload, a pricing exceptionEntering a new market, restructuring a department, replacing a core system
Who maintains itThe team that runs that weekly meetingThe leadership team

If a long-term issue is crowding the weekly list, move it to the long-term list. If a long-term issue becomes urgent, pull it onto the weekly list. Departments that run their own Level 10 Meetings keep their own weekly issues lists, and an issue can move between a department and the leadership team when it belongs to the other group.

How to build and maintain your Issues List

Step 1: Capture issues as they arise

Anyone on the team can add an issue at any time. Write each one as a short phrase, just enough for the person who raised it to remember what they meant. "Client X renewal" or "Ops overtime" is plenty. Do not try to solve it while capturing it. Getting it on the list is the whole job at this stage.

Step 2: Give each issue an owner

The owner is usually the person who raised it. When the issue comes up in IDS, that person is the one who states it clearly and confirms when the team has reached a solution. Ownership keeps issues from becoming everyone's problem and therefore no one's.

Step 3: Prioritize before you solve

At the start of IDS, scan the whole list and pick the three most important issues. Some teams number them 1, 2, and 3 as a group. Do not start with whatever is at the top, the newest item, or the easiest one. The question to ask is "If we solved only one of these today, which would matter most?"

Step 4: Work each issue through IDS

IDS stands for Identify, Discuss, Solve.

  1. Identify. The owner states the issue in a sentence or two. The team asks questions until the root cause is clear. Simple techniques like asking "why" several times help separate symptoms from causes.
  2. Discuss. Everyone shares their view once. The facilitator watches for repetition and moves the team toward a solution.
  3. Solve. The team agrees on the resolution and captures any follow-up as a To-Do with one owner and a due date. Then the issue comes off the list.

Step 5: Clean the list regularly

Issues that are solved should be removed. Issues that solved themselves, or no longer matter, should be removed too. A list full of stale items makes it harder to spot what is important, and people lose trust in it.

A hypothetical example

Imagine a 40-person services firm. During the weekly Scorecard review, the operations leader reports that project margin has been off track for three weeks. Instead of debating it on the spot, she drops "Project margin" onto the weekly issues list.

In IDS, the team picks it as the top issue. Through a few questions, they learn that the real cause is not pricing, as several people assumed, but scope changes that are being accepted without a change order. The discussion surfaces two options and the team agrees on one. The solve is a To-Do for the operations leader to roll out a simple change-order step with the account managers by next week's meeting. The issue comes off the list. If margin stays off track, it will come back as a new issue with better information.

Common mistakes and how to fix them

Solving issues the moment they are raised. It feels efficient, but it skips prioritization and usually means the loudest topic wins. Fix: capture first, prioritize second, solve third.

Discussing without solving. A good conversation that ends without a decision leaves the issue on the list forever. Fix: before moving on, ask "What is the solution, and who owns the To-Do?"

Tangents. One issue reveals three more, and the conversation wanders. Fix: put each new issue on the list and stay on the one you are solving.

Mixing time horizons. Strategic questions clog the weekly list and push out problems that could be solved today. Fix: move them to the long-term Issues List for the next quarterly session.

Avoiding hard issues. People issues and tension between leaders are often left off the list because they feel uncomfortable. Fix: build the expectation that any issue can go on the list, and that the team's job is to be open and honest about it.

Never cleaning the list. Old issues pile up until the list stops being useful. Fix: during each quarterly session, review the long-term list item by item and remove anything that is solved or no longer relevant.

How the Issues List connects to the other EOS tools

The Issues List is where the other tools send their problems.

  • An off-track number on your Scorecard becomes an issue.
  • A Rock reported as off track becomes an issue.
  • A gap revealed by the People Analyzer, such as a GWC gap for someone in a seat, becomes an issue.
  • Questions about who owns what often lead to changes on the Accountability Chart.
  • During quarterly planning, the long-term Issues List helps the team decide which Rocks to set for the next quarter, and the V/TO itself keeps a list of company-level issues.

In return, the solutions from IDS become To-Dos, process changes, or new Rocks. Over time, the Issues List is the mechanism that turns what the other tools reveal into action.

Working with your EOS Implementer

Your EOS Implementer teaches IDS during your early sessions and facilitates the long-term issues work during quarterly and annual planning. Between sessions, your team runs IDS on the weekly list in every Level 10 Meeting.

When your Implementer can see the current long-term list and the issues your team has already solved, quarterly sessions can start from where you actually are, rather than spending time reconstructing the last 90 days from memory. Teams that are self-implementing follow the same principles and can use the same weekly and quarterly rhythm.

How GoalCadence supports the Issues List

GoalCadence is built for teams running on EOS and includes the Issues List with IDS on every plan. Team members can capture and categorize issues as they come up, rank them by impact and urgency, and assign owners. Comments and updates let people add context before the meeting, and solutions become To-Dos with an owner and due date.

Every issue identified, discussed, and solved is kept in a searchable history alongside the decisions behind it, so you can see what the team has already resolved. Your Implementer can join your account at no cost on every plan. The Rocks and Issues guide in the help center walks through setup in more detail.

Frequently Asked Questions

What counts as an issue in EOS?

In EOS, an issue is anything that needs the team's attention to move the business forward. That includes problems and obstacles, but also ideas, opportunities, decisions that need to be made, and information someone needs to share. If it is on your mind and affects your team's goals, it belongs on the list. Keeping the definition broad encourages people to raise things early, before they grow into bigger problems.

What does IDS stand for?

IDS stands for Identify, Discuss, Solve. It is the EOS method for working through issues one at a time. First the team identifies the real root cause behind the stated issue. Then everyone discusses it, saying what they need to say once rather than repeating points. Finally the team agrees on a solution, usually captured as a To-Do with a single owner and a due date.

How do you prioritize issues on the Issues List?

Before solving anything, scan the full list and choose the three most important issues, not the oldest or easiest. A useful test is to ask which issue would make the biggest difference if it were the only one solved today. Work those three in order, completely, then pick the next three if time remains. Unsolved issues simply stay on the list for the next meeting.

What is the difference between the weekly issues list and the long-term Issues List?

The weekly issues list holds short-term items the team can resolve within about a week, and it is worked during IDS in the Level 10 Meeting. The long-term Issues List holds strategic items that need more time or belong to a later quarter, and it is usually worked during quarterly and annual planning sessions. Issues can move between the two lists as their urgency changes.

How many issues should a team solve in one meeting?

There is no fixed number. Some weeks a team solves one complex issue in the full hour of IDS, and other weeks it clears several quick ones. The aim is to solve the most important issues completely rather than skim many. If the team routinely solves only one or two, check whether discussions are repeating points or drifting into tangents, which are the most common time drains.

Who should own an issue on the Issues List?

The person who raises the issue usually owns it. During IDS they state the issue clearly, answer questions to help identify the root cause, and confirm when the team has reached a solution they agree with. The solution itself may then become a To-Do assigned to someone else, often whoever sits in the seat on the Accountability Chart that is responsible for that area.

Early Access: Priority onboarding for mid-market teams

Stop Wasting HoursCopying Data Between Tools

87%
Less time spent updating spreadsheets
20+
Native integrations with your tools
2hrs
Saved per week per team member
Bi-directional data sync
Enterprise-grade security
Dedicated onboarding team

Built for EOS teams and the Implementers who coach them

Finally, a business OS that integrates with everything you already use.