UPI Study › Courses › Leadership and Organizational Behavior › Free lessons › Lesson 14.8 Free with a free account
Emerging Trends in Organizational Design and Their Behavioral Implications
Leadership and Organizational Behavior · Chapter 14: Organizational Structure, Design, and Behavioral ImplicationsSection 14.8 · lesson 88 of 12211 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Leadership and Organizational Behavior.
Lesson complete
Earn the 3 college credits for Leadership and Organizational Behavior
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Managing Structural Transitions and Avoiding Common Organizational Design Pitfalls →← Evaluating Structural Effectiveness and Aligning Design With Organizational GoalsNext lesson: Managing Structural Transitions and Avoiding Common Organizational Design Pitfalls →
In this lesson
Every new form is, at heart, a bet on distributed authority.
- Explain how holacracy attaches authority differently from hierarchy
- Say why agile favors persistent teams over project staffing
- Name the new questions the platform form raises about workforce
- Judge an emerging form by readiness rather than novelty
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,551 words). Read along, or search it.
Organizational Structure, Design, and Behavioral Implications
Emerging Trends in Organizational Design and Their Behavioral Implications
This section is about the newest forms of organizational design. Holacracy, agile structures, and platform organizations. They arrive wrapped in enough enthusiasm to obscure what they actually are. So here is the frame that cuts through it. Every one of these forms is, at heart, a bet on distributed authority. That single idea explains what they share, and it explains how to judge them. We will take each form in turn, and name what it asks of the people inside it. Then we look at the bargain that distributed authority always strikes. And finally at readiness, which is the thing that decides whether any of them works. Novelty is not a reason to adopt a structure. Readiness is.
The Frontier
One Thread Runs Through All of Them
The forms covered so far in this chapter are well established. But design keeps evolving, as groups search for ways to combine two things. The reliability of structure, and the speed of change. The emerging trends can look like a scattered collection of buzzwords. They are not. A single thread runs through all of them. Each redistributes authority away from a concentrated top. Toward a wider set of roles, teams, or participants. Holacracy distributes authority to roles within self-governing circles. Agile distributes it to small self-managing teams. Platform forms distribute value creation itself, to participants outside the formal organization. That shared direction reflects a bet worth stating explicitly. In fast-moving settings, decisions made close to the work will be faster and better.
Holacracy
Authority in Roles, Not in Bosses
Start with holacracy, which is the most radical of the three. It replaces the traditional manager-subordinate hierarchy with self-organizing circles. Each circle holds clearly defined roles. And each has the authority to govern its own work, within explicit rules. Here is the key move, and it is genuinely unusual. Authority attaches to roles rather than to people. A member may hold several roles at once, across different circles. The aim is to distribute decision-making widely while keeping it disciplined. The discipline comes from a clear constitution of how decisions get made. Behaviorally, this cuts two ways. It can be liberating for those who thrive on autonomy, and disorienting for those who want clear bosses. It demands comfort with explicit process, and a willingness to act without waiting for permission.
Agile
Short Cycles, Self-Managing Teams
Agile structures were born in software development and have spread widely since. They organize work around small, cross-functional, self-managing teams. Those teams deliver value in short, repeated cycles. Rather than planning everything up front, an agile team builds a little. Then it learns from feedback, and adjusts continuously. Structurally, that has two consequences worth noticing. It favors persistent product-focused teams over temporary project staffing. And it shifts managers toward removing obstacles rather than directing tasks. Why persistent teams? Because a team that stays together carries its learning forward. Temporary staffing discards that learning every time a project ends and members scatter. The behavioral payoff is high engagement and fast learning. The cost is constant change, and the discipline to iterate rapidly without burning out.
Platform
Orchestrating Value You Do Not Produce
Platform organizations appeared earlier as a digital form. They are also an emerging structural trend in their own right. Their distinctive feature is orchestrating value created largely by participants outside the organization. Independent sellers, creators, or service providers. The internal structure becomes lean. It focuses on running and governing the platform, rather than producing the end value directly. Behaviorally, that creates something genuinely new. A workforce split between a small, highly leveraged core. And a large population of loosely attached participants. That split raises fresh questions about identity, fairness, and obligation. Traditional employment frameworks were never designed to answer them. They never had to say what is owed to someone who is neither an employee nor wholly independent.
At A Glance
Three Forms, Three Behavioral Implications
Line the three up and the pattern is easy to hold. Holacracy puts authority in roles rather than bosses. Its behavioral implication is high autonomy, and a real need for comfort with explicit process. Agile runs short cycles with self-managing teams. Its implication is fast learning, paid for with constant change. Platform forms orchestrate external value. Their implication is a workforce split between a small core and loose participants. Notice what has happened to the design question itself. The most consequential structural decisions are no longer about the shape of the chart. They are about how widely decision-making is distributed. And every move toward distribution must be matched by investment in what members can do.
The Bargain
What Members Take On in Exchange
Every step toward distributed authority strikes a bargain, and it is worth reading the small print. What members receive is real. Greater autonomy, faster response, often higher engagement. What they take on is also real, and a clear hierarchy used to spare them all of it. They must manage themselves, without a boss directing each step. They must resolve conflicts directly, rather than escalating them to a manager. They must tolerate the ambiguity of evolving roles and shifting priorities. And they must hold themselves and their peers accountable, without close supervision. So distributed authority raises the skill bar. These structures do not reduce the need for capability. They relocate it, from a few managers to many members. For people with the maturity these demands require, the bargain is liberating. For people who prefer clear direction and defined limits, it can be genuinely stressful.
Not Abdication
Leadership Does Not Disappear - It Changes Job
A common misreading of all this is that leadership simply disappears. It does not. Distribution is not abdication. Someone must still do four things that no self-managing team can do for itself. Someone designs the rules of the game. The explicit process by which decisions get made is itself a design artifact. Someone sets overall direction. Distributed decision-making is only coherent if the decisions point somewhere in common. Someone ensures the capabilities exist. That means selection, development, and support for the self-management the form assumes. And someone intervenes when the system falters. A distributed system that has failed cannot always repair itself from the inside. So leadership shifts from directing the work to shaping the conditions. A different, often harder job.
Deeper Changes
Identity, Status, and Who Enforces
The consequences of these forms go deeper than individual comfort. They change the texture of the whole organization, along four dimensions. The source of authority moves from rank and position to roles, teams, and rules. The identity anchor moves from a fixed position to roles and team membership. Accountability moves from a manager who enforces to peers who hold one another. And the leadership task moves from directing the work to shaping the conditions. Treat the middle two of those shifts as costs, not only as changes. When authority attaches to roles rather than ranks, traditional markers of seniority lose force. That frees talent, and it unsettles people whose sense of worth was tied to position. Peer accountability builds ownership, and it strains relationships. Members now have to confront colleagues directly. Rather than relying on a manager to enforce the standard on their behalf.
Unsettled
The Questions the Platform Form Opened
The platform form deserves separate attention, because its questions are not yet answered. It divides a workforce between a small internal core and a large external population. Three questions follow, and none of them has a settled answer. What obligations does the orchestrating organization owe to those participants? They are neither employees nor wholly independent, which is precisely the difficulty. How is fairness maintained when an algorithm allocates the work? And how does anyone build identity or belonging in such a loosely bound arrangement? These are not merely structural puzzles to be solved by a better chart. They are social and ethical questions. And they remain genuinely unsettled, which you should find interesting rather than frustrating. That, in part, is why the platform form is the most consequential of the three, and the most contested.
Fit, Not Fashion
New Does Not Mean Universal
These forms are easy to romanticize as the inevitable future of all organizing. A more useful stance treats each as a tool suited to particular conditions. Holacracy fits where work genuinely benefits from widely distributed, fast decisions. And where members possess the maturity and appetite for self-governance it demands. Imposed on people who want clear direction, it produces confusion rather than empowerment. Agile fits work that benefits from rapid iteration and continuous feedback. Particularly knowledge work with uncertain requirements. Applied to highly routine or safety-critical work, its constant change becomes a liability. Platform forms fit where substantial value can be created by outside participants. And where an orchestrating core adds value by connecting and governing that activity. Adopt one of these as fashion, without the conditions that make it work, and you get the worst outcome. The costs of distributed authority, without any of its benefits.
Readiness
Judge by Readiness, Not by Novelty
So how should you judge an emerging form when someone proposes one? Never by how new or popular it is. Ask what it proposes to do with decision-making authority. And whether your organization is ready for that distribution. Holacracy vests authority in roles, and needs the discipline to honor role boundaries. Agile puts authority in self-directed teams, and needs teams genuinely able to self-organize. A platform shares authority with participants, and needs trustworthy shared systems. Networked forms spread authority across partners, and need strong trust between the parties. Readiness is the hinge on which all these experiments turn. Distributed authority needs members who will actually exercise judgment. It needs a culture that supports initiative, and transparent information for local decisions. Where those exist, these forms release real energy. Where they are absent, the same forms stall.
About Leadership and Organizational Behavior at UPI Study
Leadership and Organizational Behavior (Business 206) is a self-paced online course of 122 video lessons in 20 chapters, from personality, perception and motivation to leadership and power, teams, decision-making, conflict, organizational structure, culture, ethics and change. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Compare: Management and leadership courses · Foundations of Leadership vs Leadership and OB
Why take it here
Why students take Leadership and Organizational Behavior with UPI Study
Where the credit goes
Universities that work with NCCRS
Leadership and Organizational Behavior carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Emerging Trends in Organizational Design and Their Behavioral Implications
What is holacracy?
What is an agile organizational structure?
What does distributed authority demand from employees?
Do self-managing organizations still need leaders?
About the Leadership and Organizational Behavior course
How many college credits is Leadership and Organizational Behavior?
How much does Leadership and Organizational Behavior cost and what is included?
Which universities accept UPI Study credits?
How long does Leadership and Organizational Behavior take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Leadership and Organizational Behavior.
122 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →