What You Actually Need To Know About This Framework
I came across Rebecca Soteros Decodes The Hidden Dynamics Of Leadership And Communication In Todays Workplaces about two years ago when a client asked me to help them untangle a communication breakdown between their remote team leads and ground-level managers. Something I had been wrestling with informally for years suddenly had a name and a structure. It isn't a silver bullet. It won't fix everything. But it gave me a vocabulary to talk about problems that usually get described as "culture issues" when they're actually structural. The core idea is straightforward enough that it almost feels too simple. Workplace communication breaks down not because people are bad at talking, but because leadership dynamics operate on layers most organizations never map out. You have formal authority structures, informal influence networks, and the actual workflow of daily work. When those three aren't aligned, people start acting in ways that make no sense from the outside. My last project involved a senior director who was technically "in charge" but had zero informal credibility with the team doing the actual work. That disconnect caused a six-month delay on a product launch that everyone blamed on "budget constraints." It wasn't the budget. It was the invisible hierarchy.
Rebecca Soteros Decodes The Hidden Dynamics Of Leadership And Communication In Todays Workplaces
The framework breaks down into three practical components. First, you identify the formal reporting structure. Second, you map the informal influence network. Third, you examine where decisions actually get made versus where they're supposed to get made. Most leaders stop at step one. That's why the framework exists—to push past that surface level. I use a fairly simple method to apply this. I spend a day or two just observing and asking questions. Not a formal audit, just conversations. Who do people go to when they're stuck? Who gets copied on emails but never replies? Who shows up uninvited to meetings where important decisions are being discussed? Those patterns tell you more than any org chart ever will. In one case, I found that the person with the most informal power was a mid-level engineer who happened to be the only person who understood the legacy codebase. The CTO kept trying to drive technical decisions through formal channels and was getting nowhere. Once we acknowledged that engineer as a key decision-maker, things moved fast. There's a trap here that trips people up constantly. You can't just map the network and then ignore the formal structure. The two exist in tension with each other. If you over-index on informal dynamics, you create resentment among people whose formal role gets sidelined. If you over-index on formal structure, you miss the real decision-makers and waste time convincing the wrong people. The sweet spot is somewhere in between, and it shifts depending on the situation. Crisis mode tends to flatten the hierarchy and center on whoever has the relevant expertise. Normal operations tend to reassert formal structures. Good leaders understand both modes and know when to switch between them.
The downsides of this framework are worth mentioning upfront. It takes time to do properly. Rushing through the mapping process gives you a diagram that looks informative but misses the nuance. You also need honest input, and getting honest input in some organizational cultures is basically impossible without creating real trust first. I've seen this framework applied poorly by consultants who wanted to check a box, and the results were misleading at best. If you're going to use it, commit to the process. Six to eight weeks for a thorough analysis on a mid-size team. Less than that and you're just getting vague generalizations dressed up as insights. Another limitation: this framework works best in environments where there's at least some willingness to examine hidden dynamics. If leadership is entirely closed off or punitive toward dissent, mapping informal networks can put the people you're studying at risk. I've had to walk away from projects where applying this properly would have gotten someone in trouble. In those cases, the better approach is usually working through established change management channels rather than trying to surface hidden dynamics directly. The practical application part is where most people struggle. You collect the data, you build the map, and then what? The hardest step is knowing what to change and in what order. I usually recommend starting with the smallest high-impact adjustment rather than trying to redesign everything at once. Fix the meeting cadence that's causing misalignment. Clarify one ambiguous decision-making process. Build visibility around one informal influencer so they're acknowledged formally rather than operating in the shadows. Small wins compound. Trying to restructure everything simultaneously usually just creates confusion and resistance.
Get the Full Details
I've found that this framework pairs well with regular retrospective practices. Most teams already do some version of this informally. Making it explicit and structured using the three-component model usually surfaces issues that were previously floating around as vague frustration. People can point to specific dynamics instead of just saying "communication is bad." That specificity matters because it turns an emotional problem into a solvable one. If you're looking to apply this yourself, start by picking one recent conflict or bottleneck in your organization and tracing it through all three layers. Formal structure, informal influence, actual decision points. You'll likely find at least one significant misalignment. Then decide whether fixing that one misalignment would actually move the needle. Sometimes the answer is yes, and sometimes it's no, and being honest about which it is saves a lot of wasted effort.
