Explain the feature through a situation
A feature story shows when a capability matters and what it makes possible. It differs from a tutorial: the reader understands the role of the feature without needing a complete sequence of interface instructions. Choose one audience, one situation and one verified feature.
In this fictional example, NorthStar Notes has a call note with a next-step section. That is an invented planning fact, not a customer case or an actual product screenshot.
Build a five-slide feature story
Slide 1: “The call is over. The follow-up is tomorrow.” Slide 2: “You need to remember what the team agreed to do next.” Slide 3: “Keep the next-step section with the call note.” Slide 4: “Open the note when you are ready to follow up.” Slide 5: “Start from the next action.”
The story follows one situation through an actual feature. It does not claim automatic reminders, a measurable time saving, or a customer outcome. Replace the example with facts you can verify in your own app.
| Slide | Message | Visual role |
|---|---|---|
| 1 | The call ends | Establish the situation |
| 2 | Find the agreed action | Show the audience task |
| 3 | Next steps live with the note | Show a verified feature |
| 4 | Open the note before follow-up | Connect feature to use |
| 5 | Start with the next action | Offer an honest next step |
Assign a truthful visual to each slide
Use an owned or licensed visual for the setup, then a sanitized real screenshot for the feature when available. A generated picture of an interface can illustrate an idea, but should not be labeled as a real product screen. Keep enough context around the feature for the viewer to understand where it lives.
If you do not yet have permission to show a screen or customer data, prepare the slide copy and visual brief first. Obtain the right asset before publishing a visual that implies a real product view.
Review for story, accuracy and readability
Read the slides in order. The opening should promise the same situation the later slides address, and each slide should add a new part of the story. If readers need exact clicks or setup instructions, link to a tutorial rather than squeezing unsupported directions into a feature overview.
Preview the export at phone size, checking contrast, cropped controls and the destination named at the end. This is a planning example; it does not promise views 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: __. Situation: __. Verified feature: __. Five slide messages: __. Permissioned proof: __. Destination: __.Browse the founder guide library for the next task in your workflow.