La versione breve
- Il lavoro UX parte dalle difficoltà osservate. Questi prompt chiedono di esplicitare le ipotesi, descrivere l'attività e proporre un test prima di modificare l'interfaccia.
- Le schermate generate sono un punto di partenza. Testale con contenuti reali, tastiera, schermi piccoli e persone che dovranno usarle. Una buona resa visiva non dimostra l'usabilità.
Il lavoro UX parte dalle difficoltà osservate. Questi prompt chiedono di esplicitare le ipotesi, descrivere l'attività e proporre un test prima di modificare l'interfaccia.
Le schermate generate sono un punto di partenza. Testale con contenuti reali, tastiera, schermi piccoli e persone che dovranno usarle. Una buona resa visiva non dimostra l'usabilità.
Come usare questa raccolta
Scegli l'attività più vicina al tuo lavoro. Copia il prompt, sostituisci la scena generica o il contesto del codice con i tuoi dati e mantieni i vincoli utili a valutare il risultato. Modifica una variabile alla volta per capire cosa migliora.
Il metodo segue la guida a First Draft di Figma: fornisci un contesto preciso e controlla il risultato, senza dare per corretta una prima bozza ben presentata.
Prompt per descrivere l'attività
Per descrivere l'attività, indica l'utente e la decisione che la schermata deve aiutarlo a prendere.
1. Un ripristino della password poco chiaro
Design a confusing password reset for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
2. Un modulo di candidatura lungo
Design a long application form for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
3. Un percorso di disdetta difficile da trovare
Design a hidden cancellation path for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
4. Una ricerca senza risultati
Design an empty search result for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
5. Un pannello di filtri mobile
Design a mobile filter panel for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
6. Un caricamento in ritardo
Design a delayed upload for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
7. Una pagina di impostazioni troppo densa
Design a dense settings page for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
8. Un selettore di date non accessibile
Design an inaccessible date picker for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
9. Una schermata di conferma poco chiara
Design a weak confirmation screen for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
10. Un passaggio poco chiaro al termine dell'onboarding
Design a poor onboarding handoff for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
Prompt per progettare la schermata principale
Per progettare la schermata principale, indica l'utente e la decisione che la schermata deve aiutarlo a prendere.
11. Un ripristino della password poco chiaro
Design a confusing password reset for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
12. Un modulo di candidatura lungo
Design a long application form for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
13. Un percorso di disdetta difficile da trovare
Design a hidden cancellation path for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
14. Una ricerca senza risultati
Design an empty search result for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
15. Un pannello di filtri mobile
Design a mobile filter panel for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
16. Un caricamento in ritardo
Design a delayed upload for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
17. Una pagina di impostazioni troppo densa
Design a dense settings page for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
18. Un selettore di date non accessibile
Design an inaccessible date picker for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
19. Una schermata di conferma poco chiara
Design a weak confirmation screen for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
20. Un passaggio poco chiaro al termine dell'onboarding
Design a poor onboarding handoff for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
Prompt per gestire i dati mancanti
Per gestire i dati mancanti, indica l'utente e la decisione che la schermata deve aiutarlo a prendere.
21. Un ripristino della password poco chiaro
Design a confusing password reset for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
22. Un modulo di candidatura lungo
Design a long application form for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
23. Un percorso di disdetta difficile da trovare
Design a hidden cancellation path for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
24. Una ricerca senza risultati
Design an empty search result for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
25. Un pannello di filtri mobile
Design a mobile filter panel for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
Cosa verificare prima di usare il risultato
Le schermate generate sono un punto di partenza. Testale con contenuti reali, tastiera, schermi piccoli e persone che dovranno usarle. Una buona resa visiva non dimostra l'usabilità.
Se il risultato non risponde al compito, accorcia il prompt e precisa il fatto o il vincolo mancante. Conserva la versione usata per poter riprodurre il contenuto finale o la modifica al codice.
Approfondimenti
Continua con una guida correlata
Mettilo in pratica
Il prossimo passo
Hai una domanda o una correzione?
Contatta Thrive
