Research–design timelines
| S | Representative excerpts | Initial codes |
|---|---|---|
| 8 | “I read a lot when it comes to research. Analysis, research and so on is a phase I want to keep short, but when I become curious about something it leads me to open many Internet tabs. 1t should not continue until the sixth week; within one week I need to bring what I have learned to a sufficient level and reflect it in the project.” |
|
| 9 | “We are in too much of a hurry. The first weeks go well, but after the first jury we move on to the physical phase, and we have not really digested the initial parts. The reason I do research is to do something different, but there is no time left for that.” |
|
| 10 | “My schedule is very messy. As always, I start with analyses, but that phase generally never ends. Until the very last moment there is always something new to learn. We research, we take in information, but what are we going to do with this knowledge? It just stays aside. Then a problem appears later, and if we need that information, we must research it again.” |
|
| S | Representative excerpts | Initial codes |
|---|---|---|
| 8 | →Extensive reading and research →Curiosity-driven scope creep →Need to timebox research | |
| 9 | →Accelerated studio pace →Rushed shift from analysis to production →Lack of time for research-driven design | |
| 10 | →Non-linear work schedule →Never-ending analysis phase →Non-operationalized knowledge |
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.