Design a form people actually finish
Reviews or designs a form field by field, cutting questions, fixing input types, and improving layout, validation, and completion rates.
The prompt
Help me design (or fix) a form so more people complete it correctly.
Form purpose: [e.g. signup, checkout address, insurance application, support request]
Who fills it in and on what device: [USERS, MOBILE/DESKTOP SPLIT]
Current fields: [LIST EACH FIELD WITH ITS TYPE AND WHETHER IT IS REQUIRED]
Why each field is needed: [OR "not sure" - I will check]
Known problems: [DROP-OFF, COMMON ERRORS, SUPPORT TICKETS]
Regions served: [COUNTRIES - affects names, addresses, phone formats]
Review each field and answer: Is it needed now, later, or never? Can we infer it (e.g. city from postal code)? Is the input type right (email keyboard, date picker vs. text, autocomplete attributes)? Is the label clear and visible above the field?
Then recommend:
- Field order and grouping; single column layout unless there is a strong reason.
- Whether to split into steps, and how to show progress.
- Required vs. optional marking (mark the minority).
- Validation timing and messages, input masks to avoid, and formats that should accept any reasonable entry.
- Accessibility: labels tied to inputs, error announcements, no info only in color or placeholder.
- International support: single name field where possible, flexible address and phone formats.
Return a field-by-field table (Field | Keep/Cut/Defer | Input type | Label and helper text | Validation), the revised form structure, and the 3 changes likely to matter most.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- USERS, MOBILE/DESKTOP SPLIT
- LIST EACH FIELD WITH ITS TYPE AND WHETHER IT IS REQUIRED
- OR "not sure" - I will check
- DROP-OFF, COMMON ERRORS, SUPPORT TICKETS
- COUNTRIES - affects names, addresses, phone formats
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Review a part design for manufacturability before releaseA design for manufacturability (DFM) review that flags features driving cost, scrap, or long lead times, with suggested changes ranked by impact.
- Decide which enterprise features to build before moving upmarketA prioritized enterprise-readiness roadmap covering SSO, SCIM, audit logs, permissions, and admin controls, tied to deals.
- Audit and fix the color palette in my app or websiteReviews how color is used across your interface, then gives a consistent palette, color tokens, contrast fixes, and dark-mode adjustments.
- Run a UX teardown of a competitor's product flowBreaks down how competitors handle a specific user flow step by step, comparing patterns, friction, and ideas worth borrowing or avoiding.