AI has made building easier.
But building the right thing is still hard.
Ten articles every week on what is happening across product, research, design and engineering. Curated by Rory Madden to help teams decide what to build.
Explore the editions ↓The archive
When identifying the assumptions behind our solutions, we categorised them under the four key product risks: desirability, usability, feasibility, and viability.
Read edition ↗Design is creative, it's messy, there are lot's of dead ends and backtracking as you iterate towards solutions that work. Development is a more logical, linear flow of turning the design into working software. It sounds great - but it's wrong.
Read edition ↗A thorough assumption-mapping exercise might reveal 20, 30, or even more assumptions for a single feature. We don't have time to test all of them so we need to be strategic about which assumptions we validate first.
Read edition ↗Every product or feature we build rests on a foundation of assumptions about how users will behave. If these assumptions are wrong it could sink our whole feature. That's why identifying the key assumptions is critical to enable us to test our designs before we over-invest in bui
Read edition ↗It’s so obvious. If we invest a little bit more time in design upfront then we will save so much time and money by building better products that customers actually love.
Read edition ↗Have you ever left a brainstorming session feeling more frustrated than inspired? The reasons that ideation sessions often fall flat comes down to a few predictable challenges but luckily there are proven techniques to overcome these challenges and help your team generate creativ
Read edition ↗Have you ever gotten stuck in an ideation session when trying to come up with new ideas? The blank page can be quite daunting, but the common advice is to push through because quantity equals quality. But quantity on it's own is not enough.
Read edition ↗The research space is virtually infinite. We could spend all of our research time and effort talking to the wrong people about the wrong topics.
Read edition ↗The biggest risk with research is that it sits on a shelf gathering dust. So naturally researchers are keen to communicate and evangelise their research insights.
Read edition ↗RICE, Kano, Cost of Delay or your home grown ranking method. What is the best way to prioritise different opportunities?
Read edition ↗Every article you read about Opportunity Solution Trees (OST) shows the same thing: a beautifully organised diagram with clear hierarchies, thoughtfully organised opportunities, and neatly arranged solutions. But if you've used OSTs in practice, you know the reality: they get mes
Read edition ↗Should you create a report, a user-journey map, an affinity map or an opportunity solution tree to document your research insights?
Read edition ↗I attended a workshop on interviewing by Bob Moesta a few years back. Instead of just talking theory, Bob did a live interview during the workshop and it was one of the most eye-opening experiences in terms of witnessing how effective someone who is really skilled in interviewing
Read edition ↗