Weekend Reflections #6 | The Daughter Test

[Views are my own].

She was eight and loved to sing. I had just bought her a vocal processor and asked her to help me connect the gear.

She looked at the cables. Then at the processor. Then at me.

"Which one goes where?"

I paused. Because I've done this a hundred times had never needed to explain it?

Mic in. Signal out. Amp last. Obvious.

Except it wasn’t obvious. It was assumed.

I assumed she understood signal chain. That sound flows one way. That each box has a role. That a cable is not just a cable.

I had a mental model of how sound moves through a room. She didn't.

And my mental model was invisible to me precisely because it was mine.

She didn't let me get away with it. She never does.

"Why?" "What does that mean?" "But you said two minutes ago..."

Every time I gave her instructions, she forced me to be precise. To explain the intent, not just the action. To define what I was calling obvious. To give a reason for every single thing I was asking.

I found it frustrating. Then clarifying. Then I realized: this is what good briefing looks like.

We don't share our mental models. We share our conclusions.

When you brief a team member, you hand them the output of your thinking, not the thinking itself. The steps you skip aren't obvious. They're yours. Part of a workflow you built over years. A set of defaults that feel like common sense because they became second nature.

Your direct report doesn't have that workflow. Neither does your stakeholder. Neither does the consultant you just onboarded.

And neither does your AI agent.

This is where it gets interesting. In leadership, there's usually a correction mechanism. People ask clarifying questions. They read between the lines. They bring their own experience to fill the gaps you left. The social intelligence of a team compensates for the ambiguity in your brief.

Agents don't do that. They execute on what you said, not what you meant. The gap doesn't get smoothed over. It becomes a bug.

The first time I briefed an agent the way I brief people, I got back a confident, well-structured wrong answer.

Same gap. No daughter to ask the clarifying question.

Building agents taught me to spot the assumptions I was making everywhere else.

The Daughter Test

Before you brief anyone, whether a direct report, a team, or an AI, run it through The Daughter Test.

Imagine explaining it to an eight-year-old who will challenge every assumption, refuse to act without the full picture, and hold you accountable to every word.

Would she be able to execute?

If not, the brief isn't ready.

I now check for five things before I brief someone:

Start with intent. Not the task. The why. What are you trying to achieve? What would good look like? Most briefs open with the action and skip the purpose entirely.

Define your terms. Every word that feels universal probably isn't. What do you mean by "quality"? What counts as "done"? If you're using a metric, explain what it measures and what it doesn't.

Explain why each piece of context matters. Don't just provide context. Explain how it should change the approach. Context without direction is noise.

Name your references explicitly. Phrases like "as we discussed", "based on the previous version", and "like last time" are assumption traps. Name the file, the decision, the date. Make it findable.

Add guardrails. What is explicitly out of scope? What should they not do? The absence of a constraint is often read as permission.

Every assumption you unconsciously embed in a brief becomes an ambiguity point.

In leadership, ambiguity is expensive. It costs rework, misalignment, trust. In agentic systems, ambiguity is a failure mode. It produces confident, well-executed wrong answers.

My daughter forced me to get precise. I was frustrated. She was right.

The Daughter Test isn't about dumbing things down. It's about removing the invisible scaffolding of your own mental model and building the brief from the ground up.

For someone who doesn't share your workflow. Who doesn't know your defaults. Who can't read between the lines.

What assumption are you still handing out like a cable, expecting everyone to know where it goes?