A good introduction and manual towards business problem-solving, from a consulting perspective. What does that mean? Consultants (mostly) assume all problems can be solved in a finite amount of time, and that they can actually be "solved" in some formal way. Often times if that is not the case, a savvy partner will find some way to quietly extricate his team out of the project. Not all business "problems" can be solved, and many never are, as like the proxy-wars great powers engage in with each other, many business problems in corporate America are often battles played by senior executives, vying for turf.
That being said, if one were to try to consult a company on a "challenging" problem, this is the closest thing I've read thus far, to a book on strategy-consulting, with a "quantitative" tint. Each of the major consulting companies often provide "the deck" to their new recruits, usually 100s of slides, that include principles and tutorials on how to engage in analysis of a client-problem. Though often times these decks just end up being plot/graph-fodder, recycled in any number of stylistic permutations for hastily produced client presentations. Although, each of these firms have their own "style", they often all share a "kernel" of notions that constitute the essence of the craft.
This book covers much of that essence, including the problem-definition cycle, which is to define, dis- aggregate, prioritize, analyze, synthesize, communicate, with the critical components (from an analytical standpoint) being dissaggregation, analysis, and synthesis. With respect to dissaggregation, any consultant worth their salt will have partitioned their problem-space into MECE or "Mutually Exclusive and Collectively Exhaustive". This notion was almost certainly "leveraged" (stolen) from mathematics, which knows it as set-partitions, an idea that comes in handy in probability, combinatorics, and topology to name a few of the sub-fields in the subject.
However, form a business standpoint, as the authors stresses, how one dissaggregates, or "cleave", a problem, could hold the entire key to proceeding forward to it's solution, and they give several good business case studies to accentuate that point, as well as conceptual principles to provide deeper understanding to allow the reader to "leverage" it for their own challenges. In aid of this endeavor, the authors also provide ample illustrations and explanation on several types of logic trees, including component-trees, inductive-trees, deductive-trees, hypothesis-tress, and decision-trees. Of these, inductive and deductive trees are given the most page-count in terms of coverage. Again, concepts are often followed or prefaced with business-case studies to help apply theory to practice.
Since this book is primarily aimed at business people, beside the analytic component of 'strategy", there's about 1/3 of the material dedicated to "team-stuff". Basically, how to rustle your team, and "leverage" the collective intelligence of your team to make decision and assign priority/weight to components of your "cleaved" problem to quickly, and practically, resolve it for your client (so you can get follow-on work).
Ironically, the least developed portion of the problem-solving cycle is probably the analysis portion, which is where the actual work would take place from the "problem solving" standpoint (e.g. statistics/machine learning/model/simulation etc.). A quick whirlwind tour is provided on the techniques and how they can be deployed based on what you know, what you don't know, what you know you don't know, and what you don't know that you know (to quote infamous former Secy. of Defense, and systems-analyst 'whiz-kid' Don Rumsfeld)
Overall, well-written, and concise, with sufficiently produced tables for efficient knowledge-transference. I'd recommend both the audiobook and the kindle for this one, like all consulting work, the plots are 4/5 the information. Recommended