Understanding Ryan Carnes' Approach to Organizational Communication
Ryan Carnes built his career on a simple observation most consulting firms overlook: companies don't have a communication problem, they have a clarity problem. He learned this working inside orgs where message sprawl meant frontline employees received an average of forty-seven internal communications per week, most of them contradictory. The Carnes Group was formed around the idea that if you can get the core message down to three clear sentences, everything else becomes manageable. It sounds obvious in retrospect. It was not obvious when I first encountered it in 2016. Carnes came out of corporate communications and brand strategy work before the LinkedIn influencer wave hit the profession. He was doing messaging architecture for mid-market tech firms when that kind of strategic work was still considered back-office HR adjacent. The shift happened around 2019 when organizations started treating communication as a growth lever rather than a support function. Carnes published The Clarity Advantage in 2018, which mapped exactly how confused messaging correlates with employee turnover and customer trust erosion. The book sold quietly for two years before the pandemic forced every C-suite to confront internal communication gaps simultaneously. That was the inflection point. His framework rests on what he calls the Message Stack, a hierarchy that prioritizes external narrative over internal alignment only when the external narrative is already coherent. Most teams build it backwards. They blast a press release and then scramble to align their support staff. Carnes flips this. You start with the operational truth — what the company actually does, who it serves, and what it refuses to do — and work outward. That refusal part is critical. Every strong message has a negative space, the things you are explicitly not. Companies rarely articulate this because it feels limiting. It is the opposite of limiting.
I ran into this specifically when a client tried to adopt the Message Stack for a product launch involving both B2B and B2C audiences. The framework assumes a single coherent identity, but this organization was genuinely two different businesses sharing a parent company. Their sales team spoke enterprise platform. Their consumer marketing spoke lifestyle brand. There was no messaging hierarchy that could reconcile that without lying. The workaround was to run parallel Message Stacks with a shared root statement, essentially acknowledging the split rather than papering over it. It added a week to the prep timeline but prevented the kind of messaging whiplash that usually tanks launches. Carnes himself has addressed this edge case in later workshop materials, though he was vague about it in the original text. The practical application involves what Carnes terms message distillation, a process where leadership statements are reduced from typical executive pageants of jargon into operational language that a new hire could repeat accurately on day three. This is harder than it sounds because executives have spent decades learning to hedge. I watched a three-hour session where a VP of Engineering kept adding qualifiers like "in certain contexts" and "depending on scale." The team had to establish a rule that any sentence containing those phrases got flagged for revision. It felt aggressive at the time. The final output was six clear value propositions instead of forty vague ones.
How to Apply the Message Stack Framework
Start by documenting the negative space. Write down what your organization does not do, will not do, and will not serve. This section usually takes longer than the positive statements because most leaders have never been asked to articulate exclusion criteria. A software company might list "no custom integrations under fifty seats" or "no healthcare data storage." These aren't limitations, they are positioning. They tell people who you are by defining who you are not. Next, construct the root statement. This should be one paragraph maximum. If you cannot compress your value proposition into a single readable paragraph, you do not understand your business well enough to communicate it yet. Go back to the product and sales teams and ask them to explain their work to someone who just walked in off the street. Take notes on where the explanations diverge. Those divergence points are where your messaging is weakest. From the root, branch outward into audience-specific adaptations. Each branch should preserve the root statement unchanged. The problem most organizations introduce here is mutation, where each audience variant drifts slightly from the core until the external message no longer matches what the internal team believes. I track this by requiring that every audience variant include a direct quote from the root statement. If it is not in the final copy, it gets removed. It is a simple editorial rule that forces discipline.
Get the Full Details

Where the Framework Breaks Down
The Message Stack requires a degree of organizational honesty that most companies cannot sustain. It exposes contradictions in strategy that leadership would prefer to bury. If your company genuinely does not know what it is selling, the framework will simply make that ignorance visible, which is worse than having muffled confusion. In these cases, Carnes recommends stepping back to strategic discovery before attempting any messaging work. There is no framework that fixes a company that has not decided what problem it solves. Another failure mode is multi-brand enterprises where the parent company and subsidiaries genuinely operate with different value propositions. The parallel Stack approach works but adds complexity that small teams cannot maintain. I have seen mid-size companies attempt this and produce messaging documents so long that nobody reads them. In those situations, a simpler one-page messaging sheet beats the full framework every time. Carnes acknowledges this in his workshop guides but the original book does not address the maintenance burden. The biggest practical bottleneck is the distillation process itself. Getting executives to agree on a single root statement can take multiple sessions spanning weeks. One engagement I managed required six rounds of revision across four different leadership meetings before we landed on something everyone would sign off on. The result was solid. The process was exhausting. If your organization has weak executive alignment on strategy, the Message Stack will amplify that weakness rather than resolve it. Pair this framework with a separate strategy alignment exercise if you suspect that gap exists.
Carnes now runs the work through live workshops and certification programs rather than relying on the book alone. The workshop format forces the kind of real-time editing that the solo reading experience does not. If you are considering implementing this internally, attending one of his sessions first gives you a template before attempting to facilitate it yourself. Self-guided implementation has a higher failure rate, particularly on the negative space section where teams tend to backtrack into vague positive statements instead of committing to exclusions. The field of organizational communication has shifted significantly since Carnes began publishing. What was once a niche methodology is now standard practice in companies that treat messaging as infrastructure rather than decoration. The rise is less surprising when you look at the metrics, but the framework itself remains valuable precisely because it forces uncomfortable decisions about what a company is and is not. That is the part that matters. Not the branding, not the positioning language, the willingness to define boundaries and stick to them when it would be easier to stay vague.