As a soldier in the unit, I got to work on pretty sensitive stuff.
I believed, and I still do, that to become truly world-class in your job, you need a good understanding of the entire system you work in.
In 8200, having a good grasp of the intelligence system required knowledge that seemed far-away from my day to day responsibilities as a developer of cyber tools.
“Why should a tool developer need intimate information about specific cyber operations?!” – (Cyber Operations Team Leader)
“There’s no need for a tool developer to be aware of who the intelligence is for.” – (Intelligence Analyst)
“That information is sensitive! And is far away from your realm of responsibilities” – (Information Security Officer)
“What’s the point of a tool developer knowing about details of Air Strike Operations?” – (Air Force Hakab)
I could go on and on, I heard it all, from different ranks, different roles, even from my commanders, and I disagree.
I spent far too much time fighting for access to information in 8200, information should flow freely inside the organization, everyone should work with similar knowledge. I think it’s important to contextualize the problem your startup is solving with other problems it could be solving instead. You're most likely solving the most important problem in your field, why wouldn't you want to put that in writing?
The downsides of information leaking could be easily mitigated with setting the right expectations and a culture that fosters accountability. If people understand at a deep level why it’s important for information to stay confidential, it will stay that way.