In Act Five of Romeo and Juliet, Friar Lawrence sends a letter to Romeo explaining that Juliet is not dead — that her apparent death is a ruse, a plan designed to reunite them. The letter never arrives. Romeo, receiving no message and assuming the worst, makes a decision based on incomplete information. The rest of the play is the consequence of that one failed communication.
Shakespeare wrote this nearly 430 years ago. The lesson has not aged.
The Message That Didn't Arrive
In defense contracting, the equivalent of Friar Lawrence's letter shows up constantly — and usually without anyone recognizing it as a communication failure until it is too late.
A subcontractor learns about a schedule slip from a program manager's out-of-office reply rather than a proactive update. A teaming partner hears about a contract award from a LinkedIn post rather than a direct notification. A customer reads about a capability change in an industry newsletter rather than from the company that holds the contract. In each case, the message either arrived late, arrived through the wrong channel, or didn't arrive at all. And in each case, the person who didn't receive it drew their own conclusions.
"In the absence of information, people do not assume everything is fine. They fill the silence with the most plausible explanation available — which is almost never the one you would have chosen."
What Silence Communicates
One of the most underappreciated dynamics in partner and customer communication is that silence is not neutral. When a partner goes weeks without a meaningful update from your organization, they do not conclude that nothing is happening. They conclude one of several things: that you are disorganized, that something is wrong and you are managing the optics, or that the relationship is not a priority. None of these conclusions are benign.
The defense community is small and interconnected. Reputations travel through informal networks faster than press releases. A pattern of poor communication — even unintentional, even driven by bandwidth constraints rather than negligence — accumulates into a perception that shapes future teaming decisions, contract renewals, and referral behavior.
The Infrastructure Problem
Most communication failures in defense companies are not the result of bad intentions. They are the result of missing infrastructure. There is no single owned channel. There is no assigned owner for ongoing partner and customer communication. There is no cadence, no template, no system for ensuring that the right people receive the right information at the right time.
In the absence of infrastructure, communication becomes reactive. Updates go out when someone remembers to send them. Newsletters exist in concept but not in practice. Press releases hit the wire without anyone verifying that the company's own partners received advance notice. The Friar Lawrence problem recurs not because anyone planned to fail, but because no one built the system to succeed.
Building the System
The answer is not more effort. Most defense communications teams are already stretched. The answer is a system that removes the burden of execution from the people who are also managing active programs, BD pursuits, and external media relationships.
That system looks like this: a dedicated email channel to your partner and customer list, operating on a predictable monthly cadence, with the capacity to send time-sensitive updates within 24 hours when needed. Fully written. Fully designed. Delivered by someone who owns the execution so your team does not have to.
Friar Lawrence's tragedy was not that he failed to care. He cared deeply. His tragedy was that he entrusted a critical message to a channel he did not control, with no backup and no confirmation of receipt.
The defense companies that build owned communication infrastructure are the ones whose partners and customers never have to wonder what is happening. They already know — because they received the message directly, on time, through a channel that works.
That is what Tidings is built to deliver.