The obsession with removing friction is often wrong. When users have low intent or understanding, the goal isn't to speed them up but to build their comprehension of your product's value. If software asks you to make a decision you don't understand, it makes you feel stupid, which is the ultimate failure.

Contrary to the 'minimize steps to value' mantra, adding friction like user questionnaires to onboarding often boosts conversion. By asking users about their goals, you can personalize their experience, make them feel the product is for them, and guide them to the right features, improving funnel completion.

It's easy to let edge cases and non-ideal user paths lower the ceiling of an experience. It's often better to downplay the impact on a small percentage of users if it means creating a truly special and optimized experience for your core target persona.

In early stages, the key to an effective product roadmap is ruthlessly prioritizing based on the severity of customer pain. A feature is only worth building if it solves an acute, costly problem. If customers aren't in enough pain to spend money and time, the idea is irrelevant for near-term revenue generation.

The old product leadership model was a "rat race" of adding features and specs. The new model prioritizes deep user understanding and data to solve the core problem, even if it results in fewer features on the box.

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.

Raw customer feedback is noise. To make it actionable for Product, organize it along two dimensions: impact and frequency. This simple framework separates signal from noise, distinguishing high-priority, high-impact issues from niche requests and creating a clear basis for roadmap decisions.

Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.

You can see a customer struggling with a slow, painful process and assume they're "coping." But they may be in a "good enough" equilibrium and not actively seeking change. True "coping" means they are ready to switch, not just experiencing friction. Only a sales test can validate this.