Creative Technologies Lab | dokuWiki

Repository of academic adventures, experimental technology, accidental brilliance, and collaborative nerdery.

User Tools

Site Tools

Trace:
extras:wissikon:design-development:design-process

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
extras:wissikon:design-development:design-process [2025/07/06 09:43] – Felix Hardmood Beckextras:wissikon:design-development:design-process [2026/09/14 09:20] (current) – Felix Hardmood Beck
Line 1: Line 1:
 ===== Archetypal Phases of the Design Process ===== ===== Archetypal Phases of the Design Process =====
  
-[[designphasen|link to German version]].+[[extras:wissikon:design-development:designphasen|Link zur deutschen Version]].
  
-==== 1. Definition of the Problem or Challenge ====+Design processes can be structured very differently depending on the discipline, project, and task. Within the study program, we use the four archetypal phases //<color #efe4B0/#00a2e8>Discover!</color>//, //<color #b5e61d/#22b14c>Ideate!</color>//, //<color #ff7f27/#ffc90e>Make!</color>// and //<color #ffc90e/#ed1c24>Expose!</color>// as a shared framework to structure different activities within a design process and to make the individual working process more transparent. These phases are explicitly not intended as a rigid or linear sequence, but as an iterative process in which individual steps overlap and may be repeated several times. Insights gained from experiments, prototypes, tests, feedback, or reflection can at any point lead to questioning earlier assumptions, conducting additional research, developing new ideas, or modifying existing concepts. The design process should therefore be understood less as a fixed sequence of individual steps and more as a repeated movement between **understanding, developing, testing, and reflecting**. In simplified form, this process can be described as **Discover! → Ideate! → Make! → Expose!**, while continuous loops of **Make → Test → Reflect → Iterate ↺** occur especially during development and can lead back to earlier phases whenever necessary.
  
-In the initial phase, the focus lies on defining the requirements, objectives, and constraints that shape the design task. A precise understanding of the problem to be solved is essential to guide the project in a meaningful direction. +{{ :extras:wissikon:design-development:iterativer_designprozess.png?direct |}}
  
-This involves identifying the needs, expectations, and behaviors of the target audience as well as recognizing external factors such as technical, social, economic, or environmental constraints. Techniques like stakeholder mapping, problem tree analysis, or framing design challenges can support this process. 
  
