Dietmar Sternad’s Solve It! turned out to be a game-changer for me. I went into the book expecting a somewhat formulaic approach to solving problems—probably some basic theories or methods I’d heard before. But I was wrong. The book dives into a structured, actionable system for approaching problems in a logical way that I found incredibly applicable not just to my work life, but also to everyday situations. Sternad presents problem-solving as a skill anyone can develop, but what makes it stick is how tangible and relevant his strategies are.
Key Points: The Solve It! System
Dietmar introduces what he calls the “Solve It!” system, a step-by-step guide designed to approach complex problems systematically. The structure is centered around three core steps: Understand, Plan, and Solve, which seem simple enough, but each step has layers of practical detail. Let me break down how it played out for me and why it stuck.
1. Understand: Defining the Problem
One of the first things Sternad emphasizes is the importance of really defining the problem. Too often, we rush into solutions without fully understanding the problem, and this can lead to wasted time, resources, and effort. Sternad asks us to “frame” the problem—this involves asking the right questions, gathering data, and looking at the issue from different perspectives.
This concept stuck with me because I’ve been guilty of diving into solutions too quickly. For example, at work, we had a project where sales were declining on a particular product. Initially, our team thought it was just a pricing issue and began brainstorming ways to adjust pricing to improve sales. However, applying Dietmar’s method, we took a step back to truly define the problem. After looking deeper into the data (something I hadn’t done enough of in the past), we realized that the problem wasn’t the price but poor online visibility. This small shift in our understanding of the problem led us to focus on SEO optimization and digital marketing rather than pricing, which ultimately led to a 15% increase in sales after three months—a metric-driven result I was proud of.
2. Plan: Developing a Structured Approach
Sternad doesn’t just stop at understanding the problem. The next step is about planning—a process he breaks down into smaller actions such as identifying goals, brainstorming potential solutions, and evaluating risks and trade-offs. This planning step really connected with me, especially because it’s so often skipped. At work, I’ve seen projects fail because they moved straight from problem identification to solution without a clear plan in place. Sternad uses metrics like the “effort vs. impact” framework to evaluate solutions, which really resonated with me. The idea is to prioritize high-impact, low-effort solutions first, which makes a lot of sense when resources are limited.
An example Sternad gives is about a team working on a time-sensitive project with limited budget and workforce. They brainstormed ideas and decided to pursue one that required the least amount of development time but promised the highest user impact. After measuring the results, they found a 30% improvement in user satisfaction with just minimal additional resources. This kind of metric-driven example makes it clear how important the planning stage is.
3. Solve: Implement and Iterate
Finally, there’s the execution phase, which is where Sternad’s focus on adaptability really shines. The Solve It! system doesn’t just push for rigid, one-time solutions. Instead, he advocates for continuous iteration and improvement. I liked his analogy of treating problem-solving like a scientist conducting experiments—test your solution, collect data, learn, and refine. This approach removes the pressure to get it right the first time, and I think that’s a mindset shift many of us need.
Personally, I’ve seen the benefits of this iterative approach. We had implemented a new software tool at work to streamline our customer onboarding process. Initially, the tool caused more confusion than benefits because it was too complicated for the team to use efficiently. However, instead of scrapping it, we applied Sternad’s iterative method by making small, data-driven tweaks based on feedback from our users. Over time, usage improved by over 25%, and our onboarding time dropped by 10%, both measurable improvements that validated the solution.
Real-World Application: The Structured Approach
One of the best things about Solve It! is how practical and easy it is to apply to real-world problems. Sternad isn’t just dealing with theory—he provides detailed examples, case studies, and even prompts for readers to apply the framework to their own situations. In one part of the book, he discusses how a nonprofit organization used the Solve It! approach to address a fundraising issue. They initially thought they needed to raise awareness, but after diving into the data, they found that their donor retention was the real problem. This prompted a shift in their focus toward improving donor communication and engagement, leading to a 20% increase in donor retention within six months.
This example made me think of my own challenges at work—where sometimes it’s tempting to focus on flashy solutions without addressing the real root causes. For instance, in the past, we tried to introduce a new customer feature that we thought would increase engagement. But after running Sternad’s structured analysis, we realized the real issue was customer support bottlenecks during peak hours. Solving that issue with better staffing and support led to a 12% improvement in customer satisfaction scores—something we wouldn’t have achieved without taking the time to understand the true problem first.
The Power of Problem-Solving Metrics
Another thing that really hit home was Sternad’s emphasis on tracking metrics at every stage of problem-solving. He points out that you can’t improve what you don’t measure, and this is something I’ve taken to heart. Whether it’s tracking the time it takes to solve a customer issue, measuring the impact of a new workflow on team productivity, or looking at changes in user satisfaction, these numbers are the concrete evidence you need to know if you’re on the right track.
For instance, we started measuring the number of support tickets closed per week after improving our onboarding process. Within a few months, our ticket closure rate increased by 18%, and that’s the kind of data that not only validates your solution but also helps justify it to stakeholders. Metrics give you confidence that the changes you’re making are moving the needle in the right direction.
Final Thoughts
If you’re someone who regularly faces complex problems at work or even in personal life, Solve It! is a must-read. Dietmar Sternad manages to present a framework that is not only practical but also incredibly intuitive. His examples, case studies, and emphasis on measurable outcomes make this book both relatable and actionable. I’ve already applied the Solve It! system to various aspects of my work, and the results—whether it’s an improvement in efficiency, reduced errors, or enhanced customer satisfaction—have been clear and measurable.
What I appreciate most about this book is its down-to-earth approach. It doesn’t overcomplicate problem-solving with jargon or abstract theories. Instead, it focuses on real-world application and emphasizes metrics that show progress. If you’re tired of firefighting and want a structured way to tackle your toughest challenges, Solve It! is a practical guide that will help you turn problems into opportunities for growth and success.
