Story Telling

Challenge and Selection

As a developer, I am always faced with the challenge of presenting complex contexts in such a way that  in the end the decision-makers have a good understanding of them.

Since our products often deal with the topic of "user experience" or simple and intuitive operating  concepts - and you have to get into the mind of the user - the method of "storytelling" is the obvious  choice.

With this method, tailored to the audience, you can make a subject much more exciting and personal  than just with factual logical contexts.

I can use the imagination of the audience, so that even before the first prototype a picture in mind is  created and one can even experience the emotions that should arise.

Application

To develop my story, I put myself in the role of the customer and go through the complete product life  cycle with him. From the purchase of the product, through installation, initial start-up, maintenance, etc.  Together with the customer, the highs and lows can be emotionally experienced.

In this way, I was able to turn my product vision into an exciting adventure story, and through the  customer's successes and setbacks in the story, we were able to derive many action steps.

Insight

Right at the beginning of the story, we found such a big shortcoming: The product features were in the  foreground, so the shopping experience was totally neglected.

The customer's decision to buy depends largely on the transported emotions, which starts with easy  findability, attractive packaging and appropriate advertising.

Many seemingly unnecessary things have been brought to the surface, because they contribute  significantly to the user experience.

Approach

We have made the decision to drop some product features and instead focus on usability.   Our product should be as intuitive as possible and not require a large amount of documentation.

I will continue to use this method in the future and I could also convince my colleagues of the  advantages of this method.


Story Telling Challenge and Selection As a developer , I am always faced with the challenge of presenting complex contexts in such a way that in the end the decision - makers have a good understanding of them . Since our products often deal with the topic of " user experience " or simple and intuitive operating concepts - and you have to get into the mind of the user - the method of " storytelling " is the obvious choice . With this method , tailored to the audience , you can make a subject much more exciting and personal than just with factual logical contexts . I can use the imagination of the audience , so that even before the first prototype a picture in mind is created and one can even experience the emotions that should arise . Application To develop my story , I put myself in the role of the customer and go through the complete product life cycle with him . From the purchase of the product , through installation , initial start - up , maintenance , etc . Together with the customer , the highs and lows can be emotionally experienced . In this way , I was able to turn my product vision into an exciting adventure story , and through the customer 's successes and setbacks in the story , we were able to derive many action steps . Insight Right at the beginning of the story , we found such a big shortcoming : The product features were in the foreground , so the shopping experience was totally neglected . The customer 's decision to buy depends largely on the transported emotions , which starts with easy findability , attractive packaging and appropriate advertising . Many seemingly unnecessary things have been brought to the surface , because they contribute significantly to the user experience . Approach We have made the decision to drop some product features and instead focus on usability . Our product should be as intuitive as possible and not require a large amount of documentation . I will continue to use this method in the future and I could also convince my colleagues of the advantages of this method .