Why return to “Change by Design”?
A book read for the first time meets a particular level of knowledge, experience and curiosity. The text remains the same when read again, but the reader has changed.
This matters especially in design thinking. Concepts such as empathy, iteration, prototyping, co-creation and interdisciplinarity are easy to remember. It is much harder to understand how they influence one another in a real project.
After the first reading, one may remember that users should be interviewed and prototypes built quickly. Later, it becomes easier to see that:
- research that does not affect decisions creates little value,
- a prototype is not only a presentation tool but primarily a learning tool,
- an interdisciplinary team is not useful if it cannot make decisions together,
- creativity needs constraints and a clearly defined problem,
- innovation must be desirable, feasible and economically viable.
Re-reading helps move from remembering tools to understanding the complete process.
A second reading is not a copy of the first
The value of returning to a book does not come from mechanically recalling its chapters. It comes from comparing the content with new experience.
After facilitating workshops, sections about group work are read differently. After an unsuccessful implementation, early testing becomes more meaningful. After working in an organisation divided into silos, it becomes easier to understand why innovation cannot be delegated to a single creative department.
The process resembles using a map. The general outline may be familiar, but further experience reveals:
- more precise boundaries of the problem,
- new links between different elements,
- places where earlier assumptions were too simple,
- areas that previously seemed unimportant,
- new uses for familiar methods.
Returning to the book is therefore not a step backwards. It is a way of updating one's map of knowledge.
A deeper understanding of design thinking
Design thinking is often presented as a sequence of stages: empathy, problem definition, idea generation, prototyping and testing. This model is useful for teaching, but it may encourage an overly linear understanding of the process.
Real design work rarely follows a straight line. A team may return to research after a failed prototype, redefine the problem after speaking with an operational employee or reject an attractive idea after examining the cost.
A second reading of “Change by Design” makes it easier to see design thinking as a method for working under uncertainty.
The aim is not to complete five named steps in the correct order. The aim is to reduce the risk of creating something that people do not need, the organisation cannot deliver or the business cannot sustain.
Design thinking as a balance between three perspectives
One of the most important aspects of this approach is balancing:
- human needs and behaviour,
- technological and operational feasibility,
- business viability.
A solution may be attractive to users but too expensive to deliver. It may be easy to build but irrelevant to a real need. It may look strong in a financial model while creating such a poor experience that customers refuse to use it.
Design thinking does not remove these tensions. It makes them visible earlier and allows the organisation to work with them before committing major resources.
Why does the book encourage repeated reading?
“Change by Design” is not a manual built around one precise algorithm. It is also more than a collection of definitions. It combines project stories, examples, observations and reflections on organisations.
This format has two consequences. Readers searching for a rigid procedure may find it less orderly. At the same time, it leaves behind ideas that can be revisited from a new perspective.
Some passages serve mainly as inspiration during the first reading. Later, they become practical reference points when:
- planning research,
- facilitating workshops,
- building an interdisciplinary team,
- testing an idea,
- convincing an organisation to run an experiment,
- deciding whether to invest further in a solution.
IDEO as the main source of case studies
A common criticism of “Change by Design” is the strong presence of IDEO. The book can be read as a presentation of work completed by the organisation associated with the author.
This does not necessarily reduce its value. If the goal is to understand a way of working, examples drawn from the author's experience are natural.
The important point is to maintain distance. The case studies should not be treated as proof that design thinking always guarantees success. They are better used to analyse:
- how the problem was defined,
- who was involved in the process,
- which assumptions were tested,
- how prototypes were used,
- what changed as a result of research,
- how user needs were connected with organisational goals.
The value of a case study lies not in copying the finished solution, but in understanding the path that led to it.
How to use examples from other projects
Every project has a different context: organisation, market, technology, budget, team and users. Literal copying is therefore rarely useful.
It is more productive to look for analogies and ask:
- what type of problem was solved,
- whether similar user behaviour appears in the current context,
- which assumptions can be tested quickly,
- whose perspective is missing,
- whether a simpler prototype is possible,
- whether the problem was defined from the organisation's rather than the user's perspective.
A good case study does not give a ready answer. It helps generate better questions.
Ideas are material, not the final result
Brown's book contains many inspiring concepts and project examples. It is easy, however, to collect ideas without developing them further.
In design thinking, an idea is not an outcome. It is a hypothesis that should be:
- described,
- simplified,
- represented as a prototype,
- tested with users and delivery teams,
- changed or rejected based on evidence.
The number of ideas matters less than the team's ability to learn quickly which ideas are worth pursuing.
A changing context changes the reading
Understanding design thinking develops with practice. Every discussion, workshop, test and unsuccessful implementation influences how earlier knowledge is interpreted.
Empathy may initially be associated mainly with interviews. Later, it becomes a broader ability to suspend one's assumptions and see the situation from the perspective of a customer, employee or partner.
Prototyping may initially mean creating a screen mock-up. Over time, it becomes a way to test a service, conversation, process, message, sales model or form of work organisation.
Interdisciplinarity may initially mean inviting people from different departments. Later, the real challenge becomes creating conditions in which their knowledge genuinely influences decisions.
From a more accurate map to new discoveries
Learning resembles the gradual creation of a more detailed map. The main outlines remain similar, but more relationships, exceptions and local details become visible.
Repeated reading may lead to two kinds of discovery:
Clarifying what is already known
The reader begins to understand why a method works, when it stops working and which conditions are required for it to be useful.
Discovering new areas
A familiar passage may suddenly raise questions about a business model, organisational culture, innovation metrics or the role of leadership in the design process.
The goal is not to possess a final map, but to remain willing to improve it.
Design thinking and complex problems
Design thinking is most useful when a problem has no single obvious answer and many factors influence one another.
Examples include:
- creating a new service,
- redesigning customer support,
- improving cooperation between departments,
- developing a digital product,
- reducing complaints,
- entering a new market,
- improving an internal process,
- using a new technology.
In such situations, a traditional approach may create a detailed plan before the problem has been understood properly. The plan then produces a false sense of control.
Design thinking suggests a different order: build the best possible understanding of the situation, create and test hypotheses, and only then increase the scale of investment.
Why do good ideas get rejected?
Companies generate many valuable ideas that never develop. This does not always happen because the ideas are weak.
Common reasons include:
- judging an idea only by its first presentation,
- lack of evidence to reduce uncertainty,
- requiring a complete business case immediately,
- lack of ownership,
- fear of failure,
- comparing an early experiment with mature products,
- lack of time for testing,
- the belief that a good idea must be complete from the beginning.
Design thinking creates a safer space for immature concepts. It allows them to develop before they have to prove that they are complete businesses.
This does not mean protecting every idea from criticism. It means replacing the general statement “this will not work” with a more useful question: “what must we test to decide whether this could work?”.
An open design process
One of the major strengths of design thinking is the possibility of involving people with very different skills and experiences.
The process may include:
- customers,
- support employees,
- salespeople,
- developers,
- designers,
- finance specialists,
- lawyers,
- operational employees,
- managers.
Each person sees a different part of the system. Customers know their own needs and difficulties. Operational employees understand exceptions and process limitations. Developers know technological dependencies. Finance understands cost, while sales sees market reactions.
An open process does not mean that everyone makes every decision. It means that the necessary knowledge is included before the decision is made.
A workshop is not yet design thinking
The popularity of design methods has led some organisations to identify design thinking with sticky notes, brainstorming and a short workshop.
A workshop can be useful, but it does not guarantee a meaningful result. After the session, the team still needs to:
- organise the material,
- test the most important assumptions,
- build a prototype,
- run tests,
- assess feasibility,
- make a decision,
- plan the next steps.
If the workshop ends with a photograph of a wall full of ideas but no further action, it becomes a team-building event rather than a design process.
Prototyping as a business tool
A prototype is often associated with a simplified version of a product. In reality, it is also possible to prototype:
- a customer service process,
- a new sales conversation,
- a registration flow,
- a subscription model,
- the layout of a service point,
- messages sent to customers,
- an employee role,
- an entire service.
Prototyping lowers the cost of learning. Instead of debating whether a solution will work, the team creates a simplified version and observes reactions.
A good prototype does not need to look professional. It needs to answer an important question.
Failure and feedback
Design thinking treats an unsuccessful test as a source of information rather than a final defeat, provided that the experiment is conducted early and at limited cost.
If an organisation tests a simple prototype and discovers that users do not understand the value, it has learned something useful. Discovering the same fact after full implementation would be far more expensive.
This does not mean celebrating failure for its own sake. The goal is to detect incorrect assumptions quickly and limit losses.
Design thinking and traditional business methods
Design thinking should not be presented as the opposite of analysis, planning or financial management. Organisations still need strategy, budgets, schedules and accountability.
The main difference lies in the order. Traditional approaches often try to create a complete plan as quickly as possible. Design thinking first tries to reduce uncertainty through research and experimentation.
Both approaches are needed:
- design thinking helps discover and validate the right solution,
- management helps implement, scale and maintain it.
The problem begins when an organisation manages with great precision a solution whose basic value has not yet been confirmed.
When is design thinking not enough?
No method solves every problem. Design thinking does not replace:
- industry knowledge,
- legal analysis,
- technical competence,
- project management,
- financial control,
- responsible leadership,
- the decision to abandon a weak idea.
The design process can help identify a direction, but it will not do the organisation's work. Without accountable people, time, budget and readiness to implement, even the best workshops remain only an inspiration.
How to return to the book in a practical way
Re-reading does not always require starting at the first page and continuing to the end. The book can be used in several ways:
- returning to selected chapters before a project,
- comparing cases with a current problem,
- writing down questions raised by the text,
- discussing sections with a team,
- checking which ideas were applied in practice,
- returning after a project to chapters related to mistakes that occurred.
Notes should record not only what the author wrote, but also what a particular idea could mean for one's own organisation.
How to judge whether design thinking works in a company
A company's design maturity should not be measured by the number of workshops or sticky notes.
Better questions include:
- Are decisions preceded by contact with users?
- Does the team test key assumptions before major investment?
- Can unfinished ideas be shown safely?
- Do different departments participate in defining the problem?
- Are prototypes used for learning?
- Do research findings influence decisions?
- Can the organisation abandon a solution when evidence contradicts it?
Design thinking works when it changes decision-making, not merely the appearance of meetings.
What did the second reading change?
The second reading of “Change by Design” did not provide one revolutionary answer. It offered something more useful: a clearer understanding of relationships between elements that had previously seemed separate.
It became easier to see that:
- empathy without decisions remains only curiosity,
- an idea without a test is only an assumption,
- a prototype without a research question may become an empty presentation,
- a workshop without a continued process does not create innovation,
- interdisciplinary work requires facilitation,
- innovation must include both people and business.
This is enough reason to return to the book again.
Summary
“Change by Design” remains an important book not because it provides one universal recipe, but because it helps readers look differently at complex problems.
Re-reading improves understanding of design thinking, reveals new relationships and allows the ideas to be compared with current experience. IDEO case studies can inspire, provided that the reader analyses the method of thinking rather than copying finished solutions.
The greatest practical value of design thinking lies in creating space for research, cooperation, experimentation and gradual reduction of uncertainty. Ideas do not need to be complete from the beginning in order to deserve testing.
The method does not replace business knowledge, technology or responsible management. It can, however, help an organisation understand what is worth building before it begins doing so quickly, expensively and at scale.
The second reading of Brown's book did not end my interest in design thinking. It showed that this is a subject worth revisiting as new experience accumulates.
Issues: → Change by Design, Tim Brown, design thinking, second reading Change by Design, design thinking book, IDEO, business innovation, service design, prototyping, user research, interdisciplinary team, design process, creative problem solving, innovation management, design thinking in business.