Audiobook Summary and Review by StoryShots
A problem without a number is just a complaint.
Most people attack problems the moment they appear.
They brainstorm solutions, debate options, and implement fixes without understanding what they're actually solving.
That reactive approach wastes time and often makes things worse.
Practical Problem Solving by Nerrad Draw offers a structured framework: define the problem with precision before you touch any solution.
Most problem-solving fails at step zero because people confuse symptoms with root causes.
The team misses deadlines.
That's a symptom.
The root cause might be unclear priorities, inadequate resources, or a broken approval process.
The fix starts with a disciplined definition phase: write the problem as a single sentence, then ask "why?"
five times.
Each answer peels back a layer.
By the fifth why, you're staring at the real issue.
The problem you think you're solving right now is probably not the actual problem.
"If you can't write the problem in one clear sentence, you don't understand it yet."
The real work happens in those five why questions.
Once you've defined the problem, most people skip measuring the gap between current state and desired state.
Without measurement, you're guessing.
Every solvable problem has at least one quantifiable dimension.
Time, cost, quality, frequency, or impact.
Pin down the number.
How much time does the broken process waste per week?
How many customers does the bug affect?
Measurement proves the problem is worth solving and gives you a baseline to judge whether your solution actually worked.
You're likely spending energy on problems you can't prove matter.
"A problem without a number is just a complaint."
Quantifying the gap turns vague frustration into actionable insight.
Most brainstorming sessions fail because they mix two incompatible goals: generating ideas and judging ideas.
Separate them into distinct phases.
Phase one is pure divergence.
No criticism allowed, no immediate practicality filters.
Your only job is volume.
Aim for twenty solutions minimum, even the absurd ones, because wild ideas often contain the kernel of breakthrough thinking.
Phase two is convergence.
Now you apply filters: cost, time, risk, alignment with goals.
You rank solutions against your measurements from step two.
The best solution is not the most creative one.
It is the one that closes the gap most effectively with the resources you have.
This two-phase discipline prevents premature rejection of good ideas and prevents wasting time on clever ideas that don't solve the measured problem.
"Bad solutions come from good ideas evaluated too early."
Most teams collapse these phases into one chaotic meeting where the loudest voice wins.
If you know someone navigating a persistent challenge at work, send them this summary.
This summary of Practical Problem Solving by Nerrad Draw threads together problem definition through iterative questioning, gap measurement to establish baselines, and phased solution generation into a single structured approach.
The full framework covers how to build stakeholder alignment before proposing solutions, how to prototype fixes without committing full resources, and how to conduct post-mortems that actually improve your process.
Real case studies show teams using this method to solve problems that stumped them for months.
If you manage a team or lead projects, this book offers a repeatable system.
We're putting together the full summary of Practical Problem Solving right now, with a visual infographic and animated video.
Follow the book in the StoryShots app to get it the moment it's ready.