The Problem With How We Handle Problems

There's a moment that shows up in every meaningful project, every leadership role, every relationship that matters. You're moving toward something—a goal, a deadline, a decision—and a problem lands in the middle of the path. A deliverable slips. A teammate underperforms. A client changes direction. A plan you were proud of stops working.

That moment is pivotal. What you do in the next sixty seconds tends to set the trajectory for the next sixty days. 

Two frameworks I've been thinking about—one from Brené Brown's recent book Strong Ground, the other from Ray Dalio's Principles—fit together in a way that makes that pivotal moment far easier to navigate. This is my attempt to put them side by side.

‍The first framework: Above the line, Below the line

I encountered the above-the-line / below-the-line framework most recently through Brené Brown's Strong Ground. Brown is careful to attribute it—the concept traces back to several individuals, noted on her website. Brown explains that when things go sideways and fear presents itself, we respond with an above the line approach or a below the line approach.  

Above the line, there are three patterns: 

• Create — ownership and possibility. "What outcome do I want, and what will I do about it?"
• Coach — curiosity and development. "Help me understand how you're seeing this."
• Challenge — truth and accountability. "We missed the mark. Let's name it directly."

Below the line are three protective patterns that feel justified in the moment:

• Hero — over-rescuing and control. "I'll just take this over."
• Victim — powerlessness and blame-deflection. "There's nothing I can do. This always happens to us."
• Villain — blame and judgment. "It's their fault. Engineering dropped the ball."

The way this concept clicked for me is this: above the line is responding to the pivot point (and the subsequent fear) with courage and love. Below the line is responding with fear and shame. Above the line takes courage because it requires you to sit with discomfort. Below the line is what your nervous system reaches for when it wants the discomfort to end right now.

Brown is emphatic—and I think rightly so—that the goal is not to live above the line all the time. No one does. We move above and below dozens of times a day. The goal is awareness and faster recovery: to notice where you are, recognize the pattern, and choose to come back up.

‍The second framework: Dalio's 5-Step Process

Ray Dalio's 5-Step Process is critical to improvement and evolution, and  it's his model for getting what you actually want out of life or work:

1. Have clear goals.
2. Identify and don't tolerate the problems that stand in the way of those goals.
3. Accurately diagnose the problems to get at their root causes.
4. Design plans that get you around them.
5. Push those plans through to results.

Then, look at the new outcomes and run the loop again—ideally setting your goals successively higher. Dalio is explicit: do these steps one at a time and in order. When you're setting goals, just set goals. When you're diagnosing, just diagnose. Blurring the steps produces mediocre outcomes.

I want to draw attention to step 2. Dalio doesn't just say "notice the problem." He says identify and don't tolerate it—and then, he is unusually direct about the emotional dimension. He talks about needing to be "calm and analytical" so you can move into diagnosis and treating pain as a guide. He warns that if your emotions are running the show, you have to step back until you can reflect clearly.

In other words: Dalio knows that step 2 is where most people fail because what they do (or fail to do) upon seeing the problem is what determines whether they get to step 3 at all.

‍Where the two frameworks meet

This is where I think Brown's framework and Dalio's process come together. Step 2 of the 5-Step Process is exactly the place where you choose, in real time, to respond above the line or below it.

Think about what each below-the-line pattern actually does to Dalio's loop:

The Villain response short-circuits diagnosis. "Engineering dropped the ball" feels like an answer. It is not. It is a label that satisfies the part of your brain demanding closure and prevents you from ever asking what system let the ball drop. You skip step 3 entirely.

The Victim response prevents action. "This always happens to us" relocates the problem  to outside your sphere of control so steps 4 and 5 don't apply. There's nothing to design, nothing to push through. You're absolved, and you're also stuck.

The Hero response skips diagnosis and shortcuts execution. "I'll just take this over and fix it next time" feels productive, but bypasses the diagnosis step entirely. You never learn why the problem occurred and it creates a system in which the problem will recur because nothing structural has changed. You become a single point of failure. Dalio would call this destroying the machine.

