Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

When introducing a product with new technology, consciously limit innovation to the core new features. For standard UI elements like bookmarks or tabs, stick to familiar patterns. This conserves the user's cognitive load for learning the novel aspects of your product, easing their transition.

Related Insights

Don't innovate on everything. Perfectly copy 'proven' elements, make incremental 'better' improvements all users want, and only then introduce one 'new' novel idea. This isolates your bets and de-risks the innovation process.

To introduce powerful features without overwhelming users, design interactions that reveal functionality contextually. For instance, instead of a tutorial on zooming, have the UI automatically zoom out when space becomes limited. This makes the feature discoverable and its purpose immediately obvious.

Large product teams have already hyper-optimized utilitarian flows like onboarding. Designers should leverage this existing knowledge rather than starting from scratch. The crucial skill is knowing when to follow established patterns versus when to break them for innovation.

Not all parts of an application require the same level of design polish. Founders must develop an "editorial eye" to invest heavily in the core user experience (a 9/10) while accepting "good enough" for less critical areas like settings pages (a 5/10).

The human mind rejects ideas that are too novel. Effective communication and innovation should be grounded in the familiar, introducing only about 20% new information. This principle, from designer Raymond Loewy, helps make new concepts intelligible and acceptable.

The Browser Company found that Arc, while loved by tech enthusiasts for its many new features, created a "novelty tax." This cognitive overhead for learning a new interface made mass-market users hesitant to switch, a key lesson that informed the simplicity of their next product, Dia.

For highly commoditized interactions like text editor undo or canvas pinch-to-zoom, users have powerful, ingrained expectations. Failing to match these conventions doesn't make a tool feel "different"; it makes it feel fundamentally unusable and broken, regardless of its other features. Innovation should be focused elsewhere.

To de-risk a new idea, first anchor it in elements that are *Proven* to work in the market. Then, add a feature that is clearly *Better* for users. This isolates your *New* high-risk innovation, increasing the odds of success by not failing for the wrong reasons.

To create a successful new product, find the balance between what consumers already know and what is new. If a product is too familiar, it lacks differentiation. If it's too novel, it becomes foreign and difficult for consumers to adopt, creating a high barrier to entry.

To avoid failing for the wrong reasons, focus your innovation on a single core area of your product. For all other features, like user onboarding, ruthlessly copy the most successful existing patterns instead of reinventing the wheel.