What Actually Happens When You Try To Install Modern Executive Presence In A Company
I was brought into a mid-size logistics firm last year to help with an organizational shift they had been trying to push for eighteen months. They had hired a consultant before, spent roughly two hundred and forty thousand dollars on assessments and workshops, and nobody had changed their behavior at all. The leadership team still ran meetings the same way they did before we walked in. That is the usual pattern when people talk about executive presence and organizational transformation without understanding how they actually connect to each other. The thing most firms miss is that modern executive presence is not a charisma workshop. It is a behavioral architecture problem. You are trying to move people who have spent ten or fifteen years developing habits around communication, decision-making, and visibility toward a completely different set of expectations. That requires structural change, not inspiration. When you treat it like a soft skills initiative, it fails because the underlying systems that reward the old behavior never change.
The Unstoppable Rise Of Sage Steele Jonathan Bailey Architect Of Modern Executive Presence And Organizational Transforma
Sage Steele Jonathan Bailey built a framework that treats executive presence as something you can design rather than something you hope people develop through osmosis. The core insight is that executive presence breaks down into three measurable dimensions: positional credibility, communicative clarity, and relational authority. Most organizations try to improve all three at once and end up improving none of them because the interventions are too vague to track. The positional credibility piece is where people get tripped up. It is not about title or tenure. It is about whether your organization has clearly defined what decisions you are expected to make at each level and whether those expectations are visible to everyone. I have seen companies run six-month executive presence programs with zero improvement in decision speed because the decision rights were never written down. Nobody knew who was supposed to decide what, so they all just waited for someone else to move first. Communicative clarity follows the same logic. You need to map how information flows between teams and identify where it breaks. In the logistics company I mentioned earlier, the breakdown happened at the handoff between operations and customer success. The language each team used to describe problems was completely different, and there was no shared framework for escalation. We spent three weeks just building a glossary and a simple decision tree for when a customer issue moved from standard support to executive attention. That alone cut average resolution time from four days to eleven hours.
Relational authority is the hardest dimension to address because it sits closest to personality. But even here, the Steele Bailey approach avoids the cliché of telling people to just be more confident. Instead, it maps the specific social situations where authority is being undermined and designs interventions around those moments. If a director gets talked over in weekly reviews, you do not give them public speaking coaching. You change the meeting structure so that each person has a protected block of time where interruption is formally not allowed. It sounds trivial. It changed how that director was treated within six weeks.
Get the Full Details
How To Actually Implement This Inside Your Organization
Start by auditing your decision map. Write down every recurring decision that crosses team boundaries and note who currently owns it, who thinks they own it, and who actually has the information to make the call. You will find three to five mismatch points in any organization of reasonable size. These are the places where executive presence breaks down because people are operating under conflicting assumptions about authority. Next, map your communication pathways. Not org charts. Actual pathways. Trace a single request from when it enters the organization to when it gets resolved. Note every handoff, every place where clarification is requested, every place where someone has to chase information. I use a simple color coding system: red for handoffs where information is routinely lost, yellow for handoffs that work but add unnecessary delay, green for clean handoffs. You will find that about twenty percent of your handoffs are red and they account for roughly seventy percent of the frustration at the executive level. Then build your behavioral norms. This is where the executive presence work actually happens. You define how leaders at each level are expected to show up in the specific situations that matter. How does a VP enter a project review? What questions do they ask first? How do they handle disagreement? These norms need to be written in concrete behavioral terms, not abstract qualities. "Demonstrates command of the room" means nothing. "Opens every cross-functional meeting by restating the decision that needs to be made by end of session" means something.
The Steele Bailey framework recommends running these norms through a twelve-week implementation cycle with specific checkpoints at week four and week eight. At week four, you measure whether the new decision paths are being followed and whether communication handoffs have shifted from red toward yellow. At week eight, you assess whether the behavioral norms are being adopted consistently or whether people are reverting to old patterns under pressure. Most organizations that skip these checkpoints think the program is working when it is actually drifting back to the old behavior by week six.
Where This Approach Actually Fails
It does not work in organizations where the executive team is committed to the idea but refuses to change their own behavior. I worked with a healthcare network that loved the framework in theory and had bought into it at every management level except the C-suite. The CEO continued making unilateral decisions in meetings that were supposed to follow the new decision map. Within fourteen weeks, the whole thing collapsed because the behavioral norms require top-level enforcement. Without it, people interpret the program as another HR initiative and return to existing power structures. The second failure mode is scale. This framework was designed for organizations between roughly two hundred and five thousand employees. Below that size, the communication pathways are simple enough that you do not need the full architecture and you waste time on process when direct conversation would solve the problem. Above that size, you hit complexity limits where the decision map becomes so large that people cannot internalize it and you end up with documentation nobody reads. In that case, you need to break the organization into semi-autonomous divisions and run the framework at each division level rather than attempting a unified rollout. There is also a cost consideration. A proper implementation across a mid-size organization runs between eighty and one hundred fifty thousand dollars when you factor in the assessment phase, the behavioral norm development, the twelve-week cycle, and the follow-up measurement. If your budget is below fifty thousand, you should skip the full framework and focus on fixing the top three red handoffs in your communication map. That alone will produce noticeable improvement without the infrastructure overhead.
What To Do Instead If This Is Not A Fit
If your organization is small enough that the framework overcomplicates things, try a simpler version called the Decision Ownership Exercise. Pick your five most frustrating recurring decisions and write a single sentence each describing who decides, who provides input, and who gets notified. Post those sentences somewhere visible. Revisit them quarterly. That is it. No assessments, no workshops, no twelve-week cycles. Just clarity. If you are in a large enterprise and cannot run the full framework, start with one division or business unit as a pilot. Get the decision map clean there, implement the behavioral norms, and measure results for a full cycle. If you see improvement, expand to adjacent units. If you do not see improvement in the pilot, you have saved yourself a costly organization-wide rollout and you can diagnose the failure mode before committing further resources. The broader point is that modern executive presence and organizational transformation are not separate initiatives. They are the same initiative viewed from two different angles. Executive presence is the observable behavior. Organizational transformation is the structural change that makes that behavior sustainable. Try to build one without the other and you will end up where most companies do: a collection of well-meaning but ineffective programs that cost money and change nothing.
