A Disciplined Issues List Turns Avoidance Into Decisions the Team Can Execute

At 8:07 on a Monday morning, a founder slid a notebook across the table and said, “We have talked about this for six weeks.”

The page held one sentence: “We need to fix communication.” Under it were three arrows, two question marks, and a name circled twice. The company had spent hours discussing the problem. Nobody had decided what the problem actually was, who owned the next move, or when the team would know it was solved.

I see this pattern in leadership teams that are smart, busy, and sincere. They do not lack ideas. They lack a disciplined way to move a concern from the fog of conversation into a decision someone can execute. That is where an Issues List earns its place.

In EOS, Identify, Discuss, and Solve—IDS—gives the team a repeatable path. The list captures what deserves attention. The conversation separates symptoms from the issue beneath them. The solve creates an owner, a next action, and a standard for completion. Used well, IDS gives the team fewer places to hide and more confidence to act.

The Issues List protects important problems from urgent noise

A leadership team without an Issues List carries its problems in memory. Someone mentions the hiring gap in the hallway. Another person raises the margin concern during a forecast meeting. A customer complaint takes over the agenda because it arrived ten minutes ago. The issues compete by volume, personality, or timing.

That is a poor way to run a business. The loudest problem receives attention, while the expensive problem waits for a convenient moment that never arrives.

A visible list creates a holding place for anything that needs leadership attention. It can include a missed number, a role confusion, a process failure, a recurring customer complaint, or a decision that has been delayed. Capturing the issue does two things immediately: it prevents the concern from being forgotten, and it keeps the team from hijacking every meeting with an unplanned detour.

The list also changes the emotional temperature. A team member can raise a concern without demanding an instant answer. A leader can acknowledge the issue without pretending to solve it while walking between meetings. The business gains a small amount of space, and space helps people think.

I want the list to be honest enough to include the issue behind the issue. “Sales are down” may be a number. The underlying issue could be an offer nobody can explain, a rep who is carrying the wrong seat, or a founder who keeps changing the target. “Communication is poor” may point to unclear ownership, missing meeting rhythms, or a leader who gives feedback only after frustration has accumulated.

Write the concern in plain language. Do not polish it into a slogan. If the sentence cannot help the team locate the tension, it does not belong on the list yet.

Identify names the problem without protecting the story

Identification sounds simple because leaders are good at naming symptoms. Revenue missed the target. The project is late. The team is frustrated. The candidate declined. Those statements may be accurate, but they do not give the team a solvable issue.

I use a few questions to sharpen the entry:

• What observable result is creating concern?
• Where does the pattern appear, and how often?
• Who is closest to the facts?
• What assumption are we making about the cause?
• What decision or conversation has been postponed?

The goal is not a perfect diagnosis before the discussion begins. The goal is enough precision to prevent ten people from arguing about ten different problems under one label.

Consider a team that writes “We need better accountability.” That phrase can mean a manager is not following up, a scorecard has no owner, a deadline is undefined, or a senior leader keeps rescuing people from consequences. A stronger entry might read: “The weekly scorecard has five numbers without assigned owners, so we cannot tell who is responsible when a measure misses.” Now the team has something to examine.

Naming the issue can feel confrontational because it removes the protection of general language. General language lets everyone nod. Specific language asks someone to look at reality. That discomfort is useful. Respectful clarity gives the team a fair chance to solve the correct problem.

Discuss brings facts into the open and stories back down to size

Once the issue is identified, the team needs a discussion with a finish line. Discussion does not mean everyone gets unlimited airtime. It means the right people examine the facts, test their assumptions, and keep asking what is underneath the first answer.

I listen for story inflation. A leader says, “The team does not care.” The facts may show that the team has three competing priorities, no published definition of done, and a manager who changes direction every Thursday. A founder says, “We cannot find good people.” The facts may show a vague role description, a slow interview process, and compensation that does not match the expectations. The story feels personal. The system tells a more useful story.

A disciplined discussion asks questions such as:

1. What happened, specifically?
2. What evidence do we have?
3. What have we already tried?
4. What is the cost of leaving this unresolved?
5. What issue is underneath the first issue?

The fifth question often changes the conversation. “The team missed the launch” may become “The launch owner lacked authority.” “Our meetings waste time” may become “We do not decide which issues deserve the meeting.” “The customer keeps escalating” may become “The handoff between sales and delivery has no single owner.”

