We think we’re asking for data, but we’re often asking for emotional regulation.
💚 Welcome to the weekly newsletter for ambitious leaders staying sharp and staying human in the age of AI.
Every edition is:
Curated: One standout piece I read, watched, or listened to this week + my riff on what it means for you
Counterintuitive: A surprising angle that shifts how you see your day-to-day.
Cross-pollinated: Draws unexpected connections between the worlds I live in—sales, sports, and Stanford.
📬 If you like this, share it to a fellow leader. It’s the ultimate low-lift way to stay connected to the people you care about when your calendar has zero room for 30-minute Zoom catch ups.
The Problem
You’re right in the middle of deep work when the anxious Slack spray begins.
Your CEO fires off a random, tactical ping: "Where are we on headcount for the engineering team?"
You’re busy, so you fire back a literal answer: "Three final rounds tomorrow." Box checked. You go back to your day.
But two days later, the CEO is back and nit-picking your latest sprint. Everyone is frustrated.
Why? Because you answered the headcount question they asked, not the pressure they were actually feeling. Their underlying panic wasn't about your recruiting funnel. It was about the fact that the current team is working nights and weekends, and they are terrified that their best engineer is going to quit from burnout.
We often treat communication like a transactional vending machine. Question goes in, data comes out. But when all we do is exchange surface-level data, we strip away the one thing AI cannot provide: emotional context.
The Discovery
Wes Kao is great. Not only is she an incredible teacher-entrepreneur-writer, but I really enjoy chatting coaching and life with her. She recently shared her brilliant piece1 on finding "the question behind the question" and her premise is spot on: people rarely ask what they actually want to know.
I saw this every day in enterprise sales. A prospect asks, "Is your platform SOC-2 compliant?" If you cheerfully reply, "Why yes, we are!" you’ve missed the point. The question beneath the question is almost always steeped in stress. What they are actually asking is, "Is my CISO going to block this deal at the 11th hour and make me look like an idiot for championing it?"
We know we have to anticipate the question beneath the questions we receive. But let's flip the mirror:
What about the questions we ask our own teams?
When we’re stressed and fire off rapid-fire tactical questions, we think we are asking for data. We aren’t. What’s underneath our questions is often an ask for emotional regulation.
But, when you fire off a ping without naming your underlying pressure, your team can smell your anxiety, but they are only allowed to respond to your data request. You stay stressed, and they are forced to play the guessing game to figure out what is actually driving the urgency.
One of the core principles of Interpersonal Dynamics, a Stanford GSB course I facilitate on managing conflict, is a neuroscience concept called Affect Labeling. In other words, naming your emotions. Dr. Matthew Lieberman at UCLA ran fMRI studies2 proving that explicitly naming an emotion or stressor out loud physically decreases activity in the amygdala (your brain's alarm system) and increases activity in the prefrontal cortex (your logic center). In the course we invite students to name their emotions, and in the process self-regulate so they can work through a miscommunication with more clarity to ask for what they want.
You can do this, too.
The Experiment
This week, before you hit send on a "quick question" to your team, run it through this filter:
1. Affect label your own pressure.
Are you asking about the timeline because you actually care about the Gantt chart? Or are you asking because the board meeting is next week and you are terrified you have nothing shiny to show them? Pinpoint the stressor for yourself first to quiet your own amygdala.
2. Ask for what you actually need.
When you get clear on the feeling behind your stress, you can more easily stop making your team play detective. You don’t have to confess your existential dread, but you do need to give them the context behind the ask.
Change your ping from: "Where are we on the Q3 rollout?"
To: "I have a board prep meeting tomorrow and I want to make sure our product narrative is bulletproof. Can you give me two bullets on the Q3 rollout that show we are maintaining momentum?"
When you share the actual, emotional context behind your ask, you are giving them a reason to care. An emotional string that ties you two together. A response of, Oh big meeting, I know those nerves. Let me help.
The Takeaway
I spend my days thinking about how self-awareness is the ultimate leadership skill, how to teach it, and how to use it. I can’t tell you the number of times I’ve found myself in a stress spin and just stopped and said out loud: What am I actually asking for here? What is the feeling? (often with my hands over my eyes to help me actually pinpoint the emotion) You already know that other people don’t always ask for what they really want. What you can do as a leader is to try your best to be the person who does.
Join the community of leaders staying sharp
and saying human in the age of AI.
