Leadership Decision Making: Are You Processing It, or Just Rehearsing It? - 52

How leaders turn recurring frustration into useful information, better decisions, and forward momentum

Frustration contains information. Something isn't working. An expectation hasn't been met.

A recurring problem has resurfaced. A decision feels wrong. A relationship has become difficult. A process that should be straightforward continues to create unnecessary complications. In leadership decision-making, those reactions matter because frustration can direct attention toward something that deserves examination. What matters is what happens next.

One leader notices the problem, talks about it, revisits it, and then returns to it again the next time something triggers the same frustration. Another notices the same problem, processes what is happening, determines what it means, and decides what response is available. Both leaders may be equally frustrated. But only one is converting frustration into useful leadership information.

That's the distinction between processing a problem and rehearsing it.

The Complaint Is Often the First Signal

Complaining has a bad reputation in leadership conversations. We're frequently encouraged to stop complaining, remain positive, and focus on solutions. But that framing can cause leaders to overlook something useful: a complaint often identifies a legitimate problem.

“This approval process takes forever.”

“We keep having the same conversation.”

“Nobody knows who's responsible for this.”

“I'm constantly stepping in to finish work that should've been handled before it reached me.”

Those statements may sound like complaints, but each contains information. The approval process may be unnecessarily complex. Expectations may be unclear. Accountability may be fragmented. A leader may have created dependency by repeatedly rescuing others.

The first complaint can be diagnostic. The problem begins when identifying what's wrong becomes the end of the process. At that point, the complaint stops functioning as information and begins functioning as rehearsal.

Rehearsal Keeps the Problem Active Without Moving It Forward

Think about the last frustrating experience you described more than once. The first time you told the story, you may have been trying to understand what happened. Perhaps you needed perspective, support, or simply the opportunity to articulate what you were feeling. Then you told it again. And again.

Eventually, nothing new was being discovered. The facts hadn't changed. No additional insight was emerging. Each retelling simply returned you to the same frustration. That's rehearsal.

In organizations, it can become surprisingly easy to mistake this repetition for productive engagement. A leadership team discusses the same operational problem in three consecutive meetings. Managers repeatedly complain about another department. An executive talks frequently about an employee's performance but never has the necessary conversation with the employee. Leaders agree over and over that a process is broken without assigning anyone responsibility for changing it.

Because the problem is being discussed, it feels as though something is happening. But conversation and movement aren't the same thing.

A problem can receive enormous amounts of attention without receiving a decision.

The Complaint Loop

This creates what we might call the Complaint Loop.

The repetitive version is simple:

Notice → Complain → Revisit → Repeat

Something happens. We become frustrated. We talk about it. Nothing materially changes. Then another incident occurs, and we begin the cycle again.

A constructive loop looks different:

Notice → Process → Decide → Act

The first step is identical. Both begin by recognizing that something is wrong. The difference is what follows.

Processing asks what the frustration is telling us. Decision determines what response is warranted. Action moves the issue somewhere, even if the action is simply establishing a boundary, seeking additional information, accepting what can't be changed, or deciding that the issue doesn't deserve further attention.

This is where leadership decision making becomes practical. The objective isn't to eliminate complaints. It's to keep complaints from becoming permanent destinations.

Processing Requires Better Questions

Rehearsal asks questions that keep us close to the irritation.

Can you believe they did that?

Why does this always happen?

How many times have we talked about this?

Why can't they just get it together?

Processing asks different questions.

What exactly is frustrating me about this?

Is this an isolated incident or a recurring pattern?

What assumptions am I making about why it's happening?

What part of this is within my authority or influence?

Is there a conversation, decision, boundary, or action I've been avoiding?

Those questions don't guarantee an immediate solution. They do something equally important: they change our relationship with the problem. Instead of repeatedly experiencing it, we begin examining it. That shift matters because leaders need enough distance from frustration to exercise judgment about it.

Complaining Can Become a Substitute for Deciding

One of the more subtle risks occurs when talking about a problem begins to provide enough relief that leaders never actually address it. The conversation itself becomes the release valve.

A director complains to another director about an employee rather than addressing the performance issue directly. An executive repeatedly expresses frustration with a peer but never clarifies the working relationship. A leadership team criticizes an inefficient process while continuing to operate within it exactly as before.

Everyone may genuinely want the situation to improve. But repeatedly describing what needs to change can create the psychological sensation of having done something about it. This is particularly dangerous for leaders because their unresolved frustrations rarely affect only them.

