Review: Creativity in IT and Technology for Dummies

Flawed creativity planning was to blame for the diesel scandal! At least that’s how Andrea Herrmann interprets it (with a wink). The challenge was to comply with the emission limits. Those in charge viewed this as an incremental optimization, but the laws of physics demanded a radical technical innovation. When that didn’t materialize, a creative (but illegal) solution was chosen.
This story says a lot about the book. For Andrea Herrmann, creativity is an engineering task that can be categorized and planned. Anyone who misjudges the level of innovation will run into problems.
„Creativity in IT and Technology for Dummies“ was published by Wiley-VCH in June 2026. The review follows.
Note: Andrea Herrmann is hosting a free webinar on this topic on Wednesday, October 21, 2026, from 5:00 p.m. to 6:30 p.m. Learn more and sign up >>
Target group: Systems engineers, software architects, requirements engineers, product managers, and anyone who plans or facilitates brainstorming processes in technical projects.
Rating: ★★★★★ With its process model for creativity tailored to engineers, this book fills a real gap. It is practical and serves as an excellent reference.
Acquire: The print edition costs €24.99, and the e-book costs €21.99. 416 pages, ISBN 978-3-527-72172-6.
The Author
Andrea Herrmann studied physics and engineering, earned her doctorate, and transitioned to computer science through programming. She has worked in industry, research, and higher education. At a software company serving mechanical engineering firms, she was in charge of „Research and Innovation“ and, by her own account, submitted a research proposal every week. Since 2012, she has been working as a freelance trainer and consultant at her own company Herrmann & Ehrlich and teaches as a private lecturer at Heidelberg University.
Her area of expertise is requirements engineering. Among other works, she is the author of the textbook Fundamentals of Requirements Analysis. Readers of se-trends.de know her as a guest writer, for example from her article about, What the History of Process Models Reveals About Agile Development. Prof. Rüdiger Weißbach served as the book's academic editor.
Disclosure: This article is based on a free review copy of the book.
The Process Model
At the heart of the book is a twelve-phase process model. Herrmann derives it from models that every systems engineer is already familiar with: the funnel model, V-model, an iterative approach, the "build-test-learn" cycle from Lean Startup, the Double Diamond model, the separation of the problem space and the solution space, the Twin Peaks model, and Design Thinking.
At first glance, there seems to be a contradiction here. The British Design Council’s Double Diamond model strictly separates the problem space and the solution space: first Discover and Define, then Develop and Deliver. Bashar Nuseibeh’s Twin Peaks model asserts the opposite. Decisions made in the solution space narrow the problem space, so one moves back and forth between the two iteratively. Herrmann combines the two approaches. She runs through the Double Diamond again at each level of abstraction in the Twin Peaks model.
This results in three levels, each with four phases. At the system level, the product idea and its rough architecture are developed. This is followed by the scenario level, where usage scenarios, acceptance test cases, and interface models are developed. At the detail level, high-fidelity prototypes, implementation, and acceptance testing follow. All three levels are preceded by a preparatory phase that includes a project profile, team selection, research, and legal considerations.
The book defines specific deliverables for each phase. At the end of Phase 2, there may be a requirements specification; at the end of Phase 4, an architectural decision between alternative solutions; and at the end of Phase 8, a finalized design with a cost estimate. The model is adaptable. For example, if you are making only minor changes to an existing product, you can omit the system level.
Building on what works
For readers of SE-trends, this is familiar territory: a V-model in which the creative phases are explicitly factored in. Herrmann himself articulates this approach:
„Contrary to a common misconception, creativity techniques are not at odds with engineering logic; rather, they can be effectively combined, for example, in the twelve-step process proposed here.“
Andrea Herrmann
The book is held together by a single, overarching example: a language-learning app that goes through all phases, from the initial idea to the sequence diagram. Alongside this are historical examples, such as the improvised air filter adapter on Apollo 13 or the development of penicillin, which Herrmann recounts as a long, systematic process involving only a small element of chance.
The book is divided into seven parts. In terms of content, these parts form four sections.
Motivation (Part I)
Part I clarifies concepts and dispels prejudices. Creativity is whatever is new and useful. Herrmann distinguishes between incremental and radical innovation, market pull and technology push, and proactive and reactive creativity. The starting point is a quote from Neil Maiden from his keynote address at the CreaRE 2024 workshop:
„Most professionals do not view their work as creative.“
Neil Maiden, Bayes Business School
Chapter 3, which traces creativity through the phases of the product life cycle, is worth reading. This is because it offers some rather unexpected insights. When it comes to the user interface, for example, Herrmann expressly advises against creativity and points to the need to conform to user expectations as specified in EN ISO 9241-110. When it comes to testing, however, the tester must be as creative as the least capable user and a hacker combined. We can view a risk identification session as a proactive creativity workshop focused on problems.
While there isn't much that's truly new here for experienced readers, since the book is also aimed at students and executives, this section brings everyone up to the same level.
Planning and Preparation (Parts II and III)
Part II explains why creativity requires multiple people and iterations. To illustrate this, Herrmann uses a simplified model of the brain with analytical and creative halves. She herself calls it a „very crude simplification,“ yet one that has great practical value: analytical and creative phases alternate; it is not possible to do both at the same time.
Chapter 7, which covers time requirements, is relevant to project planning. For creative projects, calendar time cannot be calculated based on working hours because ideas require an incubation period. Herrmann recommends a one- to two-week break between consecutive workshops. Chapter 8 then elaborates on the process model described above and presents two sample project plans—one detailed and one simple. Chapter 9 covers the team, open innovation with lead users and crowdsourcing, as well as initial questions regarding AI and copyright.
Part III outlines the preparation process in detail: This includes refining the project plan, briefing the team, researching the problem and solution space, preparing the technical infrastructure—including CI/CD—and so on. Chapter 13, which covers legal and contractual matters, is missing from most books on creativity. It clarifies who owns the invention, how confidentiality and licensing are handled, and what happens to paying customers if the project is terminated. Anyone who has ever set up an innovation project with external partners knows how late these questions are usually asked.
Creative Activities (Part IV)
On Part IV At around 150 pages, this is the main focus of the book. It begins with self-organization, covering idea banks, deep work, and strategies for stepping back.
Chapter 15 is devoted to the Artificial Intelligence and goes through the phases of the Double Diamond model to do so. This is demonstrated using the language-learning app. For example, an AI can compile research on competing products into a table. A human must then consolidate the data because different products use different terms to describe the same function.
Chapter 16 covers facilitating groups using the Tuckman model, taking minutes, and four fears that act as barriers to creativity: fear of the blank page, fear of criticism from the group, fear of the facilitator, and fear of making mistakes.
The book’s strongest argument lies in the distinction drawn between Chapters 17 and 18. Herrmann writes that the academic literature often overlooks how differently the search for incremental ideas differs from the search for radical ones. The degree of innovation can be controlled by how the research question is formulated: The more specific the question, the lower the degree of innovation in the answers.
Chapter 17 discusses methods for incremental improvements. Surprisingly, traditional engineering methods such as current-state analysis, modeling, requirements analysis, and FMEA are classified as creativity tools. This is followed by SWOT analysis, the innovation strategy matrix according to Geschka, the Delphi method, scenario planning, the morphological box, the SCAMMPERR checklist, and the Osborn checklist. For SCAMMPERR, there is a table with sample questions for all nine letters and a time estimate of ninety minutes for the entire session.
Chapter 18 deals with radical innovation. She no longer uses brainstorming because it is „not very creative“ and leaves „too much room for unhealthy group dynamics.“ Instead, she recommends, among other things, the 635 method, de Bono’s six thinking hats, provocative word and image confrontation, as well as analogy techniques and bionics. TRIZ She explains this using the Contradiction Matrix and the forty solution principles that Altschuller distilled from forty thousand patents. For large groups ranging from twenty to two thousand people, she introduces the World Café and Open Space formats. Chapter 19 adapts these concepts for virtual workshops.
Evaluation, Development, and Continuous Operation (Parts V through VII)
Part V guides the collected ideas through the twelve phases. Here, the book becomes a book on requirements and systems engineering. Six participants in a 635 session generate 108 ideas. Herrmann shows how to cluster these, formulate them as user stories, and, according to the Kano Model classified and filtered using elimination criteria, market analysis, and the technology acceptance model. A utility analysis with weighting and sensitivity analysis compares two minimum marketable products.
At the system level, the following elements are addressed: feasibility within the solution space, cost-effectiveness, portfolio, and requirements specification. At the scenario level, usage scenarios are developed as text and as UML activity diagrams, along with low-fidelity prototypes and acceptance test cases in Gherkin. A vertical prototype, a data model, and a sequence diagram round out the scenario level.
Part VI is titled „Endlessly Creative.“ It discusses the repository for discarded ideas, user feedback as a source of ideas, and improving the creative process itself. For innovation management, Herrmann uses milestone trend analysis and earned-value analysis; for improvement, he relies on the PDCA cycle and lessons learned. Chapter 30 provides arguments for convincing colleagues and management. As is so often the case, front-loading is crucial here: The most costly mistakes occur during the concept phase and only become apparent later. Part VII summarizes the ten most important points to remember.
The Book as a Reference Work
Herrmann recommends reading the book from beginning to end.
„While the content of each chapter can be understood independently, it cannot be applied on its own. For example, it would be of little help to you to pick out a creativity technique from Part IV and try to apply it without any preparation.“
Andrea Herrmann
That's true for the first read-through. After the first reading, however, the book works very well as a reference work, thanks to several factors.
- Cheat Sheet. The cheat sheet at the front of the book lists all twelve phases and their outcomes. It serves as a checklist for project planning and for deciding which levels can be combined in a specific project.
- Decision tree for methods. At the end of Chapter 18, there is a textual decision-making guide. It categorizes the methods by level of innovation, group size, and time required. Those working alone should use trigger-word or image confrontation. The 635 Method and confrontation techniques are suitable for sessions lasting thirty to forty-five minutes. TRIZ, analogy techniques, and risk analyses can be as time-consuming as needed. This overview is very useful for planning a workshop.
- Standardized method descriptions. The methods follow a recurring pattern consisting of a step-by-step guide and an example from the language-learning app, often supplemented by the author’s own experiences. Tables such as the overview of activities and methods for each Double Diamond phase or the SCAMMPERR question list can be incorporated directly into workshop materials.
- Symbol system. The "For Dummies" symbols highlight definitions, case studies, references, exercises, and mnemonic phrases. Herrmann strongly advises readers revisiting the book to focus on the "Memory Boxes." Each chapter ends with such a summary.
- Table of Contents. The table of contents spans ten pages and goes down to the level of individual sections. This is necessary, since the index is rather brief at just two pages. If you're looking for a specific method, you'll find it faster by using the table of contents.
How This Book Differs from Others
Anyone looking for a book on creativity in technology in German-speaking countries will find four categories of works.
Collections of Methods for Creativity Techniques List brainstorming, mind mapping, and the morphological box side by side. They are usually written in a way that applies to any industry and do not specify when each method is appropriate or what happens before and after the workshop.
Design Thinking Literature Like Lewrick, Link, and Leifer’s *Design Thinking Playbook*—which Herrmann himself cites—it focuses heavily on the problem space and user-centered design. It barely addresses the technical solution space, including architectural decisions, levels of abstraction, and acceptance criteria.
Design Methodology The approach outlined by Pahl/Beitz or in VDI 2221 is systematic and engineering-oriented, but heavily influenced by mechanical engineering. Creativity is viewed there as just one tool among many, and software is scarcely mentioned.
Books on Requirements Engineering treat creativity techniques as one investigative technique among many, usually in a single chapter.
This book recognizes the limitations of these categories and integrates them into a process model. I am not aware of any other German-language book that intertwines the Double Diamond and Twin Peaks frameworks with the levels of abstraction of the V-model and assigns defined deliverables to each phase. The distinction between incremental and radical innovation also extends to the participant group and workshop preparation.
Conclusion
„Creativity in IT and Technology for Dummies“ deserves five stars because it fills a real gap that I’ve personally observed in many development organizations. In those organizations, creativity either doesn’t exist at all or takes place in workshops whose results are rarely followed up on consistently. Herrmann combines the two through a process model that can be integrated into existing V-Model processes without replacing them.
The "For Dummies" style isn't for everyone, and experienced readers can skim through Part I. This doesn't change the substance of the book. Anyone who facilitates workshops, writes specifications, or needs to request a budget for innovation projects will find a useful tool here for their day-to-day work. Chapter 30 even provides the arguments for management.
There’s an important lesson to be learned from the diesel scandal mentioned at the beginning. Before the next workshop, we need to take a close look at the question of what we’re trying to achieve: Are we looking to improve things or to reinvent them? The answer will determine our approach, team, and timeline. This book shows how to ask that question—and what comes next.






