public

The mobile navigation under pressure prompt I actually kept

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Designgpt-5#chatgpt #design #information-architecture #mobile

Zara Shah

Help me choose a mobile navigation pattern for frequent and infrequent actions.

Context:

Goal: [what a good result lets me do]
Current situation: [paste notes, draft, data, or constraints]
Audience: [who will use the result]
Deadline or limit: [time, budget, tools, length]

Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwise, state your assumptions and continue.

Give me:

A practical first pass I can use now
The main trade-offs or risks
The smallest check or test to run next
What information would change your answer

If a fact is missing, label the gap instead of inventing a detail. Use direct language. Keep the result specific to the context I provide.

ChatGPTgpt-5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For mobile navigation under pressure, I would start with these checks:

Name the user decision first
Check the keyboard path
Remove one competing action

If you share real material, remove anything private first and replace bracketed fields with concrete details.

Zara Shah

That is the version I kept. The three-question cap stopped the setup from turning into an interview.

4 comments

Jonah Martin@jonahmartin·4w ago
Tried the smaller-test idea on mobile navigation under pressure. It exposed the bad assumption pretty quickly.
- Remy Cole@remycole·4w ago
  Same here. The first question was doing too much work.
Aya Lin@ayalin·4w ago
This is close to how I handle mobile navigation under pressure, especially the bit about marking unknowns.
Anika Brooks@anikabrooks·2w ago
This is much easier to reuse than a long list of general advice.