Product Reduction
Product Reduction
Product Reduction is one pass over one zone. Every object in the zone is gathered into one place, so the full amount owned can be seen. What stays is chosen by asking what the life being built needs. The objects that cost the most to own are removed first. A list of things to throw away is not the starting point.
Minimalism as Systems Design is the parent page. It covers volume-not-count and the concentrated-pass window.
Core takeaways
- Gather everything in one zone into one place before deciding anything. Objects kept in many places hide how much is owned.
- Choose what stays by asking what the life being built needs. Do not start from a list of things to throw out.
- Remove the objects with the highest ownership cost first. Otherwise the small easy items go and the large burdens stay.
- Do the reduction in one short, concentrated period. A box marked “without it” and one week make each removal reversible.
- Treat every discarded object as feedback about a buying mistake. The main product of the pass is one written buying rule.
The steps of a pass
A pass has a fixed order. One zone is chosen. Every object in it is gathered. The full amount becomes visible. What stays is decided. The high-cost items leave. Each removed object is examined for why it failed. A rule for future buying is written.
Why gathering comes first
Possessions kept in many places hide the true amount owned. Gathering them into one place turns a vague sense of clutter into a set of specific decisions. Duplicates can be seen. The categories become clear. The floor is empty. Each decision is about one specific object.
One short period, with a box
A short, concentrated reduction gets more done than a long series of small removals. This is a craft rule. It is not itself a trial.
The short period runs like this. Everything comes out, grouped by category. What stays is selected. A temporary box marked “without it” holds everything else. The person lives one week without those objects. If nothing breaks in that week, the objects in the box are discarded. The reduction period itself should be as short as possible. The box makes each removal reversible, so the week is a trial that can be undone.
Easy items get removed because removing them does not feel like a loss. Large items stay because removing them does feel like a loss.
Deciding from the life being built
The decision about what stays starts from the life the person wants to live. It does not start from a list of things to throw out. The questions are these.
- What life is under construction?
- Which behaviors does that life actually need?
- Which tools support those behaviors?
- Which objects get in the way of those behaviors?
- Which objects belong to an imagined self?
An imagined self is the person an object was bought to certify. That person is not the one who lives there. During a pass the question is asked and the object is sorted. Wanting Less covers the demand side, and naming the motive behind the purchase is done on that page.
Reading each discarded object
Every discarded object is feedback about a purchase that failed. For each one, the questions are these.
- 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 that runs after an attempt: what happened, how it felt and why, what rule that suggests, what changes next time. A discard is run as that cycle.
The main product of a pass is one written buying rule. The smaller pile of objects is a side result.
Ways a pass goes wrong
Easy-item bias is the main miss. Small trash leaves and large burdens stay. The repair is to remove the objects with the highest Ownership Cost first. The seven-cost table on that page is how a large burden is priced.
Resale delay is the next miss. Exit Strategy For Objects covers the nine exits and the short-deadline rule.
Storage expansion hides the problem inside more containers. The repair is to reduce before storing anything. Environment Design describes what the lighter room is for: the right objects in view by default. An empty-looking room is not the goal. Hiding objects in storage is listed as a failure on that page as well.
Guilt retention is keeping an object because of the money that was spent on it. The repair is to treat the object as feedback and update the buying rule. Keeping the object does not get the money back.
The room after the pass
The whole pass in order: one zone; everything gathered; clear floor; what stays selected from the desired life; highest-ownership-cost objects first; each failure read; one future buying rule written.
The room gets lighter when what remains supports the intended life. After the pass, the room has one rule attached to it, the buying rule written from the discards.
How to practice this
- Pick one zone. Take every object out of it and group the objects by category in one place. Notice the duplicates and the empty floor that appear.
- Decide what stays by asking what the life you are building needs. Notice which objects were bought for an imagined self.
- Remove the objects with the highest ownership cost first. Notice whether you are only removing small items that do not feel like losses.
- Put everything else in a box marked “without it” and live one week without those objects. Notice whether anything breaks. If nothing breaks, discard the box.
- For each discarded object, write why it failed: sale, fantasy identity, fake problem, too much maintenance, coordination trouble. Write one buying rule from the answers. Notice that the rule is the main result of the pass.
- If you want to keep something because of what it cost, notice that keeping it does not recover the money. Treat it as feedback and update the buying rule.
Related pages
- Kolbs Experiential Cycle: the discard as a cycle. What happened, how it felt and why, what rule that suggests, what changes next time.
- Ownership Cost: remove high-cost objects 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 are on that page.
- Minimalism as Systems Design: the parent hub. It covers volume-not-count, the concentrated-pass window, and the cluster map.
- Environment Design: what the lighter room is for. The right objects in view by default, rather than an empty look.
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.