Growth hacker

Amazon, for its part, has a couple of other easy suggestions for you if the advice “write a hypothetical press release” doesn’t quite work for your situation. Their CTO, Werner Vogels, suggests trying to write an FAQ for this product you’re developing. (That way you can address, in advance, potential user issues and questions.) Or try to define the crucial parts of the user experience by making mockups of pages, writing hypothetical case studies so you can actually start to see what it would look like and who it would work for and how. Finally, try writing the user manual, which as Werner explains usually has three parts: concepts, how‑to and reference. (Defining these means you understand your idea in and out from the customer’s perspective. Also, he says, if you have more than one type of user then write multiple manuals.)

This is from Ryan Holidays

Tags: No tags

Add a Comment

Your email address will not be published. Required fields are marked *