Design Thinking Theory and Practice (Eujin Pei, Kurt Becker, (eds.))（Z-Library）

【One-Line Pitch】 A multi-voice anthology that unpacks design thinking as both a cognitive stance and a practical toolkit, this book is for design engineers, industrial designers, and innovation managers who want to move beyond buzzwords and see how theory translates into real product and service decisions. 【Book Arc】 - **Opening (~0%–10%)**: The editors set the stage by defining design thinking as a series of cognitive, strategic, and practical steps for problem-solving. They frame the book’s unique value: pairing academic research with practitioner “stories” across disciplines, from product design to public services like healthcare. - **Early (~10%–23%)**: The focus shifts to education and innovation frameworks. Chapters argue that design thinking is a teachable 21st-century skill—useful for handling open-ended, complex problems—and introduce structured tools like the Innovation Framework, which forces teams to articulate benefits, measurements, constraints, and trade-offs. - **Early (~23%–32%)**: A deep dive into data-driven design. Using a battery-powered outdoor camera as a running case, the text shows how key datasets, Design of Experiments (DoE), and cross-functional teams validate whether an innovation truly delivers value without unintended side effects. Communication tools like the one-pager (takeaway, findings, next steps) are introduced. - **Middle (~32%–48%)**: The book pivots to the philosophy of ideas. It contrasts two perspectives: “ideas as objects” (structured, funnel-like selection of the best concept) versus “ideas as triggers-for-change” (fluid, engagement-driven, where meaning emerges through interaction). The argument is that both are complementary and necessary for sustained creativity. - **Late (~48%–end)**: The remaining chapters (per the table of contents) explore specialized angles: intuitive versus analytical design methods, co-design in engineering, metaphors in design education, and a long-term case study on interdisciplinary aging research. These chapters test design thinking’s durability and adaptability beyond product development. 【Key Takeaways】 - **Design thinking is a systematic problem-solving method, not a vague mindset** (Opening): It combines cognitive reasoning with practical steps, making it applicable to everything from banking services to public healthcare. The book’s core promise is that this process can be learned and institutionalized. - **Education is a primary vehicle for design thinking** (Early): Integrating real-world industry problems into classrooms helps students handle ambiguity and persist through difficult challenges. The tools and methods are valuable assets regardless of the teaching format—workshops, projects, or full curricula. - **The Innovation Framework forces clarity on value** (Early): Before pursuing any design change, teams must answer four questions: What is the benefit over baseline? How is it measured? What limits the current design? What trade-offs are acceptable? This prevents “innovation theater” and grounds decisions in evidence. - **Data is non-negotiable for validating design choices** (Early): Key datasets must not only prove the benefit but also reveal unintended consequences. The book stresses that a large baseline dataset gives confidence in production processes, while DoE helps isolate variables like RF chip corners in hardware design. - **Cross-functional teams are essential for holistic design** (Early): No single expert can foresee how a change ripples across product areas. Leveraging diverse teams and requesting their specific datasets closes knowledge gaps and reduces the risk of unaccounted variables. - **Ideas can be managed as objects or as triggers-for-change** (Middle): The “object” view treats ideas as entities to be filtered through a funnel for quality and novelty. The “trigger” view sees ideas as catalysts for conversation and engagement. Managers need both: structure for efficiency, and flexibility to keep creative momentum alive. - **Meaning is co-created through interaction** (Middle): An idea’s value is not fixed in its description; it emerges when people engage, interpret, and build on it. Organizations should avoid over-formalizing idea development, as excessive structure can kill the generative conversations that fuel innovation. 【Reading Tips】 - **Skim the opening chapters (0–10%)** if you already know design thinking basics; they are largely scene-setting and literature review. Focus instead on the Innovation Framework table and the camera case study in the early chapters—they are the most actionable. - **Deep-read the “ideas as objects vs. triggers” section (32–48%)** if you manage innovation teams. This is the conceptual heart of the book and will change how you structure ideation sessions and evaluate proposals. - **Treat the camera example as a template** for your own projects. The book walks through benefit definition, DoE setup, data analysis, and one-pager communication—replicate this structure for hardware or software design validation. - **Skip the reference lists** unless you need academic citations; they are extensive but not essential for practitioners. The final chapters (intuitive vs. analytical methods, co-design, metaphors) are best read selectively based on your discipline. - **Take away the one-pager format** (key takeaway, findings, next steps) as an immediate communication tool. It is simple, transferable, and likely the most reusable artifact in the entire book. 【Coverage Limits】 The excerpts do not cover the full content of the later chapters (e.g., co-design applications, metaphors in education, or the aging research case study) in detail; this guide synthesizes only the opening, early, and middle sections. Additionally, no specific design thinking process models (like Stanford d.school’s five phases) are fully detailed beyond the Innovation Framework.