UPI Study › Courses › Leadership and Organizational Behavior › Free lessons › Lesson 11.9 Free with a free account
Aligning Team Structures with Organizational Strategy and Workforce Planning
Leadership and Organizational Behavior · Chapter 11: Work Teams, Group Dynamics, and Team PerformanceSection 11.9 · lesson 70 of 12210 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: Measuring and Improving Team Outcomes in Contemporary Organizational Settings →← Emerging Trends and Best Practices in Work Team Design and ManagementNext lesson: Measuring and Improving Team Outcomes in Contemporary Organizational Settings →
In this lesson
Team design decisions are expressions of strategy, not operational housekeeping.
- Apply the strategy-structure fit principle
- Integrate workforce planning with team design
- Recognize when a structure needs redesign
- Build agility through modular team design
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,302 words). Read along, or search it.
Work Teams, Group Dynamics, and Team Performance
Aligning Team Structures with Strategy and Workforce Planning
Team design decisions look operational, and they are not. How teams are sized, structured, and empowered are expressions of strategy. Consider two companies with different strategic priorities. One pursuing rapid innovation needs teams configured one way. One optimizing for operational efficiency needs them configured very differently. The same holds for workforce strategy. A strategy emphasizing employee development requires different structures. A strategy prioritizing short-term throughput requires others. This section examines the relationship between organizational strategy and team structure. It explores workforce planning where it intersects with team design. And it addresses restructuring, which is how a structure stays aligned as strategy moves.
Not Operational
Structure Is a Strategic Statement
Start with why the reframing from operational to strategic matters. Treated as operational, team structure gets decided locally. Whoever manages the team decides how it is organized. They decide using entirely local criteria, which are usually reasonable. Team size gets set by headcount availability. Reporting lines get set by who has capacity to manage. Scope gets set by what the previous team did. None of those criteria makes any reference to the organization's direction. Treated as strategic, the same decisions are made against a different test. Does this configuration serve where the organization is trying to go? That is a question almost nobody asks when designing a single team.
Strategy-Structure Fit
Designed to Serve, Not Inherited
The principle of strategy-structure fit states the requirement directly. Organizational structure, including team configuration, should be designed to serve strategic goals. It should not be inherited from historical practice. And it should not be copied from industry convention. Notice that both alternatives are defaults rather than decisions. Historical practice reflects an earlier strategy, which may no longer be the strategy. Industry convention reflects the average competitor's structure. Deliberately copying the average is a strange thing to do on purpose. Organizations that maintain misaligned configurations incur systematic performance penalties. The word systematic is doing work there. These are not occasional problems. They recur because the structure produces them.
The Penalties
Three Ways Misalignment Costs You
Misalignment costs an organization in three specific ways. First, the wrong information reaches the wrong decision-makers. That happens because structure determines who hears what, and when. Second, coordination mechanisms do not match the actual interdependencies in the work. Teams that need to coordinate closely are separated, and teams that do not are joined. Third, incentives reward behaviors that contradict strategic intent. And people follow the incentives, as they always do. Now notice what none of those three looks like from inside the organization. Not one of them presents as a structural problem. Each presents as a people problem. Poor decisions, weak collaboration, wrong priorities. That misattribution is exactly why misaligned structures survive for years.
Four Alignments
Strategy and the Structure It Implies
Four strategies imply four different team structures. A cost leadership strategy implies functional teams. Those teams need clear efficiency metrics and standardized processes. A differentiation or innovation strategy implies something quite different. Cross-functional pods, with broad autonomy and ambiguous creative mandates. That phrase, ambiguous creative mandates, is deliberate rather than sloppy. A precisely specified mandate would foreclose the exploration the strategy depends on. A customer intimacy strategy implies account-focused teams. Those hold deep customer knowledge and carry relationship responsibility. And a rapid scaling strategy implies small autonomous squads. Squads that can spin up, execute, and dissolve quickly, without a reorganization each time.
Workforce Planning
Two Processes That Must Be One
Workforce planning is the systematic process of getting talent in the right place. The right people, with the right skills, available when and where needed. It is deeply intertwined with team design, and the dependency runs both ways. Decisions about team composition depend on talent supply. You cannot staff a structure with people who do not exist in your organization. And decisions about talent development depend on anticipated team structures. You cannot know what to develop without knowing how work will be organized. Organizations that plan these two separately produce one of two failures. Either structural designs their talent base cannot actually support. Or talent development programs disconnected from how work is really organized. Both look reasonable in isolation, and neither works.
The Interface
Five Planning Elements and Their Design Implications
Five workforce planning elements each carry a team design implication. Skills inventory and gap analysis comes first. It identifies which team competencies must be recruited, versus developed internally. That distinction determines the timeline for any structural change. Succession planning ensures critical team roles have identified successors. Its purpose is avoiding single points of failure inside a team. Capability development designs team rotations and cross-training. Those build strategic capabilities over time, ahead of when they are needed. Retention analysis identifies which team conditions predict retention. Structures then get designed accordingly, rather than in ignorance of that data. And future skills forecasting anticipates emerging needs, starting development ahead of demand.
Restructuring
Necessary, and Almost Always Disruptive
Teams well-designed for one strategic context can become misaligned as strategy evolves. Restructuring is the response. That means changing team composition, reporting relationships, scope of authority, or size. It is often necessary, and it is almost always disruptive. The question is what to conclude from that disruption. It is not a reason to avoid necessary restructuring. It is a reason to manage restructuring with care. Those are very different conclusions drawn from the same observation. And organizations regularly draw the first one. They postpone a needed redesign because the disruption is visible and immediate. Meanwhile the misalignment does years of quiet damage that nobody attributes to it.
Signals
Four Signs a Structure Needs Redesign
Four signals suggest a team structure may need redesign. Persistent coordination failures between teams that should be collaborating closely. Teams consistently working around formal structures to get things done. Skills concentrated in configurations that do not match decision authority. And strategy documents describing capabilities the current structure cannot deliver. The second signal is the most informative of the four. Consider what a workaround actually is. It is a design correction the organization has already invented. People found the coordination path the structure should have provided, and built it informally. Then the organization declined to formalize it. So a persistent workaround shows you exactly what the structure should have been.
Doing It Well
Restructuring Is Not a Structural Exercise
Effective restructuring processes share four features. Early communication about the rationale, before the change rather than alongside it. Member participation in the design, wherever that is feasible. Attention to the relational losses inherent in disbandment or reconfiguration. Those losses are real, and they are routinely dismissed as sentiment. And explicit transition support for the new structure. A new structure does not begin at full effectiveness. Leaders who treat restructuring as a purely structural exercise make a predictable error. They ignore the human dimensions entirely. And they underestimate how long the new structure takes to reach effective performance. That underestimate is what makes a good restructure look like a failed one at month three.
Agility
Three Ways Team Design Produces It
Organizational agility is the capacity to reconfigure resources quickly. Quickly, in response to environmental change. It has become a critical organizational capability rather than a competitive luxury. Team design contributes to agility in three ways. First, modular team design. Smaller, more modular structures can be recombined more easily as needs evolve. Second, cross-functional experience within teams. That experience reduces the knowledge silos which slow adaptation. Third, a culture of self-organization. It reduces the lag time between recognizing a need and responding to it. Each of those is a structural property, not an attitude the team is asked to adopt.
Enablement
Mindset Without Structure Produces Frustration
The chapter closes on a warning about how agility is usually attempted. Agile organizations do not simply create agile teams and declare success. They also redesign the management systems around those teams. Those systems either support team-level agility, or they constrain it. Budgeting is one of them. Resource allocation is another. So are performance review, and information systems. Each of those was designed for an annual cycle, and agility does not run annually. Consider what happens when the teams change and the systems do not. Teams have the mindset but not the structural enablement to act quickly. They experience frustration rather than performance, and reasonably conclude the change was rhetorical.
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 Aligning Team Structures with Organizational Strategy and Workforce Planning
What is strategy-structure fit in organizational design?
Which team structures fit different business strategies?
How does workforce planning connect to team design?
What are the signs that a team structure needs to be redesigned?
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 →