Get your free personalized podcast brief

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

Don't tie a redesign to a revenue goal. Instead, invest in a design audit or redesign only when you have clear evidence the current design is causing problems, such as user confusion or brand degradation. Beware of using redesigns as a form of procrastination to avoid harder tasks like marketing.

Related Insights

When facing a "brick wall" where user perception contradicts data (e.g., feeling ad load is high when it's low), incremental changes fail. The solution is to re-architect the experience from first principles. This can unlock growth in key metrics like ad load while simultaneously improving user satisfaction.

Instead of a full rewrite, identify the specific pain points of a legacy system (e.g., a command-line UX) and solve them with minimal development. This delivers immediate value, reduces risk, and validates the market need for a larger investment later, preventing a costly failure.

Before implementing a chatbot or complex tech to drive user action, first analyze the user flow. A simple change, like reordering a dashboard to present a single, clear next step instead of five options, can dramatically increase conversion with minimal engineering effort.

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).

Figma learned that removing issues preventing users from adopting the product was as important as adding new features. They systematically tackled these blockers—often table stakes features—and saw a direct, measurable improvement in retention and activation after fixing each one.

Don't jump directly to optimizing for high-level business outcomes like retention. Instead, sequence your North Star metric. First, focus the team on driving foundational user engagement. Only after establishing that behavior should you shift the primary metric to a direct business impact like revenue or retention.

When brand teams resist testing simpler, text-based emails, don't argue about aesthetics. Frame the proposal around business value: reduced design and QA time, and the potential for higher conversion rates. Quantify the impact on efficiency and revenue to get buy-in.

Focus on what customers value (e.g., delivery speed, order accuracy) rather than internal business metrics like ARR or user growth. This approach naturally leads to a better product roadmap and a more defensible business by solving real user problems.

Don't pivot your strategy based on a narrative about future disruption (like AI). If the threat isn't measurably affecting your business—such as increasing churn—you are solving a problem that doesn't exist. Focus on current, tangible issues and opportunities.

To give effective feedback, structure reviews at two key moments. At 20% completion, you can correct the overall direction before significant investment. At 80%, you can refine the nearly-finished product while there is still time for meaningful changes. Feedback at 0% is too early, and at 100% it's too late.