Product Reduction
Product Reduction
The pass gathers a zone so the load is visible, then keeps from the life being built and takes the high-cost objects first. What remains is chosen from that life, not from a trash list.
Minimalism as Systems Design holds volume-not-count and the concentrated-pass window this page does not restage.
Gather, then the week
A zone is chosen. The objects in it are gathered. The full amount becomes visible. What remains is decided. High-cost items leave. Each removal is read for why it failed. A future buying rule is written.
Scattered possessions hide the true ownership load. Gathering them into one place turns vague clutter into an explicit set of decisions. Duplicates become visible. Categories become clear. Empty floor appears. Decisions become concrete.
A short concentrated reduction outperforms an endless trickle. That is craft, not a trial. The burst: everything comes out, grouped by category; what remains is selected; a temporary “without it” box holds the rest; a week is lived without those objects; they are discarded if nothing breaks. The reduction period should also be minimal. The box is a reversible trial.
Easy items leave because they do not feel like losses. Large ones stay because they do.
The life being built
The center of gravity is the desired life, not a trash list.
- What life is under construction?
- Which behaviors does that life actually need?
- Which tools support those behaviors?
- Which objects fight those behaviors?
- Which objects belong to an imagined self?
An imagined self is the person the object was bought to certify, not the person who lives here. Wanting Less is the demand-side hinge: naming that motive is that page’s move; this page only asks the question.
Every discarded object is feedback.
- Why did it fail?
- Was it bought because it was on sale?
- Was it difficult to coordinate?
- Was it bought for a fantasy identity?
- Did it solve a fake problem?
- Did it require too much maintenance?
Kolbs Experiential Cycle is the loop after an attempt: what happened, how it felt and why, what rule that suggests, what changes next time.
The pass produces a buying rule, not a lighter pile.
What a pass can miss
Easy-item bias is the sharpest miss: small trash leaves, large burdens stay. The repair is high Ownership Cost first — the seven-cost table is how a large burden is priced.
Resale delay is the next miss. Exit Strategy For Objects holds the nine exits and the short-deadline rule.
Storage expansion hides the problem inside more containers. The repair is reduce before storing. Environment Design is what the lighter room is for: visible defaults, not visual emptiness. Storage-hiding is a named failure there too.
Guilt retention keeps the object as a memorial to the money. The repair is treat the object as feedback and update the buying rule. Keeping does not recover the money.
The practical close: one zone; everything gathered; clear floor; what remains selected from the desired life; high-ownership-cost first; each failure read; one future buying rule written.
The environment becomes lighter when what remains supports the intended life. The room after the pass has one rule attached.
Related
- Kolbs Experiential Cycle — discard as a cycle: what happened, how it felt and why, what rule that suggests, what changes next time.
- Ownership Cost — high-cost-first; the seven-cost table is how a large burden is priced.
- Exit Strategy For Objects — resale delay; the nine exits and the short-deadline rule live there.
- Minimalism as Systems Design — parent hub: volume-not-count, the concentrated-pass window, and the cluster map.
- Environment Design — what the lighter room is for: visible defaults, not visual emptiness.
- Wanting Less — objects bought to certify an imagined self; naming the motive is that page’s move.
Sources
- Kondo, M. The Life-Changing Magic of Tidying Up. Category-gathering as a tool class, not a required program.
- Sasaki, F. Goodbye, Things. Same tool class: the load becomes decidable once it is in one place.