Why Every Engineer Should Write
At Arrowhead Research, we build things. But we also believe that building is only half the job. If you can't explain what you built, why it matters, and what comes next — you haven't finished.
The Communication Gap
The defense technology space is full of talented engineers who struggle to communicate their work to non-technical audiences. The result: good ideas die in PowerPoint purgatory, innovative prototypes never get funded past the demo stage, and decision-makers lack the technical context to make informed choices.
We see this as a solvable problem.
Our Approach
Every Arrowhead member is expected to write. Not because we're trying to create academics, but because clear writing is clear thinking. Our Writing & Presenting program includes:
- Technical paper workshops where members draft, review, and revise papers for conference submission
- Lightning talk sessions where you have five minutes to explain a complex topic to a general audience
- Brief-back exercises that simulate real-world scenarios — briefing a commander, presenting to a review board, pitching to a potential partner
The Results
Members who go through our writing program report that the discipline of writing changes how they approach engineering problems. When you know you'll have to explain your design decisions, you make better ones.
Several Arrowhead members have gone on to publish papers at defense technology conferences, present at industry events, and contribute to professional journals. These aren't career academics — they're operators who learned to articulate their expertise.
Getting Started
If you're a servicemember who wants to develop your technical communication skills, our next writing workshop cohort starts soon. Contact us to learn more.
The best engineers aren't just builders. They're translators — turning complexity into clarity and ideas into action.