How Much Detail Should You Share?

A practical way to decide how much technical detail to share in industry conversations without oversimplifying your research. 

You’re preparing for a conversation with someone from industry.

You could explain the scientific background. The methodology matters. There are important assumptions. You have data supporting your conclusions. And there are probably a few caveats you would normally mention.

But how much of that does this audience actually need?

For researchers, this can be an uncomfortable question. Leaving information out can feel incomplete. Oversimplifying can feel like sacrificing technical credibility.

So the temptation is to include everything, just in case.

But the goal isn’t to squeeze everything you know into the time available.

The goal is to choose the communication strategy that fits the situation.

The Deep Dive Is a Strategy, Not the Default

Technical experts spend years learning how to explain and defend their work with rigor. In the research room, providing context, methodology, evidence, and qualification is often exactly what credibility requires.

So when the audience changes, it’s natural to bring the same communication strategy with you.

But a one-hour technical review with colleagues and a five-minute conversation with someone from industry are fundamentally different interactions.

One may call for considerable technical depth. The other probably doesn’t.

That doesn’t make either conversation more important or either audience more capable. They simply require different communication strategies.

Messaging mastery is the ability to say the right thing, at the right level, at the right time.

The question, then, isn’t simply How much detail should I share?

It’s What communication strategy does this situation require?

Start With Two Questions

The Commercialization Catalyst™ Messaging Strategy Matrix uses two factors to help you decide.

1. How much expertise does your audience have in your specific technical domain?

This isn’t about whether they’re smart or technically sophisticated. Someone can be an accomplished engineer, executive, investor, or scientist and still know very little about your particular field.

Think about their familiarity with your terminology, methods, assumptions, and the technical context surrounding your work.

2. How much time do you realistically have?

A conversation between conference sessions is different from a scheduled 30-minute meeting. Both are different from an hour-long technical review.

Put those two factors together, and four different messaging strategies emerge.

[I

Four Situations. Four Different Strategies.

Bottom-Line Snapshot

Lower domain expertise + less time

Imagine a tech scout approaches you between sessions at a conference.

This is not the moment for your research presentation in miniature.

Lead with the main takeaway. Use accessible language. Emphasize what matters and why it’s relevant. Give the other person enough to decide whether the conversation should continue.

The objective is clarity and relevance, not completeness.

Framed Explanation

Lower domain expertise + more time

Now imagine you’ve been invited to a 30-minute meeting with a company interested in your work.

You have room to explain more, but your audience may not share your technical foundation.

Help them understand the context, what is different about your approach, what you’ve learned, and why it matters before going deeper into technical specifics.

You aren’t avoiding the science. You’re creating the frame they need to understand it.

Expert Summary

Higher domain expertise + less time

Suppose a colleague familiar with your field stops at your poster and asks what you’re working on.

You don’t need to explain foundational concepts. Shared expertise lets you communicate more efficiently and use technical language that might slow down another audience.

But time is still limited.

Get to the technical point quickly.

Deep Dive

Higher domain expertise + more time

Now you’re in a one-hour project review with people who understand the domain.

Go deep.

Discuss methodology, assumptions, data, limitations, mechanisms, and technical tradeoffs as the conversation requires.

The Deep Dive isn’t a communication failure.

Using it when the situation doesn’t call for it is.

Selection Is Not Omission

This may be the hardest part.

If an important technical qualification doesn’t make it into the first few minutes, are you oversimplifying?

If you don’t explain the methodology, are you giving an incomplete picture?

If you translate a technical metric into something more familiar, are you dumbing down the science?

Not necessarily.

There is a difference between hiding information and sequencing information.

A detail that isn’t necessary in the first three minutes can come in minute ten. Methodology that doesn’t belong in an opening explanation can come up when someone asks how you reached the result. Supporting data can go into a follow-up document or a later technical discussion.

Selection is not omission. It is sequencing.

You aren’t deciding which parts of your work don’t matter.

You’re deciding what this audience needs first.

The rest of your expertise is still there when the conversation requires it.

Translation Isn’t Dumbing Down

Consider this technical statement:

“Our experimental results demonstrate a 37% reduction in thermal degradation compared to baseline materials under accelerated aging conditions, with statistically significant improvements in stability across repeated cycles.”

Now compare it with:

“In testing, this material lasted about 35% longer than current options when exposed to heat over time. That means it could reduce failures and maintenance in real-world applications where durability is critical.”

The second version doesn’t assume the audience is less intelligent.

It changes what the audience needs to know to understand the significance of the result.

The underlying technical evidence hasn’t disappeared. It is still available when the conversation requires it.

What changed is the entry point into that evidence.

That’s translation, not dumbing down.

Different Conversation. Different Strategy. Same Expertise.

Researchers don’t need to become less technical to communicate effectively outside their field. They need more than one communication strategy.

Sometimes the right choice is a Bottom-Line Snapshot. Sometimes it’s a Framed Explanation or an Expert Summary.

And sometimes the right answer really is the Deep Dive.

The skill is knowing which one the situation calls for.

Different conversation. Different strategy. Same expertise.