Feature discovery
Introduce something new at a moment when the crew has attention to spare, and lead with what it does for them.
On this page
Say “bosun, when is high water?” and hear the next tide for this anchorage, without opening the chart.
A discovery message tells the crew about something new or changed: a capability they have not used, or a familiar one that moved. On a vessel, when it appears matters more than what it says. A tip that appears in the middle of a tack, or beside an alarm, is a distraction at the worst moment.
When to show it
| Condition | Discovery |
|---|---|
| Moored or at anchor, board clear | May appear |
| Underway | Never |
| Any alarm, warning or caution unacknowledged | Never |
| Night theme | Never |
| Already dismissed | Never again |
Anatomy
- Title: what the crew can now do, in a few words. "Ask about the tide by voice", not "New: voice tides".
- Body: how to use it, with the exact words or the place to tap. One or two sentences.
- Actions: one to try it now, one to dismiss it.
Voice and tone
Discovery may sound a little more eager than the rest of the interface: it is the one place bosun introduces itself. It stays clear and practical, and it never interrupts.
Dismissal and durable help
Keep discovery optional and dismissible. Record dismissal at the scope that owns the preference, and do not reopen the same tip on every navigation. A dismissed tip must not remove access to the feature's ordinary label or help page. Only show an invitation where the feature is available to that reader.
In documentation, explain the feature through a working example with a direct link to its guide. Release notes can introduce a capability; they should not be the only place its ongoing behavior is documented.