The debut of HEY email has been an interesting case study in launching a new service, in part because it took place on social media — a two-way street that led to them getting public feedback that’s already led to significant changes. As others have done in recent years, the launch was a staggered rollout with invite codes and a waitlist, and the resulting members-only feel and scarcity drove tens of thousands more to join the waitlist. Some say this is intentional marketing, but it’s also legitimately done to manage the experience when someone isn’t sure how much interest there will be.
I took notes on my hands-on experience in a previous post, and have spent a week now getting to grips with it, trying to picture it as my primary email service for the foreseeable future. The commitment isn’t just a new email address to inform people about; it’s also paying a perpetual premium service fee. After 16 years of “free” Gmail, that’s a big decision. Yes, you’re free to leave any time and they’ll forward all emails sent to you anywhere else you’d like, but I wouldn’t use a @hey.com address if I wasn’t actually using HEY.
Everybody’s got opinions
But before the details of my decision (like, who cares, right?), I wanted to comment on the fascinating public launch of HEY that we’ve been spectators to, and how its creators have had to walk back some of their design decisions after product met reality.
As my friend YJ says above, Basecamp and HEY are heavily opinionated products by opinionated people; it’s what allows them to take a well-established thing like email, with its standard organizing paradigms of Inbox, Outbox, Sent, Spam, and Trash folders, and try something new. It’s only meant to satisfy a certain type of user with certain needs and preferences.
It’s not easy building something out of new ideas, at huge scale, and making sure it’s robust enough to carry the personal and business correspondence of paying customers who’ll depend on it for time-sensitive messages. By Basecamp’s account, they’ve been working quietly on HEY for two years before this month’s semi-public launch. I think they deserve a tremendous amount of credit both for attempting it and for how stable it has been.
When we design services, we know we won’t catch everything or get it right the first time. It’s about having priorities and principles, and optimizing against them every step of the way. If you’ve defined and studied your target audience, and care about pleasing them to the exception of everyone else, then you can make decisions based on their needs. If you put in the work to develop a core experience that will set your business apart, then that becomes the thing you protect even if Apple or anyone else tries to make you change it. Some companies famously put speed over certainty, and while it dazzled a lot of CIOs and inspired them to try and do the same, its pitfalls are now well known.
We don’t know what HEY’s development process looked like, or what they prioritized, and so we can only guess from what they actually shipped and what they’ve done since. Upon contact with the wider marketplace, some of those opinionated ideas are now being challenged as problematic or discriminatory. Could more user research and testing have caught them before launch? Probably. Was catching them before launch a priority for the team, or did they intend to test them in public and fix unintended consequences as they were discovered? To their credit again, they’ve fixed a lot of things very fast in the past week. From adding disposable functionality suggested by Apple to dumping fully built, non-trivial features… their responsiveness has been impressive.
Things that came broken
Let’s look at a couple of Twitter exchanges and changes I’ve spotted. On my first day with HEY, I noticed an unusual option in the “More” menu on every email thread. It was a button labeled something like “Generate Public Link”. This actually published the entire email conversation thread to a public webpage, allowing any third party to read and follow the exchange. I used it to help share a problem I was seeing with their support team, which is a nice way of enabling them to help customers without giving full access to all mail. And while you could always share private emails to a third party with copy/paste, screenshots, PDFs, etc. there was something unsettling about this. None of the other people would receive any notification that they were being “listened in on”, and anyone with the link would be able to see not just all previous emails, but any new ones added to the thread for as long as it was publicly shared.
You could be in a conversation with 20 people and not know if any one of them had generated a link and leaked it. When I explained this in a group chat, there was some disbelief. One person called it a “built-in whistleblower feature”. After others complained on Twitter about the potential for abuse, this feature was completely removed.Continue reading “Hold up, HEY”