Pick one problem and one supported response
A problem-solution slideshow works when each slide advances a single idea. Define the intended reader, a task they recognize and a product action that responds to it. Check the real feature before writing; a carousel should not promise an outcome the product cannot demonstrate.
This fictional example uses NorthStar Notes, which has a project call note with a next-step section. It is an illustrative creative brief, not an actual customer case or tested campaign.
Plan a complete five-slide sequence
Slide 1 — “The call is over. Where did the next step go?” This establishes a specific moment rather than a generic productivity promise.
Slide 2 — “You have the notes. Now you need the action you agreed on.” This clarifies the reader’s task. Slide 3 — “Open the project and choose the call note.” This introduces the first actual action.
Slide 4 — “Check the next-step section in the same note.” Pair it with a readable, sanitized view of that section if your real app supports it. Slide 5 — “Start with the next step.” Give the reader a relevant route to learn more if one exists. These are planning words, not evidence that a user achieved a result.
| Slide | Message | Visual or check |
|---|---|---|
| 1 | Where did the next step go? | Establish the situation |
| 2 | Find the agreed action | Keep the problem specific |
| 3 | Open the project note | Show an accurate product action |
| 4 | Check next steps | Use a sanitized real screen |
| 5 | Start with the next step | Choose a relevant next destination |
Give each slide a visual job
The opening can use a simple situation-focused visual. Use a project view for the action and a note view for the feature; do not use a generated interface as proof of what the application does. A real screenshot must come from an account and data you are allowed to share. Mark up only the relevant control and keep surrounding context readable.
If the product cannot show a project note or next-step section, rewrite the sequence around a feature it can actually demonstrate. Avoid invented automation, quantified savings, customer quotations and universal results.
Review the sequence as one story
Read the slides in order without an explanation. Can a reader describe the problem, the relevant action and what to do next? Remove a slide if it only repeats another. If the sequence instead teaches multiple detailed steps, a tutorial may be the more useful structure.
Preview at phone size, check contrast and text placement, then inspect the actual export. Test links and any destination separately before sharing. A clear sequence is an editorial starting point, not a promise of reach or conversion.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
Audience: __. Problem: __. Verified feature: __. Five slide messages: __. Screen permission: __. Reader next step: __.Browse the founder guide library for the next task in your workflow.