Set expectations with a thoughtful first-run experience
Ignoring the blank slate stage is one of the biggest mistakes you can make. The blank slate is your app’s first impression and you never get a second…well, you know.
The problem is that when designing a UI, it’s usually flush with data. Designers always fill templates with data. Every list, every post, every field, every nook and cranny has stuff in it. And that means the screen looks and works great.
However, the natural state of the app is one that’s devoid of data. When someone signs up, they start with a blank slate. Much like a weblog, it’s up to them to populate it — the overall look and feel doesn’t take shape until people enter their data: posts, links, comments, hours, sidebar info, or whatever.
Unfortunately, the customer decides if an application is worthy at this blank slate stage — the stage when there’s the least amount of information, design, and content on which to judge the overall usefulness of the application. When you fail to design an adequate blank slate, people don’t know what they are missing because everything is missing.
Yet most designers and developers still take this stage for granted. They fail to spend a lot of time designing for the blank slate because when they develop/use the app, it’s full of data that they’ve entered for testing purposes. They don’t even encounter the blank slate. Sure, they may log-in as a new person a few times, but the majority of their time is spent swimming in an app that is full of data.
What should you include in a helpful blank slate?
- Use it as an opportunity to insert quick tutorials and help blurbs.
- Give a sample screenshot of the page populated with data so people know what to expect (and why they should stick around).
- Explain how to get started, what the screen will eventually look like, etc.
- Answer key questions that first-time viewers will ask: What is this page? What do I do now? How will this screen look once it’s full?
- Set expectations and help reduce frustration, intimidation, and overall confusion.
First impressions are crucial. If you fail to design a thoughtful blank slate, you’ll create a negative (and false) impression of your application or service.
You Never Get A Second Chance…
Another aspect of the Mac OS X UI that I think has been tremendously influenced by [Steve] Jobs is the setup and first-run experience. I think Jobs is keenly aware of the importance of first impressions…I think Jobs looks at the first-run experience and thinks, it may only be one-thousandth of a user’s overall experience with the machine, but it’s the most important onethousandth, because it’s the first one-thousandth, and it sets their expectations and initial impression.