Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Strategic Problem Solving

Strategic Problem Solving

A Step-by-Step Guide to Solve Hard Problems: Leverage Data Analysis and Critical Thinking to Make Smart Decisions, Drive Innovation, and Lead with Confidence
Turn messy challenges into decisions your team can execute, without letting analysis stall the work.
by Mark Hartley 2024 143 pages
3.78
103 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Run hard problems through seven deliberate stages, not a burst of improvisation

Give the work an order. Hartley’s central method moves from defining the problem to breaking it into parts, ranking priorities, planning the work, analyzing evidence, communicating the recommendation, and supporting implementation. The sequence begins with a stalled project that left a young executive and his team frustrated. His lesson: a capable team can still flounder without a shared way to move from confusion to action.

Treat the sequence as a map. A clear problem definition shapes what gets divided; the division informs priorities; priorities determine the plan. The later stages turn analysis into an understandable proposal, then into assigned work with resources and support. The process can be used for workplace challenges or personal decisions, from a project launch to household budgeting.

Analysis

The framework’s strength is not that it guarantees a right answer, but that it makes skipped thinking visible. Teams often leap from a vague complaint straight to a favored fix, then mistake activity for progress. A staged process creates checkpoints where assumptions can be tested before they become expensive commitments. Its sequence should not become a bureaucratic ritual, however. New evidence can change the problem itself, so the steps work best as a repeatable loop, not a one-way conveyor belt.

Define the failure precisely before spending money fixing its symptoms

Ask what is really broken. The 5 Whys technique investigates a problem by repeatedly asking why it occurred, aiming to move from a visible symptom toward an underlying cause. A manufacturer initially blamed worn equipment for repeated failures; asking why revealed inadequate maintenance schedules. Changing the schedule addressed the source more directly than simply replacing machinery.

Widen the search when needed. A Fishbone diagram organizes possible causes into categories, helping a group examine several explanations at once. For declining customer satisfaction, branches might include staffing, product quality, and service. Surveys, interviews, and operational data add evidence from people affected by the problem. The right tool depends on the issue: a simple fault may need a short inquiry, while a complicated one calls for broader investigation.

Analysis

This emphasis resembles diagnosis in medicine: treating a symptom can help briefly, but durable improvement depends on understanding its cause. The book’s techniques also make disagreement useful by giving teams a shared surface for testing explanations. Still, a chain of why-questions can become an oversimplified story, especially when many conditions interact. A Fishbone diagram generates possibilities, not proof. Strong problem definition distinguishes observed facts from hypotheses, then checks those hypotheses against data and the experience of affected people.

Turn a tangled challenge into connected pieces, not isolated to-do lists

Make complexity visible. Disaggregation means dividing a large problem into smaller components that can be examined and acted on. A mind map places the central issue in view and branches into related causes, options, or stakeholders. A flowchart instead lays out steps and decision points in a process. Both help teams see what is involved before choosing where to intervene.

Keep the connections. A sales decline might appear to call for better marketing, until analysis shows that supply problems are preventing products from reaching customers. Breaking the problem into parts reveals that one area can constrain another. Hartley warns against both extremes: dividing too little leaves important causes hidden, while dividing too much creates disconnected tasks and obscures the overall goal.

Analysis

Breaking a problem down reduces the mental burden of holding every detail in mind, while visual maps make a team’s assumptions easier to inspect. The deeper benefit is relational: a useful map shows not only components but dependencies. This connects the method to systems thinking, which studies how changes in one part affect others. Decomposition has a risk, though. A department can optimize its own task while worsening the whole process. Teams should periodically reconnect the pieces to the shared outcome.

Rank work by impact, not by whoever sounds most urgent

Separate urgency from value. The Eisenhower Matrix sorts tasks by whether they are urgent and important. Immediate, important work gets attention first; important but non-urgent work is scheduled; urgent but less important work can be delegated; tasks that are neither can be removed. The MoSCoW method makes a similar distinction for project requirements, labeling them must-have, should-have, could-have, or out of scope for now.

Compare value with effort. RICE scoring ranks initiatives using reach, impact, confidence, and effort. In the book’s illustrative software example, customizable workflows score 400, ahead of real-time chat at 280. These methods help teams make trade-offs explicit, while quick wins can build momentum. But a quick win should support the larger goal, not distract from it.

Analysis

Prioritization is partly a protection against the loudest request winning by default. These tools expose the criteria behind a choice and help a team explain why some work waits. They also reveal an important tension: numerical scores can look more objective than the estimates used to produce them. Reach, impact, confidence, and effort may all be uncertain or politically contested. A useful ranking therefore includes the assumptions behind the score and a willingness to revise it when evidence changes.

Make the plan visible, owned, and flexible enough to survive reality

Turn intentions into commitments. A work plan translates a goal into tasks, owners, milestones, and deadlines. Hartley recommends SMART objectives: specific, measurable, achievable, relevant, and time-bound. Gantt charts show tasks across a timeline and make dependencies visible; task-flow diagrams clarify the order of work. In a product campaign, marketing, design, and sales teams can use these tools to coordinate their contributions and track progress toward launch.

