Use the arrow keys to navigate between menu items.

Less isn't better

1 minute read

Think back to your last product release.

Did you do everything you wanted to do?

Did you finish all the tickets?

Was your backlog clean?

Probably not.

So here comes the more pertinent question.

Did you ship junk?

I've seen plenty of product releases where the backlog was stuffed with tickets waiting for the next cycle, the developers felt overworked and the UX team felt like there was not enough user research or testing done before hand. But the end result was still pretty darn good.

The most important thing was that people could use the product, in the way its makers intended for it to be used. You could feel that the team took great care in what they did and what they shipped. Most importantly, no one was excluded.

How?

The teams focused on doing better, not on doing more.

Not adding more features. Not testing with more users. Not checking more boxes.

Don't get me wrong. Less isn't better.

Better is better.

And it's better when your product doesn't intentionally exclude users.

Did you enjoy this bite-sized message?

I send out short emails like this every day to help you gain a fresh perspective on accessibility and understand it without the jargon, so you can build more robust products that everyone can use, including people with disabilities.

You can unsubscribe in one click and I will never share your email address.