IDS: How Leadership Teams Solve Issues Instead of Just Talking About Them

Your leadership team meets every week. You raise the same problems. You debate them for forty minutes. Someone says “let’s table that for now.” And next Monday, the same issue is back on the list, untouched, unresolved, costing you another week of drift.

I’ve sat in hundreds of leadership team meetings across companies ranging from 30 employees to 200. The pattern is almost universal: smart, capable leaders who are terrible at resolving issues in a room together. Not because they lack intelligence or goodwill, but because nobody ever taught them a structured way to move from “we have a problem” to “here is what we are doing about it, who owns it, and when it will be done.”

That is exactly the gap the IDS process fills. IDS stands for Identify, Discuss, Solve, and it is the issue resolution discipline inside the Business Operating System framework. If your team spends more time talking about problems than solving them, this is the tool that changes the meeting from a venting session into a decision engine.

What Is the IDS Process?

IDS is a three-step discipline for resolving issues inside a leadership team meeting. It stands for Identify, Discuss, Solve, and it is one of the core tools inside the Ninety.io framework used by companies running a Business Operating System.

Here is the breakdown:

Identify means getting to the root cause of the issue, not the symptom. If the issue on the list says “sales are down,” that is a symptom. The real issue might be that your sales team does not have a documented process, or that your ideal customer profile shifted six months ago and nobody adjusted the targeting.

Discuss means the team shares perspectives openly, without crosstalk, without tangents, and without anyone dominating. Each person gets one pass to say what they see. The facilitator keeps it tight.

Solve means the team commits to a specific action: who will do what, by when. No “let’s think about it.” No “we should probably look into that.” A to-do with an owner and a deadline, or the issue goes back on the list as unresolved.

The entire cycle for a single issue should take between five and fifteen minutes. If it takes longer, the issue is either too big (break it down) or the team is discussing instead of solving.

Why IDS Matters More Than You Think

Most leadership teams believe they are good at problem solving. In practice, what they are good at is problem discussing. They talk around issues, share anecdotes, revisit the same ground they covered last month, and walk out of the meeting feeling like progress happened. It did not.

The cost is real. Every unresolved issue on your list is an open loop consuming leadership bandwidth. When I work with companies in the $5M to $50M range, I typically find 15 to 25 issues sitting on the leadership team’s list that have been there for more than 90 days. Each one represents a decision nobody made, a conversation nobody finished, or a conflict nobody was willing to name.

Here is what that looks like in practice: missed quarterly goals, recurring people problems that never get addressed, process breakdowns that the team has “already talked about,” and a growing sense among team members that meetings are a waste of time. When your team loses faith in the meeting, they stop raising real issues. They handle things in side conversations, in hallway politics, or they just quietly disengage.

IDS reverses that cycle. When a team sees that raising an issue leads to resolution (not just discussion), they raise better issues, they raise them sooner, and the whole organization moves faster.

How the IDS Process Works Step by Step

Step 1: Build and Prioritize the Issues List

Before IDS can work, your team needs a living issues list. This is not a list you build during the meeting. It is a running document that every leadership team member adds to throughout the week. Every time someone hits a roadblock, sees a misalignment, or spots a pattern that concerns them, it goes on the list.

At the start of the IDS portion of your weekly leadership meeting, the team looks at the full list and votes on the top three issues to tackle that week. Not five. Not ten. Three. This forces prioritization, which is itself a leadership discipline most teams lack.

Tools like Ninety.io make this easy: the issues list is visible to all team members, anyone can add to it between meetings, and prioritization happens with a simple drag or vote at the top of the meeting.

Step 2: Identify the Root Cause

Once you have your top issue, the facilitator asks: “What is the real issue here?” This is where most teams stumble. The tendency is to accept the issue at face value. “We are losing customers” is not a root cause. Why are you losing customers? Is it onboarding? Is it product fit? Is it a specific team member underperforming?

The rule is simple: keep asking why until you get to something actionable. You are not looking for a philosophical answer. You are looking for the one thing that, if you fixed it, would make this issue go away.

Step 3: Discuss (Once Around the Table)

Once the root cause is named, each team member gets one chance to share their perspective. Not a back and forth debate. One pass, around the table. The facilitator enforces this.

This is the discipline that separates IDS from a normal meeting conversation. In a typical meeting, two or three voices dominate, the conversation spirals into tangents, and twenty minutes later someone asks “wait, what were we solving?” The one-pass rule keeps the discussion tight and ensures every voice is heard without the meeting devolving into cross-talk.

Step 4: Solve With a Commitment

After the discussion, the team commits to a solution. This means a specific to-do: who will do what, by when. The to-do gets assigned to one person (not a committee) with a seven-day deadline by default.

If the issue requires more than one to-do, break it into pieces and assign each one. If the team cannot agree on a solution, the facilitator makes the call or the Visionary and Integrator pair decide. The point is: every issue exits IDS with a next action, or it goes back on the list as explicitly unresolved.

