7 AM. Closet open. He stands there for three minutes. "I don't know." The Iyengar & Lepper jam study (2000) — 24 flavors, 6 flavors, a 10x gap in who actually bought any — explains exactly what my kid was doing. Once I started offering two options instead of "anything," he moved in three seconds. Same logic shows up in our Todo apps and in how I scope work projects.
Morning. "What do you want to wear today?"
He stares at the closet. Three minutes. Five. "I don't know."
"Just pick something." "I can't." "Use your head." "I AM, I just don't know!"
He cries, usually. Or I lose it. Pick one.
Every parenting book I read says let them choose, it builds autonomy. But the more options I give him, the less he moves. What is this.
Turns out there's a famous psychology study that nails exactly what's happening.
Sheena Iyengar and Mark Lepper, 20001. They set up a tasting table at a grocery store and switched the number of jams on display:
More variety pulls more eyeballs. That part holds. But the conversion gap is roughly 10x. Too many options, and people walk away empty-handed.
This is the paradox of choice.
A kid asked "what do you want to wear?" with the whole closet open in front of him is in the exact same state as an adult frozen in front of 24 jars of jam.
Too many options. Too many evaluation axes (warm? itchy? matches the pants? did I wear this yesterday?). The "I don't know" isn't a stall tactic. From what I can tell with my kid, he genuinely can't process it.
"Use your head" doesn't help when the system is overloaded.
So I tried something different.
Same kid. Like a switch flipped.
Dinner is the same.
Three seconds.
He wasn't being indecisive. I was the one offering choices wrong.
The Todo apps we build at Lyco run on the same "narrow the field" idea, even though I didn't sit down and theorize it that way at first.
TodoGacha doesn't ask the kid "what next?" — it pulls one task at random. We took the decision away from him. And he moves.
TodoBingo lays the tasks out on a 3×3 grid. Nine cells, fixed. The size of the choice is visible. He can see where he is in the day.
I'm not against "let kids be free." I want to raise him that way too. But freedom and choosing are not the same thing. Choosing is heavy cognitive work, and from what I can see, my kid often isn't built for it yet.
Stacking the Iyengar study next to my kid's morning closet is one of the lenses we used when we were making design calls for the Todo apps at Lyco (TodoGacha, TodoBingo).
And honestly, the same lens shows up at work. When I'm doing requirements on a software project, I call it "the unfreedom of too many options." The more configurable a system is, the more confused the user gets — and the more surface area we have to test and support. Nobody wins. "Can do anything" ends up being the same as "didn't build anything." Building something means deciding what it does and deciding what it doesn't do, at the same time.
The three things that stuck:
The hidden rule is the last part: don't second-guess his pick after he makes it. If I say "are you sure? the other one might be better," I've just invalidated the whole exercise. The choice doesn't count anymore.
For a kid to feel like he chose, the parent has to do the narrowing before the question gets asked.
Two options: he picks. He owns the pick.
Twenty-four options: even after he picks (if he picks at all), there's still a "but maybe the other one" tail dragging behind him.
"You can have whatever you want" sounds generous. For a six-year-old, it's a weight.
"What do you want for dinner?"
"I don't care, whatever's fine."
That one's the worst, isn't it.