Three Ways People Respond to a Problem (Other Than Solving It): A Framework for Understanding Human Behavior

When faced with a problem, most of us assume the only rational response is to solve it. Yet daily life—and a growing body of research—shows that people often respond in ways that have nothing to do with finding a solution. A recent analysis published on Improve Something Today identifies three distinct, non-solution-oriented responses that reveal a great deal about human psychology, decision-making, and even organizational culture.

Understanding these three patterns is crucial for leaders, educators, product managers, and anyone who works with people. By recognizing when someone is not actually trying to solve a problem, you can adjust your communication, offer better support, and avoid common frustrations. This article unpacks each response, provides real-world examples, and offers practical tips for navigating them.

The Three Non-Solution Responses

The framework, originally outlined in a detailed post on Improve Something Today, categorizes responses into three archetypes: Avoidance, Blaming, and Resignation. Each stems from different psychological triggers and leads to distinct outcomes. Below is a summary table, followed by an in-depth exploration of each.

Let's examine each response in detail.

1. Avoidance: The Art of Not Seeing the Problem

Avoidance is perhaps the most common non-solution response. Instead of tackling a problem, a person actively or passively steers away from it. Psychologists often link avoidance to anxiety—the brain perceives the problem as a threat and triggers a flight response.

Real-World Example

Consider a small business owner who notices declining sales for three consecutive quarters. Instead of analyzing customer feedback or adjusting the marketing strategy, they immerse themselves in minor operational tasks—reorganizing the supply closet, updating the company website color scheme, or attending networking events. The core problem (declining sales) remains unaddressed, while the owner feels busy and productive.

Why It Happens

Avoidance often arises when the problem feels overwhelming or when the person doubts their ability to solve it. According to a 2021 study published in the Journal of Behavioral Decision Making, people are more likely to avoid a problem when they perceive the potential solution as requiring significant effort or when they fear the emotional cost of failure.

How to Recognize Avoidance

• Constant busyness with low-priority tasks
• Frequent topic changes when the problem is mentioned
• Excuses like "I'll get to it next week" or "Let's wait and see"
• Physical symptoms such as tension or fatigue when the subject arises

Practical Tip

If you spot avoidance in yourself or a colleague, break the problem into smaller, less intimidating steps. Use the "two-minute rule": commit to doing just one small action related to the problem for two minutes. Often, starting is the hardest part.

2. Blaming: The Reflex to Protect the Self

Blaming shifts focus from the problem itself to who is responsible for it. This response is driven by a need to maintain self-esteem and social standing. When people blame others, they avoid the discomfort of admitting their own role or the complexity of the issue.

Real-World Example

A software development team misses a critical product launch deadline. During the post-mortem meeting, the project manager blames the developers for underestimating task complexity. The developers blame the product manager for changing requirements mid-sprint. The designers blame the QA team for not catching bugs earlier. Six hours of discussion later, no one has proposed a concrete plan to prevent future delays.

Why It Happens

Social psychology research, including classic work by Jones and Nisbett (1972), shows that people tend to attribute their own failures to external circumstances (situational factors) but attribute others' failures to internal traits (dispositional factors). This 'actor-observer bias' makes blaming a natural, though unproductive, response.

How to Recognize Blaming

• Language focused on "who did what" rather than "what can we do"
• Defensiveness when the problem is raised
• A culture where mistakes are punished rather than analyzed
• Repeated cycles of fault-finding without resolution

Practical Tip

To move past blaming, reframe the conversation around systems and processes rather than individuals. Ask: "What in our workflow allowed this gap to occur?" instead of "Who dropped the ball?" This shifts the focus from blame to improvement.

3. Resignation: The Quiet Acceptance of Failure

Resignation occurs when a person believes that nothing they do will make a difference. Psychologist Martin Seligman's concept of learned helplessness explains this response: after repeated failures or exposure to uncontrollable events, people stop trying—even when they later have the ability to change the outcome.

Real-World Example

A customer service team has been dealing with a recurring software bug for months. Every time they report it, the engineering team says it's low priority. Eventually, the service reps stop reporting bugs altogether. They simply tell customers, "We know about it, but there's nothing we can do." The problem persists, and customer satisfaction declines.

Why It Happens

