Page 115 - ux-design-for-startups-marcin-treder
P. 115
Whenever you’re optimising your product, make an
assumption of how big the possible gain is, how big the
cost is and how high the probability of success is. Try
to specify both cost and gain in dollars (or whatever
currency you use).
Let’s say you need three hours to design an optimised
version of a certain feature and another five hours of
development to launch the new version. And let’s say
that your time is worth $100 per hour to the company.
That means the cost of optimisation is $800. What’s
the assumed gain? Will it be $200 per month, for
example, which means you’ll start earning on this
optimisation after one month? What’s the probability
that it will actually work? What will happen if you
don’t optimise it?
All these questions are equally important. My rule of
thumb is to deal first with anything that creates a loss.
If something irritates your customers and makes them
leave your app, that’s the first thing to optimise. If you
don’t, you’ll always have a hole in your product.
geT iT opTimised 115
