How to design great products design should not be a blueprint; learn to tell stories



narrative based design flow shows efficient

the biggest problem for product design teams is that they often confuse fashionable products with superior products, and that’s a common problem. On the face of it, this is a small mistake, but it can have very serious consequences: after all, if the user can’t change your product, even if they look better, nobody will buy it.

I think the best way to eliminate this obstacle is to adopt a narrative centered design technique. The core idea of this approach is to present a series of narrative use cases for the product. From the user’s point of view, each step of the product design is clearly described. I asked a lot of start-up companies recommended this design technique, it can always make the design team neglect specious writing, make better decisions in the real concerns of users: how to make the best use of the final product.

design should not be blueprint

I noticed that some teams in the product blueprint, often in the UI (user interface) design do things carelessly. Each screen shows the appearance of the product in different circumstances, but the screens are not somehow connected. The crux of the problem is that when the design is presented to everyone in this way, the user is only a general understanding of the appearance of the product.


design team does not focus on the work mechanism of the product, nor does it simulate how the customer interact with the product. So, when some teams treat design as a product blueprint, their ability to reason out product interactions is severely limited.

the best product designers are often good design approach to the narrative, and applying the method of pure green fire furnace. They will start with a few stories to show the customer how to interact with the product. Only after that goal can they design the screen and tell the story of a product interaction.

narrative as the main design thread

in a narrative based design process, the design team first analyzes dozens of model ordered by sequence, which is like a picture in a slide. Next, they want to read every sentence the customer reads, every move they make, and the entire system responds to every screen produced.

from the initial trigger event to the completion of a goal, the designer must always listen to the customer’s recommendations, and at the same time, show how the design supports each step throughout the process. I have recommended this narrative based design approach to many start-up companies. These techniques are applicable to mobile applications, marketing websites, data analysis, enterprise IT departments and other services.

for engineers, this design process should be >

Leave a Reply

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