INTRODUCTION: The Art of Thinking in Branches
There is an hour in every company’s life when the road bends. Sometimes it begins imperceptibly—a new competitor enters, a cost structure shifts, a technology redefines the grammar of value. Other times, it is seismic and sudden: a macroeconomic rupture, a liquidity crisis, an acquisition overture. And in that hour, the illusion that tomorrow will resemble today shatters. The CFO—so long the steward of precision—must become something else entirely. A mapmaker of the unknown. A poet of probability. A tactician of the conditional.
This letter is about that hour.
More precisely, it is about the discipline required to prepare for it.
Scenario planning, for all its corporate overuse, is not a spreadsheet exercise. It is not the stacking of best case, base case, and worst case like so many tepid Russian dolls. It is the intellectual act of thinking in branches, of modeling not only multiple futures, but how the firm would morph within each. It is not only about what could happen. It is about who we become if it does.
Strategic inflection points, a phrase popularized by Andy Grove, do not ask for forecast accuracy. They ask for organizational coherence under changing assumptions. They require that we recognize, often before the numbers do, when a system’s dominant logic is beginning to invert. The product that once led, now lags. The segment that once subsidized, now consumes. The lever that once scaled, now constrains. To see an inflection point is to feel a curvature in time—and to plan for it is to model the geometry of that curvature before it defines us.
My first encounter with a true inflection came not from a spreadsheet, but a lunch. It was 2008. The world was beginning to contract. A former competitor, newly quiet, suggested an exploratory conversation. They had been admired, once feared. Now, they were seeking alignment. “We can’t outgrow this gravity,” the CEO told me, his voice calm and thin. “But maybe we can fall together more slowly.” That conversation, and the partnership that followed, taught me what no Monte Carlo engine ever could: scenarios are not data—they are choices dressed in timelines.
In Part I, we will begin with epistemology: how do organizations misperceive inflection points? We’ll explore how cognitive biases, short horizon thinking, and inertia shape our underreaction to change. We’ll invoke complexity theory to describe systems approaching phase shift, and we’ll lay out the moral terrain of the CFO’s role—not as prophet, but as preparer of consequence.
Part II will then ground us in the design of scenarios. Not as simplistic if-then tables, but as narrative logics: self-consistent futures driven by forces we can observe but not control. We’ll walk through how to model industry disruption, cost structure evolution, and behavioral shifts using tree logic, stress-tested drivers, and adaptive feedback loops. We will explore scenario construction as economic storytelling under constraint.
In Part III, we will explore scenario deployment—not just in budgeting, but in strategic rhythm. How the CFO weaves scenario logic into board discussions, capital allocation, pricing posture, and hiring cadence. How scenarios move from PowerPoint to action, creating conditional readiness across the firm. We’ll discuss simulations, pressure tests, shadow P&Ls, and signal-based escalation systems—tools for dancing with the unknown without falling into it blindly.
And finally, in Part IV, we will turn to the cultural dimension. Because scenario mastery is not only mechanical—it is emotional. It is the ability to hold multiple futures in one’s mind without succumbing to paralysis. It is the training of a leadership team to think not in straight lines, but in constellations. It is a culture of thoughtful ifs, where plans are not brittle scripts but flexible sequences of contingent intention. We will explore how CFOs become stewards of that psychological elasticity—and why, in the end, the quality of scenario planning is a proxy for the organization’s philosophical maturity.
For in truth, what is a scenario but a form of imagined empathy? A way of stepping outside our current success and asking—gently, but bravely—What if we are wrong? What if something changes? What would we do? What would we preserve?
This is not cowardice. This is institutional courage. To simulate the breaking of one’s own models. To interrogate one’s assumptions before the market does. To make imagination a form of accounting, and uncertainty a form of design.
And if that sounds grandiose, let me assure you—it is not only grand. It is survival. For in the end, the companies that endure inflection are not those who forecast best. They are those who prepare for which self to become when the world around them moves.
PART I: On the Perils of Linear Thinking — Seeing Inflection Before the Numbers Arrive
The enterprise is a creature of continuity. Its rhythms are engineered for replication. The budget rolls forward, the hiring plan extends, the financial model propagates itself through nested assumptions. If the margin was forty-two percent last quarter, we assume it shall be forty-one next, or forty-three, but surely not nineteen. The machinery of the modern firm is built on the premise that the near future will rhyme with the recent past.
And it is in this structural fidelity that the danger hides.
For when an inflection point emerges, it does not announce itself with drama. It enters sideways—disguised as noise, footnoted as anomaly. The customer takes longer to convert. The sales team feels a new friction they cannot name. The CAC begins to rise but does not scream. And the CFO, if trained only in precision, will miss the curvature. She will mistake drift for deviation. And deviation, unchallenged, becomes the architecture of decline.
Why is this so? Why do we so often miss the approach of structural change?
The first culprit is cognitive inertia. Kahneman and Tversky named it: anchoring bias. We anchor to past experience because it gives us comfort, because the mind prefers pattern over disruption. Linear extrapolation is not merely an analytic tool—it is a psychological defense against ambiguity. We draw the straight line not because we believe it, but because the alternative—chaos—is unlivable.
And yet chaos is the natural condition of systems approaching transformation.
Complexity theory teaches us that systems behave predictably until they do not. They follow rules, then shift into a new regime. Feedback loops accelerate until thresholds are crossed. A viral product loses momentum not in a gradual slide, but in a punctuated collapse of network value. A supplier shortage does not delay product by days—it reroutes pricing logic across the firm. These are not linearities. They are phase changes. And the tragedy is that the tools of traditional finance—sensitivity tables, deterministic plans, single-path budgets—are exquisitely unfit to anticipate such transformation.
Indeed, the financial model, in its most common form, is itself a monument to linearity. It extends the present, with modifiers. It does not simulate discontinuity. And so, as CFOs, we are trained in a kind of arithmetic naiveté. We become eloquent in growth rates and operating leverage, but mute in the face of structural shift. Our slides show decimals, but not thresholds.
But inflection points are not decimals. They are curvatures in strategic time. And to detect them, we must reorient our senses—not around numbers, but around patterns that break. What does it feel like when a market becomes saturated? What does it smell like when a competitor’s proposition begins to rearrange the customer’s reference frame? These are not modelable events. They are intuitable tremors. And the CFO must be trained not only in variance analysis, but in pattern discernment.
This is where scenario planning begins—not in Excel, but in epistemic humility. The acknowledgment that our existing model is not wrong, but conditional. That the business plan is not a truth but a forecast, and every forecast is a fiction with assumptions. The role of the CFO, then, is to become the author who footnotes her own narrative. She does not merely present the plan. She articulates its contingencies. She names the dependencies that, if altered, will unmake the logic we’ve drawn.
It is no coincidence that some of the most successful strategic recoveries in business history were led not by visionaries, but by CFOs who were brave enough to say: this curve will not hold. Whether in the boardroom during the shift to cloud economics, or in the early days of digital monetization, it was the financially literate yet probabilistically aware executive who said: “This path assumes a world that may no longer exist.”
To master scenario thinking, then, the CFO must embrace non-linearity as a working assumption. This does not mean modeling disaster in every cell. It means learning to see the enterprise not as a line, but as a field of conditionally viable paths. Some will thrive under current assumptions. Others will require bending. Some will no longer exist.
And in this bending lies both risk and rebirth.
The firms that survive inflection points do not do so because they modeled the exact scenario correctly. They survive because they recognized, earlier than most, that a shift had begun—and they rehearsed their response to that shift before it arrived in full.
There is a parable, often told in military circles, about the Hungarian platoon lost in the Alps during World War I. Trapped in a blizzard, morale crumbling, they found an old map in the pack of one soldier. Guided by it, they rallied and found their way home. Only after their return did they realize the map was of the Pyrenees. The lesson? It is not the accuracy of the scenario that saves us. It is the discipline of acting within one. The CFO, then, must offer not prediction, but structure for mobilization.
So let us abandon linearity.
Let us replace projection with possibility architecture.
Let us, as stewards of economic imagination, acknowledge that the firm lives not on a line, but on a plane of futures—some fragile, some fertile, all worth preparing for.
PART II: On Designing Scenarios as Narrative Logics — Modeling the Future with Imagination and Constraint
To plan is to predict imperfectly. But to scenario plan is to prepare honorably—to simulate not the most likely future, but a portfolio of meaningful ones, each anchored not in whim but in logic. The art of scenario planning is not one of fantasy; it is the choreography of conditional truths. It asks not merely what might happen, but how it might unfold, and how the firm, under constraint, must adapt its muscle and memory to endure.
Most companies, when they speak of scenario planning, speak in weak terms. A base case, a downside, an upside. The figures shift, the drivers tick, and the output flows dutifully into the model. But this is not true scenario design. This is numerical cosmetic surgery—an effort to simulate difference without altering structure. The assumptions shift, but the logic remains linear. The behavior is unchanged. And so the exercise fails at its most critical purpose: to teach the organization how to think differently under different truths.
True scenario planning begins with the identification of forces—not metrics, but dynamics. These are not merely market shifts or input costs. They are deeper vectors: macroeconomic weather, customer psychology, technological asymmetries, competitive tempo. A proper scenario is built not from toggling a variable, but from constructing a world in which a handful of these forces recombine into a new narrative.
Consider the example of a software firm navigating a move from perpetual license to SaaS. This is not a numerical transition—it is a philosophical inversion of cash flow structure, margin timing, sales behavior, and renewal culture. The base case may assume a smooth ramp. But a robust scenario architecture might include:
- A Delayed Adoption Scenario, where enterprise clients resist subscription, elongating sales cycles and lowering near-term bookings.
- A Compression Scenario, where ARR ramps but gross margins decline due to higher onboarding and support burdens.
- An Acceleration Scenario, where product-market fit in verticals leads to early scale, but strains implementation and net retention.
Each of these is not a prediction. It is a narrative logic—a branching of the world into conditions we can simulate, test, and preemptively design responses to. Each scenario must contain four qualities: internal consistency, strategic relevance, distinctiveness, and plausibility under pressure. Without these, we are not planning—we are storytelling without consequence.
This is where the CFO becomes less a forecaster and more an economic dramatist. She does not merely plug assumptions into cells. She constructs possible realities in which customers behave differently, capital becomes more or less constrained, competitors move first or falter, and internal capacity is either sufficient or severely tested. These realities are not speculative fiction. They are rehearsals for lives the company may yet live.
A scenario, to be useful, must possess structure. Begin not with numbers, but with forces: What is changing in the macro environment? What behavioral shifts are observable in the customer? What technology curve are we climbing, and how steeply? Then introduce strategic consequences: How do these forces disrupt the firm’s economic logic? Does our current cost structure flex or fracture? Does our revenue rhythm hold or stutter? Finally, cascade into operational implications: What does this mean for sales headcount, product roadmap, marketing posture, vendor dependency?
The best scenarios are not imaginative in their optimism. They are rigorous in their constraint. They do not model everything going wrong. They model what happens when a few core truths break and our current system design is found inadequate.
In one of the more instructive scenario cycles I led, we modeled the introduction of a regulatory constraint on a financial technology platform that relied heavily on user-level behavioral data. The base case assumed compliance with minimal change. But a shadow scenario explored the inverse: what if data portability was restricted? What if the cost of compliance climbed, and with it, latency in decision-making? We built a model that traced this narrative through loss in throughput, decline in underwriting accuracy, and a counterbalancing strategy of premium pricing. When, a year later, the regulatory terrain shifted toward restriction, we had not only modeled the impact—we had already begun adapting the muscles to withstand it. This is not clairvoyance. This is pre-emptive design.
Let us be clear: scenario planning is not merely an analytic tool. It is a social technology. Its power lies in the act of shared modeling. When leadership teams build scenarios together, they develop a common language of future tension. They begin to speak in if-then conditionals—not from fear, but from muscle memory. “If expansion CAC rises above 2.5x, we shift to high-retention verticals.” “If NRR drops below 105%, we delay Tier 3 product development.” These conditionals, once embedded, allow the company to act not from surprise, but from prepared responsiveness.
This conditional language is deeply tied to decision theory. At its core, every scenario is a probabilistic branch with an expected utility function. But instead of trying to calculate the precise probability of each outcome, the wise CFO designs decision triggers: thresholds, signals, and stress indicators that cue action. These are not predictions—they are invitations to adapt. And they build a kind of epistemic calm into the executive function.
The elegance of well-designed scenarios lies in their parsimony. You do not need ten. Three to five is enough. Each distinct. Each rigorous. Each lived through in simulation. Each carried forward in executive discussion as a living map, not a presentation relic.
When done well, scenarios become not a quarterly exercise, but a firmwide reflex. Sales uses them to plan pipeline resilience. Product uses them to test roadmap priority under stress. HR uses them to shape hiring under variable growth. Finance becomes the conductor, but the music is played by all.
Scenario planning, in this richer form, is not about multiple budgets. It is about multiple futures held simultaneously, modeled for behavior, tested for strain, and aligned to the firm’s values.
Because in the end, the virtue of a scenario is not that it came true.
It is that it made the firm ready to be true to itself, regardless of what the world became.
PART III: On Deploying Scenario Planning as Strategic Rhythm — Conditional Readiness in Practice
There is a peculiar danger that haunts even the most beautifully constructed scenario models: their stillness. They sit in decks, admired, sometimes even rehearsed, and then laid to rest in folders marked “strategic offsite” or “board prep.” The scenarios, once alive with tension and consequence, are frozen—neither acted upon nor lived within. And yet it is precisely the purpose of scenario planning to become something more than artifact. It is to become an instrument in motion, a part of how the company thinks, adjusts, and acts under constraint.
The transition from scenario design to scenario deployment begins with an essential mindset: that the future is not a point, but a sequence of decisions made under changing assumptions. And the CFO, as custodian of temporal discipline, must transform scenarios into strategic cadences—frameworks that embed probabilistic thinking into quarterly forecasts, capital allocation, hiring posture, and cross-functional accountability. The scenario becomes not a destination, but a compass, and the firm becomes not a fortification, but a responsive instrument.
Let us begin with perhaps the most neglected but most powerful tool in this orchestration: the shadow P&L. In nearly every firm I have worked with, the budget serves as a fixed projection, derived from the base case and assumed to define the company’s intent. But what if, in parallel, we ran a scenario-informed P&L, updated quarterly, that assumed an alternate curvature in customer acquisition, a variation in gross margin trajectory, or a funding constraint six months hence? This shadow model is not a prediction. It is a second rhythm. It creates optionality. And when, inevitably, reality diverges from the primary projection, the CFO is already fluent in the economic language of that divergence.
The operationalization of such a model does not require new systems—it requires new habit. A habit of modeling the Month 3 ARR drop if renewal dips by 10%. A habit of tracing CAC recovery shifts under slowed payback. A habit of pressure-testing assumptions before they deteriorate into emergency. This is what I have come to call scenario fluency—the ability to think, communicate, and decide within contingent frameworks, without losing coherence or confidence.
Scenario fluency begins to transform the cadence of executive meetings. The forecast review ceases to be a binary yes-no debate. Instead, it becomes a conditional check-in: “We are tracking toward Scenario B, unless these two signals break trend.” In one company I advised, we color-coded our forecast dashboards to match scenario pathways—green for base case, yellow for constrained expansion, red for contraction resilience. The shift was immediate. Teams no longer asked, “Are we behind plan?” They asked, “Which trajectory are we entering, and are we ready for its constraints?”
This shift is not semantic. It is strategic. It replaces defensiveness with preparedness. It allows capital planning to flex. It teaches teams to see leading indicators as activation levers, not post-mortems. And it gives the CFO a language of probability that protects against overconfidence without surrendering to indecision.
One of the most elegant forms of deployment is what I call conditional allocation logic. Rather than locking marketing spend to top-line growth, we define spend ceilings based on scenario-bound CAC efficacy. In expansion scenarios, acquisition velocity justifies more risk. In contraction scenarios, retention economics take precedence. This dynamic allocation principle—rooted in context-aware constraint—prevents waste while preserving strategic aggression where warranted.
The same principle can be extended to headcount planning. Rather than freezing hiring or opening the spigot blindly, we stage hires in response to validated indicators. If customer onboarding time increases by more than 20% under Scenario B, a second wave of success hires triggers. If usage density stalls, product resourcing pauses. In this way, the hiring plan becomes a contingent response mechanism, not a fixed expense plan.
Capital strategy, too, finds new clarity under scenario rhythm. In a world of volatile markets and capricious capital access, scenario-driven CFOs no longer anchor valuation assumptions to a singular fundraising outcome. Instead, they construct capital corridors, modeling the firm’s cash runway, dilution path, and debt tolerance under three or more credible futures. In one firm, we tracked burn multiple across scenarios—not just to preserve options, but to decide which growth bets to defer and which bets to protect under stress. This approach allowed us to move from capital dependency to capital strategy, where each scenario gave us a contingency-aware financial posture, not just a funding gap.
But perhaps the most powerful benefit of scenario rhythm lies in how it reshapes narrative within the firm. The story is no longer “Plan A or bust.” It is: “Here is the family of futures we are prepared for. Here is how we behave in each.” When employees understand this, fear recedes. They see not volatility, but design. They understand that flexibility is not compromise. It is an asset class in itself—one the CFO trades in daily.
There is a beautiful paradox at play. The more the CFO speaks in scenarios, the more confident the firm becomes—not because uncertainty is resolved, but because it is integrated into planning. Risk no longer lives at the edge. It is named, modeled, embedded.
And from that embedding, a quiet strength emerges.
The CFO becomes not the architect of the one correct plan, but the steward of organizational readiness. She moves from controlling outcomes to designing for response. She no longer promises that the future will unfold in a linear manner. She promises that the firm will not be caught flat-footed when it doesn’t.
This is the true measure of scenario deployment: not how accurate the paths, but how fluent the firm becomes in switching paths with speed and grace.
PART IV: On Cultural Adaptation — Building Organizational Maturity Through Scenario Literacy
Every discipline, no matter how numeric, contains a hidden emotional cost. Financial modeling wears the mask of certainty, but behind it lies vulnerability: the fear of being wrong, the burden of assumptions, the exposure of decision made visible. Scenario planning, when truly practiced, does not alleviate this vulnerability—it formalizes it. It demands that we rehearse what we fear. That we narrate not only triumph but failure. That we confess—before the world does—that the ground may shift beneath our plans. And for that, there must be cultural permission.
The most elegant scenario models are inert if the culture cannot emotionally metabolize uncertainty. Without this maturity, scenarios become compliance exercises—slides to be endured, not realities to be inhabited. People nod, then retreat to the comfort of the plan. And the plan, as ever, becomes an article of faith, not a system of navigation.
The CFO’s final duty, then, is not merely analytic or procedural. It is psychological. She must act as interpreter, yes—but also as a cultural architect. She must midwife a culture in which multiple futures can coexist, in which conditional thinking is not seen as weakness but as wisdom, in which planning is understood not as clairvoyance but as preparedness with empathy.
The journey begins with language. The words we use to describe scenarios matter. If we speak of “worst case,” the room recoils. It hears defeat. But if we speak of “resilience path,” of “contingency tier,” of “staged readiness,” we engage the imagination without triggering defensiveness. The CFO must learn to speak in terms that frame uncertainty as stewardship, not surrender. This is not merely rhetorical—it is neurobiological. The human brain, when confronted with catastrophic vocabulary, narrows its field of perception. But when presented with variation as manageable, the mind remains open to design.
Language leads to behavior. In a scenario-literate culture, meetings begin with calibration, not correction. “Which signals are diverging?” becomes as common a question as “Are we on plan?” And from that question, a thousand micro-decisions bloom—each one building reflex, not rigidity.
This cultural fluency must extend across disciplines. In operations, it manifests as staged capacity deployment. In sales, as quota plans that flex with pipeline confidence. In engineering, as roadmap elasticity contingent on uptake velocity. Scenario literacy is not the domain of finance—it is a firm-wide cognitive upgrade, embedded in the DNA of how the company learns from reality.
But such literacy must be earned. It does not emerge from edict or template. It emerges from repetition with consequence. One of the most formative practices I have seen is the quarterly scenario rehearsal—a live exercise in which the leadership team inhabits a scenario: “What would we do if retention dropped 15%? What if funding closed late? What if growth doubled?” Not abstractly. Specifically. Roles, decisions, trade-offs. These sessions become more than risk reviews. They become rituals of organizational humility, in which planning is not presented but interrogated. Over time, this ritual becomes a vaccine against panic. Because when disruption comes, it has already been named.
To institutionalize scenario thinking is to accept that the firm must live in tension. Not the paralyzing tension of indecision, but the constructive tension of preparedness. It is to normalize the idea that good plans contain exits, that strong strategies flex, that coherent organizations can hold competing possibilities in balance without fracturing.
The CFO plays a delicate role here. She must be the skeptic without becoming the cynic. She must protect optionality without fueling paranoia. She must hold ambiguity without outsourcing accountability. Her voice becomes a tempo-setter, one that neither overreacts nor underprepares. This is not neutrality—it is leadership in conditions of partial knowledge.
Scenario culture also demands emotional honesty about what we do not know. This honesty, once modeled, gives others permission to speak from uncertainty. A product lead, once afraid to admit a demand signal looks soft, now says, “If this cohort behaves like the March curve, our path may need revisiting.” That sentence is not a weakness. It is a signal of cultural maturity. It says: “I understand the logic of conditions. I am playing the long game of truth.”
Over time, this shared language becomes organizational identity. The firm no longer says, “We must hit this target at all costs.” It says, “We manage toward our long-term truths, under short-term contingencies.” This is not risk aversion. It is resilience realism. And in an era of accelerating external shocks, such realism is the only form of optimism that lasts.
Scenario culture changes not only decisions, but memory. When history is told, it is no longer “we missed plan.” It is, “Scenario B unfolded, and we were ready.” This retelling matters. Because memory is not just data—it is how an organization teaches itself what kind of entity it is. A firm that remembers its scenario planning as performance theater becomes brittle. A firm that remembers it as adaptive rehearsal becomes wise.
EXECUTIVE SUMMARY: A Geometry of Coherence Under Uncertainty
It begins innocently enough. A forecast drifts. A customer acquisition cycle extends by two weeks. A competitor ships a feature that subtly redraws the value terrain. The change is quiet—too quiet for alarm. But the CFO feels it in the substrata of pattern. And if she has trained for inflection, if she has thought not in paths but in branches, she will already have a map for this moment. Not to predict it—but to move through it with coherence intact.
This is the central project of scenario planning as we have argued it here—not a hedging ritual, but a form of financial storytelling under contingent truths. Across these four letters, we have shown that the scenario-capable CFO is not one who forecasts correctly, but one who prepares the company to remain intellectually honest and operationally ready as its operating assumptions dissolve and reconstitute.
In Part I, we confronted the illusions of linearity. We saw how financial models, by their nature, domesticate uncertainty—smoothing over the wild topography of real strategic change. The mind, seeking comfort, extrapolates from the past and, in so doing, invites surprise. We learned that inflection points are not spotted by models alone. They are felt as tremors, often before the first metric budges. And thus, the CFO’s most vital act in times of shift is not precision, but perception—epistemic humility coupled with narrative courage.
In Part II, we rebuilt the practice of scenario planning from first principles. Not as a set of spreadsheets or best-worst-base tropes, but as narrative logic—economic stories rooted in driver-specific tension. We explored how scenarios emerge from crosswinds: macro volatility, technological tempo, behavioral shifts. And we saw that the finest scenarios are not dramatic—they are plausible, constrained, lived-in. Designed not to entertain, but to train the mind for adaptive response.
From this conceptual footing, Part III extended the conversation into operational strategy. We showed how shadow P&Ls, conditional allocations, and leading indicator frameworks convert scenario logic into financial readiness systems. We saw how firms that deploy scenarios as rhythms—not relics—move with greater poise. They do not ask, “Are we off-plan?” They ask, “Which curve are we entering, and what muscle is required here?” The CFO becomes not a presenter of plans, but a choreographer of switchable futures.
And finally, in Part IV, we turned to the human heart of the problem: culture. Scenario fluency is not analytic—it is emotional. It requires a leadership culture unafraid to hold uncertainty, a narrative voice that defuses fear by converting ambiguity into design. Scenario planning, when deeply internalized, becomes a firm’s immune system—a set of shared reflexes honed not for catastrophe, but for continuity of character under dislocation.
What, then, is the philosophical yield of this scenario work?
It is not risk aversion. Quite the opposite.
It is the audacity to grow without hubris, to dream under constraint, to lead without pretending omniscience. It is the humility to say: “We will not be surprised when the future turns. Because we rehearsed not only what it might look like—but who we must become when it arrives.”
And from that discipline emerges something rare: a firm that acts, not reacts; that adapts without panic; that preserves its long memory while navigating short-term divergence.
Scenario mastery does not eliminate volatility.
It transforms volatility into an arena of design.
It makes resilience visible.
And it gives the CFO her most enduring legacy—not numbers well predicted, but decisions made with courage under contingent truth.