CONVERSION

Form field reduction analysis

Use when a form has too many fields and you need to decide which to cut, defer, or make optional.

form-field-reduction-analysis.md

Download .md

You are auditing a form for unnecessary friction.

FORM PURPOSE: {{FORM_PURPOSE}}
FIELDS (name, type, required or optional): {{FIELD_LIST}}
WHAT HAPPENS AFTER SUBMISSION: {{POST_SUBMIT_PROCESS}}
WHO USES THE DATA INTERNALLY: {{INTERNAL_CONSUMERS}}

For each field, decide one of: KEEP (needed to fulfill the action), DEFER (collect later in onboarding or by enrichment), MAKE OPTIONAL, or CUT.

OUTPUT a table: Field | Verdict | Reason | What breaks if removed | Who to check with before removing.

Then output:
- A recommended minimum viable version of the form, listed in the order the fields should appear.
- Any field that should be split or combined, and why.
- Fields where an inferred or enriched value could replace user input.

Constraints: do not recommend removing a field that is legally or operationally required if I have said it is used internally - instead recommend deferring it. Do not suggest progressive profiling as a blanket answer without saying which specific fields move to which later step. If you cannot tell whether a field is needed, ask the question rather than assuming. No em dashes in the output.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{FORM_PURPOSE}}
{{FIELD_LIST}}
{{POST_SUBMIT_PROCESS}}
{{INTERNAL_CONSUMERS}}

Getting a better result

Include the field types, since dropdowns and free text carry very different costs.
Say honestly which fields sales actually uses - most cut lists die because nobody asked.
Ask it to estimate which single removal would have the largest effect, and treat that as your first test.

Questions about this prompt

When is this the right prompt rather than the sequencing one?

When the argument is about which fields exist, not what order they sit in. Every field gets a verdict of keep, defer, make optional or cut, judged against what happens after submission and who uses the data internally. Once the list is agreed and the losses are at the step breaks, move to the multi step sequencing prompt.

What do I need in front of me before running it?

The form purpose, every field with its type and whether it is required, what happens after submission, and who consumes the data internally. Field types matter because a dropdown and a free text box carry very different costs. Be honest about which fields sales actually uses, since most cut lists die the moment somebody claims one.

What comes back, and which part is worth acting on?

A verdict table with the reason, what breaks if the field goes and who to check with first, then a minimum viable form in field order, fields to split or combine, and fields an enriched value could replace. The who to check with column is what gets the change shipped rather than argued about for a fortnight.

What is the mistake that costs me here?

Cutting a field that came back marked defer. Anything you said is used internally is moved to onboarding or enrichment rather than removed, and deleting it breaks a process nobody told you about. Ask which single removal would move the number most and test that one, rather than shipping the whole minimum viable form at once.