Your core action is the thing people do in your product to deal with the problem they signed up to solve. A clear understanding of your problem comes from listening to your users and understanding how they think about it. Find the right level of abstraction. You’ve found the sweet spot when you can explain […]
List out all of the actions people can do that indicate they’re addressing their core motivation for signing up. There are a finite number of things people can do in your app and common sense is your friend here. If you do rideshare then it’s booking a cab, if you deliver food then it’s ordering […]
Your product was designed to solve a problem. Understanding when this problem occurs is important because it lays the foundation for how often people are expected to use your product. Airbnb helps you find a great place to stay when you go on vacation. People go on holiday once, maybe twice a year. If Airbnb […]
Your product can be a mediocre solution to lots of vague, undefined use cases. Vague use cases make things hard to use and difficult to remember. A clear understanding of your primary use case helps you set the right goals and prioritise the right features. The problem with thinking about products in terms of a […]
If it’s a problem worth solving then there are people out there trying to solve it right now. When someone goes to solve the problem your product was designed to solve, that’s your use case. That’s when they should be thinking about you and reaching for your thing. Wait, so what problem is Facebook solving […]
Your use case defines the problem your product was designed to solve. A use case draws a boundary around the natural behaviour that you’re trying to tap into, it highlights where things break down and how you fit in. It is important that you understand them because they are the foundation that you use to […]
Rather than asking if we’ve released the feature, we should be asking if we are getting closer to the outcome. This means starting the conversation with an outcome, to begin with. How’re we supposed to build something that drives an outcome if we don’t know what the outcome is? How’re we measuring it? How will […]
This post outlines my experience building a web-based tool that makes learning complicated information quick and effective. You add information to the system in the form of cards, and the app works out which cards you need to review on what days.
This post was originally published on the Beeminder Blog. In April this year I began working with the Beeminder team to redesign their interface. Over three months, I tracked a total of a 167 hours towards the project. But let’s start at the very beginning.