As a designer, there are plenty of questions that you would ask yourself when critiquing your work or other’s work. The other day I came by Jason Fried‘s blog post called Questions I ask when reviewing a design. It’s a great list he compiled.
Having a list of questions to ask would be tremendously useful when reviewing design and giving constructive feedback. At Sniply, one question that we ask ourselves most often is ‘Is what the design says and what it means the same thing?’ For us, one thing we are constantly trying to refine and improve on is our overall message to the users. The rest of the questions I picked out from Fried’s list.
1. Is what it says and what it means the same thing?
When we say you can add a message to any webpage that idea may seem foreign or impossible, but we mean it.
2. Why do we need to say that here?
One of the first things people see on our front page is how many clicks Sniply has generated so far which is a form of validation and how many people are creating snips.
3. How else can we say this?
When creating a snip and entering a URL that is not valid, instead of saying ‘We are currently not yet supporting this URL’, we now say ‘Due to security settings, we don’t support [insert site]- find out why‘. It wasn’t a good experience for the user because it wasn’t necessarily that we couldn’t support a certain URL, but because of the individual website’s security.
4. How would someone know that?
Because adding a message onto someone else’s website is a foreign concept to most, the first thing you will see when you land on Sniply’s website are use cases of effective snips.
5. How does that work?
Sniply is very visual. To help with the creation experience, people can see how their snip will appear as they are adding a message or a call-to-action.
6. Why is that worth a click?
Everything on the internet starts with a click. Especially when users use Sniply to drive conversion, it is important to know how to create a successful snip people will click on.
7. Is that worth scrolling?
We ask ourselves will the user derive benefit from having to scroll to find this material?
8. Are we assuming too much?
We can’t assume the average person will know how link shortening works and what they can do with it after. Some people assume that after creating a snip, it is automatically shared via Twitter. To avoid that assumption, we simply tell people to copy the link and share with options via Twitter or Facebook.
9. Why that order?
We try to put ourselves in the users’ shoes, ask ourselves how we go about creating a snip, and what is the hierarchy. We first see the webpage a user shares, the message in the snip they created, followed by their call-to-action. That determines the order of the fields people fill out as they are creating a snip.
10. How can we make this more obvious?
Helping people convert leads is great, but how do get people to know it’s powered by Sniply? Small decisions such as adding our logo to the snips and decreasing the opacity really helped increase our exposure.