repeating-making-and-breaking-in-the-design-process Web Design

Web Design

Repeating Making and Breaking in the Design Process

About this topic

The 'design process of repeating making and breaking' refers to the iterative cycle of materializing ideas, evaluating and testing them, and intentionally dismantling parts or the whole for reconstruction when necessary. This question reexamines design not as a linear process of 'completion' but as an evolutionary process premised on destruction and regeneration. It explores how excellent web design emerges in the tension between seeking perfection and having the courage to break.

Conceptual positions
01 Iterative Design Theory

Design is inherently iterative; breaking is an essential condition for evolution. A process premised on failure produces optimal solutions.

02 Perfectionist Design

Aiming for high quality in a single construction while minimizing breaking. A position that values stability and predictability.

03 Agile Design

Repeating making, breaking, and validation in short cycles. A modern method flexible to changing requirements.

04 Intuitive Destruction Theory

Great designers know the 'timing to break' through intuition beyond logic. The core of creativity lies in the courage to destroy.

Talk entry points

  1. In a recent project, have you had the experience of breaking a screen or component you once made? Please share the emotions you felt at that time.

  2. Is there a design or UI you thought 'I don't want to change it anymore'? Why do you think you felt that way?

  3. When you received feedback or test results and broke something substantially, what resistance did you feel at first?

  4. Is there a trigger or turning point when you became able to view 'breaking' positively?

  5. Have you had the experience of a project stalling or being pressed for deadline because you sought perfection too much?

  6. When the team proposed 'let's try breaking everything for now', how did you feel and how did you act?

Conceptual tensions
Completion vsImprovement
Breaking something once 'completed' damages the sense of achievement, but in the long term improves user experience quality. Whether to rush completion or prioritize improvement.
Efficiency vsExploration
Breaking and rebuilding takes time and effort, but there are essential improvements unreachable by superficial fixes. The trade-off between short-term efficiency and long-term value.
Individual vsTeam
Breaking what you made touches personal pride and sense of ownership, but is a necessary sacrifice for team goal achievement. The balance between ownership and sharing.
Intuition vsData
Should the timing of breaking be decided by user data and test results, or entrusted to the designer's experience and intuition? Integration of both is key.
Fear vsCourage
Fear of breaking comes from attachment wanting to protect the current state. On the other hand, without breaking, new value cannot be born. The tension between attachment and innovation.
Talk note

This topic is not for competing over the 'correctness' or 'completeness' of design. It is a quiet space to put into words and share as they are our emotions, fears, and joys that waver between making and breaking. Through dialogue, please feel that both seeking perfection and having the courage to break are necessary for excellent design and a fulfilling creative life.

Glossary
Iteration
The fundamental design cycle of creating, testing, and evaluating prototypes, then repeating modifications based on feedback. Making in order to break.
Prototyping
Creating simplified models before the final form to validate on the premise of breaking. Reduces risk and encourages discovery.
Destructive Improvement
The strategic act of deliberately breaking existing good parts to create a better whole. A challenge to status-quo bias.
Feedback Loop
The mechanism for immediately reflecting evaluations from users or self into the next iteration. Becomes the basis for decisions to break.
Minimum Viable Product (MVP)
An approach of releasing with minimal features and iterating improvements while breaking. The antithesis of perfectionism.
Refactoring
Rebuilding internal structure while preserving appearance and function. Applicable to both code and design.
Talk prompts
Ice breaker

Recall one moment in recent design work when you thought 'I don't want to break this'. What did you feel at that time, and why did you think that?

Deep dive

If you lived in a world where all your designs had no choice but to repeat making and breaking, what meaning or value would you find in the act of design?

Bridge

When the other person is passionately talking about their design, gently ask: 'If we deliberately broke this part, what new possibilities do you think would emerge?'

Further questions
  • In an era when AI instantly generates perfect designs, does the human role of 'breaking' still have meaning?
  • Does 'perfect design' exist, or should it always be created on the premise that it will be broken?
  • Does the 'sense of loss' or 'regret' after breaking become fuel for creativity, or is it merely pain?
  • Are we not using user test feedback as justification for 'breaking'? What is the balance between data and intuition?
  • Does traditional design education sufficiently teach 'the courage to break', or does it overemphasize 'completion' too much?
  • Why is the culture of 'don't touch what you've made once' so persistent in web design practice?