Plan for disruption. Timelines should draw on past experience, account for task complexity, and include buffer time for delays. A five-day estimate, for instance, might include an extra day to absorb a minor setback. Regular check-ins allow the team to adjust without abandoning the objective. A plan is a guide for coordination, not a promise that every step will unfold exactly as expected.

Analysis

Visible plans reduce the coordination cost of teamwork: people can see who depends on whom, what is late, and where help is needed. This is particularly valuable when work crosses departments or time zones. Yet detailed schedules can create false certainty if estimates are treated as facts. A plan should distinguish fixed deadlines from uncertain forecasts and make dependencies explicit. The goal is not to eliminate surprises, which is impossible, but to detect them early enough to respond without losing sight of the intended result.

Use evidence to challenge intuition, then stop analyzing when it blocks action

Combine numbers with context. Quantitative data, such as sales figures or satisfaction scores, can show where a problem is occurring. Qualitative evidence, such as interviews or customer comments, can help explain why. A retailer could spot complaints about checkout in customer feedback, then examine the process to find where shoppers abandon a purchase. Critical thinking means checking assumptions, considering alternative explanations, and using evidence to guide choices rather than treating first impressions as conclusions.

Set a limit on analysis. The book identifies analysis paralysis as a cycle in which fear of a wrong decision prompts more data gathering and delays action. Clear decision criteria, a deadline, and a focus on essential information can restore momentum. Reflection journals and Socratic questions, such as asking what evidence supports a conclusion, help expose bias before it shapes the decision.

Analysis

The combination of numerical and descriptive evidence is valuable because measurement can locate a pattern while people’s accounts help interpret it. Neither source is neutral by itself: a metric reflects what an organization chose to measure, and a story may not represent the wider population. Critical thinking therefore means asking how evidence was collected and what it cannot show. The advice to set deadlines is equally practical, but urgency should not be used to silence legitimate uncertainty in high-stakes or difficult-to-reverse decisions.

Translate your analysis into a story stakeholders can understand and act on

Build a clear argument. A persuasive presentation gives the audience a route through the issue: establish the problem, explain the evidence, present the recommendation, and clarify what action is needed. Hartley stresses adjusting the level of detail and language to the audience. A specialist group may want a detailed analysis; a broader audience may need the main finding and its implications first.

Make the evidence usable. Charts and other visuals can make complicated information easier to grasp, while a case or narrative can show why the issue matters. The book also describes persuasion through credibility, emotional connection, and logical support. In an investor pitch, for example, a founder needs to explain the problem and proposed solution, support claims with evidence, and show why the opportunity matters to that audience.

Analysis

Communication is not packaging added after the real work. It is a test of whether the analysis can be made coherent enough for other people to evaluate and use. Audience-aware explanation lowers the effort required to understand a proposal, which can improve collaboration. But a compelling narrative can also make weak evidence feel convincing. The strongest presentation uses story to orient attention, not to replace scrutiny. It states uncertainty plainly and gives stakeholders enough information to question the recommendation as well as support it.

Give every solution an owner, resources, and a feedback loop

Make execution someone’s work. Implementation requires clear responsibilities, appropriate resources, and continuing support. Role mapping matches project tasks to people’s skills and highlights gaps before they become delays. Progress meetings, feedback, and relevant performance indicators can show whether the plan is working and where it needs adjustment. Hartley emphasizes that teams should adapt when results do not match expectations rather than cling to an ineffective initial approach.

Measure what changes. The book reports that a manufacturer applying the structured process improved operational efficiency by 30 percent. In a separate retail example, a retailer cut customer wait times in half after identifying staffing and process bottlenecks. These examples illustrate how monitoring can connect a proposed fix to an outcome. The book also recommends reviewing setbacks and successes so teams can learn instead of repeating mistakes.

Analysis

A recommendation has little practical value if no one has the authority, time, or tools to carry it out. Clear ownership turns intention into accountable action, while feedback makes implementation a source of new evidence. This is the point where strategy meets organizational behavior: incentives, capacity, and communication can matter as much as the quality of the original idea. Metrics need care, however. If teams are rewarded for one number alone, they may improve that number while neglecting service quality or other important outcomes.

Treat setbacks as information, then improve one part of your approach

Practice learning, not self-blame. Hartley uses growth mindset to describe the belief that abilities can develop through effort and learning. In his example, an entrepreneur facing investor skepticism and market setbacks treats obstacles as chances to adapt rather than proof of inability. Reflection, constructive feedback, and achievable incremental goals help turn that attitude into practice.

Make improvement continuous. Kaizen refers to pursuing improvement through small, ongoing changes rather than waiting for a sweeping overhaul. A team can review what worked, identify what failed, and adjust its next attempt. The same problem-solving habits can apply outside the workplace: someone managing personal finances might identify overspending, separate expenses into categories, prioritize changes, and agree on responsibilities with family members. The point is to use each attempt to improve the next one.

Analysis

A learning orientation supports experimentation because it makes a setback informative rather than purely threatening. Small adjustments can also make improvement easier to sustain than a grand plan that demands immediate transformation. The important nuance is that mindset alone cannot compensate for inadequate resources, poor leadership, or conditions outside an individual’s control. Treating every failure as a personal lesson can become unfair self-blame. Reflection is most useful when it asks both what a person can change and what conditions need to change around them.

