The following is a guest post by Gregory Menivelle, a French-American entrepreneur and founder of smartnotify.us and Pyrasolutions, He also has a background in international expansion, helping companies achieve success on a global scale.
Chef David Chang (a famous US chef) was recently interviewed by Adam Savage and had an intriguing insight into one of his biggest business challenges: Whenever he goes to a restaurant, Chef Chang cannot help but deconstruct the dishes and find ways he would improve them. As a result, he hardly ever enjoys a meal anymore.
However, he is acutely aware that what makes restaurants successful is not the chef’s talent but the patrons’ experience. So he works hard at making sure that his bias does not trump the “User Experience”. You can view the interview here and yes, I admit to being a MythBusters fan. There.
This focus on User Experience (UX) should permeate outside of the restaurant world into our software; UX will become the next frontier in software development and the true differentiator between companies that succeed and companies that fail. The problem is that many companies have a trumped view of UX and waste resources on things that do not matter. Too often UX is associated with design and user-interface and, as long as the software “looks good”, people think that the UX work is done. This approach is likely to fail in the long run. There is a huge difference between making something look good, making something useful, and making something successful. Doubting me? Then honestly ask yourself if you’d rather have (as an owner, investor….) the volume of craigslist or some of the supposedly paradigm-shifting mobile applications that act as marketplaces?
UX should refer to all the emotions we have before, during, and after interacting with a specific piece of technology or software. It’s the delicate combination of your end-users’ preconceptions, prior experience, moods, beliefs, personal state of mind, and location. Let’s look at some of the elements involved in each stage of engagement:
- Before using the software: Which emotions do you trigger in your audience before they even use your software? These emotions go far beyond how your site looks. For example:
– Do they get the feeling that you cater to them or is your website simply a showcase of how good/smart/witty your company is?
– Do they feel they can trust you or will they believe you see them as guinea pigs because of AB tests or even pricing testing?
– When they email or call you (or text, tweet, message…), how quickly do you respond?
– Do you ask for their credit cards before letting them trial the software (horrible practice if you ask me)?
All these elements, and I am sure you can think of a few others, are part of UX and will setup your audience’s emotions and expectations for your software. It’s with this “baggage” that they enter the next stage.
- While they use the software: Like it or not, customers only use your stuff because of the promise that it is the best tool for the job (even games work that way). The goal of the UX is to reinforce this belief and here are a few tricks:
– A good onboarding process to make it simple for people to get started. This can be done via in-software help, webminars, drip emails.
– Gamification. Gamification is a fantastic way to enhance the UX. We will talk about Gamification in future posts.
– Support. How well do you support your customers when they have a problem? Do you simply refer them to a FAQ (bad) or do you proactively help them regardless of their membership level (great)?
If you want to look at these topics further, I encourage you to see the steps put in place by companies such as Twilio or SendGrid. They really focus on UX and have fanatic customers as a result.
- After they use the software: UX does not stop when the user shuts down your software. Quite to the contrary. The UX steps you take when users are not actively engaged with your software are as important as the ones implemented when they do. For example:
– Do you use drip emails to give hints about how users can further benefit from the software?
– Do you listen to requests and improve your product based on their ideas?
– Do you make it simple for customers to share with others how successful they are using your software?
The challenge in implementing these steps is that UX is a very fluid and dynamic process. Here is an example: On smartnotify.us we used to have a decent UX for the “newly acquired users”. Notice the use of the past tense! As our users are becoming savvier, they are seeking a different experience with the software. The end usage of the software stays the same but the expectations around the usage are shifting. Of course we help our users be successful in their jobs and adapt the UX but in doing so, it has now become harder for new users to get started! Our new challenge in the coming months is to setup multiple UX paths based on the user’s sophistication levels. This may seem like overkill, even for a startup, however, it is a guarantee to build a better, more engaged customers that will then help your company grow. UX is fluid, do not try to make it a once-a-year initiative.
Which then leaves us with the last UX challenge: Who should be the UX leader in the company? My recommendation is to look at who should not be your UX leader! It should not be your tech group because as tech people we have the tendency of simply throwing more tech at any question. It should not be your design team either because what looks good has little to do with UX. Rather I’d recommend having a UX team. The main stakeholder needs to whomever does Business Development. This person is at the frontline of interacting with the customers and can act as their advocate in the company. This person can then bring in the tech and design competencies to implement the UX strategy.
Finally, hire your customers to be your UX experts. Get them involved in your company, meet with them, be proactive. Of course to do this properly there is one other role you need to grow and promote in your company. Next week we’ll look at this other key role that most startups neglect (not that I’m talking from experience!)