Form Friction Analysis
Find fields, labels, and errors that cause form abandonment.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Find the fields, labels, and errors that cause form abandonment. Form purpose and audience: [FORM_PURPOSE_AND_AUDIENCE]. Field list with labels, types, required status, and error messages: [PASTE_FIELDS]. Analytics (starts, completions, field drop-off, error rates, time to complete): [FORM_ANALYTICS]. Device split: [DEVICE_SPLIT]. Tables: 1. Field audit: Field | Required? | Needed for the stated purpose? | Friction type (effort, privacy worry, confusion, format strictness, error-prone) | Drop-off or error data | Recommendation (keep, optional, remove, defer, auto-fill, split). 2. Label and help text review: current text | Problem | Rewrite. 3. Error message review: current message | Problem | Rewrite that says what is wrong and how to fix it. 4. Mobile checks: input types, keyboard, tap targets, autofill, and field order. 5. Flow options: single page versus steps, progress display, save and resume. 6. Test plan: changes grouped into three experiments with the metric, sample caution, and the expected effect (state it as a hypothesis, not a promise). Include accessibility fixes (labels, error association) and privacy points (why we ask, who sees the data). Do not recommend removing fields the business needs for legal or operational reasons.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.