{"id":135021,"date":"2024-11-12T16:24:50","date_gmt":"2024-11-12T20:24:50","guid":{"rendered":"https:\/\/www.shortform.com\/blog\/?p=135021"},"modified":"2024-11-14T16:32:01","modified_gmt":"2024-11-14T20:32:01","slug":"first-step-in-problem-solving","status":"publish","type":"post","link":"https:\/\/www.shortform.com\/blog\/first-step-in-problem-solving\/","title":{"rendered":"The First Step in Problem-Solving: Information Gathering"},"content":{"rendered":"\n

What’s holding your business back from reaching its full potential? How can you uncover the real issues that need solving?<\/p>\n\n\n\n

Richard Rumelt argues that the first step in problem-solving is thorough information gathering<\/a>. By examining situations from multiple angles and making strategic comparisons, leaders can identify core issues that might otherwise remain hidden.<\/p>\n\n\n\n

Read more to learn how to start any problem-solving process on the right foot.<\/p>\n\n\n\n\n\n\n\n

The First Step in Problem-Solving<\/h2>\n\n\n\n

Rumelt writes that the first step in problem-solving is information gathering. To gather information about your broad issue, make a list of every aspect of that issue. That includes not only the challenges it involves but also the potential solutions and the opportunities your solutions might lead to. Seek input from your executive team and any employees who may have insight into the broad issue. These tactics will help you avoid the tunnel vision that causes you to focus only on the first few problems that you think of.<\/p>\n\n\n\n

(Shortform note: You can use questioning techniques to help you gather information about your issue. In The Lean Startup<\/em><\/a>, Eric Ries describes a technique for identifying a root problem by asking \u201cWhy?\u201d five times in a row<\/a>. When you encounter a problem, ask yourself why it occurred\u2014then why that occurrence happened, and so on. This helps you move past the surface-level problems to uncover the underlying issue. Seeking input from your team and employees can help you discover these answers, but be careful to avoid assigning blame<\/a> while you gather this information, as this can distract from the process and result in unhelpful scapegoating.)<\/p>\n\n\n\n

Rumelt provides some specific tools you can use to gather information about your core problem<\/a>. These include thinking about the situation from different perspectives and using comparisons. <\/p>\n\n\n\n

Different Perspectives<\/h3>\n\n\n\n

According to Rumelt, strategists should look at the broad issue from different perspectives to reveal aspects of the issue that weren\u2019t immediately obvious.<\/strong> It can also help you uncover underlying assumptions and biases you weren\u2019t aware of, question the established way of doing things, and extend your thinking beyond current constraints and mental boundaries.<\/p>\n\n\n\n

(Shortform note: In Thinking in Systems<\/em><\/a>, Meadows explains specific ways your perspective on an issue can be constrained<\/a>. These include focusing on events and linearities, ignoring limits and delays to progress, and failing to properly grasp or apply the knowledge about an issue. To avoid these pitfalls, she recommends looking for patterns in your organization\u2019s performance over time and recognizing that changes often happen exponentially instead of linearly. She also advises that you address the most limiting factors in your issue and, if they can\u2019t be addressed, accept them and work around them. And, like other experts, she warns against assigning blame and encourages you to focus on changing the system, not the people in the system.)<\/p>\n\n\n\n

Rumelt says that, to take on a new perspective about your broad issue, you should consider the many different ways other people in different positions might view your situation.<\/strong> This includes stakeholders, employees at all levels, customers, outside analysts, and competitors. Any of these perspectives could provide you with a brand new insight that helps you crack your core problem. <\/p>\n\n\n\n

For example, imagine a retail chain that\u2019s struggling to maintain its customer base. Looking at the issue purely from the perspective of an executive, it may seem inexplicable. But, when the business asks frontline employees for input, they may discover that outdated inventory management<\/a> is causing stock issues and lost sales. This perspective adds an essential insight to the business\u2019s understanding of its overall broad issue and helps it zero in on the core problem.<\/p>\n\n\n\n

(Shortform note: Being in a leadership position can limit your perspective on the issues your company is facing. In Extreme Ownership<\/em><\/a>, Jocko Willink and Leif Babin<\/a> explain that leaders only have a high-level view of what\u2019s going on<\/a> in the company, so they need to collaborate with people at all levels to get comprehensive information about the issue they\u2019re trying to solve. This process also helps keep everyone in the loop about the issue and strategy you\u2019re formulating, so lower-level executives and employees better understand the reasoning behind what you\u2019re asking them to do.)  <\/p>\n\n\n\n

Comparisons<\/h3>\n\n\n\n

Rumelt also advises using comparisons to assess your core problem. He emphasizes that comparisons across industries, countries, or even seemingly unrelated fields can offer valuable insights into organizational issues.<\/strong> This broader scope of comparison can help identify inefficiencies, uncover hidden opportunities, and challenge long-held assumptions. By comparing situations or issues to similar cases in different contexts, strategists can recognize patterns that might not be apparent when they focus solely on their specific situation. <\/p>\n\n\n\n

For example, a university with declining enrollment might compare its recruitment strategies to those of tech companies attracting top talent, inspiring new approaches to student outreach and program design.<\/p>\n\n\n\n

Consider the following comparisons you could make:<\/p>\n\n\n\n