All three of these are responses of fear: fear of accountability, fear of inadequacy, fear of conflict. And all three of them prevent the loop from doing its actual job, which is to convert problems into improvements.

Now look at what each above-the-line pattern enables:

Create takes you cleanly into step 3 and 4. "What does success look like from here, and what can I do to get us there?" It owns the situation, points forward, and treats the problem as raw material for a better design. It is, almost word-for-word, what Dalio means by "design plans that will get you around them."

Coach unlocks better diagnosis. "What got in the way, from your perspective?" produces information you cannot get from a Villain stance. The people closest to the problem usually have the clearest view of its root causes, but they will only share it when they know they won’t be blamed. Curiosity is a diagnostic tool. Judgment is not.

Challenge enables step 2 itself. This is the one most leaders get wrong. Dalio says don't tolerate the problem, but he does not mean attack the person. Challenge above the line means naming reality with care: "We missed the deadline. Let's walk through what happened and how we prevent it." It's directness without aggression. It's the only way to actually get a problem on the table where it can be diagnosed.

A worked example

Picture a team that misses a meaningful deadline. The slip has real consequences for a client and for the team's credibility.

Below the line, the responses sound familiar:

• Villain: "Engineering dropped the ball."
• Victim: "This always happens to us. The scope was impossible."
• Hero: "I'll just take it over next sprint."

Each one feels reasonable in the moment. Each one is a way of ending the discomfort. Each one also guarantees the same miss happens again, because none of them produce the diagnosis that Dalio's step 3 requires.

Above the line, the same situation sounds different:

• Create: "What system gets us to predictable delivery?"
• Coach: "What got in the way from your perspective?"
• Challenge: "We committed to this timeline. What needs to change?"

The above-the-line responses are not softer. The Challenge question is harder than "engineering dropped the ball," not easier because it asks the team to look honestly at its own commitments. But it points the conversation toward diagnosis instead of away from it. It moves the loop forward.

Putting the frameworks to work

When you're moving toward a goal and a problem arrives, that is step 2 of Dalio's loop. Step 2 is also the moment your nervous system will offer you a below-the-line response, free of charge, in under a second. Recognizing that offer for what it is—a fear response dressed up as a reasonable conclusion—is the discipline that separates teams and leaders who actually iterate from those who keep running into the same wall.

The above-the-line patterns aren't just better behavior. They are the entry points into the rest of Dalio's process. Create gets you to step 4. Coach gets you to step 3. Challenge gets you cleanly through step 2 without dropping it. Below-the-line patterns terminate the loop before it can do its work.

And the goal is not perfection (borrowing Brown's phrasing because I haven't found a better one). No one stays above the line consistently under pressure. The goal is awareness and faster recovery: to notice when you've gone below, name it without shame, and come back up so the loop can keep running.

What this changes in practice

A few things shift for me when I hold these two frameworks together:

When a problem surfaces, I try to ask myself a single question before I respond: am I about to react, or am I about to diagnose? Reacting is below the line. Diagnosing is above it. The pause is small, and it changes everything that comes after.

When I'm leading a retrospective, I listen to the language. "Whose fault is this?" is a Villain response phrased as a question. "What system produced this outcome?" is the same question with the fear taken out.

When I'm tempted to jump in and fix something a teammate is struggling with, I try to notice the Hero pull. The short-term cost of coaching them through it is real, but the long-term cost of doing it for them is even more so.

When something has clearly gone wrong and needs to be said out loud, I try to remember that Challenge above the line is not the same as conflict. Naming reality with care is one of the most helpful things you can do for a team that is about to repeat a mistake.

Brown gives you the inner move—the recognition of what's happening inside you when a problem hits. Dalio gives you the outer process—what to do with the problem once you've stayed grounded enough to look at it clearly. Neither one is sufficient on its own. Together, they're a pretty good map for the moment that matters most.