Teams get stuck when discussion becomes a performance. People repeat their positions, defend their departments, and wait for the leader with the highest title to declare an answer. I interrupt that pattern by asking, “What would we need to believe for this issue to be solved?” The question moves people from defending a narrative toward defining a condition.

Solve turns a conversation into a commitment the team can inspect

The decision should be clear enough to repeat. “We need to improve onboarding” is a wish. “Every new hire will receive the role scorecard, a 30-day plan, and a named training owner before the first day” is a standard. The owner should be one person, even when several people contribute. Shared responsibility often becomes distributed ambiguity.

Then decide how the team will know the issue is closed. A closed issue has evidence. The scorecard has owners. The handoff document exists. The conversation happened. The customer complaint dropped under an agreed threshold. The team may discover that the original solve failed. That is useful information, not a reason to pretend the issue was resolved.

I am careful with the word “done.” Leaders often use it to describe a task that was completed, even though the business condition remains unchanged. Sending the email is not the same as creating clarity. Holding the meeting is not the same as changing the process. A solution earns closure when the result matches the standard the team agreed to.

This is where IDS creates trust. People learn that a concern can be raised without drama, examined without blame, and resolved without disappearing into an executive’s head. The team starts to believe that difficult issues will receive a fair process.

A clean Issues List reveals the leadership work beneath operations

After a few weeks of disciplined IDS, the list becomes a mirror. Repeated issues usually point to a leadership pattern.

If the same decision returns every week, the owner may lack authority or the leader may be unwilling to make the call. If the team keeps adding “communication” issues, roles and meeting rhythms may be unclear. If the list fills with people problems but no expectations are written down, the company may be using performance conversations to compensate for missing systems. If every issue is labeled urgent, the leadership team has not agreed on priorities.

That self-examination matters because EOS tools cannot carry a team that refuses to tell the truth. A well-designed agenda can still become theater. A scorecard can still be ignored. An Issues List can become a parking lot for problems if nobody has the courage to discuss and solve them.

I want the team to leave each IDS conversation with less ambiguity than it carried in. That requires a leader who can tolerate the moment when the facts challenge the story, and a team that understands the purpose is progress through clarity. The measure is not how many issues disappear from the page. The measure is whether the business is making better decisions sooner.

If your leadership team has issues that keep returning, do not add another motivational speech to the calendar. Put the issue on the page. Name it precisely. Follow the facts. Find what sits underneath. Decide who will act and what evidence will close the loop.

Action Items From Today

1. Create one visible Issues List. Use a shared document or the tool your leadership team already opens. Add every recurring concern that currently lives in hallway conversations, private texts, or a leader’s memory.

1. Rewrite three vague entries. Replace “communication,” “accountability,” or “hiring” with an observable result, the place it appears, and the decision that needs to be made.

1. Schedule one IDS block. Give the top issue 30 focused minutes this week. Assign a facilitator, invite the people with the facts, and end with either a solve or a clearly defined next issue.

1. Give every solve one owner and one date. Write the decision, the first action, the owner, and the deadline in the meeting notes before anyone leaves the conversation.

1. Define the evidence for closure. Ask, “What will we see when this issue is actually solved?” Keep the issue open until the agreed result exists in the business.

1. Study the repeat offenders. At the end of the month, review which issues returned. Choose one leadership pattern underneath them and address that pattern in your next quarterly planning session.

Five Bridges Challenges

Internal — Name the issue you have been explaining instead of solving. Choose one leadership concern you can describe in a polished sentence but have not converted into a decision. Write the observable facts, identify the postponed conversation, and put the first action on your calendar before Friday.

Relationships — Have the conversation the issue has been protecting you from. Choose a team member, partner, or peer connected to a recurring problem. State the behavior or result without attacking character, ask what you may be missing, and agree on one next step together this week.

Environment — Put truth where the team can work on it. Create the shared Issues List, add three real entries, and reserve a recurring IDS block. Keep the list visible, assign owners, and review the evidence of closure for the next four meetings.

A leadership team does not become clearer because it talks about clarity. It becomes clearer when it names reality, works the issue, and keeps the commitment visible until the result changes.

Inspire & Impact,

Josh