The Next Feature Fallacy<\/a>,\u201d he cites that your next feature will not drive mass engagement because all too often the feature is something that either too few people would use or makes too little of an impact when they do engage with it. <\/p>\nI\u2019ve learned to prioritize features that directly contribute to primary business goals and still delight users, though sometimes these two functions can actually be diametrically opposed. Usually, these features are primary actions that take place during or shortly after onboarding. Features that are more geared towards power users have their place, but they won\u2019t be something that everyone uses.<\/p>\n
Focus on simple and hide the\u00a0complex<\/h2>\n
Keep things simple. This doesn\u2019t just include the simplicity of a feature, but also the product in aggregate. Every feature has a learning curve to it. Features that skew more towards power users or extend beyond core functionality shouldn\u2019t be key parts of the experience. They could be hidden in the settings or deprioritized in the UI so their functions aren\u2019t critical to the experience. <\/p>\n
<\/div>