-Establishing a well-defined problem space provides the foundation for all subsequent creative and strategic decisions within the design process. A clear definition ensures alignment among project participants and helps to maintain focus throughout iterative development cycles. +^  ^ **<color #efe4B0/#00a2e8>Discover!</color>** \\ Understand and contextualize ^ **<color #b5e61d/#22b14c>Ideate!</color>** \\ Develop possibilities ^ **<color #ff7f27/#ffc90e>Make!</color>** \\ Make ideas visible and testable ^ **<color #ffc90e/#ed1c24>Expose!</color>** \\ Communicate process and result ^ 
- +| **Goal** | Understand the task, context, needs, problems, and opportunities. | Develop different ideas and solution approaches and open up the solution space. | Develop selected ideas further, test them, and make them tangible and assessable. | Structure and communicate the design process and its results in a clear and understandable way. | 
- +| **Focus** | Observe, research, analyze, identify relationships, and consolidate insights. | Explore, vary, combine, question, and select. | Develop, prototype, test, reflect, and iterate. | Select, document, present, explain, and reflect. | 
----- +| **Possible methods** | Research, observation, analysis, interviews, mapping, problem definition, design challenges | Brainstorming, brainwriting, mind mapping, sketches, storyboards, scenarios, simple models | Sketches, models, mock-ups, experiments, prototypes, scheme design, detailed design, testing | Presentation, documentation, critique, feedback, posters, process visualization | 
- +| **Result** | A well-founded question or a clear starting point for the further process. | Different possible solution approaches and a reasoned selection for further development. | An increasingly concrete design or prototype that can be tested and developed further. | A comprehensible representation of how the initial question, process, and result have developed. | 
- +| **Iteration** | New insights can at any time require additional research or a redefinition of the problem. | Insights from prototyping and testing can at any time trigger new ideas. | **Make → Test → Reflect → Iterate ↺**; return to Ideate! or Discover! if necessary. | Feedback and reflection can raise new questions and trigger another iteration. |
-==== 2. Research and Analysis ==== +
- +
-Following the problem definition, the research and analysis phase involves gathering, synthesizing, and interpreting relevant information. This builds a rich contextual understanding of the design environment and the factors influencing it. +
- +
-Methods used may include user research (interviews, observations, surveys), market and trend analyses, competitive benchmarking, and ethnographic studies. Visual tools such as personas, customer journeys, or system maps help structure and communicate findings. +
- +
-The research phase uncovers hidden needs, identifies opportunities for innovation, and helps designers anticipate potential obstacles. It establishes a knowledge base that informs and inspires the following ideation and development phases. +
- +
- +
----- +
- +
- +
- +
-==== 3. Ideation (Idea Development) ==== +
- +
-Ideation is the phase where creative exploration takes center stage. It aims to generate a wide range of potential solutions without premature evaluation or restriction, promoting divergent thinking. +
- +
-Creativity techniques such as brainstorming, 6-3-5 methods, mind mapping, or role-playing can be used to stimulate new perspectives and uncover unexpected connections. At this stage, quantity matters more than immediate feasibility. +
- +
-Early visualization through sketches, scenarios, or low-fidelity prototypes supports communication and discussion. Iterative rounds of ideation can occur throughout the project, especially when new insights or challenges emerge. +
- +
- +
----- +
- +
- +
- +
-==== 4. Design Development ==== +
- +
-During the design development phase, selected ideas are elaborated into concrete design concepts. Abstract ideas are translated into tangible forms, considering functionality, usability, aesthetics, and technical feasibility. +
- +
-Techniques such as sketching, 3D modeling, wireframing, storytelling, or physical prototyping help to explore and refine the concepts. Both scheme design (overall structure) and detailed design (specific features and elements) are addressed. +
- +
-Design development is iterative by nature: early concepts are evaluated, tested, and modified repeatedly to strengthen the solution's coherence, user relevance, and viability before moving into final production stages. +
- +
- +
----- +
- +
- +
- +
-==== 5. Evaluation and Selection ==== +
- +
-Once different design options have been developed, they are systematically evaluated to identify the most promising solution(s). This evaluation focuses on how well the concepts meet the defined goals, user needs, and contextual requirements. +
- +
-Evaluation methods can include user testing, usability studies, expert feedback sessions, comparative analysis, or structured decision-making tools like criteria matrices. Emphasis is placed not only on technical performance but also on user experience, emotional impact, and long-term sustainability. +
- +
-Evaluation is seen as an opportunity for reflection and learning. Rather than providing definitive conclusions, it often leads to adjustments, refinements, or new directions within the iterative design cycle. +
- +
- +
----- +
- +
- +
- +
-==== 6. Implementation ==== +
- +
-The implementation phase transforms refined design concepts into real-world applications. Depending on the project, this may involve manufacturing physical products, coding digital solutions, producing services, or preparing communication materials. +
- +
-Attention is given to material choices, production processes, technological integrations, and ensuring that the design intent is faithfully realized. Cross-disciplinary collaboration between designers, engineers, developers, and other specialists is essential at this stage. +
- +
-Implementation often includes creating final prototypes, pilot versions, or minimum viable products (MVPs) that can be tested and evaluated before full-scale deployment. +
- +
- +
----- +
- +
- +
- +
-==== 7. Review and Iteration ==== +
- +
-After implementation, the design is reviewed through real-world testing and evaluation to assess whether it achieves its intended outcomes. Data collection, user feedback, performance monitoring, and qualitative observations are key activities during this phase. +
- +
-Identified gaps, shortcomings, or emerging opportunities inform further adjustments and iterations. Iteration may involve minor refinements or major rework, depending on the complexity of findings and project goals. +
- +
-Recognizing that design is an evolving process, this phase reinforces a mindset of continuous improvement and adaptability. Successful designs embrace iteration not as a sign of failure but as a core strategy for innovation and meaningful impact. +
- +
- +
----- +
- +
-===== Progression of Prototyping Methods in the Design Process ===== +
- +
-Ideation → Exploration → Testing → Refinement → Presentation +
- +
-  * **[[extras:wissikon:prototyping-and-modelmaking:sketch-modeling|Sketch Model]]** → Early spatial and formal exploration +
-  * **[[extras:wissikon:prototyping-and-modelmaking:quick-and-dirty-prototyping|Quick & Dirty Prototype]]** → Fast testing of ideas and interactions +
-  * **[[extras:wissikon:prototyping-and-modelmaking:mock-up|Mock-up]]** → Visualization of layouts, interfaces, or product structure +
-  * **[[extras:wissikon:prototyping-and-modelmaking:funktions-prototyp|Work-like Prototype]]** → Testing of technical functions and processes +
-  * **[[extras:wissikon:prototyping-and-modelmaking:look-like-prototyp|Look-like Prototype]]** → Representation of form, materiality, and haptics +
-  * **[[extras:wissikon:prototyping-and-modelmaking:appearance-model|Appearance Model]]** → Highly detailed presentation of the final appearance+
/var/www/vhosts/ct-lab.info/wiki.ct-lab.info/data/attic/extras/wissikon/design-development/design-process.1751795000.txt.gz · Last modified: by Felix Hardmood Beck