Peter Drucker, Management: Tasks, Responsibilities, Practices — Chapter 44: Design Logics and Design Specifications
Introduction
“Then will you make up the loss from the ad?”
That was the response I got from the head of our TV division when I, as the chief strategy officer at a major Korean media company, proposed shifting the business toward IP-based revenue. For a long time, I remembered him as a textbook case of a leader resisting change—someone protecting his turf. I framed it as a personality problem.
Reading Drucker’s Chapter 44 forced me to reconsider. He wasn’t wrong. Within the structure he sat in, his response was perfectly rational. The problem wasn’t him. It was the structure—and more precisely, the position that was supposed to balance that structure. The position I held.
The real question this chapter raises is this: when an organization’s structure must reconcile seven competing specifications, does the person responsible for balancing them actually have the tools to do so?
The Structure Type Is Fixed; The Balance Within It Is Not
Drucker presents two things in this chapter. First, five design principles: functional, team, federal decentralization, simulated decentralization, and systems. Second, seven specifications that any structure must meet, regardless of which principle is chosen. These range from clarity to perpetuation and self-renewal—conditions that any structure must reconcile to be capable of performance and continuity.
I had expected the chapter to compare the strengths and weaknesses of the five principles. Instead, Drucker offers an important clarification. The choice among them is about finding the best fit, not the right one.
What matters more, however, is this: most executives never get to design the structural type from scratch. Year-end reorganizations are frequent, but rarely do they shift the design principle itself—a ‘functional structure’ does not become a ‘team structure’ overnight.
Their actual task is different. It is to constantly check whether the existing structure still supports the current strategy, by managing the balance among the seven specifications. That is the real work.
And these seven specifications cannot all be fully satisfied at once. They compete with one another. Strengthen one, and another weakens. So who balances them, and how? Our discussion followed that question.
The Paradox of Clarity: A Well-Designed Structure Can Block Change
The Korean media company I worked for ran on a federal decentralization model—six business units, each with its own P&L. Within each unit, functional teams and program teams operated together. In TV, for example, production, sales, and marketing existed as functional groups, and when a new program launched, members from each came together to form a team. It was a working example of Drucker’s principle that functional and team structures can be complementary.
The structure scored high on clarity. Each program team had a simple goal: maximize ratings. Roles were defined. Decision paths were clear.
That is exactly where the problem began.
I argued that the company needed to shift its revenue model from TV ad sales to content IP. The ad market was stagnant, while global platforms were rapidly raising the value of content IP. The center of gravity of the business needed to move.
The TV division head’s response: “Then will you make up the loss from the ad?”
He wasn’t being defensive. He was being rational. As long as his KPIs were tied to ratings and ad revenue, agreeing to an IP shift would mean undermining his own performance metrics.
This is where clarity reveals its paradox. The stronger the clarity, the harder structural change becomes. The clearer one’s KPIs, the more rationally one rejects anything that doesn’t fit them.
A well-designed clarity becomes the wall that blocks change. Strengthen clarity and adaptability suffers; strengthen adaptability and clarity erodes. Both are necessary, but no design principle scores fully on both at the same time.
What is needed at moments of strategic transition is the authority to temporarily rebalance clarity against adaptability. Someone has to redraw KPIs, reset evaluation criteria, and shift resource priorities. Only then does the balance move. But is that actually possible? Where does that authority sit?
The Tools to Balance Are Scattered
I could propose an IP-centered strategy at the corporate level. That was where my authority ended.
I had no power to change KPIs. Adjusting the TV head’s evaluation metrics—raising the weight of IP revenue, lowering that of ad revenue—belonged to HR and finance. Reallocating resources across business units belonged to corporate planning. Restructuring the organization itself was even further out of reach.
Strategy, structure, KPIs, and resource allocation each lived in a different headquarters function.
For the seven specifications to stay in balance, these four levers must move together in one executive’s hands. To rebalance clarity in favor of adaptability, strategic direction, KPIs, and resource allocation must all shift in the same direction at the same time. Move only one, and the balance breaks further. If strategy points toward IP but KPIs still reward ad revenue, the division head follows the KPIs. The rational choice.
The person asked to balance had no tools to balance with.
This fragmentation is a recurring structural problem in Korean conglomerates. As companies grow, each headquarters function becomes more specialized—and ironically, success accelerates the fragmentation. The executive running the business is left with no single lever that moves all four at once.
A revealing counterexample came up in our discussion. One participant contrasted a past role running a new business unit with his current position overseeing a much larger organization.
“Back then, I ran things my way. Resources were laughably scarce, but the goal was clear and I could focus on it alone. Now I lead a much larger organization with far more headcount, and yet I can’t even hire one person on my own terms.”
This is not simply a story about having more authority. It is a story about being in a position to balance things oneself. Resources were scarce, but the tools were in one hand. When the balance shifted, he could reset it on the spot. The organization could respond while remaining alive.
When the tools are scattered, no one can balance. There are legitimate concerns about concentrating too much authority in one person—and those concerns deserve attention. But they are side effects to be managed, not reasons to disperse the tools themselves. Disperse the tools, and the work of balancing becomes no one’s work.
Closing
Organizations do not balance themselves. Someone must do it deliberately, with the tools in hand. Drucker himself acknowledges this: “These are clearly conflicting specifications. No design principle could fully satisfy all of them… This means, inevitably, compromises, trade-offs, balancing.”
So I find myself asking again: in your organization, who is supposed to create the balance? And do they have all the tools they need in their hands?
Appendix: Drucker’s Seven Specifications of Organizational Structure
These are the formal specifications any organization structure must satisfy, regardless of design principle. They are objects of balance, not items on a checklist.
- Clarity: Each member must know where they belong, where they stand, and where to go for information, cooperation, or decisions.
- Economy: The structure should require minimum effort to control, supervise, and motivate. The more energy consumed by internal control, communications, and personnel problems, the less energy converts into performance.
- Direction of Vision: The structure must direct attention toward results rather than effort, toward the whole enterprise rather than the part.
- Understanding of Task: Each individual must understand both their own task and the task of the whole. The structure must help communication, not hamper it.
- Decision-Making: Decisions must be made at the lowest possible level. The structure must not force decisions upward, delay them, or focus attention on jurisdictional disputes.
- Stability and Adaptability: Stability is not rigidity. A fully rigid structure is brittle. True stability requires the capacity to adapt to new situations and new people.
- Perpetuation and Self-Renewal: The organization must develop tomorrow’s leaders from within and remain accessible to new ideas. The structure itself must be designed for continuous learning.