"What should I wear today" is exhausting not because your wardrobe is small, but because it is not one decision. You are making four stacked ones at once: where am I today, what will the weather do, do these two pieces work together, and did I wear this recently. Asked simultaneously, none of them resolves and the decision stalls.
This piece is about the order in which those four should be answered. The order is not a preference. Each input eliminates a differently sized slice of your wardrobe, and if you leave the biggest eliminator for last you spend your thinking on pieces that were never candidates.
Why isn't the morning decision a single decision?
Because you are answering four separate questions at once and three of them depend on a fourth. Whether a jacket works depends on where you are going, and where you are going determines how much the weather matters. Asking dependent questions in parallel means trying to solve each one before its input exists.
The time spent in front of the wardrobe confirms it: you look at pieces, build an outfit, then say "but it is cold out" and start over. What you lose is not clothing, it is the same decision made twice.
Boundary: the stall grows with wardrobe size but does not come from it. With ten pieces and an undefined context, you get the same stall.
What does each input eliminate?
Inputs are ordered by eliminating power; the strongest goes first. The matrix below shows what each of the four does and why it sits where it does.
| Order | Input | What it eliminates | Why here |
|---|---|---|---|
| 1 | The day's context | Every category that does not belong to today | Removes the widest slice in one move; the other three are only meaningful on what remains |
| 2 | Weather | Pieces in the remaining set that will leave you cold or overheated | Comes after context: the same temperature needs different pieces at a desk and on a site |
| 3 | An anchor piece | Everything incompatible with the anchor | Turns an open search into a closed one; choosing an anchor before context and weather is an early commitment |
| 4 | Repetition | What you wore recently | The weakest eliminator, so it goes last: after the first three, the remaining set is already small |
The fourth input eliminates nothing on most mornings. It stays on the list because the one case it does catch — "I wore this yesterday" — is the case that breaks the decision at the latest possible moment.
Boundary: this order assumes you own pieces in every category. If a category is missing, the context input does not narrow, it blocks outright — and then the problem is not the decision, it is the inventory.
How does weather actually enter the decision?
Temperature alone is not enough; the feels-like value, humidity, wind and the condition are weighed together. Veedrobe's weather endpoint carries exactly these five fields: temperature, feels-like, humidity, wind speed and condition. Read together, "12 degrees" and "windy at 12 degrees" become two different decisions.
The practical consequence: a sharp but cold choice turns into a decision you regret all day, and the next morning you skip that piece without evaluating it. A bad weather call costs you more than today — it costs that piece its future.
Boundary: if you are indoors all day the weight of the weather input drops and the order effectively becomes three. Lowering its weight is right; dropping it entirely is not, because the commute is still outside.
Why does starting from one piece speed things up?
Because it converts an open search into a closed one. "What should I wear" is an unbounded question; "what goes with this shirt" is a finite one. The answer set of the second is not your whole wardrobe, only the pieces compatible with that shirt.
Veedrobe has a direct equivalent: you can pin one piece and have the rest of the outfit built around it. The decision does not start from zero, it grows from an anchor.
Boundary: an anchor only helps when it is a piece you actually want to wear. A randomly chosen anchor does not narrow the search, it narrows it in the wrong direction — and a search narrowed the wrong way is slower than a wide one.
How many alternatives are enough?
Two. One main choice and one alternative covers most mornings; past the third option what you gain is not decision quality but decision time.
Unlimited options create decision fatigue, and fatigue breaks the final step even when the first three inputs were applied correctly. So generating alternatives should be bounded: in Veedrobe you can ask for an alternative when a suggestion does not land, or swap just one piece. The second option reopens only the part you are stuck on, not the whole decision.
Boundary: the two-alternative rule is for everyday decisions. For a rare, high-stakes day, looking at more is reasonable; the time lost there is a cost you have already accepted.
What does saving a decision buy the next morning?
Saving an outfit that worked lets the same context skip all four inputs next time. The record is not an archive, it is a shortcut.
Veedrobe closes this loop with feedback: you can like a suggestion, skip it, or say it should never be suggested again. Each signal becomes an input to the next suggestion, so every morning you decide shortens the following one slightly.
Boundary: a saved outfit is a shortcut only while the context repeats. When the season turns, the same outfit may no longer hold in the same context; the record does not remove the decision, it moves its starting point.
How does Veedrobe automate this order?
By applying the same four inputs in the same order. It reads the context and the weather, builds a suggestion from the actual pieces in your wardrobe, and explains why it chose that outfit — the explanation matters, because a suggestion whose reasoning you cannot see is not something you can evaluate, only accept or reject.
The saving and feedback side belongs to the same loop: what you liked, skipped and wore becomes the input to the next morning.
This piece covers the order of the decision; how the pieces inside it fit together is a separate subject. For the colour side, three simple rules of colour harmony; for building a wardrobe that yields many outfits from few pieces, the capsule wardrobe logic continues from here.
Expert note: Apply these four inputs by hand one morning and time the decision. The stall may come from an unclear context rather than wardrobe size. Make "where will I be today?" explicit first, then compare how many options remain.