Last call for Form Design Mastery 2.0 (and a design tip inside)


The launch for Form Design Mastery 2.0 ends in a few hours – I wanted to use this final email to give you a design tip.

Here goes:

My friend Rachael (a product manager) once said to me:

“People love the comfort of a number because they think that data = facts. But it doesn’t tell you if that number is good or bad. You need research for that.”

Like I said to Rachael:

Yep! Sadly, a lot of designers love the comfort of a number. A simple metric that they can use to tell themselves they’ve done a good job.

In the case of forms, they often think:

Less clicks = better UX

But if that was true you’d just put your entire form on a single page – no matter how big or complicated it is – and call it a day.

The problem is that that is likely to be a very bad decision.

Because putting everything on one page is usually the best way to:

  1. Increase abandonment
  2. Overcomplicate UX
  3. Add friction

I know this because I’ve watched 100s of users struggle again and again with forms designed this way.

But I’ve also seen that doing the opposite is usually the best way to:

  1. Reduce abandonment
  2. Simplify UX
  3. Remove friction

Now I’ll be the first to admit that form UX (and UX in general) is much more nuanced than this but if all you did was follow this advice you’d be off to a bloody good start.

This leads me back to Form Design Mastery 2.0.

I can, hand on heart, tell you that if you want to be able to design forms that users fly through and be able to influence your teammates and stakeholders to do the same, there’s no better product.

I only launched it a few days back but I’ve just (this morning) received feedback from one of my new students:

I’m pretty chuffed with that but let me address the bit about wanting more complex examples:

She’s watched:

  • Module 1, Nail the basics
  • Module 2, Kill your questions

And she’s in the middle of:

  • Module 3, Form validation

But she has not yet watched:

  • Module 4, Multi-step forms
  • Module 5, Supersized forms

Both of these modules cover complex, real world examples...

Module 4 is a holistic and in-depth redesign of a real-world multi-step form flow, including first-time and repeat-use flows. And it’s not GOV related.

Module 5 walks you through multiple real-world examples of complex forms that take hours, days or even weeks to complete. And I show you the research-proven patterns that help users complete them.

There’s a mix of GOV and non-GOV examples in there, but mostly GOV.

Here’s the thing though:

The design patterns I recommend in the course, work just as well for the private sector as they do for the public sector.

But don’t take my word for it. Here’s what some of my students have said:

“This improved our flow and enhanced conversion. Totally worth the cost!”
​– Simon Vandereecken, Product designer at Checkout.com
“Since employing some changes around field labels and removing unnecessary steps, we’ve seen an increase in qualified form completions.”
– Ryan Weisser, Senior product designer at Gartner
“Following Adam’s advice, we’ve seen abandonment rate and exit rate decrease, whilst conversion rate has increased”
– Paul Braddock, Lead designer at Co-op Group

If you’d like to design (complex, supersized) forms (without counting clicks) now’s the best time to pick it up as the price is going up tonight at 9:45pm (GMT):

https://formdesignmastery.com

See you soon,
Adam

Design tips to help you create products that are ridiculously simple and accessible to use

Join 9000+ designers, content designers and engineers who get my free weekly newsletter with evidence-based design tips (in 3 minutes or less). Mostly forms UX, but not always.

Read more from Design tips to help you create products that are ridiculously simple and accessible to use
Me holding a sign saying less but better

A year ago I posted this on LinkedIn: === I tell my students to avoid select boxes. Because it’s often better to use radio buttons. But students often say “But it’ll make the page too long”. Yep, but that doesn’t necessarily mean it’s bad UX. See the page I designed to let users select a course. Huge list of radio buttons. But no issues in user research whatsoever. Does this mean you should always use radio buttons? No. But most designers would balk at a design like this even though it worked...

Me holding a sign saying sometimes there’s no perfect

Last week, I had a meeting with two devs and two designers. The meeting’s purpose was to let developers raise problems and get quick design decisions. One of the devs brought up an issue with a form that had conditional radio buttons. Here’s what the screen looked like (it’s a bit different to what I’m actually working on but close enough): When the user selects “Yes” it reveals a field to enter the name: If you leave it blank and submit the form, the page refreshes and shows an error: So far...

Quick one: Yesterday I sent you an email “My response to Hacker news comments”. I received a few responses asking for clarification in my second illustration – because I screwed it up. Here’s what it should have been: Enjoy,Adam