BUS4013 examines how organizational structure shapes behavior, communication, and performance — and how leaders design or redesign structures to support strategic goals. The course connects structural theory to learning capacity, showing how organizations can be deliberately designed to learn, adapt, and continuously improve performance.
Organizational structure types
| Structure | Description | Best Suited For |
|---|---|---|
| Functional | Departments organized by function (marketing, finance, operations, HR) | Stable environments; organizations with a single product line; efficiency-focused |
| Divisional | Separate divisions organized by product, geography, or customer segment, each with functional sub-units | Large, diversified organizations; multiple products or markets |
| Matrix | Dual reporting lines: functional managers and project/product managers share authority over the same employees | Complex, project-based work requiring cross-functional integration; professional services |
| Flat/Horizontal | Few levels of hierarchy; wide spans of control; decentralized decision-making | Innovative, agile environments; knowledge-intensive work; startups |
| Network/Virtual | Core organization outsources most functions to a network of partners and contractors | Industries where speed and flexibility outweigh integration; platform businesses |
What BUS4013 covers
Mintzberg's organizational configurations theory provides a systematic framework for understanding how organizations group their activities, coordinate their work, and distribute authority. Mintzberg identifies five basic parts of any organization: the operating core (those who do the basic work), middle line (managers who connect the core to the strategic apex), strategic apex (top management), technostructure (analysts who design and standardize work), and support staff (internal service functions). Different configurations weight these parts differently: the machine bureaucracy concentrates power in the technostructure and standardizes work processes (manufacturing); the professional bureaucracy concentrates power in the operating core and standardizes skills (hospitals, universities); the divisional form concentrates power in the middle line; the adhocracy concentrates on the support staff and mutual adjustment (innovative project organizations); and the entrepreneurial structure concentrates in the strategic apex. BUS4013 applies these configurations to real organizations, analyzing which structural approach fits a given strategy and environment.
Performance management systems translate organizational strategy into individual and team behavioral expectations, provide the feedback and development support needed to achieve those expectations, and create the accountability mechanisms to ensure sustained performance. Effective performance management systems include clear goal setting (aligned from organizational strategy to individual objectives using frameworks like OKRs or SMART goals), regular performance conversations (not just annual reviews, but frequent check-ins that identify obstacles early and recognize progress), multi-source feedback (collecting performance information from multiple perspectives — manager, peers, subordinates, self, customers), and differentiated consequences (ensuring that high performance is rewarded and sustained low performance is addressed). BUS4013 examines what the research says about what makes performance management systems effective versus counterproductive (many traditional annual review systems demotivate and are no longer trusted).
Writing an organizational design analysis or performance management plan?
Our business writers apply organizational structure frameworks and performance systems to real scenarios with the depth Capella's rubric requires.
Key topics you write about in BUS4013
- Organizational design principles: differentiation, integration, formalization, centralization, span of control
- Mintzberg's structural configurations: machine bureaucracy, professional bureaucracy, adhocracy, divisional, entrepreneurial
- Contingency theory: aligning structure to environment, technology, strategy, and size
- The learning organization: Senge's five disciplines, double-loop learning, after-action reviews
- Performance management: goal setting, feedback systems, performance appraisal, OKRs
- Organizational culture and structure: how culture and structure interact and constrain each other
- Restructuring and redesign: when and how to change organizational structure
Single-loop vs double-loop organizational learning (Argyris and Schon)
- Single-loop learning: detecting and correcting errors within existing mental models — "we did X and got Y; next time we'll do X differently"
- Double-loop learning: questioning the underlying assumptions and norms that produced the error — "why did we think X was the right approach? What assumption was wrong?"
- Most organizations are proficient at single-loop learning and poor at double-loop learning
- Double-loop learning is required for genuine strategic adaptation and organizational transformation
- Leaders enable double-loop learning by modeling genuine inquiry, rewarding constructive challenge, and creating safe space for examining underlying assumptions
Get Help With BUS4013
Organizational design analyses, structural configuration papers, performance management plans, learning organization assessments. Org structure coursework done right.
Place Your OrderView All ServicesRelated courses
Frequently asked questions
The matrix structure overlays functional and project (or product/geographic) dimensions of organization, resulting in employees having two reporting lines: to a functional manager (who manages their professional development and functional expertise) and to a project manager (who manages their work on specific projects). It is designed for complex, cross-functional work that requires integrating diverse expertise — common in engineering, consulting, aerospace, and professional services. The main challenges are "two-boss" confusion (which manager's priorities take precedence?), authority ambiguity (who really decides?), and coordination overhead (managing dual-reporting relationships requires sustained communication and conflict resolution). Matrix structures work best when supported by clear role definitions, strong interpersonal relationships across the functional-project divide, and leaders who actively manage the inherent tensions rather than allowing them to produce gridlock.
Contingency theory holds that there is no one best organizational structure — the appropriate structure depends on contingency factors including the organization's environment (stable vs dynamic, simple vs complex), technology (routine vs non-routine), strategy (cost leadership vs differentiation vs innovation), and size (larger organizations require more formalization and specialization). Burns and Stalker's classic research found that mechanistic structures (hierarchical, formalized, specialized) suit stable environments while organic structures (flexible, decentralized, interdependent roles) suit dynamic environments. Lawrence and Lorsch found that effective organizations match their internal differentiation (how specialized their sub-units are) to environmental differentiation and their integration mechanisms to the need for coordination across those differentiated units. Contingency theory provides the analytical framework for organizational design decisions: before redesigning structure, diagnose what the organization needs to do and in what environment it operates.
OKRs (Objectives and Key Results), popularized by Intel and Google, is a goal-setting framework that distinguishes between the Objective (a qualitative statement of what you want to achieve, inspiring and directional) and Key Results (2–5 measurable outcomes that define what "achieving the objective" looks like). OKRs differ from traditional MBO (Management by Objectives) in several ways: they are typically set more frequently (quarterly rather than annually), they are designed to be ambitious rather than achievable (Google targets 60–70% achievement as success — full achievement indicates insufficient ambition), they are meant to be transparent across the organization (everyone can see everyone else's OKRs, enabling alignment), and they separate development OKRs from compensation (so high ambition is not penalized in the pay conversation). OKRs work best when leadership models the framework, the cultural environment rewards learning from failure, and there is organizational discipline to keep OKRs focused rather than proliferating.
The research on traditional annual performance reviews is damaging: they are widely found to be unreliable (the same performance is rated differently by different raters, a problem called "idiosyncratic rater effects"), inaccurate (what raters primarily measure is their own mental model of the ratee, not actual performance), demotivating (most people leave annual reviews less motivated than before), and ineffective for development (feedback delivered once a year, months after the behavior in question, is too delayed to shape behavior). Companies including Microsoft, Deloitte, and Adobe have moved away from annual ratings toward frequent check-ins, real-time feedback, and development-focused conversations. The research supports this direction: frequent, specific, timely feedback focused on development (what can you do better? what obstacles do I remove?) produces more performance improvement than infrequent evaluative conversations focused on rating.