Why observation is an excellent method for agile frameworks
To gain real insights about your customers and users, you have to contact them. One method for doing this is observation – it’s simple yet unfortunately used far too infrequently.
To gain real insights about your customers and users, you have to contact them. One method for doing this is observation – it’s simple yet unfortunately used far too infrequently.
In agile projects, the question of the customer’s point of view arises at many points. The involvement of this stakeholder is even an elementary component. One way to generate these insights is through interviews – but there are some hurdles here.
Maybe you will enjoy it? Get a short insight, how you could do good interviews with real insights with your customers. As a freelance journalist for over 20 years I collect huge experience in this method. The webinar will last round about 30 min and is introductional; english language!
The interview is a central method of all agile methods. And not only there. After all, good interviewing brings real insights into the problem and solution space of products and services.
The classification of creative thoughts, for example after a brainstorming session, into a concrete action set is not so easy. The High/Low-Grid can be of help here, as it helps to set priorities.
In a smart-technologically optimized future society, “Peter’s problem” suddenly becomes a synonym for the fact that an algorithm may not be omniscient after all. In his novel “Qualityland,” author Marc-Uwe Kling tries his hand at a dystopian societal credit yet ends up delivering a consumer product: an excellent read, but still not exactly profound.
Brainstorming is also an essential method of Design Thinking. But it is usually misused. Used correctly, it has the potential for authentic creativity.
Why doesn’t Design Thinking work in your company? The answer is simple and complicated at the same time: Often, it is the missing “mindset.” Why is it so important to think about this?