Product demos & UI / Prompt

Prompt: navigate a nested menu without losing the viewer

Show one route through the menu and preserve its hierarchy. Give each selected label enough time to be read before the next level appears.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Teams explaining multilevel navigation.

What to prepare

  • Complete menu-state sequence
  • Actual activation behavior
  • Destination screenshot

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Plan a 30-second illustrative navigation demo using the actual product menu structure. The example path is Workspace settings, then Notifications, then Review reminders; replace those labels if the supplied interface differs. Start with the full navigation context. Open the first level, hold its selected label, then open the next level through the verified interaction. Keep a breadcrumb or short production path label visible as the hierarchy deepens. Arrive at the Review reminders heading and hold it with the relevant setting visible. Do not change the setting in this navigation-only demo. Exclude unrelated branches and avoid sweeping the cursor across every menu item. Use “Find review reminders” as the task and “You are in Review reminders” at the confirmed destination.

Make it your own

Menu path
Use exact labels in their actual order.
Activation
Show verified hover, click or keyboard behavior.
Destination
Confirm arrival through a real heading or state.

Verify the route

Supply each menu state and the destination. Confirm whether a submenu opens on hover, click or keyboard activation. A familiar menu appearance does not establish its trigger.

Adapt the hierarchy

For a mobile navigation drawer, use its actual back controls and headings. If there is no native breadcrumb, a clearly styled video annotation may describe the route without pretending to be part of the interface.

Fix lost orientation

If the selected parent disappears before the child is understood, hold longer or retain the path label. If the final screen has a different heading, verify the route rather than relabeling the screenshot. Remove accidental setting changes from the task.

Review checklist

  • Each hierarchy level is readable.
  • The route remains identifiable.
  • Navigation is not confused with configuration.
Explore product demos & ui ↗