Is It Okay to Let Kids Make Bad Decisions When They Know It’s Wrong?
It was 10:37 pm last Saturday when I passed my 11-year-old Leo’s bedroom on my way to lock the front door. A strip of blue screen light seeped under the door, and I knocked once. The light cut out, and he mumbled “come in” from under the covers. I pushed the door open, and there he was, half-propped up on pillows, his phone shoved under his sheets like a contraband candy bar. “I know,” he said before I could speak. “I know I have the soccer game tomorrow. I just need one more episode. Please.”
I’d already reminded him twice that day: we agreed he’d charge his phone outside his room on game nights. He’d nodded, said he got it, that he knew staying up late would leave him dragging for kickoff at 9 am. So that question was hanging in the air right there: he knows it’s bad. Is it okay to let him do it anyway?
I used to take the phone every single time. When Leo was 7, he wanted to wear flip-flops to our hour-long hike in 40-degree weather, even though he knew his feet would get cold and blister. I made him put on boots, and he complained the whole way. A year later, he forgot his lunch on the counter three Tuesdays in a row, and I drove it to school every time, because I didn’t want him going hungry. I thought my job was to keep him from making bad calls, to save him from the frustration and disappointment that came with messing up.
That night, I leaned against the doorframe and thought about the cheap Lego knockoff he’d bought with his birthday money two months earlier. His best friend had gotten one, and it fell apart halfway through building. I showed Leo the reviews online, told him it was almost certainly half the number of pieces it said, and the plastic would break the first time he knocked it over. He nodded, said he knew, but it was half the price of the real one, and he wanted it anyway. I didn’t stop him. He bought it, brought it home, and it fell apart an hour after he finished building. He sat on his floor, glared at the pile of cracked plastic, and threw it in the trash. He didn’t ask me to replace it. He didn’t cry. He just said “that was dumb” and went back to playing his Switch.
So that night, I nodded at Leo. “Okay,” I said. “Keep the volume down, and set your alarm like we planned. Just so you know: if you’re too tired to play the whole game tomorrow, I’m not talking to coach about extra time. That’s how this goes.” He blinked, like he expected me to argue, then nodded. “Got it,” he said. I closed the door and went to bed, where I laid awake for 20 minutes worrying I was being too lax, that I was letting him fail for no reason.
The next morning went exactly how we both expected it to. He hit snooze twice, stumbled to the kitchen 10 minutes before we had to leave, couldn’t find his soccer cleats for 15 minutes, and missed the entire pre-game warmup. Coach started him on the bench, and he only played 10 minutes in the second half. On the drive home, he stared out the window, picking at a granola bar wrapper, and finally mumbled “I shouldn’t have stayed up. That sucked.” I didn’t say I told you so. I just said “Yeah, that does sound really frustrating.”
That’s the thing no one tells you about letting kids make bad decisions they already know are wrong: the consequence is usually lesson enough. You don’t have to add extra punishment, or a lecture, or a smug I told you so. All of that just shifts the focus from their bad choice to how mean you are, and they miss the whole point.
The concrete rule I use now, that I’ve started telling other parents when they ask me about this, is first check if the consequence is dangerous or permanent. If your 8-year-old wants to pet a strange stray dog, or jump off the roof of the play set, you stop them immediately. But almost all the bad decisions kids make when they’re young fall into a safe category: staying up late, wasting allowance on a bad toy, forgetting a homework assignment, wearing the wrong clothes for the weather. These are all small mistakes that don’t leave a lasting mark, but they teach far more than any lecture ever can.
Second, state the consequence out loud before they decide, so there’s no surprise and no gotcha. You don’t have to scold. Just say what’s going to happen, like I did with Leo and the soccer game: “If you stay up late, you’ll be tired, and you might not get much play time. That’s what will happen.” No extra stuff.
Third, hold back the I told you so after. Just let them feel the bad result, and let them connect it to their own choice. When they say it was dumb, just agree that it sucks. That’s it.
I still don’t get this right every time. Last month, I stepped in and made Leo bring an extra jacket to a field trip, even though he said he was fine and he’d be hot. He complained the whole time, and I ended up carrying it for him. Sometimes I still catch myself driving his forgotten lunch to school when I should let him buy one from the cafeteria. It’s hard to sit back and watch your kid mess up, even when it’s small.
Last night, Leo showed me a cheap skateboard he found online. It’s a third the price of the solid one we looked at the sporting goods store last week. He said he knows the wheels might wear out in a month, but it’s all he can afford with his current allowance, and he wants it anyway. I told him that’s his call. If it breaks, we can keep saving for the better one next time. He hasn’t ordered it yet. We’ll see what happens. I’m still learning, too.
Please indicate: Thinking In Educating » Is It Okay to Let Kids Make Bad Decisions When They Know It’s Wrong