Reviewing the Story Plan
Guides you on how to confirm the logic of your presentation by reviewing the audience, narrative axis, recommended structure, lack of evidence, and additional questions.
The story plan is a design draft that outlines who the presentation is intended to persuade and with what logic before writing slide copy. Correcting the direction at this stage can greatly reduce the scope of later storyline and skeleton revisions.
Items to Check in the Story Plan
Key Components
Domain and Data Scope
Verify what business context and data Rhetis used to plan.
Audience and Required Decisions
Confirm that the audience’s perspective, concerns, and post‑presentation actions are correct.
Narrative Axis
Check the one‑sentence logic that runs through the entire presentation from problem to conclusion.
Recommended Structure
Compare several development options suitable for the audience and purpose, their fit, and the reasons for selection.
Lack of Evidence
Identify parts that lack supporting numbers, sources, or examples.
Additional Questions
Confirm items the user must decide on or supplement before moving to the next step.
Review Order
- 1
Read the audience and decisions first
Check whether the presentation truly matches the situation. If the audience differs, even the same material will change the position of the conclusion and depth of explanation.
- 2
State the narrative axis in one sentence
Team members should understand “why this presentation is being made” by reading just that sentence. If it’s too generic, revise it so that the problem, change, proposal, and expected effect become clear.
- 3
Compare recommended structures
Look at what each step does rather than the structure’s name. Investor, executive‑report, and customer‑proposal versions emphasize different evidence and order.
- 4
Address lack of evidence
Attach the necessary data, delete or soften the claim, or request it be marked as an assumption. Do not generate arbitrary numbers to create evidence.
- 5
Answer additional questions
Decide on the scope and priorities that are still unsettled. If answers are difficult, limit the scope to what can be confirmed with current data.
- 6
Generate the storyline with the chosen structure
Once logic and essential evidence are sorted, move to the next step. If there are still major disagreements, conduct a team review at this stage.
Questions to Use When Reviewing
- Is the most important information for the audience placed at the front?
- Are the conclusion and request sufficiently specific?
- Do problem, evidence, proposal, and expected effect flow naturally?
- Does each claim have evidence that actually exists in the data?
- Are internal information and externally publishable information distinguished?
- Is there any content that can be omitted from this presentation?
- Can the core logic be explained within the allotted length?
Example Revision Requests
- “Use Recommended Structure 1, but move the conclusion and budget request to the second step.”
- “Because existing customer usage data is a stronger evidence than market size, change the priority.”
- “Delete the 2027 growth forecast that has no evidence, and use only the confirmed pipeline.”
- “The audience is a board with no technical background. Redesign to focus on risk and business impact rather than product structure.”
The story plan is not the final copy. Focus on confirming the order, logic, evidence, and requested actions of the presentation rather than polishing sentence wording.