{"id":306,"date":"2012-01-12T18:51:50","date_gmt":"2012-01-12T18:51:50","guid":{"rendered":"http:\/\/intercom.com\/blog\/?p=306"},"modified":"2020-07-30T13:04:24","modified_gmt":"2020-07-30T12:04:24","slug":"sustainable-advantages-for-start-ups","status":"publish","type":"post","link":"https:\/\/www.intercom.com\/blog\/sustainable-advantages-for-start-ups\/","title":{"rendered":"Sustainable advantages for startups"},"content":{"rendered":"

In Gimmicks and Patterns<\/a> I wrote that new features either become table stakes, or are dismissed as being gimmicky. As some readers noted, this is a simplification of what happens. The Kano model<\/a> shows exactly how the slide happens, and explains why any one particular feature or trait will never be a sustainable advantage.<\/p>\n

Here’s how it works\u2026<\/p>\n

When new features emerge, even the smallest investment in them delights users as they are novel. Take “Location” for example. even a tiny investment, such as defaulting country and timezone correctly impresses users. As you invest further you really begin to delight them.<\/p>\n

\"\"<\/div>\n

The first few apps to use a new trick like this are heavily praised for it. No one has seen anything like it before, and many of these apps do well on their novelty alone. Blog posts are written, videos are posted, all to demonstrate that with just a few lines of Javascript this review site can indeed find a coffee shop in your area, assuming as always that you live in San Francisco.<\/p>\n

No feature stays delights forever. Once everyone is using it, it quickly becomes a performance payoff.<\/p>\n

\"\"<\/div>\n

A performance payoff is a feature where, roughly speaking, the more you invest, the happier your customers are. Most investments in user experience tend to fall into this category. A few years back UX was a delighter; it was easy to wow people just by laying out a web form correctly, and not putting a reset button beside submit. These days it is expected that websites are designed with the user in mind.<\/p>\n

Just like all delighters turn into payoffs, all payoffs eventually become table stakes. That is, they become the absolute least you have to do. Satisfaction for these tasks is a binary switch. There is no scale. It either “does the job” or it’s the terrible. Here’s what that looks like:<\/p>\n

\"\"<\/div>\n

What’s most frustrating about these basic expectations is that it can take a huge investment to just meet them. Think of all the money and time invested in ensuring a plane lands correctly, compared to how unimpressed passengers are every time it lands. Just five years ago a touch screen phone was an absolute delight. “Slide to unlock” was the sort of feature people would borrow your phone just to play with. Nowadays you’d struggle to sell a phone without a touchscreen. With web technology websites that could handle file uploads via AJAX were impressive, but today people are appalled if they can’t just drag files into the browser. Feature by feature the basic expectations add up, making some markets very difficult to enter. Here’s one example:<\/p>\n

If you’re building a new project management application, some of the table stakes are:<\/p>\n