The hottest User Research Substack posts right now

And their main takeaways

To truly understand the problem you're solving, talk to people experiencing it
Market research is important, but speaking directly with prospects is crucial for validation
Prioritize user research to inform business, product, and engineering decisions

Learning from failure is important. When things go wrong, take the time to understand what happened so you can do better next time.
Project retrospectives help teams reflect on their work. These meetings let everyone share what went well and what didn't without placing blame.
To reduce the risks of failure, use a step-by-step approach to launching new features. Start small, gather feedback, and make improvements before a full release.

Many products end up with absurd, unusable features because no one on the team ever pays attention to real users or real-world use.
Make the customer’s needs omnipresent: short release cycles, engineers talking to customers, and seeing real usage expose design problems quickly and stop bad decisions spreading.
Create a culture where anyone can flag absurdity by encouraging psychological safety and cross-functional responsibility so problems get fixed instead of ignored.