Hire an AI long web form usability planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A field audit showing each field as keep, cut or merge, with the reason
• A shorter field list with labels, help text and checks for each answer
• A decision on one page or steps, with step order, progress labels and save-and-resume if steps are used
• A test script with tasks, a read-aloud script and rules for what counts as finished
• One next step

How it does the job well

• Start from the user's task and the content, then the layout. Decoration comes last.
• Design every state: empty, loading, error, long text and mobile.
• Keep one visual system. Reuse spacing, type and colour tokens instead of one-off values.
• Check text contrast (at least 4.5:1 for body text) and keyboard focus as you go.

Mistakes it avoids

• Cutting a required field or one whose use nobody knows.
• Splitting a short form into steps to make it look shorter.
• Promising more finished forms before anyone has tested.
• Writing tasks that give away where to click.
• Designing only the happy path at desktop width.
• Copying a reference's logo, text or claims instead of learning from its structure.

What a good result looks like

An example, not your task: Your quote or sign-up form has 15 or more fields and people leave halfway.

• Field audit. Every field marked keep, cut or merge, with its use and whether it is required.
• Revised fields. The kept fields with labels, help text and answer checks written in plain words.
• Form flow. One page or a step order, with progress labels, skip rules and save-and-resume when steps are used.
• Test script. Tasks, a read-aloud script, finished and stuck rules, and one error to recover from.
• Hand-back summary. Saved files, MISSING lines, checks not run and the next change to try.

How the work is checked

• Every screen has its states, breakpoints and interactions written down.
• Colour pairs and type sizes pass the stated contrast checks.
• The handoff names components, tokens and open questions.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Don Norman and Jakob Nielsen would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Web form designer. Lists every field, what it is used for and whether it is required. Cuts or merges fields nothing depends on, then sets labels, help text and answer checks. Hands step 2 the kept field list. Check before moving on, every cut field has a reason and every required field is still there.
• Multi-step form designer. Decides if the kept fields need several steps. A short simple form stays on one page. Otherwise it plans step order, progress labels, skip rules, saved progress and a final review. Hands step 3 the flow. Check before moving on, each kept field sits on exactly one step.
• Small usability test planner. Writes tasks from the revised flow, a read-aloud script with neutral prompts, and a rule for what counts as finished. Includes an error the person must recover from. Check before moving on, no task tells the person where to click.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id make-a-long-form-easier-to-finish only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/make-a-long-form-easier-to-finish/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your current form, as a link, screenshot or list of fields
• What the form is for and what you do with each answer
• The fields that law or your process makes required
• Where people quit and your finish rate, if you know them (optional)
• Who fills it in, such as new customers on a phone (optional)

Helpful context (optional)

• Approved examples of a good result.
• A named reviewer and their acceptance rules.

Tools and access

• A capable chat AI with file support: Read the full pack and supplied sources; connected actions need the corresponding authorized tools.
• Any good chat AI: Planning tasks and writing the script is text work any strong chat AI does with this skill.
• A screen and voice recorder: Record each session from the first screen so you can replay the pauses.

Functions and deliverables

• Long web form usability planner: Share the current form, required fields and user goal. Get field choices, a revised flow and a usability-test script.
  • A field audit showing each field as keep, cut or merge, with the reason
  • A shorter field list with labels, help text and checks for each answer
  • A decision on one page or steps, with step order, progress labels and save-and-resume if steps are used
  • A test script with tasks, a read-aloud script and rules for what counts as finished
  • One next step
• Web form designer: Describe your form and goal. Get field, error and spam tips.
  • A recommended field list
  • Error message and validation rules
  • Spam protection plan
  • Steps to track and raise completions
  Source: RampStack.
• Multi-step form designer: Share the fields and audience. Choose a single page or staged form, with progress cues, relevant questions, validation and resume rules.
  • A step-by-step form layout
  • Progress indicator advice
  • Conditional question rules
  • A save and resume design
  • An audit of what to cut
  Source: RampStack.
• Small usability test planner: Plan a small usability test in one morning. Name what people should do. You get tasks, a read-aloud script and a fix list of the worst problems.
  • The three to five tasks to test, in order
  • Who to recruit and how, including one outsider
  • A read-aloud script and a note sheet
  • A fix list template, limited to the worst problems
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Don Norman: Find why a product, form or service is hard to use through Don Norman’s public approach. Check cues, controls, feedback and recovery from mistakes.
  • Your problem worked on the way Don Norman would: their questions, their method, their push-back
  • The answer or the work, in Don Norman's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Jakob Nielsen: Review a website, app or form through Jakob Nielsen’s recorded approach. Find likely usability problems and plan small rounds of realistic user tasks.
  • Your problem worked on the way Jakob Nielsen would: their questions, their method, their push-back
  • The answer or the work, in Jakob Nielsen's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• Your quote or sign-up form has 15 or more fields and people leave halfway.
• A sales team asks for three more fields and you want to know which ones earn their place.
• Your analytics show people quit at one field, such as phone number or company size.
• You are about to split a form into steps and are not sure it will help.

Limits to check before starting

• Your form has about five fields on one page. Use the Web form designer on its own.
• You already have a finished design and only want a test plan. Use the Small usability test planner.
• Every field is required by law or by a contract. It can still reorder and reword, but it cannot cut fields. Use the Forms and instructions rewriter for wording.
• You want clearer error messages on a form. Use the Error message rewriter.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the workflow pack and add it to your AI, such as Claude, ChatGPT or Gemini.
• Attach your current form and say what each answer is used for. Say which fields are required and why.
• After step 1, read the cut list. Push back on any field you cannot lose and say why. The AI should keep it.
• After step 2, check the page-or-steps decision. A short form should stay on one page.
• Use the test script with a few people who have not seen the form. Change the form before you ship it, then run the test again.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/make-a-long-form-easier-to-finish for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.