Stories from 30,000 Feet: Using Narrative to Share Technical Data
- Scriptorium Team
- Apr 22
- 4 min read
Whoever said, “The data speaks for itself!” never had to explain a technical problem to a room full of executives.
Data is objective, precise, and undeniable. It’s why engineers and technicians like to lead with data when explaining their work. However, non-specialist audiences don’t have the same context; instead, they’re thinking in terms of risk, hassle, opportunities, and wins. If you work in a technical field, you and your team no doubt have a wealth of specialist knowledge. But even your keenest insights can be ignored if the data isn’t humanized.
For example, let’s say an engineer has discovered an inefficient workflow that is reducing productivity. They have the spreadsheets to prove it! They inform leadership that the problem can be fixed with new equipment and training... but for some reason, leadership is unmoved.
Data is powerful, but only when it’s framed in a way that people can relate to. And the most tried-and-true shortcut to understanding? Storytelling.
Stories create emotional relevance to your data. They use metaphor and universal experiences to reduce the cognitive load of your complex information, making it easier to absorb. Non-specialist audiences want the view from 30,000 feet: they don't want to be in the weeds of technical data but rather understand the landscape and why they should go there.
Our example engineer discovered an important problem and presented the data to leadership. Leadership sees that the engineer wants expensive new equipment, which also requires employee training. That sounds like a big investment, so if things are already working, the problem must not be a priority.
The engineer might have better luck if they pitched their request with a narrative. Here are some examples of storytelling frameworks that can be used to translate technical data.
1. The Journalistic Approach
This is the simplest structure, best for scenarios where you need to keep your case brief. It ignores the sequence of events that led up to the discovery, and puts the most critical data point first: “Why does this matter?” Your research serves as supporting evidence.
Example: “We’ll save thousands per year preventing costly engine failures by changing our diagnostic process.”
For comparison, this statement would be the alternative to “We noticed a lot of trucks were out of commission. It turns out they were poorly maintained. So, we updated our diagnostics to incorporate additional sensor inputs, revised fault‑code logic, and provided a new review step for technicians.”
2. Problem > Solution > Impact
This is a versatile framework that works well with technical scenarios. Explain the problem, present a solution, and then describe how much better life will be with that solution in place. People are great at the first step, but it’s the third step that sways your audience.
Example: “Backed-up traffic at our mining site slows down production. A simulation program would let us safely test and optimize the site layout. This would enable much more efficient production, which would significantly boost our revenue.”
3. Hero > Obstacle > Guide > Victory
For more emotional impact, take your customer or company on The Hero’s Journey. You frame the audience as the hero and describe the challenge they face. Your product or solution comes in as the guiding hand. With your help, the audience can achieve a glorious victory.
Example: A food bank (the hero) is struggling with unpredictable shortages. They’ve found that their inventory management system is not robust enough to handle growing needs in the community (the obstacle). A software engineer (the guide) proposes a digital tracking system that forecasts demand and flags low-stock items. The food bank could then predict shortages and serve more families with less stress (the victory).
4. Situation > Complication > Question > Answer
A bit more complex, this structure is for when you need to persuade a possibly resistant audience on top of explaining the situation clearly. The goal is to get clients on board with a solution before introducing complex information.
First, state a fact that the audience agrees with. Then explain why this situation is not sustainable based on your data. This will “beg the question,” meaning that you pose the question that everyone is probably thinking at this point. Finally, answer their question with your data.
Example: Let’s say our example engineer tries this approach to reframe their expensive equipment ask.
Situation: Our current machining workflow has been the backbone of our production for a decade.
Complication: However, 30% of our time is spent on re-calibrations and workarounds for this aging equipment just to meet our baseline output. We're treading water instead of growing.
Question: How do we stop babysitting our equipment and increase output?
Answer: Upgrading our equipment will increase production by at least 30% and save $50,000 per year in lost hours.
The spreadsheets are still there to back up the engineer’s claims, but with this approach leadership quickly sees the value of the proposal.
Choose Your Story
When deciding on a narrative framework, choose one that matches your audience’s priorities, such as risk management, clarity, or transformation. Simple frameworks are best if you need to communicate quickly, like in an email or executive summary. More complex frameworks are great for formal presentations, challenging asks, and emotional impact.
However you tell them, stories offer a high-level perspective that makes your data more immediate. The next time you need to relay complicated information, make your expertise shine with a memorable narrative.
If you need help turning your technical data into investor-ready stories and visuals, our team can craft narratives that resonate. Reach out to us to discover how!
Comments