Analysis

The book’s most useful contribution is its insistence that solving a difficult problem is not the same as producing a clever answer. The work includes framing the issue, organizing its parts, deciding what deserves attention, and creating the conditions for execution. This broader view helps explain why apparently smart teams can stall: they may be debating solutions to different problems, or agreeing on a recommendation without clarifying who will act on it.

The seven-stage process offers a strong teaching scaffold, especially for readers who have never used formal problem-solving tools. Its value is practical and cumulative. Root-cause techniques improve the initial question; decomposition makes complexity manageable; prioritization limits wasted effort; planning and communication connect analysis to action. The book’s examples also extend the approach beyond business, which makes the process easier to transfer to personal decisions.

Its main limitation is evidentiary. Several cases and impressive outcomes are presented without enough methodological detail to judge how the intervention produced the result, what else changed, or whether the outcome lasted. The reported 30 percent efficiency improvement and halved wait times illustrate possible value, but they do not establish that the method alone caused those gains. Readers should treat these cases as demonstrations, not guarantees.

A second limitation is the risk of making a linear method seem more orderly than real work. Problems evolve as teams learn, and stakeholders may disagree about which outcomes matter. In practice, the strongest use of the framework is iterative: define, investigate, act on a proportionate scale, observe the effects, and revise. That cycle also protects against false precision in scoring models and against measuring what is easy rather than what is important.

The book is best read as a toolkit for disciplined attention. It cannot eliminate uncertainty or substitute for expertise, but it can make reasoning visible, assumptions discussable, and responsibility clearer. Its central promise is modest and valuable: structure can reduce avoidable confusion, leaving more attention for judgment, collaboration, and adaptation.

Summary in 30 Seconds
Good solutions start with a precise problem definition, since fixing symptoms can waste resources. Breaking a challenge into connected parts reveals causes and dependencies, while ranking options by value and effort directs attention. Evidence from data and interviews can test assumptions, but decision criteria and deadlines keep analysis from delaying action. Plans need owners, resources, and feedback loops. The examples report 30 percent higher operational efficiency and customer wait times cut in half.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

7-step process

Structured problem-solving sequence

A seven-stage method for moving from a clearly identified problem to action. It involves defining the issue, breaking it into components, prioritizing, planning, analyzing, communicating the recommendation, and supporting implementation. Each stage informs the next, while new information may require revisiting earlier decisions.

5 Whys

Repeated cause investigation

A root-cause inquiry that asks why a problem occurred, then asks why again about each answer. Repeating the question is intended to move beyond a visible symptom toward an underlying cause. It is most useful for relatively straightforward problems and should be checked against evidence rather than treated as proof by itself.

Fishbone diagram

Map of possible causes

A visual tool, also called an Ishikawa diagram, that organizes possible contributors to a problem into branches or categories. A team investigating low customer satisfaction might examine staffing, product quality, and service as separate branches. The diagram supports broad, collaborative hypothesis generation, but does not establish which cause is correct.

Eisenhower Matrix

Urgency and importance sorter

A prioritization tool that places tasks into four groups according to whether they are urgent and important. It directs immediate attention to tasks that are both, schedules important but non-urgent work, delegates urgent but less important work, and removes tasks that are neither. The purpose is to distinguish genuine priorities from mere urgency.

MoSCoW method

Project requirement ranking

A method for sorting project requirements into must-have, should-have, could-have, and will-not-have-for-now categories. It helps a team establish what is essential for a project phase and what can be delayed or excluded. The method is especially useful when limited time or resources make it impossible to deliver every desirable feature.

RICE scoring model

Value compared with effort

A prioritization model that scores initiatives using reach, impact, confidence, and effort. Reach estimates how many people are affected, impact estimates the effect, confidence reflects certainty in those estimates, and effort represents required resources. The book calculates a score by multiplying reach, impact, and confidence, then dividing by effort.

SMART criteria

Goal-setting checklist

A checklist for shaping objectives so they are specific, measurable, achievable, relevant, and time-bound. Applying these criteria clarifies what a project aims to accomplish, how progress can be assessed, and when the result is expected. The criteria make goals more actionable, though teams still need to ensure that chosen measures reflect meaningful outcomes.

logic tree

Visual breakdown of choices

A branching diagram that divides a central problem into major elements and then into more specific factors, decisions, or outcomes. It helps teams examine alternatives systematically, identify missing considerations, and see possible pathways. Logic trees make complex reasoning easier to discuss, but their usefulness depends on whether the branches capture the relevant possibilities.

Kaizen

Incremental ongoing improvement

A Japanese term used in the book for continuous improvement through small, repeated changes. Rather than relying only on major overhauls, a team reviews its work, learns from results, and makes adjustments over time. The approach supports a learning culture in which improvement is part of routine practice.

Download PDF

To save this Strategic Problem Solving summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.28 MB     Pages: 16

Download EPUB

To read this Strategic Problem Solving summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.32 MB     Pages: 18
Want to read the full book?
Follow
Listen2 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...