5 microcopy (UX writing) best practices we can learn from Lemonade
This post was originaly published on Invision Blog
Lemonade offers renters and home insurance policies for homes, apartments, co-ops and condos. And it seems like everywhere I go, they come up in conversation.
- At an entrepreneurship meetup, there was a discussion about their innovative business model;
- At a CX meetup, attendees noted the company’s disruption of the insurance world;
- And in a Facebook group for female UXers, amember mentioned Lemonade for their gender inclusiveness.
Curious to see what the fuss is about, I finally checked out Lemonade and was delighted by the user experience. For this post, I’m going to share some examples of how Lemonade uses microcopy to make their experience as smooth as possible, and the best practices we can learn from them.
1. Form a conversation with an experienced and cordial service rep
The feeling of being in a conversation is formed by two main ingredients:
- Each screen holds only one question, and you move on to the next when the former is answered, just like in a real life conversation.
- The opposite end of the conversation — the UI — sounds and feels like a human would. In Lemonade’s case, it’s a bot named Maya (who even has a human face), but the most important ingredient is the simple, natural language. Although the subject matter is insurance, there’s no use of formal legal language (I’ll talk more of this later), and everything is written in contemporary, convincing, conversational language.
A golden tip
If your product features a form, a bot, or any other registration process that simulates an interaction with a service rep, take the time to visit a service call center and listen in. The calls you listen to will give you the simple conversational language in which to phrase questions and provide answers.
When I wrote a chatbot for a banking process, visiting a call center gave me almost the entire representative side of the conversation, in the most natural and authentic way.
2. Write your questions as a continuous conversation, not separately
For example:
- The first question asks my name, and in the next screen I’m referred to by my first name.
- In one question they ask, “What’s your home address,” and in the next they ask, “Do you rent or own it?” Maya the bot does not repeat “your home,” as I’m relied upon to hold my end of the conversation and keep in mind what “it” refers to, even though the former question is no longer on screen.
3. Present dynamic content so at any given moment, users have only the information (and all of it) they need right now
For example, only after I indicated I had roommates did a notice appear to inform me they are not covered by the insurance policy. If Lemonade had indicated that (or any other comment) permanently, they would have cluttered the screen with text only some of users might need.
Before choosing:
After choosing:
On top of that, the notice appeared as if Maya were telling it to me in response to the choice I made, thus strengthening the feeling of a personally customized conversation.
On Lemonade’s registration screens, I clearly experienced how information presented to me according to the choices I make:
- Gives a sense of personalization
- Reduces difficulties and the sense of uncertainty
- Boosts the confidence that an explanation will appear as soon as I need it (like the insurance company of our dreams, once you need it — it really shows up).
Before choosing:
After choosing:
4. To create certainty, give complete information about each choice
What am I choosing here, who is it for, and what are the ramifications of making this choice? Only when users have all the information needed, can they make an informed and settled choice.
In this example, someone who wants to take out insurance for a rented apartment can add interested parties to the policy. This choice appears with all the requisite information: price (free), who can be considered as an interested party (building supervisors or property owners), and what it means to add interested parties (they get notified on any change made to the insurance policy).
This way people are sure they got what they meant to get, or they can decide they need something else.
5. Figure out, together with your legal team, a way to explain things in simple words and still meet legal requirements. Yes, it’s possible
Under Lemonade’s excellent and clear explanations on what the insurance policy does and does not cover, appears this magical sentence:
Any other legal department I encountered would have demanded to write something like this:
The coverage detailed here is only an incomplete summary and reading it does not exempt the insurance buyer from reading the entire policy as it appears in the company books, including changes which are published from time to time…
Huh?
Using archaic, long-winded legalese works against the sense of trust, human contact, and experience of digital products.
Lemonade shows it can be done differently. Everything is simple and clear, accompanied with real-life everyday examples — straightforward and trustworthy.
This interface speaks to humans in way that’s easy to understand, thus gaining their trust.
Off-topic marketing bonus: The value to the users before the business model
Lemonade’s business model makes it so that they can settle claims faster and easier, resulting in happy customers. Plus, part of their revenue goes to charity.
But you have to really look to find information about this great model — it’s towards the bottom of their homepage, below six strips where the main focus is on the customers by explaining who Lemonade is for, the rates offered, the short process time for claims, how to migrate an existing policy from another company, and more.
First you, the clients, and what will you get from us, and only then, briefly and concisely — us and how we do what we do.
Although their model is important, and some clients will choose them because of it, it is much more basic than that: The main product should be perfect, give real value and keep its promises.
Curious to see what the fuss is about, I finally checked out Lemonade and was delighted by the user experience, especially the microcopy (surprise surprise). For this post, I’m going to share some examples of how Lemonade uses microcopy to make their experience as smooth as possible, and the best practices we can learn from them.
