18 Jun Future Leadership Development: Why Structure Beats Behavior
A leader comes back from a two-day seminar. She’s understood that she needs to delegate more, control less, give the team more trust. Three weeks later, she’s back in the same loop. A decision that could have been made by the team lands on her desk anyway.
Not because she didn’t learn anything. Because nothing changed in the organization around her.
This pattern repeats in almost every organization that invests in modern leadership and leadership development. The program is well designed, participants are motivated, and yet day-to-day behavior barely shifts. The mistake is rarely the program. It’s the sequence. Leadership development changes the person and hopes the organization follows. That’s the wrong order.
It gets expensive, quietly, over the years. Nobody notices it on any single day. But the budget for leadership development keeps growing year after year, while the actual bottlenecks stay exactly where they were.
Contents
Why Leadership Development Can’t Treat Every Problem the Same
What an Organization Actually Is, If Not a Collection of People
Why Teams Aren’t Built Through Team-Building, but Through Design
Value Creation Is Not the Same as Busywork
Future Leadership Doesn’t Mean Less Leadership, It Means Different Leadership
Where Structure Doesn’t Explain Everything – Leadership and Psychodynamics
Why Leadership Development Can’t Treat Every Problem the Same
The physicist and management consultant Dr. Gerhard Wohland distinguishes between two types of problems that exist in every organization at the same time.
Complicated problems can be solved with existing knowledge. A standard process, a checklist, a proven method is enough.
Complex problems have no known solution. They need ideas, talent, and closeness to the market, not more procedure.
A production line that keeps producing the same defects has a complicated problem. A product strategy in a market that shifts every month has a complex one. The fix for one is useless for the other, sometimes actively harmful.
The difficulty is that both kinds of problems exist side by side in the same organization, often in the same department. Accounting and logistics mostly need procedure. Product development and sales in volatile markets mostly need judgment and speed. Anyone who puts one leadership culture over both areas inevitably gets half of it wrong.
Leadership development almost always treats both cases the same way. It trains behavior, communication, decisiveness, regardless of which problem the leader is actually facing. That explains why the same intervention works in one department and goes nowhere in the next. It was never about the intervention. It was about nobody asking which problem was actually on the table.
What an Organization Actually Is, If Not a Collection of People
Niklas Luhmann described organizations as social systems that reproduce themselves through decisions, not through people. That’s not a technicality. It explains why the same person thrives in one organization and withers in the next. Behavior comes from what the structure allows, not from character.
We’ve shown elsewhere in detail why organizational development rarely works at scale, and the reason here is the same. What can actually be changed are an organization’s decision premises. Who decides what? What is success measured by? Which information reaches whom? These questions are designable. Culture and mindset aren’t, not directly. They emerge from those same structures over time.
For example, a sales director gets coaching because he supposedly delegates too little. Three months in, nothing has changed.
The question nobody asked beforehand: what can he actually decide without checking with someone else? The answer: almost nothing. Any exception above a certain amount has to go through senior management.
His behavior was never the problem. It was the only sensible reaction to a structure that demands exactly that.
Trust and psychological safety belong in this same category. Both are real needs, and both determine whether people can do their best work. But neither can be produced through a leader’s attitude or training. They emerge when decision rights, information flow, and accountability actually line up. The sales director from above could have extended all the trust in the world, and the approval threshold would still have sat with senior management.
Cases like that repeat across nearly every coaching practice I know of. The diagnosis is wrong from the start, and then a behavior gets trained that has to fight an intact structure. No surprise it rarely sticks.
That points to an uncomfortable consequence for leadership development. The image of the leader who knows everything, makes every call with confidence, and carries the team through sheer presence isn’t just unrealistic. It distracts from the actual work. Programs that train people toward that image are optimizing for a trait no human can sustain, while overlooking the structure that decides, every day, what’s even possible.
Why Teams Aren’t Built Through Team-Building, but Through Design
Most teams inside organizations aren’t really teams. They’re groups of people sitting in the same box on the org chart. They talk to each other, sometimes well, sometimes badly, but they aren’t bound together by one shared problem they’re actually working on.
Football has a clean word for this difference: a squad versus a team. A squad is the full roster of available players. A team is the line-up that actually takes the field together, in defined positions, with a shared game plan everyone understands. Eleven excellent individual players without that system regularly lose to a well-drilled mid-table team that simply knows who does what, and when.
The same logic applies to organizations. A real team has a shared, externally focused goal, brings together the competencies actually needed, and works on it with genuine commitment, not as a side project. That’s what separates it from the classic department, which is organized by function and oriented toward internal process. Both forms have their place. The problem starts when a department is expected to deliver team performance without being organized like a team.
For a real team like that to exist at all, it usually needs two roles that classic departments don’t have. Someone who carries the initiative and makes the problem visible in the first place. And someone with real formal power who protects that space when the rest of the organization tries to reclaim it. Without that protection, any newly built team slides back into old patterns within months, because the surrounding environment pulls harder than the original intent.
A software company in Hamburg wanted to improve collaboration between engineering and sales. The decisive question wasn’t which initiative to start with, but what the two groups were actually measured on together. The answer was sobering: nothing. Sales had revenue targets, engineering had sprint velocity. Only once both sides got a shared customer problem as their reference point did the collaboration change for good.
Value Creation Is Not the Same as Busywork
An organization can do a lot of busywork and still produce very little value creation. Alignment meetings, internal reporting, status updates, all of it feels like work and solves exactly zero problems that anyone outside the organization would pay for.
The difference sits in the reference point. Anyone oriented toward an internal reference, budget on track, process followed, meeting held, eventually loses sight of the market. Anyone oriented toward the external reference, the customer’s actual problem, the competition, what’s happening out there, stays relevant.
A customer service team gets measured on how fast tickets close. Speed becomes the internal metric everything aligns to. Whether the customer’s actual problem got solved fades into the background. The number looks good. The market sees it differently.
Over time, the yardstick shifts across the whole company. Success gets measured by how smoothly internal operations run, not by how much value actually reaches the customer at the end. That shift never happens through one bad decision. It happens step by step, every time an internal metric matters more than the external problem it was supposed to represent.
Leadership development that mainly trains leaders to manage internal process better reinforces exactly the wrong signal. It turns good employees into better administrators of busywork, not of value creation. The real question a leader should face every day isn’t whether the process was followed, but whether what the organization is doing right now makes a difference to anyone outside it.
Future Leadership Doesn’t Mean Less Leadership, It Means Different Leadership
Future Leadership is often misread as less leadership, more self-organization, flatter hierarchies. That misses the point, and sometimes it goes in exactly the wrong direction. Anyone who flattens hierarchy without clarifying how decisions actually get made afterward isn’t creating Future Leadership. They’re creating a vacuum, and a vacuum usually fills up with informal power that nobody controls.
There are two fundamentally different ways people get led inside organizations.
Management works through formal power, rules, and hierarchy. It works well for problems that can be solved with known knowledge.
Leadership in the proper sense is a social phenomenon. People follow someone because they trust that person to solve a problem that has no known solution yet. This kind of leadership can’t be assigned. It gets attributed, and it can shift, depending on who has the most convincing read on a given situation.
Power and authority are part of this picture too, not as the opposite of leadership, but as a tool that has to be used at the right moment.
In practice, that looks like this: on a project with no clear technical answer, the person with the highest title doesn’t automatically take the lead. The person whose judgment is most convincing in that moment does. On the next project, that can be someone else entirely. That’s what nomadic leadership actually means, not randomness, but leadership emerging wherever the problem actually gets solved.
That’s the real core of Future Leadership. Not less leadership, but leadership that follows competence instead of position. At CoHive, we call this shift New Leadership, the same logic applied consistently across the whole organization. An organization that simply flattens hierarchy or leaves teams to fend for themselves, without actually designing that shift from management to leadership, mistakes self-organization for self-neglect. The result is usually more chaotic, not more free.
Where Structure Doesn’t Explain Everything – Leadership and Psychodynamics
I’m sticking to the core argument. Structure is the primary lever, and skipping it wastes time and budget. But there’s a second category of cases I can’t ignore.
A leader gets a clean redesign of decision rights and still has every important decision handed back to them. The team is formally allowed to decide, but doesn’t, because the leader is unconsciously signaling that they’d rather do it themselves. The structure is clean. The behavior undermines it anyway.
Klaus Eidenschink, an organizational psychologist and systemic coach, calls it a “self-amputation” when consulting takes psychological dynamics completely out of the equation and only works on structure. His criticism isn’t aimed at the structural perspective itself, but at too narrow a reading of it, the assumption that people simply can’t be influenced and should therefore be left out of the picture.
I think he’s right, with one qualification. Structure creates the conditions for good behavior. But if the person in the key role doesn’t recognize their own patterns, even the best structure can’t compensate for that. Then it takes both: work on the design, and a space where the leader can get honest feedback without filters, without the rest of the organization watching. That’s not a contradiction of the structural perspective. It’s an extension of it.
Conclusion: Leadership Development as Structural Work
Anyone who has to sign off on a leadership development budget tomorrow should ask a different question first, before picking a program. Is the problem missing knowledge or behavior in the person? Or is it a structure that practically forces certain behavior, regardless of who holds the role?
In most cases, it’s the latter. The right order is to clarify the decision architecture first, who decides what, what success gets measured by, which information reaches whom, and only then invest in the person. Doing it the other way around burns budget on symptoms while the cause stays untouched.
That doesn’t mean people never need to be worked with. It means the order has to be right, and most programs have it backwards.
Anyone who has understood that asks the same question before every new program. Not: how do we develop this leader? But: what about the structure makes their current behavior the path of least resistance, and what would have to change there for different behavior to even become possible?
That question takes five minutes. It still changes what the entire next program looks like.
Get in Touch
If your leadership development is costing a lot of energy and leaving little behind, it’s worth a look at developing leaders who understand their role in the system, before the next program starts.
In a first conversation, we look together at where the real levers sit in your organization. Free, no pitch, no obligation.