Seminar 1 - Emma Klint

While doing a design project it’s important to set up goals and requirements. What these requirements are depend on a lot of different aspects, and getting them right is important for the success of the design. There are different kinds of requirements and you might have to use different methods for data gathering and analysis to find them all. It’s actually preferable to use a couple of different methods to make sure you get all the data you need.  Before doing a study you need to set up goals and really think through your choice of method. Your method need to provide you with the data you need to use the, for the project, preferable analysis technique. What also matters is how you’re presenting you’re gathered data. Regardless if you’re presenting it to a colleague or a customer, the data need to be presented in a distinct way to make sure that everybody understand the importance in the design choices you’d like to make.

What really got me thinking during the reading was, when do you stop setting up new requirements and are a software project ever considered all done? Perhaps it’s was easier a couple of years ago, when software was more of a physical product which was sold in i physical store without the possibility of sending out a small updates at any time. How do you keep a design team motivated if they can’t see a light at the end of the tunnel?