Israeli intelligence had the attack plan for October 7 and called it "totally imaginative." Credit rating agencies had the loan data before 2008 and stamped it AAA. Nokia's engineers saw the iPhone threat and were told their concerns weren't supported by the data. A pressure gauge on the Deepwater Horizon read 1,400 psi when it should have read zero, and the crew talked themselves into ignoring it.
Every organization runs on a set of assumptions about how its world works. Those assumptions decide what gets measured, who gets heard, and which warnings get taken seriously. When the assumptions are right, the organization looks brilliant. When they stop being right, the people closest to the problem usually know first. They raise alarms. The alarms get absorbed into a prevailing model and come back out as reassurance.
This book traces that pattern across case studies spanning intelligence, finance, technology, industrial safety, and national security. It explains why the pattern keeps recurring, because successful organizations build their operations, metrics, and career incentives on top of assumptions that become too expensive to question. In the book, we force every strategic question through competing analytical perspectives and pay attention when they disagree.
Israeli intelligence had the attack plan for October 7 and called it "totally imaginative." Credit rating agencies had the loan data before 2008 and stamped it AAA. Nokia's engineers saw the iPhone threat and were told their concerns weren't supported by the data. A pressure gauge on the Deepwater Horizon read 1,400 psi when it should have read zero, and the crew talked themselves into ignoring it.
Every organization runs on a set of assumptions about how its world works. Those assumptions decide what gets measured, who gets heard, and which warnings get taken seriously. When the assumptions are right, the organization looks brilliant. When they stop being right, the people closest to the problem usually know first. They raise alarms. The alarms get absorbed into a prevailing model and come back out as reassurance.
This book traces that pattern across case studies spanning intelligence, finance, technology, industrial safety, and national security. It explains why the pattern keeps recurring, because successful organizations build their operations, metrics, and career incentives on top of assumptions that become too expensive to question. In the book, we force every strategic question through competing analytical perspectives and pay attention when they disagree.
In July 2023, a veteran analyst at Unit 8200, Israel's signals intelligence agency, wrote a report that should have changed everything. She had been monitoring Hamas communications and training activity in Gaza. What she documented was specific: Hamas fighters were conducting exercises that mirrored, point by point, a forty-page attack blueprint that Israeli intelligence had obtained the previous year. The exercises included simulated assaults on kibbutzim and practice runs at destroying border observation posts. The fighters rehearsed overrunning a military base. They used drones in the same configurations described in the blueprint. At the top of both the document and the training exercises, the same Quranic verse appeared: "Surprise them through the gate."
The analyst wrote that Hamas was building the capacity to execute the plan. She assessed that the training was not aspirational but operational.
Her superiors told her the scenario was "totally imaginative." The analyst pushed back in writing: "I utterly refute that the scenario is imaginary." The training, she wrote, fully matched the blueprint. "It is a plan designed to start a war. It's not just a raid on a village."
Nobody acted on it.
At the Nahal Oz military outpost, half a mile from the Gaza border, a different group of soldiers had been watching the same preparations with their own eyes. They were tatzpitaniyot. Female surveillance soldiers, all of them teenagers or barely into their twenties, assigned to stare at screens and monitor every movement along the fence. They knew their sectors stone by stone. They could identify individual Hamas operatives by face.
Throughout the summer of 2023, these women reported escalating activity. Hamas fighters were training at the border in plain sight. They built a scaled replica of an Israeli observation post and practiced attacking it with drones. They constructed a mockup of a Merkava tank and ran assault drills against it. Drone flights near the border went from occasional to daily, sometimes several times a day, as close as 300 meters from the fence. One soldier later described how Hamas terrorists increased their training frequency from once a week to nearly nonstop, eventually driving tanks to the border and crossing into Israeli territory during exercises.
The soldiers knew their sectors with an intimacy that their superiors did not share and could not appreciate from a distance. "In my sector, I know every stone, every vehicle, shepherd, Hamas training camp, laborers, birdwatchers, trails and outposts," one tatzpitanit told reporters afterward. They had been watching these specific Hamas operatives for months. They recognized faces and understood patterns well enough to notice when those patterns changed.
One soldier, Roni Eshel, regularly briefed her father about what she was seeing. Cameras along the fence were failing and nobody was coming to fix them. Hamas was making holes in the fence. Her father asked her for commanders' phone numbers so he could call and ask why nobody was listening.
The tatzpitaniyot sent their reports up the chain. They were told it was "another training session." The senior intelligence officer for IDF Southern Command dismissed the reports as alarmist. One soldier who persisted was threatened with court martial for talking "nonsense" about a Hamas attack.
"You're our eyes, not the head that needs to make decisions about the information," one soldier recalled being told. Another assessment was more blunt about why the warnings were ignored: "It's a unit made up entirely of young girls and young female commanders. There is no doubt that if there were men sitting at those screens, things would look different."
By September 2022, Hamas was at 85% operational readiness. A full year before the attack.
The blueprint the analyst referenced had a name inside Israeli intelligence: "Jericho Wall." It described a coordinated ground invasion of southern Israel. Thousands of fighters would breach the border fence in multiple locations simultaneously. Drones would neutralize Israel's automated surveillance systems. Motorcycle and paraglider teams would penetrate deep into Israeli territory under the cover of a massive rocket barrage. The document listed specific targets: military bases, kibbutzim, the locations and sizes of IDF forces in the area. It specifically mentioned the Re'im military base.
Israeli intelligence had obtained versions of this plan twice. The first iteration surfaced in 2016, when a top-secret Ministry of Defense memorandum, signed by then-Defense Minister Avigdor Lieberman, warned that Hamas had purchased sophisticated weapons, GPS jammers, and drones, and was working to expand its fighting force to 40,000 by 2020. The second version, dated August 2021, arrived in Israeli hands in May 2022 and was compiled into the "Jericho Wall" report. It described a large-scale ground invasion of border communities and IDF posts by Hamas's elite Nukhba Force.
The document was shown to the head of the Intelligence Directorate, the Gaza Division intelligence officer, the chief of Southern Command, and the head of the Operations Division. In a November 2022 briefing at Southern Command, Jericho Wall was presented at the very end of a list of conflict assessments. An afterthought on the last slide.
The officials who reviewed it reached a consensus: the plan appeared unrealistic. Hamas lacked the capability to execute it.
Intelligence officials also failed to connect the 2022 document to the 2016 version. The two iterations of the same plan were treated as separate, unrelated pieces of information. The newer version was assessed as "aspirational," representing Hamas's force-building ambitions rather than an operational plan. Nobody asked why Hamas kept updating an aspirational document with specific operational details, or why those details kept getting more concrete.
The intelligence community's confidence rested on a model. In Hebrew, the concept has a name: konzeptzia.
The word entered Israeli security vocabulary after the Yom Kippur War of 1973, when Egypt and Syria launched a surprise attack that nearly destroyed the state. A postwar commission found that Israeli intelligence had received clear warnings of the attack but dismissed them because the prevailing conceptual model held that Egypt would not attack without first achieving air superiority. The intelligence existed. The model filtered it away.
Fifty years later, the model had a different subject but the same bones. The konzeptzia before October 7 rested on several interlocking assumptions. Hamas was deterred by Israel's military superiority, demonstrated most recently in the 2021 Gaza conflict. Hamas preferred governing to fighting. Hamas was more interested in economic concessions, like work permits for Gazans, than in military confrontation. The group's leadership calculated that a major attack would invite a devastating Israeli response and risk everything they had built in Gaza.
The model was not stupid. Each individual assumption had evidence supporting it. Hamas had accepted ceasefires. Hamas had participated in governance. Hamas had shown restraint during rounds of fighting between Israel and Islamic Jihad, choosing not to escalate. The Netanyahu government's strategy of economic engagement appeared to be working. Qatar was funneling money into Gaza with Israel's quiet encouragement, on the theory that a Hamas leadership focused on governing would be a Hamas leadership that didn't fight.
Beyond shaping analysis, the model shaped policy and resource allocation. Israeli military and intelligence officials, convinced that the primary threats were Iran, Hezbollah in Lebanon, and settler violence in the West Bank, moved resources away from Gaza. Intelligence collection programs focused on Hamas were cut or deprioritized. The Gaza Division was treated as a quiet sector. The soldiers stationed there received less attention, less equipment, and less institutional respect than their counterparts on the northern border or in the West Bank. The tatzpitaniyot at Nahal Oz felt this acutely. They described an environment where their reports were processed by a system that had already decided Gaza was manageable.
Hamas recognized this dynamic and exploited it deliberately. After the 2021 conflict, which Hamas interpreted as a strategic victory, the group adopted a posture of public restraint specifically designed to reinforce the Israeli model. When Islamic Jihad launched rockets at Israel, Hamas stayed out. When tensions escalated, Hamas issued calming signals. The group avoided conflict precisely to accumulate power for a conflict on a scale Israel's model said was impossible. The restraint was the deception, and the Israeli model read it as confirmation of its own accuracy.
The model had evidence behind it. But it had become the only lens through which evidence was interpreted.
When Hamas avoided joining Islamic Jihad's operations against Israel, the model read this as confirmation of deterrence. An alternative reading, that Hamas was deliberately staying out of smaller fights to preserve its forces for a larger one, was available. Nobody pursued it.
The increasingly elaborate military exercises at the border were categorized as morale maintenance for fighters. The tatzpitaniyot saw something different: operational rehearsals for a specific plan. They were overruled.
The Jericho Wall document was filed as aspirational. A second iteration of a detailed operational plan with updated force projections and observable rehearsals matched to its content. The intelligence officials who reviewed it did not connect it to the 2016 predecessor.
Every piece of contradictory evidence was reprocessed through the model and emerged on the other side as confirmation of deterrence.
On the evening of October 6, 2023, the Shin Bet, Israel's domestic security agency, began detecting anomalies.
At 1:00 a.m. on October 7, the agency reported that Hamas was conducting emergency preparedness measures. Analysts noted signs that could indicate mobilization, but also observed what they interpreted as "signs of restraint." Their assessment: Hamas was not interested in escalation.
At 3:03 a.m., the Shin Bet alerted security branches, including the Prime Minister's National Security Council, that several Hamas brigades were activating their networks of cellphones. Forty-five SIM cards known to be in the possession of Hamas fighters were gradually switched on throughout the night. In a message to other agencies, the Shin Bet assessed that this activity, combined with additional indicators, "could point to Hamas offensive activity."
At 4:30 a.m., Shin Bet chief Ronen Bar briefed his deputies. A team of forces was sent to southern Israel to prepare for a possible infiltration.
It was not sufficient.
At approximately 6:30 a.m., thousands of Hamas and other Palestinian fighters began breaching the border fence. The IDF later determined that some 6,000 attackers crossed into Israel at 119 separate points, including 3,800 from Hamas's elite Nukhba Force. Drones destroyed Israel's automated surveillance cameras along the fence line in the opening minutes. Motorcycle teams and paragliders penetrated deep into Israeli territory under cover of a rocket barrage, roughly 4,000 rockets in the first hours, that overwhelmed the Iron Dome system through sheer volume. The attack followed the Jericho Wall blueprint with operational precision.
At Nahal Oz, the base where the tatzpitaniyot had spent months sending warnings up the chain, Hamas fighters arrived within thirty minutes of the initial breach. The women who had been monitoring the border were now trapped inside the base they had been trying to defend with their reports. Some ran to the command center. Others sheltered in the base's bomb shelter. Around sixty soldiers were killed at Nahal Oz that day. Fifteen of the dead were the female surveillance soldiers whose reports had been dismissed. Most of them burned to death in the command center. Seven more were taken hostage and dragged into Gaza. Hamas body camera footage later showed the captured soldiers with hands tied, faces to the wall, being told: "You dogs, we will step on you."
The command center where they had worked, where they had watched Hamas rehearse this exact attack for months, was reduced to charred walls and melted equipment. Months later, the smell of fire still lingered inside the building. Bone fragments were found in the ashes.
One soldier's last call to her father: "Terrorists in the base. It's going to be a huge event."
She had been saying that for months. On October 7, the event arrived.
Across southern Israel, about 1,200 people were killed. About 250 were taken hostage. It was the deadliest day in Israeli history.
The Israeli investigations that followed confirmed what should have been obvious from the timeline. The intelligence community had the attack plan. They had multiple versions of it spanning seven years. They had HUMINT, a credible Shin Bet source from Gaza who warned of an attack in the week after Yom Kippur, the very week it occurred. They had SIGINT, the Unit 8200 analyst who matched Hamas training to the Jericho Wall blueprint. They had real-time observation from the tatzpitaniyot who watched the rehearsals from their screens. They had strategic warnings from the Military Intelligence Directorate to Prime Minister Netanyahu on at least four occasions between March and July 2023. The Shin Bet chief personally warned Netanyahu in July 2023 that "war is coming," based on his assessment that the Iran-led axis of resistance perceived Israel as weakened by internal political turmoil over judicial reforms. Netanyahu dismissed the warnings as "exaggerated."
The IDF's own investigation found approximately ten separate opportunities between 2017 and October 2023 where intelligence was obtained or incidents occurred that, examined critically, could have contradicted the prevailing assessment. Each time, the intelligence was reinterpreted to fit the konzeptzia. The investigation cataloged them: Yahya Sinwar's rise to power in 2017, signaling a shift in Hamas's center of gravity to Gaza. The initial 2016 intelligence on Hamas's attack plans. The 2021 conflict, which left Hamas feeling emboldened while Israel read the outcome as reassertion of deterrence. The 2022 Jericho Wall report. Hamas's conspicuous avoidance of Islamic Jihad's rounds of fighting. Intelligence gathered in mid-2022 indicating Hamas's aspiration for a multi-front war coordinated with Iran and Hezbollah. And finally, the cascade of signals on the night of October 6.
Each of these moments was a fork. Each time, the intelligence apparatus took the branch that confirmed the model and ignored the branch that challenged it. Not because the analysts were lazy or incompetent. Because the organizational structure rewarded confirmation and punished dissent. A hierarchical military intelligence culture stifled alternative views, especially from women and junior personnel. Information that should have moved rapidly up the chain was filtered, reframed, or simply stopped moving when it encountered an officer who found it inconsistent with the assessment they had already committed to.
One American analysis of the failure put it precisely: "If the September 11 attacks were made possible in part by the U.S. intelligence community's failure to connect the dots, then the October 7 attack was enabled by Israeli political and military leaders' unwillingness to see the connections that analysts made for them."
"The Shin Bet did not prevent the massacre of October 7," said Ronen Bar, the agency's director, in the published summary of findings. "As the one who led the organization, I will carry this heavy burden on my shoulders for my entire life."
Israel had the collection and the technology. Its surveillance apparatus along the Gaza border was among the most sophisticated in the world. What it lacked was a way to challenge interpretation. A fixed model filtered the evidence, and no formal mechanism existed to compete with it. The intelligence community had no process that required alternative hypotheses to receive equal analytical weight, no dissent channel with institutional protection, and no requirement that the konzeptzia be tested against competing explanations at regular intervals. The model was monolithic, and it was wrong. And the people closest to the evidence, the young women at their screens and the junior analyst at her desk, had no path to make the model listen.
The Yom Kippur parallel matters because the pattern of failure is nearly identical, separated by fifty years of institutional learning that apparently changed nothing.
In October 1973, Egypt and Syria launched a coordinated surprise attack on Israel during the holiest day of the Jewish calendar. A junior IDF intelligence officer named Binyamin Siman-Tov had submitted reports to his superiors days before, assessing that ongoing Egyptian military exercises along the Suez Canal were disguising preparations for an all-out assault. His reports were dismissed. The prevailing konzeptzia held that Egypt would not attack without first achieving air superiority, and Egypt had not yet acquired the aircraft to do so. A different flavor of the same failure: one fixed model, no competing analysis, catastrophic surprise.
After the war, the Agranat Commission produced specific findings about how the konzeptzia had functioned as an evidence filter. Its recommendations led to structural reforms: new analytical processes, mechanisms for challenging consensus assessments, and institutional requirements for alternative hypotheses to be documented and escalated. A generation of intelligence professionals trained to be wary of fixed models.
Those reforms worked for a generation. Then the generation turned over. The mechanisms built to challenge fixed models themselves calcified into fixed models. Institutional memory of why the reforms existed faded into doctrine that was taught but no longer felt. New leadership brought new priorities. New threats occupied analytical bandwidth. The konzeptzia returned, wearing different clothes, carrying different assumptions, producing the same result.
Fifty years between the Yom Kippur War and October 7. Organizations that reform after catastrophe tend to follow the same arc. Organizations implement changes after catastrophe, sustain them while the memory is fresh, and gradually let them atrophy as new personnel who never experienced the original failure inherit the system. The reforms shrink into paperwork, the paperwork into compliance rituals that nobody connects to the original purpose. And then one morning the phone rings at 3 a.m. with forty-five SIM cards activating along the border, and nobody remembers why the reforms were supposed to prevent exactly this.
I want to be precise about what the konzeptzia is and what it is not, because the concept runs through every chapter that follows.
The konzeptzia is larger than a bias. Confirmation bias, anchoring, groupthink, all of these are cognitive tendencies that operate at the individual level. The konzeptzia operates at the institutional level. It is a set of assumed causal relationships that become organizational plumbing. The assumptions determine which questions get asked, which signals get prioritized, which evidence gets escalated, and which gets filtered out. The assumptions shape staffing decisions, resource allocation, reporting structures, and promotion criteria. Challenging the konzeptzia doesn't feel like challenging a hypothesis. It feels like challenging the organization itself.
Calling it a "culture problem" is too vague to be useful. You can't fix a culture in a specific way. You can identify and challenge a specific set of causal assumptions.
The Israeli konzeptzia before October 7 rested on a specific causal chain: Hamas has experienced Israel's military superiority. Therefore Hamas understands that a major attack would be met with a devastating response. Therefore Hamas's rational self-interest prevents it from attacking. Therefore any evidence of attack preparation reflects aspiration, not intent.
Each link in that chain is a testable assumption, and every link turned out to be wrong.
The most revealing failure was the third one, the intent assumption. The model assumed that because Hamas leadership was rational, and because the cost of attack would be enormous, Hamas would choose not to attack. The model focused on intent and stopped analyzing capability.
But rational actors can arrive at different calculations than the ones your model assumes. Hamas's leadership had watched the 2021 conflict and concluded they had achieved a strategic victory. They had watched Israel's internal political crisis over judicial reform and concluded the country was divided and distracted. They had coordinated with Iran and Hezbollah on a vision for multi-front war and concluded that a simultaneous escalation across multiple borders could overwhelm Israel's military capacity in ways that a Gaza-only operation never could. Every one of these conclusions might have been wrong. But they were Hamas's conclusions, not Israel's. The konzeptzia assumed Hamas would calculate costs and benefits using Israel's framework. Hamas was using its own.
The capability was there. Hamas had built a force of thousands of trained fighters. They had specific, detailed operational plans, refined over seven years. They had conducted observable rehearsals. They had acquired drones, GPS jammers, and the ability to neutralize Israel's border surveillance. The question of whether Hamas could execute a large-scale ground invasion had a clear answer by mid-2023. The answer was yes.
The konzeptzia converted that answer into irrelevance. Capability didn't matter because intent was assumed to be absent.
The separation of capability from intent is the oldest diagnostic tool in intelligence analysis. It appears in every introductory course on the subject. Assess what an adversary can do. Separately assess what they want to do. Do not let one assessment contaminate the other. Israeli intelligence codified this distinction decades ago. They taught it to their officers. They wrote it into their doctrine.
On October 7, their entire analytical apparatus was running the contaminated version. Intent overrode capability. The model overrode the evidence. More than three thousand people at the Nova music festival near Re'im, the exact military base named in the Jericho Wall document as a primary target, had no idea that the intelligence system responsible for their safety had decided that the scenario unfolding around them was totally imaginative.
The instinct, after reading a story like this one, is to think: this is an intelligence problem, specific to spy agencies and national security and Israel. It's distant. It doesn't apply to me.
That instinct is worth examining, because it is the same instinct that let Israeli intelligence dismiss the tatzpitaniyot's reports. The pattern feels distant until you notice it running in your own organization.
Every organization that makes high-stakes decisions runs a model of how its environment works. That model tells the organization what matters and what doesn't, what's likely and what's not, where to invest attention and where to look away. When the model is right, the organization looks brilliant. When the model is wrong, the organization is blind. And the longer the model has been right, the harder it becomes to see the evidence that it might be breaking.
The investment committee that dismissed subprime risk in 2006 was running a konzeptzia: housing prices don't fall nationally. The model was backed by decades of data. The analysts who built the mortgage-backed securities used the best statistical methods available. The rating agencies that blessed the products employed hundreds of PhD economists. And the model's assumption, that geographic diversification of mortgage pools eliminated correlated default risk, had never been contradicted by historical data. When a few analysts at peripheral firms began asking whether lending standards had converged enough to create national correlation, the question was processed through the model and dismissed. Housing prices don't fall nationally. The data says so.
The Nokia board that dismissed the iPhone in 2007 was running a konzeptzia: phones are communication devices, not computing platforms. Nokia had more smartphone patents than Apple. They had more market share. They had more engineering talent. They tracked the metrics their model told them to track: call quality, battery life, carrier relationships. The iPhone scored poorly on all of them. The model said Nokia was winning. Engineers inside the company who tried to raise the alarm that the competitive frame itself was wrong were told the data didn't support their concerns. The data didn't support their concerns because the model measured the wrong things.
The BP engineers who accepted anomalous pressure readings at the Macondo well in April 2010 were running a konzeptzia: blowout preventers work because they've always worked. The physical evidence was there. Pressure test results were abnormal. The cement job was flagged by multiple people on the rig. But the model that said "blowout preventers don't fail catastrophically" had been right for so long that contradictory evidence was processed as anomaly, not alarm. Schedule pressure and cost optimization gave the organization a reason to accept the model's reassurance. Eleven workers died in the explosion.
In every case, the people making the decisions were not stupid. They were often the best in their fields. They had access to the relevant information. They had smart people in the room raising concerns. And in every case, the model processed the concerns and produced reassurance. The concerns were filed under "doesn't fit" and the model continued undisturbed.
We will examine each of these failures in the chapters that follow. Not as isolated disasters, but as specimens of the same pathology. The konzeptzia is a tendency that runs in any organization that has been successful long enough to trust its own assumptions.
October 7 did not happen because Israeli intelligence was incompetent. It happened because the most sophisticated intelligence apparatus in the Middle East had no structured mechanism for forcing its own assumptions into competition with alternatives. One model held the floor, and contradictory evidence could not get a hearing.
The rest of this book is about a discipline designed to give the evidence a better hearing. Not by making people smarter, or less biased, or more open-minded. People resist those changes, and the changes don't stick anyway. The discipline works by building a hard rule into the analytical process: every strategic question must be examined through twelve independent lenses, each designed to surface a different category of causal mechanism, each producing its own scenario from the same evidence. The model doesn't get to be the only voice in the room. It becomes one voice among twelve.
Why twelve? Because the October 7 failure was not a single blind spot. The konzeptzia suppressed information across multiple analytical dimensions simultaneously. Capability analysis was overridden by intent assumptions. Physical evidence from the border was overridden by strategic-level assessments. Internal political dynamics in Israel, which made the government less responsive to warnings, were never integrated into the threat picture. Hamas's information operations, specifically the deliberate deception of appearing restrained, were never analyzed as a deception campaign. Shadow coordination with Iran and Hezbollah was treated as background noise. Each of these failures maps to a different analytical dimension. A discipline that forces attention across all of them, in parallel, from the same evidence base, makes it much harder for any single model to monopolize the assessment.
The tatzpitaniyot at Nahal Oz already knew something was coming. The Unit 8200 analyst already documented the evidence. The Shin Bet chief already warned the prime minister. The information existed. What was missing was a system that required the information to be examined from enough angles that the konzeptzia couldn't suppress it.
That system is what the next chapter introduces.
Research and analysis are the key to reformation, which when applied to organizations and systems ensures safety and stability. The Shape of Outcomes by Aaron Trubic offers analysis of the failure of organizations, ranging from governmental to corporate and independent ones, which resulted in major disasters in the recent human history.
Trubic starts with the most recent disaster of the political world, namely the October 7, 2023, attack on Israel by Hamas militants from Gaza. His analysis of the security model on which Israeli government’s decisions were based provides an explanation of why such a preventable disaster materialized. Readers get to see the component of the failed model and its flaws responsible for the failure. In subsequent chapters, Trubic applies his analysis of the modular failure to four other major disasters in the 21st Century, most/all of which happened in developed countries and tied to organizations run by educated and qualified people.
The Shape of Outcomes offers interesting and important facts and valuable insight into the nature of failures in organizations that employ the same model for safety against loss but ignore to update and reform it by learning from past mistakes. The notable cases of disastrous failures fall in various fields from politics to oil exploration, smartphone technology, and real estate finance (the financial disaster of 2008). Applying his analysis to diverse cases of disasters gives Trubic’s work an appeal for readership beyond a single topic or area of interest.
The latter sections of the book, particularly Part 3 (The Method) take a different turn and deal with details of the role of the model’s components, how they function in the whole, and what additional checklists can be applied for more thorough vetting so as to get better outcomes. These parts feel rather dry to read and seem best suited for academic perusal than the general readership.
The Shape of Outcomes itself has a good organization with presentable division into parts, stylized fonts in chapter numbers and headings etc. Individual chapters are short; Trubic speaks with authority from a position of knowledge and insight; the book’s tone is demonstrative and in the latter parts becomes rather scholastic. The book carries a feel of disconnect from the earlier chapters in these parts as the narration zooms in on the components of the model while losing sight of the bigger picture that would keep the flow of the narration uniform.
Finally, The Shape of Outcomes has some formatting issues on both word and line levels (at least in the PDF copy that this reviewer got). It could certainly benefit from another round of thorough formatting.