My thumb hit the green button before my brain knew I was awake. 5:08 AM. The room was that specific shade of pre-dawn gray that makes everything look like it’s underwater. A voice on the other end, raspy and impatient, asked for someone named Lenny. I told him he had the wrong number, but he didn’t hang up. He just sighed, a long, heavy sound that carried the weight of a 48-hour shift, and whispered, ‘Just tell me if the shipment moved.’ I stared at the ceiling for 18 seconds. I wasn’t Lenny, I didn’t have a shipment, and yet I felt this strange, crushing guilt that I couldn’t provide the simple ‘yes’ he needed to go to sleep.
This is how most interviews feel when you’re cornered by the demand for brevity. You are standing there with a complex, 1508-piece puzzle of a professional experience, and the person across the table-the one who supposedly values ‘deep dives’ and ‘ownership’-taps their watch and says, ‘Keep it high level, please.’ In that moment, you watch the real causal chain dissolve. You look at the intricate web of 28 different variables you managed, the 88 percent risk of failure you navigated, and the subtle interpersonal shifts that made the win possible, and you realize you have to lie. Not a malicious lie, but a lie of omission. You give them the polished, hollow shell of the story because they’ve told you they don’t have time for the meat.
The High-Level Lie vs. The Depth of Truth
The interviewer demands the skyline (summary), but the pilot’s value is in the 58 floors they navigated.
Promise of Efficiency
Proof of Systems Thinking
The Micro-Decisions: Where True Expertise Lives
I’ve spent the last 38 weeks thinking about why this happens. As a handwriting analyst, I, Drew P.-A., have spent a lifetime looking at the pressure applied to a page. People think handwriting analysis is about the shapes of letters, but it’s actually about the micro-decisions made in the space between those letters. It’s the tension in the ‘t-bar’ or the sudden, erratic loop of a ‘g.’ If a client asks me for a summary, I could say, ‘You’re stressed.’ But that’s useless. The value is in the ‘why’-it’s in the 8 specific indicators of repressed anxiety and the 18 instances of over-compensation in their upward strokes. Yet, even in my line of work, the pressure to ‘just get to the point’ is relentless.
These details are the structure of performance.
We are taught that conciseness is a virtue, a sign of a sharp mind. And in some contexts, it is. If the building is on fire, don’t tell me about the thermal conductivity of the drywall; tell me where the exit is. But in the context of a leadership interview or a strategic planning session, brevity often acts as a cloak for superficiality. When an interviewer asks a candidate to simplify a multi-layered turnaround project, they are effectively asking the candidate to stop being a systems thinker. They are asking for a fairy tale where ‘Action A’ led directly to ‘Result B,’ ignoring the 58 messy steps in between that actually prove the candidate knows what they are doing.
Terrified of Being Seen
I remember analyzing a sample from a high-level executive who was known for her ‘concise’ communication style. Her handwriting was microscopic, almost illegible. To a layperson, it looked efficient. To me, it looked like a woman who was terrified of being seen. Every stroke was a retreat. She had been so conditioned to provide the ‘bottom line’ that she had lost the ability to articulate the process. When I pointed out that her 28-millimeter margins were unnaturally consistent, she admitted she felt like she was constantly performing a version of herself that didn’t have any ‘unnecessary’ thoughts.
This is the management failure of our era. We want the complexity handled, but we don’t want to hear about it. We want the 1008-page report summarized into 8 bullet points, and then we wonder why the subsequent strategy fails to account for market volatility. It’s because the volatility was in the pages we didn’t read. It was in the nuance we told the analyst to cut. We are effectively training our best people to hide the very evidence of their expertise.
“
The tragedy of the summary is that it assumes the result is more important than the method.
– Narrative Observation
Forcing the Shortcut
During a recent session, I watched a candidate try to explain a technical failure in a data center. He started to describe the cooling system’s 88-degree threshold and how the humidity had spiked due to a localized weather event. The interviewer interrupted: ‘Just tell us how you fixed it.’ The candidate paused. The ‘fix’ was a combination of 18 different manual overrides and a 48-minute negotiation with a third-party vendor who didn’t want to honor their SLA. By being forced to skip to the end, the candidate looked like he just got lucky. The ‘high-level’ version made him sound like a passenger, not a pilot.
The Soundbite Candidate
Minutes Skipped
I’m a firm believer in the ‘yes, and’ approach to this problem. When someone asks for the high-level view, you give it to them in 28 words or less, and then you immediately pivot to the danger of that simplification. You have to be the one to advocate for the context. You have to say, ‘I can give you the summary, but the reason this succeeded was actually in a detail that most people miss.’ You have to invite them into the 58th floor of the building instead of just showing them the postcard of the skyline.
The Paradox of Executive Communication
In the high-stakes environment of executive coaching and preparation, companies like
Day One Careers often see candidates wrestling with this exact demon: the fear that if they don’t strip the story to its bones, they’ll be seen as rambling, even though the marrow is where the value lives. It is a delicate dance. You have to prove you can be concise to show you respect their time, but you have to provide depth to show you can handle their problems. If you only do the former, you’re just a narrator. If you only do the latter, you’re a professor. You need to be both.
The Required Equilibrium
Concise
Respect Time (Narrator)
Depth
Handle Problems (Professor)
I think back to that 5:08 AM phone call. I eventually told the man, ‘I’m not Lenny, but if the shipment is like anything else in this world, it’s stuck in a port because someone tried to save 38 minutes by skipping a manifest check.’ There was a long silence. Then he said, ‘That’s exactly what happened.’ He didn’t need a summary; he needed someone to acknowledge that the details were the reason he was awake.
We often mistake ‘brevity’ for ‘clarity.’ They are not the same thing.
Substance Lost in Speed
We often mistake ‘brevity’ for ‘clarity.’ They are not the same thing. Clarity is the result of deep understanding, whereas brevity is often just a lack of space. You can be clear and still take 18 minutes to explain a concept. You can be brief and leave everyone in the room more confused than when you started. In my handwriting work, I see it all the time-people who write with huge, sweeping letters to appear confident, but the ink is thin. There’s no pressure. There’s no substance. They are taking up 88 percent of the page saying nothing.
“
I sacrificed truth for speed, and in doing so, I lost the client’s trust.
– Analyst’s Admission
I’ve made the mistake of over-simplifying my own work before. I once told a client their signature indicated a ‘strong ego’ because it was 18 percent larger than their body text. I thought I was being efficient. The client walked away feeling insulted. If I had taken the time to explain the 8 different factors that contribute to signature size-the social anxiety, the compensatory drive, the specific letter-to-space ratio-they would have understood it was a nuanced observation, not a judgment. I sacrificed truth for speed, and in doing so, I lost the client’s trust.
Management wants complexity handled, just not explained in ways that slow the meeting down. It’s a paradox that produces ‘the polished but misleading sentence.’ We see it in quarterly earnings calls where 880 million dollars in losses are attributed to ‘market headwinds.’ What headwinds? Which of the 28 specific economic indicators failed to align? When we accept the summary, we accept the ignorance that comes with it.
Don’t Apologize for the Blueprint
If you find yourself in an interview, and you feel the urge to cut the exact information that makes your answer make sense, don’t. Or rather, don’t do it without a disclaimer. Tell them that the 8-minute version of the story contains the actual blueprint for how you solve problems, while the 48-second version is just a result they could have read on your resume. Force them to choose. Most of the time, if they are the kind of leader you actually want to work for, they will choose the 8 minutes. They will realize that the ‘causal chain’ is the only thing that proves you aren’t just a lucky bystander in your own career.
By the time I finally got back to sleep after the 5:08 AM call, the sun was up. The ‘gray’ was gone, replaced by a harsh, clear light that showed every speck of dust on my nightstand. The world was back in high-resolution. I realized then that I didn’t want the high-level version of my day. I wanted the 158-item to-do list. I wanted the 8 different conversations that would inevitably go off the rails. I wanted the mess. Because the mess is where the work happens. The mess is where the 238 small decisions live that eventually add up to a ‘successful’ year.
Stop apologizing for the context. Stop cutting the marrow out of your stories just to fit into a 48-second soundbite. If your work required a system to function, your explanation requires a system to be understood. If they can’t handle the 18 moving parts of your greatest achievement, they probably won’t be able to handle you when the shipment actually stops moving at 5:08 AM.
What are you actually losing when you ‘get to the point’ before you’ve established the path?