If you focus only on new features you’ll build a product that is miles wide
and inches deep. And if you focus only on repairs you’ll never innovate, thus
becoming irrelevant. Hard decisions indeed.
Put simply: a minor improvement on an important task is almost always a larger opportunity than a big improvement on an ancillary one.
Here’s an example: A typical date might involve a movie, dinner, and a lift home. If a cinema owner is constantly worried about what other businesses will build, and hungry to capture more value, they’ll put a restaurant into their cinema and start a cab company. Then they’ll be weak at all three. Then restaurants start screening movies…
Key point: Scope grows in minutes, not months. Look after the minutes, and the months take care of themselves.
There’s a big difference between the retail price and cost of ownership.
Jeff Bezos is famous for saying “focus on the things that don’t change”. The problems that people and businesses encounter don’t change often. The ways they can be solved changes almost yearly. So it stands to reason that making things people want should start with the “what people want” bit, and not the more tempting “things we can make”.
Remember: It’s easier to make things people want, than it is to make people want things.
Feedback on what it’s like to use a feature can only come from people who have used it. What you’re looking for here is:
»» Discoverability – are people finding this feature?
»» Engagement – are people using this feature?
»» Adoption – is it now being used as part of a workflow?
»» Use Cases – how is it being used? what use-cases are popular?
»» Barriers – Who isn’t using it? why? what’s preventing them?
The first screen your users see has three important jobs:
»» Explain how your application works.
»» Motivate your users to get started.
»» Let your users know how to get help, if and when they need it.