Reveal The Technical Details of a Debug on Demand: Say Less, Land More
Most technical people know how to reveal technical details of a debug on demand in theory, and dump all of them in practice. We go deep to find the real cause of a problem—and then we relay the whole journey, every twist and detail, to someone who just needed the headline. Last week I wrote about finding the real cause and leading with the bottom line using BLUF (Bottom Line Up Front). This week is about the harder half: everything you deliberately leave out, and reveal only when it’s asked for.
Because BLUF only works if you can hold everything else back.
Knowing the details isn’t the same as sharing them
As technical folks, we have to know the details. You can’t triage or debug without going deep—down to the query, the component, or the manufacturing step. But knowing the details and sharing them are two different jobs.
Once you’ve led with the bottom line, the rest of what you know isn’t discarded. It’s queued. You reveal it on demand, as the questions come.
Knowing the details and sharing them are two different jobs.
One caveat: this is for time-limited audiences
This isn’t a blanket rule. If I’m bringing a team up to speed in the middle of an incident, I’ll gladly spend five or ten minutes on the full context—what happened, why, what we already tried and what failed, and where we’re headed next. That audience needs the details to do their part.
Why holding back works: assumed credibility
Leading with a clean ask trades on assumed credibility. When you open with the bottom line and skip the details, you’re relying on the room to assume you know them—that you did the work, and you’re credible.
That assumption is what makes withholding acceptable. So it’s exactly why you have to actually know the details. And if you don’t? That’s okay—but say so, and either point to the person who does or explain how you’ll get the answer. That’s what preserves the trust the whole approach depends on.
Watch it work: my $30K water heater
Here’s the bottom line from my recent water-heater saga:
Our tankless water heater has failed. A full fix runs about $30,000—but there may be a cheaper path: replace the tankless water heater first to deliver hot water asap. I’d like the go-ahead to try that first before we commit to the full fix. Can we decide by Friday?
That gives the decision-maker the problem, the ask, and the deadline. Now they might ask: why did it take six years to break down? That’s when the detail earns its place:
Our water usage climbed as the household grew from three people to five. Laundry went from one or two loads a week to as many as three a day, and the dishwasher sometimes runs twice. Scale built up faster than it otherwise would have—and we didn’t know the system needed to be flushed regularly, because that maintenance requirement was never explained to us.
It’s a useful explanation because it answers a question the other person actually asked. Lead with all of it, and you risk losing the room before you reach the decision.
Waiting for the question also keeps you from sounding defensive. Instead of opening with everything you might have done differently, you can explain how the system changed over time—and surface the missing information that reframes the story: we were told the tankless system would “just work,” with no mention of maintenance. That detail matters. It just doesn’t need to come first.
Lead with all of it, and you lose the room before you reach the decision.
What a room full of engineers caught
Last Friday I ran a Femgineer Forum on communicating complexity clearly and concisely. First, a thank-you to everyone who practiced with something they were actually working on—putting your work in front of a group and letting people pull it apart is the hard part.
Narain volunteered to go first. His car battery had died less than two years after he bought it, and he needed the dealer to honor the warranty—fast. But the first version included the age of the car, a recent oil change, a fluid leak, two mechanics, and all the phone calls in between. By the time he reached what he actually needed, we were lost in the plot.
Reworked, it opened with the ask:
My battery is dead. I bought it less than two years ago, so it’s still under warranty, and my mechanic sent me to you to honor it. I need it replaced today.
Problem. Ask. Deadline. Everything else is context he can keep ready in case the dealer asks.
As everyone worked through their examples, the group kept catching the same patterns:
- Wishy-washy language or a story that wandered.
- An unclear ask—lots of context, but no crisp “Here’s what I need.”
- No deadline, allowing “yes” to quietly become “Let me think about it.”
- A history lesson that started with what happened years ago instead of why the situation matters now.
- Too many details up front, leaving no room for the other person to ask questions.
That last one connects directly to the water heater. The fix isn’t to know less. It’s to prepare your Q&A ahead of time. Anticipate the questions. Have the answers ready. Then resist the urge to offer them until they’re asked. That’s the discipline that keeps everyone out of the rabbit hole.
It can feel curt—and that’s okay
One honest thing about BLUF: it can feel curt. If you’re naturally warm and effusive, leading with the bare bottom line can feel unnatural, and the instinct is to soften it.
Sometimes that instinct is right. Not every message needs to be tight, and depending on your audience and the moment, warmth is exactly what’s called for. But sometimes short and direct is the clearest, kindest thing you can do. The real skill isn’t always being terse—it’s sensing which moment you’re in.
The takeaway
Knowing every detail is your job. Deciding when to reveal it is the skill. Lead with the bottom line, hold the rest, and let the questions pull the details out of you.
So try this: think about the last long explanation you gave someone. Which two sentences contained the actual bottom line? Which details could you have held for the Q&A?
If you want to practice this judgment for real—including when to lead with BLUF and when a moment calls for something warmer—my Confident Communicator Course returns this fall, a six-week cohort running October 9 through November 13.
Related: last week’s issue on the comprehension gap and BLUF. Origin of the framework.
