How to Resolve Business Problems Before They Become Crises
Every business owner knows the feeling. There’s a problem everyone’s aware of but nobody’s addressing. It gets mentioned in hallways, complained about after meetings, maybe even joked about—but it never actually gets fixed. Weeks turn into months. The problem compounds. And eventually, what could have been a simple conversation becomes a full-blown crisis that costs you a key employee, a major client, or a chunk of revenue you’ll never recover.
This isn’t a character flaw. It’s a systems failure. Learning how to resolve business problems before they escalate isn’t about working harder or caring more—it’s about building a reliable process that surfaces issues early and drives them to resolution. That’s exactly what the Issues management system does.
Why Companies Let Issues Fester
Most leadership teams aren’t avoiding problems because they’re lazy or unaware. They’re stuck in patterns that feel productive but actually prevent resolution.
The first pattern is the assumption that someone else owns it. Your operations manager assumes the sales manager will address the pricing confusion. Your sales manager assumes operations will fix the delivery delays causing the pricing confusion. Nobody explicitly owns the problem, so it bounces between departments indefinitely.
The second pattern is meeting culture that rewards discussion over decision. I’ve watched leadership teams spend forty-five minutes dissecting a problem from every conceivable angle, congratulate themselves on a “productive conversation,” then realize six weeks later that nothing changed. Talking about a problem feels like progress. It isn’t.
The third pattern is fear of conflict. The real issue often involves a person, a department, or a sacred cow nobody wants to touch. So the team talks around it, addressing symptoms while the root cause remains untouchable.
In trades businesses, this shows up constantly with underperforming crew leads or field supervisors who’ve been around forever. Everyone knows the problem. Nobody wants the conversation. So you lose good technicians who get fed up working under poor leadership, and the cycle continues.
The Four Types of Issues
Not all problems are the same, and treating them identically leads to wasted time and missed priorities. Issues typically fall into four categories:
People issues involve someone not meeting expectations—wrong seat, wrong values fit, or insufficient competency/commitment/capacity. These are often the most avoided because they feel personal.
Process issues are about how work gets done. Something’s broken, undocumented, or followed inconsistently. These feel safer to discuss but often mask underlying people or structure issues.
Strategic issues involve direction—market positioning, service offerings, pricing, or target customer decisions. These require dedicated time and often can’t be resolved in a single meeting.
External issues come from outside your organization—economic shifts, competitor moves, regulatory changes, supply chain disruptions. You can’t control these, but you can decide how to respond.
Naming the type matters because it shapes the conversation. A people issue masquerading as a process issue will never get resolved through better documentation.
The RDR Process: Raise, Discuss, Resolve
The Issues management system uses a deceptively simple three-step framework called RDR: Raise, Discuss, Resolve. Simple doesn’t mean easy—most teams struggle with it initially because it requires discipline they haven’t built.
Raise
Anyone on the leadership team can raise an issue at any time. In platforms like Ninety.io — try it free for 30 days, you maintain a running Issues List that team members add to throughout the week. By the time your Weekly Team Meeting arrives, you’re not trying to remember what’s wrong—it’s already documented.
The raise step requires just enough detail for the team to understand the problem. Three to seven words is often enough. “Project manager capacity” or “Customer complaints about invoicing” or “Truck 7 downtime.” The goal isn’t to solve it yet—it’s to get it visible.
Discuss
Discussion starts by identifying the root cause. The person who raised the issue provides context, but the team’s job is to dig beneath symptoms to find what’s actually broken. This often takes three to five “why” questions.
“Customer complaints about invoicing” might trace back to field techs not logging materials properly, which traces back to no mobile system for job site entry, which traces back to the previous software decision made three years ago that nobody ever revisited.
Discussion should be focused and time-aware. If you’ve spent fifteen minutes and you’re still circling, you either haven’t found the root cause or the issue is strategic and needs dedicated time outside the weekly meeting.
Resolve
Resolution means one of three things happens:
- The issue is solved in the meeting through a decision that addresses the root cause
- The issue becomes a To-Do assigned to a specific person with a specific due date (usually seven days)
- The issue is elevated to a Rock if it requires more than a few weeks to resolve
What doesn’t count as resolution: “We should think about that.” “Let’s keep monitoring.” “I’ll look into it.” These are discussion phrases pretending to be resolution. They guarantee you’ll see the same issue on next week’s list.
Short-Term vs Long-Term Issues
The Issues List serves two purposes, and conflating them creates problems.
Short-term issues are tactical problems that can be resolved in one or two meetings. Most of what hits your weekly Issues List falls here. These should be resolved quickly—ideally the same week they’re raised.
Long-term issues are strategic or structural problems that require extended work. “We need a new CRM” or “Our pricing model doesn’t fit the market” aren’t going to resolve in a weekly meeting. These belong on a separate Long-Term Issues List, reviewed quarterly, and addressed through Rocks or dedicated planning sessions.
Teams that mix these together end up with an Issues List that never gets below twenty items. The strategic issues sit there week after week, creating noise that makes it harder to see the tactical fires that need attention now.
The Keep, Kill, Combine Review
Once a quarter—typically during Quarterly Planning—review your entire Issues List with fresh eyes. For each item, decide:
- Keep: This is still a real issue we need to address
- Kill: This resolved itself, is no longer relevant, or isn’t actually an issue worth leadership time
- Combine: This is a symptom of another issue already on the list
You’ll typically eliminate 20-30% of your list through this review. Issues that seemed urgent three months ago often look trivial now. Symptoms that appeared separate reveal themselves as the same root problem.
This review also prevents the shame spiral of a bloated list. When your Issues List hits forty items, adding new problems feels pointless because nothing ever gets resolved. The quarterly cleanup resets psychological energy and makes the system feel manageable again.
What Makes a Good Issues Discussion Leader
The person facilitating Issues isn’t usually the person who raised the issue or the person most affected by it. It’s often the Integrator or meeting leader, and the role requires specific skills:
Comfortable with conflict. Issues discussions expose disagreements, underperformance, and sacred cows. The facilitator needs to stay neutral and keep pushing toward resolution even when people get uncomfortable.
Skilled at root cause identification. When someone says “the problem is communication,” a good facilitator asks “specifically what communication, between whom, about what topic?” The vague issue always masks a specific problem.
Disciplined about time. Issues can expand to fill available time. The facilitator needs to recognize when discussion is productive versus when it’s circular, and either drive to resolution or table the issue for dedicated time.
Focused on action. Every issue must end with a clear outcome. The facilitator closes each issue explicitly: “So the resolution is [X], owned by [person], due by [date]. Agreed?”
The Most Common Failure: Confusing Discussion with Resolution
This single mistake kills more Issues processes than anything else. It’s so common because it feels like progress.
The team discusses the problem thoroughly. Everyone shares their perspective. The root cause seems identified. Then someone says “okay, good discussion” and the meeting moves on. No decision. No owner. No due date.
The issue reappears next week. Same discussion. Same non-resolution. Eventually the team stops raising it because what’s the point.
Resolution requires commitment to action. That means someone specific agrees to do something specific by a specific date. If you can’t get to that commitment, you haven’t resolved the issue—you’ve just talked about it. Be honest about the difference.
Signs Your Issues Process Is Broken
- The same problems appear on your Issues List for multiple consecutive weeks
- People stop raising issues because “nothing ever happens anyway”
- Your list has grown beyond 25 items without recent cleanup
- Discussion time regularly exceeds thirty minutes per issue without resolution
- To-Dos generated from Issues aren’t completed by due dates
- Major problems surface as crises that “nobody saw coming”—when everyone actually saw it coming and didn’t raise it
Getting Started This Week
If you don’t have an Issues process, start one in your next leadership meeting. Create a shared list—even a shared document works initially. Ask each person to add two or three issues before the meeting. Spend thirty minutes working through as many as you can using RDR.
If you have a process that isn’t working, diagnose it honestly. Are you actually resolving issues or just discussing them? Is your list segmented between short-term and long-term? When was the last time you did a keep/kill/combine review?
The goal isn’t perfection in week one. It’s building the muscle that surfaces problems early and drives them to resolution consistently. That muscle prevents the crises that cost you time, money, and people you can’t afford to lose.
Tired of the Same Problems Circling Back?
If your leadership meetings feel productive but nothing actually changes, you’re not alone. Most teams discuss problems endlessly without the system to resolve them. A 30-minute call costs nothing and could be the clearest conversation you’ve had about why issues keep festering in your business.
For tracking Issues alongside your Rocks, Scorecards, and weekly meetings, we use Ninety.io—it keeps everything visible and connected.
