UPI Study › Courses › Business Essentials › Free lessons › Lesson 7.2 Free with a free account
Organizational Design and Structure: A Formal Overview
Business Essentials · Chapter 7: Organizational Design and BehaviorSection 7.2 · lesson 37 of 10515 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 Business Essentials.
Lesson complete
Earn the 3 college credits for Business Essentials
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Organizational Designs: Traditional and Modern Approaches →← Foundations and Architecture of Organizational ManagementNext lesson: Organizational Designs: Traditional and Modern Approaches →
In this lesson
6 design elements, the trade-off in each, and how to diagnose from symptoms.
- Describe the 6 elements of organizational structure
- Explain specialization, span of control, and where authority sits
- Match authority to responsibility
- Diagnose a structural problem from its symptoms
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 (2,016 words). Read along, or search it.
Organizational Design and Behavior
Organizational Design and Structure: A Formal Overview
This section treats structure as something a manager designs, not something that just happens. We'll define organizational structure, and the six elements that describe nearly any organization. For each element, we'll find the trade-off. None of them has a single correct setting. We'll see why specialization is efficient, and why every handoff adds a hidden cost. We'll work through the arithmetic of span of control. And we'll ask where decisions should sit, one decision at a time. Then we'll learn to diagnose a structural problem by starting from its symptoms. We'll finish with two cases where the problem turns out to be structural.
What Structure Is
Who Does What, and Who Decides
Organizational structure is the formal arrangement of jobs, reporting relationships, and authority. It answers a few practical questions. Who does what? Who reports to whom? Who may decide what? And how are the pieces grouped? Every organization has a structure, whether or not anyone designed it. Picture a three-person startup that has never drawn a chart. One person makes the final call on spending, another handles customers, and the third builds the product. That pattern is a structure. The difference is that a designed structure can be examined, tested against the organization's purposes, and corrected. Section seven point one introduced the historical principles. Here they become design elements a manager sets. There are six. Work specialization, departmentalization, chain of command, span of control, centralization, and formalization.
Work Specialization
Efficiency, and Its Hidden Cost
Work specialization, also called division of labor, is how far a job is divided into steps, each done by a different person. Repetition builds skill and speed. And someone who stays with one step doesn't lose minutes switching tools and mental gears. Think of a kitchen where one cook prepares only sauces, and another only grills. But specialization has a diminishing return point. Beyond it, each additional division of the job adds more cost than benefit. Boredom sets in. Quality slips, because no one owns the finished result. And turnover rises. Organizations respond by widening roles, or rotating people. But the trade-off can't be escaped. Now the cost that's easy to overlook. Coordination cost. It's the time, effort, and risk added whenever work passes between people or units. Every handoff is a point where information can be lost, work can wait, or assumptions can differ. Here's an illustration with made-up figures. An order passes through six people, so there are five handoffs. Each handoff has a two percent chance of an error. The chance of at least one error somewhere is just under ten percent, though each handoff looks reliable. Fewer handoffs reduce that exposure, at the price of asking each person to master more.
Departmentalization
5 Ways to Group Jobs
Departmentalization is the basis on which jobs are grouped into units under a common manager. Five bases are common. Grouping by function puts together people doing similar work, such as all the accountants, or all the engineers. Grouping by product puts together everyone working on one product line. Grouping by geography organizes units by territory, such as a western and an eastern region. Grouping by customer organizes units by type of buyer, such as retail and government customers. And grouping by process organizes units around a stage of the workflow. Intake, review, and fulfillment, for example. Here's the key insight. Every basis groups some things together, and by the same act, separates others. Functional grouping deepens skills and shares resources. But it separates the functions that must cooperate on a finished product. Product or customer grouping brings skills together around the outcome. But it spreads one specialty across several units. No basis groups everything that should be together. So the choice is really about which connections to make easy, and which to make hard. Section seven point three develops the resulting forms.
Chain of Command
Who Decides, and Who Answers
The chain of command is the unbroken line of authority, running from the top to the lowest level. It matters for two reasons. It tells each person where to take a problem, and whose decisions bind them. And it tells the organization where accountability for a result finally sits. Unity of command says each person reports to only one superior, so instructions don't conflict. Some modern designs deliberately break that rule, trading clarity for coordination across boundaries. Section seven point three covers them. Responsibility is the duty to achieve a result. Authority is the right to make decisions and direct resources. Accountability is the obligation to answer for results to the person above. Accountability is only fair when the person also holds the authority needed to influence the result. Violating that principle is probably the most common source of structural frustration. Imagine being held to a deadline when you can't set priorities, spend the budget, or direct the people involved. The remedy is to add authority, or reduce responsibility. Leaving the mismatch in place produces workarounds, informal favors, and burnout.
Span of Control
How Many Reports? It Depends
Span of control is the number of people reporting directly to one manager. Four determinants shape it. Task complexity. Simple, repetitive work needs little guidance, so the span can be wider. Employee capability. Trained, experienced people need less direction. Geographic dispersion. Supervising people in one room is easier than across several time zones. And information systems. Tools that show the status of work in real time reduce the effort of staying informed. Span decides the shape of the organization. Here's the arithmetic, with illustrative figures. Picture four thousand ninety-six operating employees, with equal spans throughout. With a span of four, you need six layers above them, and about one thousand three hundred sixty-five managers. With a span of eight, you need four layers, and about five hundred eighty-five. A flat structure means lower cost, and a shorter path for information. But flat structures load each manager heavily, and depend on employees who can work without much direction. Tall structures give close supervision and clear promotion steps, but slow communication and distance the top from the front line. So one organization may sensibly run wide spans in routine processing, and narrow spans in research.
Centralization
Where Should This Decision Be Made?
Centralization is how far decision-making authority is concentrated at the top. Decentralization is how far it's pushed down. These are ends of a continuum, not two states. And organizations are rarely at either end. It's also a mistake to ask whether a whole organization is centralized. The better question is asked decision by decision. Where should this particular decision be made? Five factors decide it. First, where the information is. Moving facts up the hierarchy costs time, and loses detail. Second, the cost of a wrong decision. Expensive or irreversible errors justify more senior review. Third, speed. A decision needed in minutes can't wait for a chain of approvals. Fourth, consistency. Where customers, safety, or the law need the same answer everywhere, central control is justified. Fifth, capability below. Pushing a decision down only works if people are equipped to make it, which may mean training first. Take a regional retailer. Store managers might decide local staffing schedules, where information and speed favor the store. But pricing for regulated products stays at headquarters, where consistency and legal exposure favor the center.
Formalization
Rules or Judgment?
Formalization is how far jobs and procedures are standardized and governed by written rules and documented steps. A highly formalized job leaves little discretion about what to do, when, and how. A low-formalization job leaves much to individual judgment. So the trade-off is consistency against judgment. Formal rules produce consistent results, make training easier, and protect against arbitrary decisions. That's why safety-critical work, like aircraft maintenance, is highly formalized. But rules can't foresee every case. Applied rigidly, they produce poor results in exactly the cases nobody anticipated. That's the goal displacement of section seven point one. A rough guide follows. Creative work, or work responding to unpredictable situations, needs more discretion. Work where errors are catastrophic needs more rules.
Figure 7.2.1
What the Chart Reveals, and What It Hides
An organization chart diagrams the formal structure. Positions, departments, reporting lines, and levels. Read carefully, it reveals the chain of command, the number of layers, how jobs are grouped, and each manager's span. This simplified chart, for a fictional company, marks two problems. At A, the Director of Operations has nine direct reports, drawn from different kinds of work. At B, the launch lead in Marketing is charged with a result. But it depends on units outside the lead's own line. Both problems are visible in the chart's geometry. But the chart can't say whether they're serious. That depends on how complex the work is, how capable the people are, and whether the launch lead has informal influence. And the chart hides a great deal. How decisions are really made, who influences whom, and how heavy anyone's workload is. It can't show whether reporting lines are honored, or how the informal organization operates. A chart can look orderly while the real work runs through side channels. So treat it as the starting point for a diagnosis, never the diagnosis itself.
Table 7.2.1
Diagnose From the Symptom Back
Structural problems rarely announce themselves as structural. They show up as symptoms. So the useful habit is to start from the symptom, and work backward to the element most likely causing it. Don't start from the chart and hunt for defects. Boredom, turnover, and errors at handoffs point to specialization. Units meeting their own goals while the whole fails, or work stalling between units, point to departmentalization. Conflicting instructions, or responsibility without authority, point to the chain of command. Overloaded managers and neglected employees mean a span that's too wide. Slow, costly communication means one too narrow. Routine decisions escalating and waiting suggest too much centralization. Inconsistent or risky decisions suggest too little. And rote rule-following with workarounds suggests formalization set too high for the work. Errors in critical tasks suggest too low. The payoff is precision. Matching a symptom to its element lets you propose a targeted change, not a general reorganization.
A Worked Diagnosis
Brandt Dental Supply: 3 Symptoms, 3 Fixes
Here's the method in use. At Brandt Dental Supply, a fictional distributor, the sales director reports three complaints. Customers wait several days for quotes that need pricing approval. The warehouse supervisor can't take time off, because no one else is authorized to release shipments. And the two people handling returns each say the other decides when a refund is due. Starting from the chart, nothing stands out. Every box has a line to a boss. Starting from the symptoms, each one points somewhere. Waiting quotes are a routine decision made too high. The information sits with sales, and a mistake costs little. The shipment problem is centralization again, plus a capability gap below the supervisor that was never addressed. The returns problem is a shared responsibility, where neither person holds the authority to settle it. So the fixes differ. A pricing limit for quoting without approval. A trained deputy with release authority. And a written statement of which of the two decides refunds. None of these fixes needs a new chart. That's the practical value of diagnosing from symptoms.
Case Vignette (Composite)
The Deliverable Without Authority
In this composite case, Tomas is a project manager at Halden Cycle Works, a fictional company. He must launch a new bicycle model by a fixed date, and his performance review depends on it. But the design work is done in the Design department, the parts are bought by Purchasing, and none of these people reports to him. Each department head sets priorities by their own goals. When Tomas asks for a revision by Friday, he's told to join the queue. He has three options. He can escalate every conflict to the President. That moves work, but slows decisions and damages relationships. He can rely on persuasion and favors. That might work this time, but it leaves the mismatch in place. Or he can ask for a change to the role. That means authority over a named share of design and purchasing staff time. Or written commitments from each department head, about what will be delivered and when, backed by the President. The reasoning is that Tomas's problem isn't skill or effort. It's responsibility assigned without the authority to influence it. Giving him authority takes control from the department heads, who'll resist. But leaving the mismatch hides the launch's true cost. So the sound decision is to correct the role, rather than depend on workarounds.
About Business Essentials at UPI Study
Business Essentials (Business 100) is a self-paced online course of 105 video lessons in 24 chapters, from the business environment, economics and global markets to ownership, management, leadership, operations, people, marketing, accounting, finance and banking. 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 →
Why take it here
Why students take Business Essentials with UPI Study
Where the credit goes
Universities that work with NCCRS
Business Essentials 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 Organizational Design and Structure: A Formal Overview
What are the six elements of organizational structure?
How does span of control affect the number of management layers?
What is the hidden cost of work specialization?
Should decision making be centralized or decentralized?
About the Business Essentials course
How many college credits is Business Essentials?
How much does Business Essentials cost and what is included?
Which universities accept UPI Study credits?
How long does Business Essentials take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Business Essentials.
105 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →