When Stakeholders Want Different Messages: Choosing a Script Structure That Works

You're in a conference room. Legal says the script must lead with the bottom line—no softening. PR insists on building empathy first. Operations wants step-by-step instructions. And the CEO just wants it done by 5 PM. Sound familiar?

When stakeholders want different messages, choosing a script structure becomes the first—and most consequential—decision you'll make. Get it right, and the rest is editing. Get it wrong, and you'll rewrite under deadline pressure, risking coherence and trust. This article gives you a framework to decide, not just another template.

Who Must Choose—and By When?

The Decision Maker: Usually the Communication Lead

Someone has to own the choice. If you have five stakeholders arguing for five different messages, the person holding the pen—the communication director, the crisis team lead, or the designated risk communicator—must decide which script structure carries that multiplicity of voices. Not the CEO. Not the legal team. The person accountable for the output. I have watched a deputy comms director poll her executive team for three days, collecting preferences like seashells, then deliver a draft that satisfied no one. Why? She never claimed the authority to choose the container before she filled it. The catch is that authority can feel uncomfortable—especially when your CRO wants a linear narrative, your brand team demands modularity, and your legal counsel insists on pyramid formatting. That tension is normal. The mistake is letting the tension delay the decision.

The Deadline: Before the First Stakeholder Sees a Draft

The deadline is not "by Friday." It's not "when we have consensus." The deadline is before you write a single sentence that anyone else reviews. Show a draft based on a pyramid structure to a stakeholder who expected a narrative, and you have already lost a day—at minimum. They will mark up content when the real problem is form. I fixed this once by sending a one-paragraph structure description to seven stakeholders before writing a word. "I plan to open with the bottom-line recommendation, then layer evidence. Do you consent to that order?" It felt bureaucratic. It saved three revision cycles. Most teams skip this step, then wonder why the document that every inbox wanted turns into a battlefield about paragraph placement. The odd part is—these battles are entirely avoidable.

"A script structure chosen after drafting is not a choice at all. It's a post-hoc rationalisation of whatever the first writer happened to type."

— notes from a communication lead post-mortem, anonymised

The consequence of missing this deadline is not just revision fatigue. Delay breeds confusion across the team. Writers begin to hedge. They embed caveats because they don't know which structure will survive review. The prose gets flabby. The rationale gets buried. And when you finally force a structure choice under time pressure, you pick the one that offends the fewest people—not the one that serves the audience best. That hurts. It hurts the clarity of the message and the speed of the release. You lose a day. Then two. Then the seam blows out.

The Consequence: Delay Breeds Confusion

What usually breaks first is trust. Not trust in the message—trust in the process. When stakeholders see drafts mutate structure between versions, they assume the communicator is indecisive. They start sending their own restructured versions. Chaos. I have seen a six-person crisis team produce eleven different document versions in one afternoon because no one had locked the scaffolding. The modular group drove a version. The narrative group drove another. The pyramid people waited it out, then rewrote the whole thing at 5 PM. Was any version wrong? No. Was the process broken? Completely. The resolution came when the lead flatly stated: "We're using a modular structure. Everyone gets a tile. No one gets to re-tile the roof." That was not a glib moment—it was recognition that the who and the when must be resolved before the how. Choose your decision maker. Set your deadline. Then write.

Three Script Structures That Break the Deadlock

Pyramid: front-load the bottom line

Start with the conclusion. No throat-clearing, no context, no apologies. The Pyramid structure puts your most critical risk statement in the first sentence — the one thing everyone must hear, regardless of their role. I have seen this work brutally well in operations where a plant manager, a legal officer, and a journalist all receive the same email at 7:03 AM. The plant manager needs the evacuation order; the legal officer needs liability language; the journalist needs a quote. Pyramid gives them one shared anchor: Evacuations begin at 8:00 AM.

That sounds clean. The catch is this: stakeholders who feel rushed to that bottom line often push back. They want to know why before they accept what. In a slow-brewing contamination report — where the toxin levels rose over weeks, not minutes — a Pyramid opening can feel like an ambush. The odd part is, it still works for the decision-maker who has sixty seconds before a board call.

Best paired with a single audience whose biggest disagreement is speed, not substance. When both sides agree the risk is real but fight over how fast to respond, Pyramid ends the argument by stating the response first.

Narrative: build context first

Here you invert the order: scene, conflict, resolution. The Narrative structure opens with a concrete moment — a water sample bagged at 2:00 AM, a logbook entry, a phone call from the field. Then it traces the path from that moment to the risk. I have watched a narrative script defuse a room where one stakeholder group believed the company was hiding history. By walking them through the sequence — first the lab flagged an anomaly, then we double-checked the batch, then we found the pattern — the structure answers the question Why didn’t you tell us sooner? before it gets asked.

But narrative takes time. The reader must follow the thread. If your audience includes a regulator who wants only the legal risk code and a community liaison who wants the human story, you can't serve both with one story arc. The regulator will skim. The liaison will feel unheard.

Fragments work here: Wrong audience. Wrong stakes. Narrative thrives when the core conflict is trust, not time. If your stakeholders already distrust the data source, a cold bottom line at the top will read as a cover-up. Narrative earns trust by showing your work.

Modular: assemble blocks per audience

Modular is the cheat code for multi-stakeholder deadlocks — but only if you admit it's not one script. You build three to five content blocks: a risk summary, a technical detail box, a timeline, a Q&A, a call-to-action. Each block is self-contained. Then you arrange them based on who reads first.

One block says 'Stop production.' Another says 'Here is the data that justifies it.' A third says 'Here is how we tell the public.' The order changes; the blocks don't.

— internal team debrief after a product recall, Portland, 2023

The modular structure survives the worst-case scenario — a stakeholder who reads only two blocks and forwards only one. Your message doesn't collapse because the blocks are designed to stand alone. The trade-off: modular scripts are longer. They repeat information. A reader who consumes all blocks will hit redundancies, and that can feel like the writer doesn't trust them to connect dots.

Most teams skip this choice because it feels like extra work. They default to one script and one order, then patch the gaps with cover emails or separate briefings. That approach creates version-control nightmares. Modular demands upfront planning — but it's the only structure that lets you hand the same document to a union rep and a federal inspector without editing the text itself. You just reorder the stack.

Criteria to Compare Them By

Decision speed

How fast must stakeholders sign off? I have watched teams burn three weeks debating a single paragraph when the crisis had already moved to phase two. If your window for alignment is measured in hours—not days—pick the structure that lets people say yes without rewriting the entire spine. Pyramid works here: top-loaded findings mean executives can approve the headline and let you fill in details later. Narrative, by contrast, demands buy-in on a story arc. That's slower. One client needed approval from legal and communications and the regional VP. Pyramid got them a signed script in ninety minutes. Narrative would have killed the afternoon.

Reality check: name the epidemiology owner or stop.

Reality check: name the epidemiology owner or stop.

Not yet convinced?

The catch is speed can mask deeper disagreement. A fast sign-off sometimes means nobody read past the bullet—and that bullet might contradict what the field team actually needs to say. So pair speed with a rule: anyone who approves the structure must also approve a worst-case scenario sentence buried three paragraphs deep. If they flinch, you have not achieved alignment. You achieved avoidance.

Audience trust

Which audience will feel manipulated by the format itself? Communities recovering from a plant incident, for example, resent glossy storytelling. They want data, chronology, and a clear statement of who failed. Narrative structure can signal empathy—but if the empathy feels polished, trust fractures. Modular structure, where each stakeholder group gets their own discrete block, preserves honesty: the investor block says "we're investigating" while the employee block says "here is exactly what changed on the line." The trick is labeling those blocks transparently. Hide the segmentation and you look like you're hiding bad news.

We tested three structures with a focus group of affected residents. Pyramid scored highest on clarity. Narrative scored lowest on honesty—even when the words were identical.

— Risk communications lead, chemical manufacturing firm

That pattern holds broadly. If your stakeholder map includes people who already distrust your organization, default to the structure that foregrounds evidence over emotion. Save narrative for internal audiences who already share your mission.

Message retention

What do you want people to remember in forty-eight hours? Long sentences kill recall. So does burying the action step inside a story. Modular structure lets you repeat the core instruction—"evacuate zone B"—in every module, which boosts retention by brute force. Narrative relies on emotional anchoring: the story of the engineer who spotted the leak sticks because it has a character, not because the data was repeated. Pyramid sits in the middle: the lead conveys the decision, but supporting details fade fast.

Here is the trade-off no one admits: retention for one audience can undermine retention for another. If employees remember the heroic rescue story but forget the safety protocol change, you have a problem. I have seen this exact failure—company A told a gripping narrative about their recall response; six months later, customer service reps could not name the refund process. Retention without precision is dangerous. Match structure to the single must-remember action per audience, not to what sounds memorable.

Organizational alignment

Who has to execute this script—and will they actually use the format you choose? A modular script looks clean on paper but demands discipline from every regional office. If your compliance team won't enforce module boundaries, the whole thing degenerates into a messy hybrid nobody trusts. I once watched a multinational adopt a narrative structure because the CEO "liked stories," but the field teams in three countries could not adapt the single story to local regulations. They ended up rewriting everything anyway—defeating the purpose of a shared script.

Map your org chart first. If you have ten people who can veto content, pyramid gives each one a single slot to inspect. Narrative invites them to rewrite the whole sequence. Modular lets them edit their own block without touching yours. That last option is often the most realistic for large, siloed organizations—even though it produces a fatter document. Fat is fine if it means everyone actually uses the script instead of writing their own.

Trade-Offs at a Glance: Pyramid vs. Narrative vs. Modular

When speed beats storytelling

The Pyramid structure front-loads the critical update—what happened, how bad, what next—in the first thirty seconds. That sounds perfect for a fast-moving industrial fire or a product recall where minutes cost credibility. I have watched crisis teams run this exact play: one line of context, then the risk, then the immediate action. The trade-off is brutal, though. You can't warm up. No scene-setting, no empathy preamble, no gradual reveal. Stakeholders who expect a human touch—say, grieving families or worried local officials—may feel processed, not protected. The pyramid wins when the clock wins. But it answers a question nobody asked: “How fast are you?” instead of “Do you care?”

Most teams skip this: the pyramid works only if your audience already trusts your authority. Without that trust, the headline lands like a slap. It answers the “who” and “what” but leaves the “why” hanging. And in a crisis, the “why” is often the only thing that prevents the next wave of panic.

When trust requires a story

The Narrative structure reverses the order. You begin with context—the patient, the product, the history—then walk toward the bad news. This buys you something the pyramid never can: emotional permission. I have seen a hospital CEO use a narrative script to explain a surgical error to a room of families, and the difference was visceral. People nodded before the data came. They wanted to hear the numbers because they felt heard first. The catch is speed. Narrative scripts take longer to write, longer to approve, and longer to deliver. A 2020-ish manufacturing crisis taught me this: the legal team cut the story opener, the CEO rewrote it, and by noon the news cycle had already framed the event as a cover-up. Narrative can cost you the narrative window. You trade velocity for resonance—and sometimes the market trades back.

That hurts when your audience is a mix of journalists and victims. Journalists want the bullet. Victims want the story. One narrative script can't serve both unless you're willing to make one group wait. The real risk? You pick narrative to seem “caring,” but the delay makes you seem evasive. Wrong order. Wrong audience. Wrong outcome.

When multiple audiences force modularity

The Modular structure solves the deadlock by refusing to choose one flow. Instead, you build a core message block—two or three sentences—and then attach audience-specific branches: a technical insert for regulators, a human-impact paragraph for community members, a financial context snippet for investors. Each branch is a self-contained section that can be swapped, dropped, or reordered without breaking the spine. I have seen this work beautifully during a multi-site contamination alert where the corporate team needed to speak to employees, regulators, and retail partners simultaneously. One spine. Three tails. No contradiction.

The trade-off is maintenance complexity. Modular scripts require version control, careful tagging, and a writer who understands each audience’s information threshold. If the core block changes—say, the contamination source shifts—every branch must be rechecked. The risk is drift: branches that contradict each other because nobody updated the regulatory tail after the legal team rewrote the community version. Modularity scales, but it also multiplies failure points. You gain flexibility. You lose simplicity. And in a live crisis, simplicity is often the only thing that keeps a team from shouting past each other.

“Pyramid buys speed at the cost of empathy. Narrative buys trust at the cost of speed. Modular buys coverage at the cost of control. Pick the cost you can afford.”

— crisis comms lead, after a three-site food recall

The decision tree in section eight will walk you through the exact moment to choose each structure. For now, hold this tension: no script format is safe. The right choice depends on which failure mode you fear most—being slow, being cold, or being inconsistent. That's the trade-off at a glance. The next step is implementation, where most teams trip over their own approval chain.

How to Implement After You Pick a Structure

Draft with a single spine

One script, one narrative backbone. That sounds obvious. The reality is messier. I have watched teams produce three separate drafts simultaneously—one for legal, one for community relations, one for the C-suite—only to discover nobody can remember which version says what, and the seams between them blow out during the first real test. Pick your chosen structure—Pyramid, Narrative, or Modular—and commit the first draft to a single spine. If you chose Pyramid, write the lead message first, then let every sentence beneath it answer the question "So what?" If you chose Narrative, lock the protagonist and the conflict before you touch the resolution. If you chose Modular, write one standalone module end-to-end before branching to the next. Don't let the document branch until the main thread holds together on its own.

Flag this for epidemiology: shortcuts cost a day.

Flag this for epidemiology: shortcuts cost a day.

The catch is efficiency feels like waste. Stakeholders will ask for parallel tracks. Resist. The odd part is—when you force a single spine, the cuts reveal themselves faster. A paragraph that can't connect to the lead gets flagged on day one, not during final review.

“A draft is a map of what you think matters. A single spine shows you where the map folds wrong.”

— corporate comms lead, after a 14-revision cycle that finally stuck

Stress-test with a devil's advocate

Draft done? Great. Now break it before your crisis does. Hand the script to someone who openly disagreed with the structural choice. Not a friendly reviewer. A skeptic. Their job is to read it as if the first audience were hostile, confused, or distracted—all of which is likely. What usually breaks first is the connector language: the "however" that masks a logical gap, the "meanwhile" that jumps timelines without warning. I have seen this exercise kill a Pyramid script inside twenty minutes because the lead message collapsed when tested against a known data point the stakeholder group would remember. That's not failure. That's a repairable crack.

You want the advocate to ask three things: Does the structure survive a hostile read? Does any single module contradict another? Is the payoff worth the setup? Be specific with them—give them the actual audience persona, not a generic "reader." If the script holds, you have authority. If it cracks, you have a fix before go-live. Either outcome beats a post-launch apology.

Align stakeholders on one master version

Here is where most implementations stall. The structure is chosen, the draft is tested, and then someone in a Friday afternoon email suggests "just swapping the order of the first two blocks." That's the structural debate reopening through the back door. Stop it. You agreed on a structure. Now you agree on one master version. Not a working copy, not a "legal alternative," not a version that lives in a shared drive with three filenames. One master. The way to get there is to schedule a single sign-off meeting with the people who hold veto power—no more than four people. Show them the tested draft. Show them the devil's advocate notes. Then ask for one of exactly two decisions: approve or identify one specific, non-structural edit. If they demand a structural change, the decision tree from the previous section gets reopened, and you reset the timeline. That hurts.

Most teams skip this hard boundary. They maintain parallel versions "just in case," and two weeks later nobody remembers which one went to the regulator. The consequence is a return spike in clarification calls—exactly the waste the script was supposed to prevent. Lock the master version in a shared folder with a date stamp. Remove edit permissions for anyone not in the sign-off group. Then distribute the living document only to the person who will read it during the actual risk event. Everyone else gets a PDF summary. That's how you protect the structure you fought for.

Risks of Choosing the Wrong Structure—or Skipping the Choice

Wasted drafting time—and the resentment that follows

You spend three days polishing a script. The executive team signs off. Then legal rewrites half of it because the narrative flow buried a compliance note. That sounds fine until you realize: the rewrite invalidated the stakeholder map you spent a week building. I have seen teams cycle through five drafts because nobody asked “What structure does this audience actually need?” before anyone typed a word. The result isn't just lost hours.

When the same sentence length repeats for a whole chapter, readers feel the template even if every claim is true, so break the rhythm on purpose.

It's quiet anger. Copywriters stop volunteering for risk work. Subject-matter experts stop responding to Slack messages. They learned—correctly—that their effort will be overwritten. The next time a crisis hits, you have no bench. That's the hidden cost of a structure mismatch: you burn goodwill faster than you burn deadlines.

Wrong structure causes rewriting, not just reordering. A pyramid script that buries the action step under background paragraphs forces reviewers to rebuild from scratch. A modular structure that was never meant for a linear rollout makes every reviewer feel like their section is an afterthought. The fix isn't more collaboration—it's a deliberate structural decision before the first draft exists.

Eroded stakeholder trust—the slow leak nobody monitors

Picture a public-health agency using a narrative script for a rapidly evolving outbreak. The narrative builds suspense. It saves the recommendation for the climax. But the county officials reading it need the mitigation step now, not in paragraph eight. They start ignoring the script entirely. They develop workarounds. They call the communications lead and say “just send me the bullet points.” That's not efficiency—that's a trust breakdown coded as a preference. Once stakeholders decide the script structure is incompatible with their workflow, they stop waiting for approval. They go rogue. And once that pattern sets in, it takes months of consistent, usable scripts to rebuild the habit of compliance.

‘A script structure that fights the user’s context is worse than no script at all—it teaches users to ignore you.’

— emergency manager, after three months of field-testing modular scripts in a hospital network

The odd part is: most teams never get feedback on this erosion. Stakeholders don't file a ticket saying “your narrative intro is costing me ten minutes per read.” They just stop reading. Then they blame the messenger. The structure becomes invisible—until it isn't.

Mixed signals that amplify confusion—especially in cross-functional crises

This is the worst failure mode. A financial services firm tried to satisfy both retail investors (who wanted step-by-step reassurance) and regulators (who wanted chronological fact logs). They compromised on a hybrid script: narrative opening, modular middle, pyramid close. The result was a Frankenstein document.

Not always true here.

The tone shifted three times. The action step appeared twice, with slightly different wording. Retail investors felt patronized by the regulatory boilerplate. Regulators flagged the narrative opener as “potentially misleading emphasis.”

That hurts. Because nobody made a wrong call per se—they just refused to choose. They tried to serve two masters with one script, and both masters rejected it. The lesson is uncomfortable: a structure that tries to be everything to everyone usually ends up being trusted by no one. A modular script with clearly labeled audience tracks—one for investors, one for regulators—would have prevented the collision. But that required admitting early that one size doesn't fit. Most teams skip this admission.

What usually breaks first is the seam between the sections. The narrative arc clashes with the modular list. The pyramid summary contradicts the story's implied priority.

Odd bit about epidemiology: the dull step fails first.

Odd bit about epidemiology: the dull step fails first.

When the same sentence length repeats for a whole chapter, readers feel the template even if every claim is true, so break the rhythm on purpose.

You end up with a document that needs a foreword explaining how to read it. That's not a risk script anymore. That's homework.

Skip the structural choice entirely, and you default to whatever the most vocal stakeholder wants in the moment. That is reactive. It shifts with each meeting. Your script becomes a mirror of the last person who complained—not a tool designed for a specific audience. The fix is boring but necessary: pick one structure, defend it with logic, and let the other audience get a different version. Silence on structure is not neutrality—it's drift.

FAQ: Common Doubts About Script Structure Choices

Can you combine pyramid and narrative?

You can, but the seam usually blows out. I have seen teams try to open with a narrative hook—"At 3:14 PM, the sensor array went dark"—then pivot hard into inverted-pyramid facts: who, what, when, root cause. The reader feels whiplash. A story primes emotional attention; a pyramid demands transactional scanning. Those are different cognitive gears. The hybrid works only if you clearly gate the two: one full section for narrative context, a second section for the hierarchy of facts, and a visible divider like a subheading or a horizontal rule. Without that gate, stakeholders on both sides complain the message is "neither fish nor fowl."

What usually breaks first is tone. Narrative paragraphs use conversational syntax. Pyramid bullets strip that away. The transition reads like a genre error.

What if legal wants bottom line but PR wants story?

That is not a structure problem; it's a sequence problem. PR wants a chronology that builds toward a reassuring outcome. Legal wants the liability disclaimer at the top so nobody scrolls past it. The fix is modular: write the mandatory bottom line as the first block—one <p> that answers "What happened and who is liable?"—then immediately hand the reader a narrative second block. Each side gets its own territory. No mixing. No compromise sentence that tries to be both blunt and lyrical. That fails every time.

"We wrote one paragraph that said 'The valve failed due to material fatigue. No personnel were at fault.' Then the next paragraph started 'Here is how our team caught it…' Both parties approved because neither had to edit the other's section."

— risk communication lead, industrial manufacturer

The trick is to sequence, not blend. Legal gets the first word. PR gets the last word. Neither has to share a sentence.

How do you know when modular is overkill?

Modular scripts—discrete, self-contained blocks that can be reordered or omitted—are a good choice when you have three or more stakeholder groups with incompatible framing preferences. But modular has a hidden cost: each block repeats context. The risk summary block has to restate the incident. The timeline block restates it again. The customer-facing block restates it a third time. For a single-audience memo—say, a one-page ops alert for internal engineers only—that repetition wastes space and slows comprehension. You end up with a document that feels like a binder of fact sheets rather than a coherent read.

The catch is that modular scripts also fail when the message must unfold in a fixed order. If the regulator insists on cause before consequence and the community team insists on consequence before cause, a modular structure lets each group read their preferred block first—but it can't prevent them from seeing the other blocks. That visual adjacency can cause confusion if the blocks subtly contradict each other. I once saw a modular script where Block A said "no immediate risk to residents" and Block D listed "evacuation zones." The blocks were factually consistent but visually jarring when read side by side. Wrong order. Not yet. That hurts.

How do you spot overkill early? Map your audience groups. If you have two groups—executives and affected users—modular is usually unnecessary. If you have five groups—regulators, investors, frontline staff, media, legal—modular starts paying for itself. The inflection point is three. Fewer than three: pick pyramid or narrative. Three or more: consider modular, but budget time for a duplicate-context review pass.

Next action: take your stakeholder list from Step 1 and count groups. If the count is one or two, stop reading about modular. Pick pyramid if the news is bad, narrative if the news requires explanation. Your decision tree starts there.

Recommendation Recap: No Hype, Just a Decision Tree

Start with crisis type — it prunes most options fast

You can waste weeks arguing about audience preferences when the real constraint is the situation itself. A confirmed chemical release with shifting wind data? You don't have time for a narrative arc. Pyramid wins — fact-first, no ornaments. The opposite holds for a slow-burn policy change where trust is already cracked. Here a bare-list pyramid reads like a diktat; narrative structure lets you acknowledge pain before you propose fixes. I have watched teams burn two days debating modular vs. narrative when one glance at the incident timeline would have settled it. Crisis type first. Everything else is secondary until that filter runs.

The catch is — some crises blur. A data breach that started three weeks ago but only emerged today: is that urgent or chronic? Treat it as urgent with a narrative tail. Open with the facts (breach scope, remediations in place) then pivot to a short narrative about what went wrong. That hybrid is not on the tree, but the tree gets you 80% of the way. You tweak the last 20% after the filter runs.

Audience second — one stakeholder changes everything

Executives want brevity. Regulators want traceability. Employees want acknowledgment before instructions. You can't serve all three with one spine. The decision tree branches here: pick the audience whose rejection would kill the message fastest. Usually that's the regulator — a compliance mismatch stops distribution before anyone reads further. But I have seen a community-relations script where the resident council was the wall. We fixed that by swapping modular (which looked disjointed to them) for a narrative that placed their concerns in scene one.

‘We chose pyramid for the regulator, then rebuilt the top section as a narrative for the public version. Same data, different emotional entry point.’

— crisis comms lead, industrial incident, 2023

That sounds fine until you realize you now maintain two scripts. The trade-off is real: one structure, one audience, one editorial pass. Two structures means double the review cycle. The decision tree can't eliminate that cost — it just ensures you incur it deliberately rather than by accident.

Timeline third — the hidden variable that flips decisions

Most teams skip this. They pick a structure for the first message and then discover the structure fights them on day three. A modular script that worked for the initial ‘we're investigating’ release becomes a messy patchwork when you need to issue three sequenced updates. Pyramid handles sequencing cleanly — each update just replaces the top fact block. Narrative fights sequencing because readers expect emotional closure, not incremental reveals. Wrong order. Not yet. That hurts returns and trust.

So the third branch is: will you issue multiple updates within 72 hours? If yes, lean pyramid or modular. If this is a one-and-done statement — a policy rollout, a one-off apology — narrative can carry the full weight. I have watched a single narrative script outperform every modular version for a hospital apology precisely because there were no follow-ups. The family heard one story, complete. No awkward sequel needed.

The decision tree is not magic. It's a cheap filter that kills bad options before they waste a meeting. Crisis type, then audience, then timeline. That order, applied honestly, will eliminate four of the six theoretical script structures you considered. You're left with two. Now you argue about cost, not about philosophy. That is the win.