If a manager spends six months complaining about poor performance without addressing it, other employees experience the consequences. If executives repeatedly criticize cross-functional dysfunction without confronting its causes, their teams inherit the conflict. If a senior leader continuously complains about being overwhelmed while refusing to delegate, the bottleneck remains.

Eventually, the organization may reasonably ask:

If this problem is significant enough to keep discussing, why isn't it significant enough to address?

Not Every Problem Can Be Solved

Some frustrations don't have clean solutions. A leader may be navigating a difficult organizational transition they can't accelerate. A budget constraint may be real. A senior executive may have made a decision that won't be reversed. A valued employee may leave despite every reasonable effort to retain them. Market conditions may create pressures leadership simply has to manage.

Processing doesn't require pretending we can control what we can't. Sometimes the decision at the end of the constructive loop is acceptance. Sometimes it's adaptation. Sometimes it's asking for support, changing an expectation, establishing a boundary, or determining how much emotional energy the situation deserves.

That is still movement. A leader who concludes, “I don't like this decision, I can't change it, and I need to determine how I'm going to lead effectively within it,” has moved further than one who spends the next six months repeatedly explaining why the decision was wrong.

Agency doesn't always mean changing the circumstances. Sometimes it means choosing how we will operate within them.

Be Careful What Leadership Rehearses

What leaders consistently reinforce helps determine where an organization directs its attention. When executives repeatedly complain about customers, employees notice. When managers constantly describe senior leadership as incompetent, their teams absorb that framing. When a leader repeatedly focuses on everything that is wrong without helping people determine what can be done, frustration can become part of the team's operating environment.

This doesn't mean leaders should soften reality. People don't need manufactured optimism when circumstances are genuinely difficult. In fact, leaders who refuse to acknowledge obvious problems can lose credibility quickly.

But acknowledgment and rehearsal are different. A credible leader can say, “This situation is difficult. Here's what we know. Here's what we don't know. Here's what we can influence. Here's what we're going to do next.”

That statement doesn't deny the problem. It gives the problem somewhere to go.

Don't Confuse Processing With Positivity

The distinction between processing and rehearsing isn't an argument for positive thinking. Leaders don't need to turn every disappointment into gratitude, search immediately for a silver lining, or rush people past legitimate frustration. Some experiences require time.

A failed initiative may need to be examined carefully. A difficult organizational decision may need to be grieved. An employee may need space to articulate anger before they're ready to consider what comes next. Healthy processing can include disappointment, frustration, anger, uncertainty, and disagreement.

What distinguishes processing is movement toward understanding. Rehearsal reproduces the emotional experience. Processing metabolizes it.

That's why the goal isn't to ask people to “stop being negative.” It's to help them determine whether repeatedly returning to the problem is producing additional understanding or simply another experience of the same frustration.

Leaders Can Interrupt the Loop

When a complaint begins repeating itself, leaders have an opportunity to change the conversation without dismissing the concern.

They can ask:

What do we understand now that we didn't understand the last time we discussed this?

That question immediately tests whether the conversation is producing new information.

Another useful question is:

What does this require from us?

Perhaps the answer is a decision. Perhaps someone needs to have a conversation. Maybe ownership needs to be clarified. Additional information may genuinely be necessary. Or the group may need to acknowledge that the circumstances aren't going to change and decide how to proceed.

The purpose isn't to shut down frustration. It's to prevent frustration from becoming the work. Because leaders have limited attention, and recurring complaints can consume enormous amounts of it without producing corresponding value.

The Leadership Takeaway

A complaint can be useful. It can alert us to misalignment, surface a recurring problem, reveal an unmet expectation, or identify something that deserves closer attention. But identifying the problem is only the beginning.

Leadership requires deciding what happens to that information next. We can rehearse the frustration until it becomes familiar, repeatedly returning to the same story without changing our understanding or our response. Or we can process it. We can examine what's happening, determine what belongs within our control, make the decision available to us, and take the next responsible action.

Sometimes that action changes the situation. Sometimes it changes how we respond to the situation. Both are forms of movement.

So the next time you hear yourself or your leadership team returning to a familiar complaint, don't immediately shut it down.

Ask a better question:

Are we still learning something from talking about this, or are we simply rehearsing it?

If the conversation is no longer producing insight, perhaps it's time for the problem to become a decision.