Real-World Application: What IDS Looks Like in Practice

I worked with a professional services firm, about 60 employees, $12M in annual revenue. Their leadership team of six met weekly, but they described their meetings as “painful.” Same issues on the list for months. Long debates that ended with “good discussion, let’s revisit next week.”

When we introduced IDS, the first thing that happened was discomfort. The CEO, Renata, was used to leading the conversation. Under IDS, the facilitator (in this case, the Integrator) controlled the flow. Renata got one pass to share her perspective, same as everyone else. She did not love it at first. Within three weeks, she told me it was the best change they had made in years, because she was finally hearing what her ops director and her finance lead actually thought instead of hearing them agree with her.

The second thing that happened was speed. In their first IDS session, they resolved three issues that had been sitting on their list for over 90 days. One was a pricing structure problem their sales director had been trying to raise for months but kept getting talked over. It took eleven minutes to identify the root cause, discuss options, and assign a to-do to the sales director to present a revised pricing model within seven days.

I see this pattern repeatedly. The first two or three IDS sessions feel awkward. By week four, teams start saying: “Why did we ever run meetings any other way?”

Another example: a 40-person SaaS company whose leadership team was stuck in a cycle of “we need to hire” conversations. The same hire had been discussed in six consecutive meetings with no decision. When we applied IDS, the root cause was not headcount. It was that nobody had defined the seat clearly on the accountability chart. Once they identified that as the real issue, the to-do was simple: the COO would draft the seat description by next Wednesday. The hire was posted two weeks later.

Signs Your Team Needs the IDS Discipline

If you recognize three or more of these patterns, your team is solving issues through discussion instead of decision:

• The same issues appear on your meeting agenda week after week with no resolution.
• Your meetings regularly run over time because “we just need five more minutes” on every topic.
• Two or three people dominate every discussion while the rest of the team stays quiet.
• Team members raise issues in side conversations or one-on-one meetings instead of in the leadership meeting.
• You leave meetings feeling like you had a good conversation but you cannot name what was actually decided.
• Your to-do completion rate from meetings is below 80%.
• Issues that should take ten minutes to resolve take forty because the conversation spirals into tangents and war stories.

How to Get Started With IDS This Week

You do not need a full Business Operating System implementation to start using IDS. Here is how to run your first IDS session in your next leadership meeting:

1. Before the meeting, ask every team member to add their top three issues to a shared list.
2. At the start of the IDS portion, vote on the top three issues to solve that meeting.
3. For each issue, follow the sequence: name the root cause, go once around the table, commit to a to-do with an owner and a deadline.
4. Track the to-dos and review completion at the start of the next meeting.

If you want the full framework (including the issues list tool, the meeting structure, and the accountability system that makes it stick), Ninety.io gives you the platform to run IDS inside a structured weekly meeting. And if your team needs a facilitator to help them build the muscle, that is exactly what a Fractional COO engagement provides: someone who has run IDS in dozens of leadership teams and knows how to coach yours through the learning curve.

Frequently Asked Questions

How long should the IDS portion of a leadership meeting take?

In a standard 90-minute weekly leadership meeting, the IDS segment typically runs 60 minutes. That is enough time to resolve three to five issues if the team stays disciplined. If you are consistently running out of time, it usually means you are discussing too long and not identifying the root cause fast enough. Tighten the “identify” step, and the rest accelerates.

What if the team cannot agree on a solution during IDS?

This happens, and it is normal. The rule is: someone has to make the call. In most Business Operating System frameworks, the Integrator (or whoever serves as the operational leader) breaks the tie. The team commits to the decision even if not everyone agrees. This is “disagree and commit” in practice. If the decision turns out to be wrong, it goes back on the issues list, and you IDS it again.

Is IDS only for leadership teams?

No. IDS works at every level of the organization. Department teams, project teams, and even field crews can use the same discipline. The key is having a facilitator who enforces the structure: identify the root cause, discuss once around, solve with a commitment. I have seen IDS run effectively in weekly contractor meetings and in quarterly planning sessions.

How do we handle issues that are too big to solve in one meeting?

Break the issue into smaller pieces. If “we need to fix our onboarding process” is on the list, the first IDS cycle should identify which specific part of onboarding is broken. That becomes the actionable issue. The to-do might be: “Map the current onboarding process and identify the three biggest drop-off points by next Wednesday.” The larger initiative stays on the list, but each week you are solving one piece of it.

What is the difference between IDS and the broader problem resolution framework?

IDS is the tactical tool you use inside a meeting to resolve a specific issue in 5 to 15 minutes. The broader problem resolution framework covers how to think about systemic business problems, including root cause analysis, stakeholder alignment, and implementation planning. Think of IDS as the weekly drill and problem resolution as the strategic playbook. They work together: IDS surfaces the issues, and the resolution framework handles the ones that require more than a single to-do.