Discovery is the only way to keep living. Join me as I explore what's new, both online and offline. I observe. I post. I think. I share. And I welcome you to do the same.
Thursday, June 18, 2009
Havaianas Filipinas | Ride the Travelling Jeepney!
Sunday, June 14, 2009
Have you seen an Eye-Fi?
Saturday, June 13, 2009
Email Marketing: Why we use Silverpop (inspired by an iMedia article)
ARTICLE HIGHLIGHTS:
- Many marketers' email deliverability measurements are incomplete
- True delivery measurement requires both your failure logs and your seed list results
- Tracking your "potential rate" will determine the real value of your campaigns
Lately, I have heard a number of people talking about email delivery rates and what they really mean. While the topic of deliverability is not new to the email space, it is an important one that deserves discussion. Most of the time, when marketers are talking about numbers and various metrics, they invariably focus on opens and clicks, not delivery rates. With that being the case, I wanted to take a look at what delivery rates really are and, more importantly, how you should be looking at them.
One of the things that always makes me laugh is when clients or prospects tell me that some other email service provider promised them 99 percent delivery. Here is the problem with that: It's impossible to make such a promise without knowing anything about your list, your previous practices, or other important factors affecting deliverability. When it comes down to it, the sending platform is only half of the deliverability equation; a sender's practices make up the other half.
There is also confusion around how people look at deliverability. Some folks in the email space think that delivery rates are simply the number of messages sent minus the messages failed, while others look at it strictly from an inbox percentage perspective. I would argue that neither view by itself is correct. Instead, I see it as a combination of the two. While this viewpoint may be a little more complicated and harder to track, it is the most effective way to look at deliverability over the long term. Both of these statistics should be monitored, followed, trended, and acted upon, but they don't tell the whole story. What we really need is a new metric: "productive rates." But, I'll get into that a little later. First, let's discuss these two approaches in more detail.
Tracking your delivery rate based on the number of messages sent minus the number of messages bounced will tell if you are keeping your list clean and not having any issues with ISPs from a blocking standpoint; however, it won't tell you where your messages are landing. Did your messages get to the inbox, the bulk folder, or did the ISP just accept the messages and then never actually deliver them to its users? This practice of "dropping messages on the floor" is not as uncommon as you might think; ISPs do it to help protect their networks and monitor mailings from suspicious senders. This makes it all the more important to know what ultimately happens with your messages.
I'm sure you'll agree that if your message isn't in the inbox, you will get very little response. Fewer and fewer people are checking their spam folders, and that's not surprising since 99 percent are typically messages that they don't want. The increasing number of messages landing in the spam folder makes it less likely that people will take the time to search for a marketing message.
That being said, you might think it's better to use a seed list to determine your inbox delivery and use that as the actual delivery rate. Unfortunately, there's a problem with this approach as well. Seed lists can only offer you a representative sample to show you what likely happened with your mailing, which can't account for users who have changed their default email settings. For example, customers could change their settings to junk any message received from an address not already in their address book. On the other hand, the seed list could show your message arriving as spam, but if the recipient has added your email to the safe sender list, it will arrive in the inbox. In short, there are several different scenarios that could affect these numbers, which is why I am continually stressing the importance of testing.
So, what's the best approach? Should you be looking at your failure logs or your seed list results? The answer is "both." Think of email delivery as a puzzle, where you need to use all the pieces to get the complete picture. If you are missing any piece, the puzzle is incomplete.
Measuring email delivery comes down to using both your failure logs and your seed list results to determine what I call your "campaign potential rate" (i.e., the potential your campaign has to reach customers and get them to act on your email).
In order to figure your campaign potential rate, you must first gather failure data from your email system and then compare it to your seed list results. For example, let's say your delivery rate is 95 percent, but your seed list shows that your mail was sent to the spam folder at MSN/Hotmail, which makes up 30 percent of your overall list. In that case, your actual campaign potential rate would be 65 percent.
While it's possible that more than 65 percent of the people will have received the message in the inbox, this is still a good way to look at your mailings. Not only will this approach allow you to do trending, when you fix the spam problem, you will also be able to measure the actual effect it had on the overall ROI on your campaigns. So, say you earned $10,000 from the campaign with the 65 percent campaign potential rate, but the next campaign got to the inbox at MSN/Hotmail and you earned $15,000. You can now see the direct impact of getting junked at MSN/Hotmail. This is very valuable information that can be used to push for the best practices that will help ensure inbox delivery.
The bottom line is that you should use all the tools available to you to better understand your delivery rates and the overall potential of your campaigns. No one metric should be used to evaluate your email marketing programs because they are all interconnected.
Good luck and good sending.
Spencer Kollas is director of delivery services for StrongMail Systems.
Thursday, June 11, 2009
What A Successful User Interface Should Have (from UsabilityPost.com)
There is a lot of information out there about various interface design techniques and patterns you can use when crafting your user interfaces and websites, solutions to common problems and general usability recommendations. Following guidelines from experts will likely lead you towards creating a good user interface — but what exactly is a good interface? What are the characteristics of an effective user interface?
Here are 8 things I consider a good user interface needs to be:
Lets take a closer look at each.
1. Clear
Clarity is the most important element of user interface design. Indeed, the whole purpose of user interface design is to enable people to interact with your system by communicating meaning and function. If people can’t figure out how your application works or where to go on your website they’ll get confused and frustrated.
What does that do? Hover over buttons in WordPress and a tooltip will pop up explaining their functions.
2. Concise
Clarity in a user interface is great, however, you should be careful not to fall into the trap of over-clarifying. It is easy to add definitions and explanations, but every time you do that you add mass. Your interface grows. Add too many explanations and your users will have to spend too much time reading through them.
Keep things clear but also keep things concise. When you can explain a feature in one sentence instead of three, do it. When you can label an item with one word instead of two, do it. Save the valuable time of your users by keeping things concise. Keeping things clear and concise at the same time isn’t easy and takes time and effort to achieve, but the rewards are great.
The volume controls in OS X use little icons to show each side of the scale from low to high.
3. Familiar
Many designers strive to make their interfaces ‘intuitive’. But what does intuitive really mean? It means something that can be naturally and instinctively understood and comprehended. But how can you make something intuitive? You do it by making it ‘familiar’.
Familiar is just that: something which appears like something else you’ve encountered before. When you’re familiar with something, you know how it behaves — you know what to expect. Identify things that are familiar to your users and integrate them into your user interface.
GoPlan’s tabbed interface. Tabs are familiar because they mimic tabs on folders. You figure out that clicking on a tab will navigate you to that section and that the rest of the tabs will remain there for further navigation.
4. Responsive
Responsive means a couple of things. First of all, responsive means fast. The interface, if not the software behind it, should work fast. Waiting for things to load and using laggy and slow interfaces is frustrating. Seeing things load quickly, or at the very least, an interface that loads quickly (even if the content is yet to catch up) improves the user experience.
Responsive also means the interface provides some form of feedback. The interface should talk back to the user to inform them about what’s happening. Have you pressed that button successfully? How would you know? The button should display a ‘pressed’ state to give that feedback. Perhaps the button text could change to “Loading…” and it’s state disabled. Is the software stuck or is the content loading? Play a spinning wheel or show a progress bar to keep the user in the loop.
Instead of gradually loading the page, Gmail shows a progress bar when you first go to your inbox. This allows for the whole page to be shown instantly once everything is ready.
5. Consistent
Now, I’ve talked before about the importance of context and how it should guide your design decisions. I think that adapting to any given context is smart, however, there is still a level of consistency that an interface should maintain throughout.
Consistent interfaces allow users to develop usage patterns — they’ll learn what the different buttons, tabs, icons and other interface elements look like and will recognize them and realize what they do in different contexts. They’ll also learn how certain things work, and will be able to work out how to operate new features quicker, extrapolating from those previous experiences.
The Microsoft Office user interface is consistent for a reason.
6. Attractive
This one may be a little controversial but I believe a good interface should be attractive. Attractive in a sense that it makes the use of that interface enjoyable. Yes, you can make your UI simple, easy to use, efficient and responsive, and it will do its job well — but if you can go that extra step further and make it attractive, then you will make the experience of using that interface truly satisfying. When your software is pleasant to use, your customers or staff will not simply be using it — they’ll look forward to using it.
There are of course many different types of software and websites, all produced for different markets and audiences. What looks ‘good’ for any one particular audience will vary. This means that you should fashion the look and feel of your interface for your audience. Also, aesthetics should be used in moderation and to reinforce function. Adding a level of polish to the interface is different to loading it with superfluous eye-candy.
Google are known for their minimalist interfaces that focus on function over form, yet they clearly spent time polishing off the Chrome user interface elements like buttons and icons to make them look just right as evident by the subtle gradients and pixel thin highlights.
7. Efficient
A user interface is the vehicle that takes you places. Those places are the different functions of the software application or website. A good interface should allow you to perform those functions faster and with less effort. Now, ‘efficient’ sounds like a fairly vague attribute — if you combine all of the other things on this list, surely the interface will end up being efficient? Almost, but not quite.
What you really really need to do to make an interface efficient is to figure out what exactly the user is trying to achieve, and then let them do exactly that without any fuss. You have to identify how your application should ‘work’ — what functions does it need to have, what are the goals you’re trying to achieve? Implement an interface that lets people easily accomplish what they want instead of simply implementing access to a list of features.
Apple has identified three key things people want to do with photos on their iPhone, and provides buttons to accomplish each of them in the photo controls.
8. Forgiving
Nobody is perfect, and people are bound to make mistakes when using your software or website. How well you can handle those mistakes will be an important indicator of your software’s quality. Don’t punish the user — build a forgiving interface to remedy issues that come up.
A forgiving interface is one that can save your users from costly mistakes. For example, if someone deletes an important piece of information, can they easily retrieve it or undo this action? When someone navigates to a broken or nonexistent page on your website, what do they see? Are they greeted with a cryptic error or do they get a helpful list of alternative destinations?
Trashed the wrong email by mistake? Gmail lets you quickly undo your last action.
To conclude…
Working on achieving some of these characteristics may actually clash with working on others. For example, by trying make an interface clear, you may be adding too many descriptions and explanations, that end up making the whole thing big and bulky. Cutting stuff out in an effort to make things concise may have the opposite effect of making things ambiguous. Achieving a perfect balance takes skill and time, and each solution will depend on a case by case basis.
Wednesday, June 10, 2009
Why Do Clients Think This Way?
Monday, June 8, 2009
Google Wave: Six Game-Changing Features (From Mashable)
1. Wiki-style functionality
The feature: While Google Wave works a lot like email or IM, there is a huge difference: you can edit not only your messages, but the messages of anybody within your wave. You can reply to messages within a conversation string and reorganize conversations.
Why it’s game-changing: There was a perfect example of how this changes communication during Google’s demo of the product. A group of people are trying to plan a group dinner, and want to see who can come or not. In email, you have a string of emails with yes or no, which can get messy.
In Wave, you can edit the original message with a section with who can or cannot go. Replies can be made within a conversation string, rather than at the end, making conversations a great deal easier to track.
2. Wave Extensions
Why it’s game-changing: It’s game-changing just as the Facebook platform or the Twitter application boom has been paradigm-shifting for both companies. Imagine only needing to have Google Wave open to manage your Facebook, Twitter, project management, email, and even your video games. You can make Google Wave your all-in-one communication tool.
3. Drag-and-drop file uploads
The feature: In email, you have to search for files, and then attach them before sending. Then you need to open them up when you actually receive the email. Google Wave ignores that entire process by allowing users to drag files from the desktop and dropping them. Anyone can then see the files as they’re being uploaded. Images are shown in an album format, music can be played, and docs can be quickly shared
Why it’s game-changing: Drag-and-drop file uploads makes Google Wave not only a communication platform, but a useful project management system. Companies could use Google Wave as their communication and file-sharing platform. Combined with Wave Extensions, you could build an entire project management platform and time management system better than anything on the market.
4. Wave Embeds
Why it’s game-changing: Embedding is not only an easy way to share conversations with millions of people, but is in fact a way to replace a lot of forms of communication. Instead of a chatroom, you can add a Wave on your company’s website and do customer service through it. Instead of static comments, imagine real-time conversations via Waves. Conversations are easily shared with embeds.
5. Playback
The feature: If you’re added to an email conversation late into the game, it can be a pain to parse all of the back-and-forth within an email conversation. With Wave’s playback feature, you can actually see how the entire conversation developed from the start, making it incredibly easy to catch up on conversations.
Why it’s game-changing: Playback clarifies any conversation and makes it simple to get anyone up-to-speed. Instead of “check your email,” it will become “just playback the wave” and you will have all the information that you need. You could get someone up-to-speed within minutes, rather than hours.
6. Open-source
Why it’s game-changing: You may not think of open-source as a feature, but this may be the most important aspect of Google Wave. Open-source code fosters innovation by allowing developers to improve and correct code. Developers have the freedom to create a Wave server for their company or to create a branded version of Wave.
Open-source is central to Google’s strategy to foster quick adoption. And if people start using or even switching over to Google Wave, then it could very well be the game-changing communication tool that everyone has been waiting for.
Friday, June 5, 2009
Microsoft Bing: 'Manifesto' launched
What did you think about the ad? Microsoft says the idea behind 'Manifesto' is to elicit an emotional response about a concept that is decidedly not emotional. It didn't for me. Fail.
What it looked like was a typical US ad -- a montage of people shots, a long running voice-over, and a long explanation on how we should be emotional about Microsoft's new product. Fail. Nothing visceral. All logic.
When will Microsoft ever learn?