What My Daughter's "No" Taught Me About Boundaries

My daughter is almost two, and she has never once tried to win me over.

When she doesn't want to put her shoes on, she doesn't build a case. She doesn't offer a compromise. She doesn't soften it with "but maybe later." She just says no, plants herself on the floor, and waits for the world to catch up to her position.

It is, genuinely, one of the most clarifying things I've ever watched up close.

Because here's what I've spent most of my adult life doing: negotiating things that were never actually up for negotiation. Saying "let me think about it" when the answer was already no. Agreeing to "just a quick call" because saying no outright felt rude. Softening a boundary into a suggestion, then watching someone treat the suggestion as an opening bid.

My daughter doesn't do any of that - not because she's been taught some framework about boundaries, but because she hasn't yet learned that you're supposed to make people feel okay about your "no." That's not a toddler problem. That's a skill most adults have been trained out of.

The cost of a negotiable "no"

When I say my calendar isn't a democracy, I mean something specific: a boundary that can be argued with isn't a boundary, it's an opening position. The moment you frame a "no" as something the other person might be able to talk you out of, you've already told them it's negotiable. You've just outsourced the decision to whoever pushes hardest.

Watching my daughter, I realised how much of my own "no" had quietly become performance. Not a decision, but a pitch for permission to have a decision.

What I'm trying to unlearn

There's something underneath her "no" worth keeping: she has decided, the decision is made, and she's not going to spend energy justifying it to make someone else feel better about it.

At work, I used to think a good boundary needed a good reason - that "no" only worked if it came with an explanation solid enough that the other person couldn't push back. What I'm relearning, watching a two-year-old, is that the explanation is often the weak point. It's the crack people pry open. "I can't do lunch meetings" is a boundary. "I can't do lunch meetings because I need to eat and reset, but if it's really important maybe..." is a negotiation, and you've already lost it before anyone's said a word.

This isn't about going cold on people - it's about not confusing context with negotiation. You can still tell someone why, if it helps them. The line is whether the why is information or an opening.

The one question worth asking

Here's the practical version of all this. Before you respond to a request, ask yourself one question: is this actually a decision, or did I already decide?