Every single day founders (myself included) are bombarded with feature requests. Our gut instinct is to rush ahead and provide as much customization “power” as we can. But do users really need endless choices? Today we’ll explore three possible levels of customization. You’ll see how three web applications handle reminder settings in totally different ways.
Why are reminders interesting to me? Because I address them directly with my own product, Tiny Reminder. But I was very surprized when the same topic came up in my client work twice over the last few weeks.
In Tiny Reminder, delivering notifications is the key feature. It’s front and center! So I’m offering fully customized reminder schedule for each request. Users go through three steps (tabs) with each request: build a form, set a reminder schedule, and add recipients.
Here’s what their reminder options look like.
Why is such advanced customization important?
Seems like the best approach, right? But full customization is not always the best for the user. Let’s look into other use cases.
RoasterTools, made with love by Jon Ewalt, automates production process for coffee roasters. Roaster’s wholesale customers typically make orders every week on the same day. These customers need to be reminded to place their order on time.
During our consultation, Jon expressed a concern. Ideally, the reminder settings should be application-wide, because most customers require the same typical reminder schedule. But what about edge cases? A handful of customers would speak up and request more reminders, and some would request less. But the whole “custom schedule” thing for each customer would result in a clumsy, crowded interface.
That’s where presets come in handy. We can define a typical reminder scenario (let’s say, on the day of the deadline, and a day before that) and call it “Regular.” Then we introduce two other options that deviate from the typical scenario in both directions — for example, “Light” and “Intensive.”
Now, instead of a wall of advanced settings, the user gets a beautiful dropdown list with a few simple options. Something along these lines.
A few tips here:
Bryan Marble, the founder of ClientSherpa, helps attorneys automate their client intake. The idea of his app is somewhat relevant to Tiny Reminder — forms, reminders, etc. But it’s way more advanced, detailed, and targets a narrow audience. It was exciting to design a completely different product around a similar idea.
In the intake layout, I sketched up a list of scheduled reminders, and thoughtfully included an “Edit Reminder Schedule” option. Here’s what I heard back from Bryan: “I think I’m going to keep the ”magic“ of the reminders out of their view. In other words, not let them make custom reminder schedules.”
It was a revelation! Bryan is probably the first founder who offered to cut back on customization (it usually goes in a different direction). We ended up with two simple toggles in the intake settings.
These settings offer some customization, but they’re deadly simple, and also hidden from the main workflow. The user typically views them once — when creating a new matter type.
Why did we cut back on customization? Two big reasons:
Whenever you’re in doubt about customization, ask yourself the following qualifying questions:
Answers to these questions — and, of course, your product intuition — will help you make the right decision.
Have complex UI situations in your own product? Send in the screenshots to firstname.lastname@example.org, and I’ll tear down the most interesting situations here in UI Practicum.
With this free email course you’ll conduct a simple do-it-yourself audit of your web app: eliminate the obvious design flaws, gain control of your features, and start building the UI that customers really want.