Resignation often emerges in environments where people lack agency or where previous attempts at change were ignored. It can also be a rational response to genuinely intractable problems, but more frequently it reflects a perception of powerlessness that may not match reality.

How to Recognize Resignation

• Statements like "It's always been this way" or "Nothing ever changes"
• Low energy and lack of initiative
• Passive acceptance of poor outcomes
• Avoidance of any suggestion that improvement is possible

Practical Tip

To counter resignation, create small, quick wins. Give the person or team control over a small aspect of the problem. Celebrate even minor improvements to rebuild a sense of efficacy. For example, if a team feels powerless about a broken process, let them redesign just one step of it.

Why This Framework Matters for Leaders and Teams

Understanding these three responses is not just an academic exercise. In organizational settings, misinterpreting a non-solution response can lead to wasted time, damaged relationships, and missed opportunities.

For instance, if a manager sees avoidance and responds with pressure or threats, they may increase the anxiety that caused the avoidance in the first place. If they see blaming and respond with punishment, they may reinforce a defensive culture. If they see resignation and respond with motivational speeches, they may come across as out of touch.

The Improve Something Today article emphasizes that the first step to helping someone move toward a solution is to recognize which response they are exhibiting. Only then can you choose an appropriate intervention.

A Comparative Look: Problem-Solving vs. Non-Solution Responses

How to Help Someone Shift from These Responses

The material from Improve Something Today also offers a practical guide for helping others (or yourself) move from non-solution responses toward actual problem-solving. The key is to match the intervention to the response.

For Avoidance

• Reduce the perceived threat: Emphasize that mistakes are learning opportunities.
• Set concrete deadlines: Avoid open-ended tasks. Use specific, short timeframes.
• Pair up: Working with someone else can reduce the fear of facing the problem alone.

For Blaming

• Focus on shared goals: Remind everyone what you collectively want to achieve.
• Use neutral language: Replace "you did X" with "X happened, let's explore why."
• Model accountability: If you are a leader, admit your own mistakes first.

For Resignation

• Restore agency: Give the person choices, even small ones.
• Highlight past successes: Remind them of times when they made a difference.
• Set achievable milestones: Break the problem into pieces that can be solved quickly.

Real-World Case Study: A Product Team's Transformation

To see this framework in action, consider the example of a mid-sized SaaS company that was struggling with user retention. The product team had been working on new features for months, but churn rates kept climbing.

At a quarterly review, the team exhibited all three non-solution responses:

• The product manager avoided the data, saying "We need more time to see if our changes work."
• The engineering lead blamed the marketing team for not communicating the new features properly.
• The designer resigned, saying "Users never appreciate our work anyway."

The CEO, familiar with the framework, addressed each response differently. She asked the product manager to review just one user feedback report per week (reducing avoidance). She shifted the engineering lead's focus to how the onboarding flow could be improved instead of who failed (reframing blame). And she tasked the designer with creating a simple survey to gather user input, giving them direct influence over the next iteration (restoring agency).

Within three months, the team had identified the core issue—a confusing onboarding process—and reduced churn by 15%. The key was not a grand solution, but recognizing and responding to the non-solution behaviors first.

Tips for Applying This Framework in Your Own Life

1. Self-check regularly: When you face a problem, ask yourself: Am I avoiding it? Blaming someone? Giving up? Just naming the response can help you shift.
2. Use the 'five whys' technique: When someone gives a non-solution response, ask 'why' five times to uncover the root cause of their reaction.
3. Create a safe environment: The more psychological safety a team has, the less likely members are to avoid or blame. Encourage open discussion of mistakes.
4. Celebrate process, not just outcomes: Recognize people for trying, even if they fail. This reduces the fear that drives avoidance and resignation.

Conclusion

Problems are an inevitable part of life, but solving them is not the only possible response. The three patterns outlined in the Improve Something Today article—avoidance, blaming, and resignation—offer a powerful lens for understanding human behavior. By learning to identify these responses in ourselves and others, we can move past them and toward genuine solutions.

The next time you encounter a problem that seems stuck, pause and ask: Is this really a problem-solving issue, or is it a response issue? Often, the answer will surprise you.

This article is based on the analysis originally published at Improve Something Today.