In-App Feature Discovery Brief Template
Introduce a released capability where it helps an existing task, with truthful limits, optional detail and a route back to work.
When to use this template
Use this when a real product update could help a specific task and the team needs to decide where and how to explain it inside the app.
Choose another approach when: You want to announce planned functionality as released, force everyone through a feature tour, or hide an upsell inside help that appears necessary to continue.
Gather these inputs
- The released capability and actual audience eligibility.
- The existing task where the capability becomes useful.
- A short accurate explanation, working action and revisit path.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
A fictional app releases section reordering. The discovery brief places a short explanation near checklist editing for users who can access it, with an optional demonstration. It does not block someone opening an existing client preview with a full-screen celebratory tour. If the feature is limited to an approved beta, the message respects that eligibility. Dismissing it does not remove all future help, and the text explains actual behavior rather than promising that reordering will eliminate client questions.
How to use it
- Verify release state and identify a task where the capability is relevant.
- Design the smallest accurate explanation and optional deeper route.
- Check eligibility, dismissal and rediscovery in the real product journey.
Check before using it
- The announcement describes a genuinely available capability.
- The person can continue unrelated work without a forced tour.
- Material access or pricing conditions are clear.
What to measure
Observe whether eligible users understand and use the capability when relevant. Announcement impressions or dismissals alone do not prove adoption, value or retention impact.
Research and sources
Contextual non-intrusive help and accurate information support this original brief. It does not claim a universally effective feature-announcement pattern.
- NN/g: Onboarding Tutorials vs. Contextual Help — checked 2026-10-23. Task-relevant contextual help, dismissibility and avoiding unnecessary memorization or interruptions.
- NN/g: Help and Documentation — checked 2026-10-23. Proactive and reactive help focused on the user’s task, findable concrete steps and appropriate context.
- Google: Creating helpful, reliable, people-first content — checked 2026-10-23. Original value, useful answers, transparent sourcing and a clear audience.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.