Capítulo 1
The Problem-Solving Revolution: How to Tackle Business's Toughest Challenges
Have you ever wondered why some of the brightest minds in business make catastrophic decisions? When Dell's performance plummeted in 2007, most observers quickly blamed CEO Kevin Rollins-a classic case of jumping to conclusions without proper analysis. This tendency to create coherent narratives from incomplete information isn't just a business problem; it's fundamentally human. The book "Cracked It!" has become a cult favorite among management consultants and business strategists precisely because it addresses this universal challenge. Endorsed by executives from McKinsey, BCG, and Bain, it's considered required reading at top MBA programs worldwide. What makes this methodology so powerful is that it bridges the gap between academic theory and practical application, offering a systematic approach to problem-solving that's both rigorous and adaptable to real-world complexities.
Capítulo 2
The Mental Tug-of-War: Fast vs. Slow Problem Solving
Our brains have two competing approaches to tackling problems. "System 1" thinking-fast, automatic, and unconscious-quickly constructs coherent narratives through association. When Dell's stock price fell in 2007, this system immediately blamed CEO Kevin Rollins. But this fast thinking often misses crucial information. Maybe Dell's troubles stemmed from shifting customer preferences away from customization, strategic disagreements with founder Michael Dell, industry consolidation through HP's acquisition of Compaq, or problems that began before Rollins's tenure.
"System 2" thinking, by contrast, is slow, deliberate, and effortful. It searches for missing information, questions assumptions, and applies analytical frameworks. This mental tug-of-war creates a fundamental tension in problem-solving: avoid both Othello's hasty conclusions and Hamlet's analysis paralysis.
What makes this challenge particularly tricky is that expertise can become a liability. Within their domains, experts possess rich mental models and recognize patterns effectively. However, when facing problems outside their expertise, experts often perform worse than novices. Their mental models become rigid, they grow overconfident, and they develop poor solutions based on superficial analogies. This explains why a brilliant engineer might struggle with marketing challenges or why a finance expert might mishandle organizational problems.
Complex business problems are typically ill-defined, non-routine, and involve many interrelated causes. They contain "unknown unknowns"-uncertainties we're not even aware of. The more we're unaware of the factors producing a problem, the more likely we'll be surprised when our solutions fail. This is why over 40% of startup failures stem from insufficient market acceptance-developing offerings that don't effectively solve customers' problems.
Intelligence alone isn't enough either. While IQ explains about one-fifth of problem-solving effectiveness variation, over 80% is determined by other factors. This explains why consulting firms invest heavily in building problem-solving skills beyond just hiring smart people. As organizations increasingly rely on fluid, cross-functional teams, the ability to solve complex problems becomes essential for career success.
Capítulo 3
The Five Deadly Pitfalls of Problem Solving
Even experienced professionals fall into common traps when tackling complex problems. Through compelling case studies, we can see how these pitfalls derail even the most sophisticated organizations.
The music industry's catastrophic response to digital disruption perfectly illustrates the first pitfall: flawed problem definition. When Napster exploded onto the scene in 2000, record companies framed their challenge as "How do we stop illegal file-sharing to protect CD sales?" This narrow framing led them to fight unwinnable battles while missing business opportunities. Meanwhile, Apple asked a different question: "How can we make money in a world where technology is changing music distribution?" This reframing led to iTunes and the iPod, generating billions in revenue while the traditional music industry lost two-thirds of its value.
The Grameen-Danone yogurt venture in Bangladesh demonstrates the second pitfall: solution confirmation. Despite their noble goal of addressing childhood malnutrition, the partnership fell into the trap of starting with their existing capabilities rather than analyzing the problem first. They assumed Grameen's distribution system could be replicated and that Danone's yogurt was the answer. The venture struggled with fundamental flaws-yogurt required refrigeration in a country lacking cold-chain infrastructure, milk was too expensive for poor communities, and consumers treated it as an occasional treat rather than nutritional supplement. They never seriously considered alternatives like ready-to-use therapeutic food (RUTF), which requires no refrigeration and has helped thousands of African children.
The third pitfall involves adopting frameworks with hidden, questionable assumptions. In one case, an HR director at a call center was offered a personality assessment tool to reduce turnover. The solution relied on the assumption that "job tenure is a function of personality" while exit interviews revealed that "job tenure is driven by multiple factors, including job satisfaction." This cognitive trap, known as "the law of the instrument," reflects our tendency to see everything through the lens of our preferred tools.
Ron Johnson's disastrous tenure at J.C. Penney illustrates the fourth pitfall: narrow framing. Johnson applied Apple's retail playbook to Penney's without understanding why customers were dissatisfied. He eliminated popular coupons and implemented nationwide changes without testing, scoffing "We didn't test at Apple." Sales plunged by $4.3 billion, and Johnson was ousted after just 18 months.
The final pitfall involves miscommunication. British scientist John Yudkin discovered in the 1950s that sugar-not fat-was the primary cause of obesity, diabetes, and heart disease. Despite publishing his findings, his research was largely ignored until 2009. For 40 years, nutritionists focused on reducing fat consumption while the food industry quietly loaded products with harmful sugar. This massive error persisted because Yudkin's rival Ancel Keys was charismatic and politically connected, placing allies in key healthcare positions to direct research funding. Being right isn't enough-solving a problem is worthless if you can't convince decision-makers to adopt the solution.
Capítulo 4
The 4S Method: A Systematic Approach to Complex Problems
To overcome these pitfalls, the 4S method-State, Structure, Solve, and Sell-offers a systematic approach to problem-solving. This method combines hypothesis-driven thinking, issue-driven approaches, and design thinking into a pragmatic framework.
The method has its roots in the Problem-Solving Approach of Consulting (PSAC) developed by prestigious strategy consulting firms like McKinsey & Co. This practical approach combines Aristotelian logic and Cartesian method with modern critical thinking practices, assuming that facts are objective, causal links can be established, and logical reasoning can lead to verifiable conclusions.
The 4S method addresses two limitations of traditional consulting approaches. First, hypothesis-driven problem-solving faces challenges from confirmation bias-our tendency to seek evidence confirming our hypotheses while ignoring contradictory information. Second, some problems resist mechanical application and require creative approaches. This is where design thinking becomes valuable, particularly for problems that are poorly understood, hard to structure logically, or require active idea generation.
The flowchart for the 4S method may initially seem complex, but it guides problem solvers to select the most appropriate path for their specific situation. Consider Tracy, a new CEO joining Solar, a family-owned industrial company with two money-losing business units. Management has conflicting views: some believe the problems are temporary market conditions, others see fixable operational issues, while a third group advocates selling or closing the struggling units. Tracy must determine the best course of action and convince the Board of her solution.
In the "State" phase, Tracy would use the TOSCA framework to define the problem: Trouble (financial losses), Owner (Tracy), Success criteria (what will success look like?), Constraints (limitations on solutions), and Actors (stakeholders). This comprehensive problem statement would help her avoid the music industry's fatal mistake of misframing the challenge.
For the "Structure" phase, Tracy could choose between hypothesis-driven and issue-driven approaches. If she hypothesizes that Solar should sell the struggling units, she would build a hypothesis pyramid to test this solution. Alternatively, she could create an issue tree to systematically examine different facets without preconceived notions of solutions.
The "Solve" stage follows three possible routes depending on the approach chosen in the Structure phase. Tracy might test her hypothesis through analysis, explore an issue tree that breaks the problem into discrete parts, or use design thinking to generate fresh solutions when analytical approaches stall.
Finally, in the "Sell" phase, Tracy would need to convince the board to approve her plan by switching from problem-solving mode to communication mode. This requires developing a clear core message and supporting arguments using the pyramid principle, which starts with the governing thought followed by supporting points in a logical structure.
Capítulo 5
TOSCA: The Art of Problem Definition
The first S in the 4S method is "State the problem." Unlike Puccini's opera Tosca, where the protagonist faces a crystal-clear dilemma, most business problems lack sharp definition. The TOSCA framework helps clarify problems by addressing five critical elements:
Trouble represents the gap between observation and aspiration-the dissatisfaction that drives problem-solving. When defining trouble, focus on specific symptoms rather than interpretations, and ask "why now?" to understand urgency. Vague complaints like "creating a results-oriented culture" aren't solvable troubles; "20% of customer calls remain unanswered" is.
A critical distinction: trouble isn't diagnosis. While medical problems fit into pre-existing categories with standard treatments, complex business problems often don't. The music industry's fatal mistake was misdiagnosing file-sharing as traditional piracy. Unless you're confident in your diagnosis, stick to describing symptoms without leaping to conclusions about causes.
Identifying the problem owner is crucial because it shapes both the solution space and success criteria. The owner ultimately judges whether a problem statement and solution are "good enough." Without knowing who's on the hook to solve the problem, you can never properly define or solve it.
Success criteria push beyond the initial "trouble" to uncover what the owner truly wants. Despite our results-oriented mindset and the mantra "bring solutions, not problems," properly defining a problem requires temporarily ignoring possible solutions.
Constraints limit potential solutions and come in three types: constraints on success criteria (conflicts with other objectives), constraints from the owner's resources and capabilities, and constraints on the problem-solving process itself (time, budget, confidentiality).
Actors are stakeholders with different objectives who react dynamically to recommendations. Understanding their objectives and stakes is indispensable to defining the problem completely.
After completing these steps, formulate your core question-not a statement like "We must stop piracy," but an actual question. The essential choice is question scope. You can frame closed questions ("Should we launch a music download service?") or open ones ("How can we stop piracy?"). The harder the problem and the earlier in the process, the more appropriate a broader scope becomes.
Capítulo 6
Structuring Complex Problems: Pyramids and Trees
After defining the problem, the next step is structuring it effectively. Consider Librinova, a French digital self-publishing platform launched in 2014. By 2018, with over 1,000 writers and 40 books picked up by publishers, investors were pushing Librinova to expand internationally-despite publishing being essentially a domestic industry with few cross-country synergies due to linguistic and cultural differences.
Using the TOSCA framework, we define the problem: The CEO needs a viable international expansion strategy that satisfies investor pressure while working within the constraints of limited resources and the domestic nature of publishing. The core question becomes: Which international expansion strategy-when, where, and how-should Librinova use to respond to shareholder pressure?
When working with a potential solution as your starting point, you build a hypothesis pyramid from the top down. Start with your leading hypothesis and break it down into sub-hypotheses that are necessary conditions for it to be true. For Librinova, the leading hypothesis "Librinova should collaborate with De Marque to launch a sister platform in Canada" breaks down into necessary conditions: Canada must be an attractive market, collaboration must be the best entry mode, De Marque must be a good partner, and this must be the best available option.
Hypothesis-driven problem structuring offers efficiency benefits but comes with significant risks. It's highly efficient when starting from sound hypotheses, conserving resources by focusing efforts on candidate solutions. However, hypotheses immediately narrow your problem frame, creating self-inflicted "narrow framing" where alternatives remain unexplored. Confirmation bias becomes a serious risk-even experienced problem solvers tend to seek information that validates rather than challenges their hypotheses.
Issue-driven problem structuring provides an alternative approach. Unlike the hypothesis-driven approach, it seems more mundane but requires greater time, thoroughness, imagination, and critical thinking. Issue trees consist of questions rather than hypothetical statements. Each branch bears a question divided into finer-grained questions on thinner branches, making them analytically searchable.
For narrowly defined problems, especially "yes or no" issues, hypothesis-driven and issue-driven approaches are nearly equivalent. However, in most situations, using an issue tree as the "default choice" helps avoid common traps and reach more insightful conclusions, even when you already have candidate solutions in mind.
Capítulo 7
The Power of Analytical Frameworks
Frameworks provide prepackaged, MECE (Mutually Exclusive, Collectively Exhaustive) breakdowns of typical problems, serving as invaluable shortcuts when structuring complex questions. They function as building blocks for issue trees and hypothesis pyramids, much like LEGO bricks that skilled problem solvers combine. These frameworks have evolved through decades of business practice and consulting experience, distilling common patterns into reusable templates that accelerate analysis.
For example, the classic Porter's Five Forces framework examines competitive intensity through supplier power, buyer power, competitive rivalry, threat of substitutes, and threat of new entrants. Similarly, the 4Ps marketing framework (Product, Price, Place, Promotion) provides a comprehensive lens for analyzing marketing strategies. Each framework offers a distinct perspective and analytical approach.
However, frameworks come with an important warning: they assume the question is generic and belongs to a class for which the framework was designed. Using a framework means adopting the mental model of a function or industry, including all its underlying assumptions. This can be dangerous if the situation doesn't fit the framework's core assumptions or if unique circumstances require a different approach.
When analyzing whether a private equity firm should invest in Company X, a stock analyst and PE investor apply different frameworks reflecting fundamentally different worldviews. The stock analyst's framework assumes prices correctly reflect company prospects and public information, focusing on market multiples, earnings growth, and relative valuations. In contrast, the PE investor assumes management actions create value and that new ownership can improve performance through additional interventions, examining operational improvements, strategic repositioning, and financial engineering opportunities.
Industry frameworks reflect value drivers-the key levers of value creation in a business. For retailers like Starbucks, this means examining metrics like comparable store sales growth versus new store openings, customer acquisition costs, average ticket size, and potentially exploring alternative business models beyond retail stores. A restaurant framework might focus on table turnover, food costs, and labor efficiency, while a software company framework emphasizes customer lifetime value, churn rates, and R&D productivity.
When lacking industry-specific knowledge, experienced businesspeople can still approach problems using functional frameworks from marketing, finance, or other disciplines. The balanced scorecard framework, for instance, provides a general approach to performance measurement across financial, customer, internal process, and learning/growth perspectives. The BCG growth-share matrix offers insights into portfolio management regardless of industry context.
When no ready-made framework fits your problem, logical decompositions can fill the gaps. Simple logical splits like "these/others," "old/new," "past/present/future," or "inside/outside" can help structure problems when specialized frameworks don't apply. These basic organizing principles can be combined with industry knowledge to create custom frameworks tailored to unique situations. The key is maintaining MECE principles while adapting to the specific context of the problem at hand.
Capítulo 8
Design Thinking: When Traditional Analysis Falls Short
For problems that resist traditional analytical approaches, design thinking offers a powerful alternative. This human-centered approach is particularly valuable when problems are poorly understood, hard to structure logically, or require active idea generation.
Doug Dietz, an industrial designer at GE Healthcare, transformed pediatric MRI experiences using design thinking. After witnessing a child's fear of his award-nominated MRI machine, Dietz reframed the problem from "how to maximize child patient scans while reducing anesthesia costs" to "how might we turn MRI scans for children into an adventure?" Through deep user empathy and observation, Dietz and his team created the GE Adventure Series-themed MRI installations that dramatically reduced sedation rates from 80% to as low as 10%, increased patient satisfaction, and boosted scan efficiency.
Design thinking consists of five iterative phases: Empathize, Define, Ideate, Prototype, and Test. The process is built on alternating between divergent thinking (creating options) and convergent thinking (making choices) across all phases. It requires moving between concrete realities of users and abstract conceptual models, as well as between analysis of data and synthesis of solutions.
Empathy forms the foundation of design thinking, with results from this phase informing all subsequent steps. The task is to understand the people for whom you're designing-their physical and emotional needs, constraints they face, current solutions, context, and overall experience. Empathizing consists of three broad activities: observation, engagement, and immersion.
Rather than focusing solely on average users, design thinkers seek out extreme users who fall at the tails of the distribution. These atypical users often develop workarounds and hacks that reveal unmet needs and opportunities for innovation. The OXO Good Grips kitchen tools exemplify this approach-by designing for people with arthritis (extreme users), they created products that worked better for everyone.
The Define phase transforms concrete observations into abstract representations by identifying patterns in data and extracting valuable insights about users. This phase bridges empathy work to solution development by synthesizing qualitative information into coherent models like empathy maps, journey maps, and user personas.
Capítulo 9
From Problem Solving to Solution Selling
After finding a solution and conducting supporting analyses, you need to persuade the problem owner to take action. This requires a different mindset-instead of digging deeper into the problem, you must understand how your solution fits into the problem owner's context.
A common mistake is telling the story of your search process rather than presenting a clear solution. Decision-makers don't want to follow your detective work; they need a straightforward recommendation with compelling reasoning. The "pyramid principle" offers an effective structure for this communication challenge.
Barbara Minto, a former McKinsey consultant, developed the pyramid principle based on a fundamental insight: people understand and remember ideas better when organized in coherent patterns. For business recommendations, Minto advocates a top-down pyramid structure that starts with the core message (the "governing thought"), followed by supporting arguments (the "key line") that announce the plan.
Starting with your governing thought and main points is critical for effective solution selling. Unlike saving a punchline for the end of a speech, your core message should be stated upfront to initiate dialogue. It functions as a directional compass, driving conversation rather than ending it.
When structuring your storyline, choose between two fundamental patterns: grouping or argument. A grouping pattern presents points of the same kind that collectively support the core message, with each point independently supporting the recommendation. The argument pattern follows a linear reasoning from premises to conclusions, with each point logically connected to the prior point. The most common argument structure is "situation-complication-(question)-resolution" (SCR), where you start with the triggering situation, explain complications, optionally reframe the question, and provide a resolution that solves the problem.
Once you've crafted a compelling core message and pyramidal storyline, bring your story to life by developing a written and visual presentation. Your report typically serves dual purposes: a slide deck for oral presentation and a written document for future reference. Rather than creating separate documents for these purposes, build a modular document that mirrors your storyline.
Content pages form the majority of your report, supporting key points with analytical results. Each page should feature three main components: an action title that conveys the message as a complete sentence, a tracker indicating the specific point in the storyline, and the content itself illustrating the analytical finding.
Capítulo 10
Mastering the Art of Problem Solving
While some believe AI will eventually solve all problems from mundane to vital, complex problems require human framing, structuring, and critical assessment that AI cannot replace. Though technology will assist problem-solving as calculators and computers have done, humans remain essential for identifying problems, structuring approaches, interpreting evidence, imagining novel solutions, and convincing decision-makers to implement them. The unique human ability to recognize patterns, draw from diverse experiences, and apply contextual understanding makes us irreplaceable in the problem-solving process.
Problem-solving skills require practice, just like riding a bike. Business environments provide abundant opportunities to develop these skills through daily challenges. Start with small, familiar problems to practice structuring them properly-identify the Trouble (what's wrong), Owner (who's responsible), Success criteria (what does winning look like), Constraints (what limits us), and Actors (who's involved). For instance, when addressing a decline in customer satisfaction, clearly define the specific issue, identify the department head accountable, establish measurable improvement targets, understand budget limitations, and map out all stakeholders.
For communication skills, try building simple storylines for routine emails or progress reports. Practice the pyramid principle: start with the conclusion, followed by key supporting arguments, then detailed evidence. When reporting monthly sales performance, lead with the main message (e.g., "Sales exceeded targets by 15%"), support with key drivers (new customer acquisition, higher repeat purchases), and back with specific data points.
The most effective practice happens in teams, where colleagues can provide feedback and detect flaws in your reasoning. Regular problem-solving sessions, case study discussions, and post-project reviews create opportunities for collective learning. Master problem solvers aren't necessarily smarter or more creative-they've simply mastered these tools through practice, becoming comfortable with multiple approaches and frameworks while remaining open to revisiting solutions when new facts emerge. They also recognize that different problems require different approaches, from quick tactical fixes to comprehensive strategic solutions.
The 4S method-State, Structure, Solve, and Sell-provides a systematic approach to overcome the common pitfalls in problem solving. State involves clearly defining the problem and its scope. Structure requires breaking down complex issues into manageable components and identifying key relationships. Solve focuses on gathering and analyzing relevant data to generate solutions. Sell ensures solutions are communicated effectively to stakeholders and implemented successfully. By properly defining problems, structuring them effectively, applying appropriate analytical techniques, and communicating solutions persuasively, you can tackle even the most complex business challenges with confidence and clarity. Regular application of this method helps develop a consistent, reliable approach to problem-solving across various business contexts.
