People and Performance Drucker

1. 1Locate identity in the answer to today's question: people used to ask 'What do you do?' but now ask 'Whom do you work for?' Direct achievement motivation by making the individual's contribution visible against the organization's purpose, not against a job title.
2. 2Define the specific contribution each person must make. Drucker's rule: the manager's job is to make the strengths of people productive and their weaknesses irrelevant — so assign work that draws on what a person does well.
3. 3Grant autonomy and decision power to sustain the drive. In the automated plant the manager has two or three people, each with 'greater autonomy, more responsibility and far more decision-making power' than the old assembly-line worker under a foreman of fifty — structure work so the worker owns real decisions.
4. 4Study the work itself before motivating the worker. Follow Taylor: do not take work for granted; look at it, study it, and reorganize it so productivity rises and toil that is 'destructive of body and soul' is removed.
5. 5Tie the work to results the worker can see. Use measurement where it exists (profitability, output) and, where only opinions exist, define concrete objectives so the person can judge their own contribution.
6. 6Treat the educated employee as an expensive, perishable resource: society invests upward of $40,000 in a graduate's education and the employer $50,000–$500,000 per managerial job — protect that investment by giving knowledge a place where it 'can become productive and can be paid for.'
7. 7Connect the job to the wider purpose so the person finds status, function, and personal fulfillment through the institution, since in an employee society people look to institutions for exactly these things.

Robert Owen at his Lanark textile mill in the 1820s is the passages' concrete case. He became the first manager to stop taking work and the worker for granted and instead tackled 'the problems of productivity and motivation, of the relationship of worker to work, of worker to enterprise, and of worker to management.' Rather than treating labor as an interchangeable cost fixed by the Iron Law of wages, he addressed the worker as a person with a stake in the enterprise. Decades later Taylor pursued the same drive from a different angle: he studied work to free the laborer from heavy toil and to break the poverty the classical economists thought inescapable, aiming to give a decent livelihood through higher productivity. Both show the pattern: raise the worker's contribution and standing by redesigning the relationship between worker, work, and enterprise. The motivation follows the restructured work, not a slogan.

• If a person's weakness blocks a task, then reassign the task to where their strength applies rather than trying to fix the weakness — make weaknesses irrelevant.
• If the work is knowledge work, then grant autonomy and decision power proportional to responsibility; a knowledge worker starved of decisions loses the drive.
• If you cannot measure results directly, then define explicit objectives, because opinions alone are 'hardly an adequate foundation' for judging contribution.
• If the work itself is destructive or ill-structured, then study and redesign the work before addressing the worker's attitude — Taylor's order of operations.
• If an employee looks to the institution for status and fulfillment, then connect their specific job to the institution's purpose, since that is where meaning is found in an employee society.

• Taking work for granted — motivating the worker without studying the work first. Tell: you push harder on people while the task itself stays unexamined.
• Managing knowledge workers like semi-skilled operators under a foreman of fifty. Tell: wide spans of control and little decision-making power delegated downward.
• Treating the educated employee as a cheap, replaceable input. Tell: no accounting for the years and $50,000–$500,000 invested per job, and rapid, casual turnover.
• Relying on opinions instead of objectives to judge contribution. Tell: nobody can say concretely what 'good performance' looks like, so drive drifts.
• Trying to correct weaknesses instead of deploying strengths. Tell: development plans focus on what people can't do rather than making their strengths productive.

• ▸Worker/role: name the person and their function
• ▸Whom they work for: state the institution and its purpose in one line
• ▸Specific contribution: the one result this person must produce
• ▸Strength deployed: the strength this work draws on
• ▸Weakness made irrelevant: how the design routes around it
• ▸Autonomy granted: which decisions this person owns outright
• ▸Measure or objective: how contribution is judged (metric or defined objective)
• ▸Investment at stake: education + job investment to be protected

1. 1Derive every job's performance target from the goals of the whole business, not from the function's own craft. For each role, write the specific contribution the enterprise needs before you write duties.
2. 2Make each manager's objectives point at the success of the whole enterprise, so a chemist, cost accountant, or advertising director sees how their piece fits the common goal.
3. 3Have both the manager and the superior state, in writing, what contribution to demand and expect — align expectations before measuring performance.
4. 4Measure results by contribution to enterprise success, not by activity or workmanship; the yardstick is the whole, not the department.
5. 5Fit contributions together so efforts pull the same direction: check for gaps (nothing owned), friction (conflicting aims), and unnecessary duplication.
6. 6Extend this to individual professional contributors — senior chemist, cost accountant, quality and advertising leads — who shape results without bossing anyone; give them defined contribution, status, and self-respect so their efforts align too.
7. 7Give people vision and the ability to perform — the one contribution only a manager can make — so alignment comes from shared purpose, not orders from the boss.
8. 8Guard against misdirection by the boss and by 'drives': periodically ask whether stated objectives still serve the common goal or have drifted into craft or campaign.

The multinational corporation is the passage's clearest case of common direction of vision. It brings together management people from many countries with different languages, cultures, traditions, and values and unites them in a common venture and common purpose. None of these managers shares a nation, yet each contributes toward one goal, so the effort transcends national boundaries that fragment the surrounding world. Contrast Ford: the first Henry Ford refused managers and wanted only 'helpers' who took no action without his orders — no independent contribution could be aligned because none was permitted, and the empire collapsed by 1927. Where GM under Sloan built a management team, direction came from understood contributions fitting a whole; where Ford monopolized decisions, there was no team to align. The lesson: a whole greater than the sum of parts requires each part to know the common goal and how it fits — not a single boss issuing orders.

• If a job's target is set from its own craft or workmanship rather than from the business goals, then reset it — workmanship is a necessity but also a danger of misdirection.
• If a manager cannot state how their results contribute to the success of the whole enterprise, then their objectives are misdirected and must be rewritten.
• If someone shapes results (senior chemist, cost accountant, quality lead) but bosses no one, then treat them as management and align their contribution too — rank and pay do not define who is a manager.
• If efforts show gaps, friction, or duplication, then the directions are not common — fit the contributions together before proceeding.
• If a 'drive' or the boss's preference is pulling effort away from the common goal, then correct the direction, because misdirection by the boss and by drives is the main threat.

• Defining the manager by rank and pay instead of function and contribution — the tell: professional contributors have real impact but no status, and their efforts drift unaligned.
• Monopolizing decisions like the first Ford, letting no one act without orders — the tell: 'helpers' who make no independent contribution and messes that pile up from a single point of control.
• Directing effort toward workmanship or craft excellence for its own sake — the tell: a department proud of its standards but disconnected from enterprise results.
• Misdirection by the boss's personal drives or campaigns — the tell: this quarter's initiative overrides the derived, whole-business objectives.
• Leaving individual professional contributors out of the alignment — the tell: gaps and duplication because people who set measurements and standards never had their contribution tied to the common goal.

• ▸Role / person: name the job, including non-boss professional contributors
• ▸Common goal served: the specific enterprise goal this role points at
• ▸Expected contribution: what the whole business needs from this role (agreed by holder and superior)
• ▸Measure of results: how contribution to enterprise success is judged, not activity
• ▸Direction check: does this pull the same way as adjacent roles? (yes/no + note)
• ▸Gaps / friction / duplication found: what is unowned, conflicting, or repeated
• ▸Vision given: what this person understands about how their part fits the whole
• ▸Misdirection risk: any craft-pull, boss-drive, or campaign steering effort off-goal

1. 1Define the output first, not the input: name the specific result the resource must produce (economic goods, a service, a decision) before you count effort or cost. Drucker's frame is opportunities and results, not efforts and costs.
2. 2Identify your scarcest, most expensive, most perishable resource — in most businesses this is the manager, carrying $40,000 of society's education investment plus $50,000–$500,000 of employer investment per job. Allocate this resource to opportunities, not to defending yesterday.
3. 3Make each person's strengths productive and their weaknesses irrelevant: assign work so what a person does well is the thing that matters, and what they do poorly does not block results.
4. 4Recognize the 'change of phase' point. When a business crosses roughly 300–1,000 employees or jumps in complexity, stop running it as a 'boss with helpers' and build a management skeleton — a structural replacement, not an add-on.
5. 5Design spans and autonomy to fit the work. In automated operations a manager carries only two or three people but each has more decision-making power; do not staff for supervision headcount, staff for autonomous responsibility.
6. 6Treat the knowledge worker as a high-grade, expensive resource whose productivity has to be deliberately made, not assumed: give them the conditions in which knowledge becomes performance and gets paid for.
7. 7Continuously replenish the management team. Because it depreciates fastest and can be depleted in a short period though it takes years to build, run recruitment and development as ongoing, not episodic.

Take Ford as the passages' controlled experiment in mismanagement: the older Ford tried to run a giant enterprise as a 'boss with helpers' — an insect held together by a hard skin, which D'Arcy Thompson showed can only reach a certain size before it fails. The business had crossed the change-of-phase line but kept its hard-skin structure, so resources were not made productive and the company floundered. Contrast Pierre du Pont, who between 1915 and 1920 restructured the family firm and gave it a management to make growth possible while preserving family control. When the du Ponts acquired the near-bankrupt General Motors, they installed Alfred P. Sloan, Jr., as president, and he built a 'professional management' skeleton — a different organ with different antecedents, not an evolved skin. The lesson: productive work at scale came not from more effort but from replacing the structure so people and capital could be directed at results. GM went from floundering conglomerate to functioning enterprise because the balance of factors, not the volume of effort, was reset.

• If you are measuring effort and cost rather than opportunity and result, then you are managing productivity backward — re-anchor on output.
• If the business has crossed 300–1,000 employees or sharply increased in complexity, then shift from hard-skin (boss-plus-helpers) to a management skeleton; do not adapt, replace.
• If a person's weakness is blocking output, then redesign the assignment so their strength carries the result and the weakness becomes irrelevant.
• If the work is automated or knowledge-based, then widen autonomy and narrow span — give two or three people real decision power rather than supervising fifty.
• If your most expensive and perishable resource (managers) is being spent on defending existing operations, then reallocate it to opportunities, since that is where output-per-effort is greatest.

• Confusing activity with productivity: counting hours and costs while the result goes unnamed. The tell is dashboards full of inputs and no line for output.
• Letting a business outgrow its structure — running a complex enterprise like a boss with helpers. The tell is that everything routes through one person and decisions stall as size grows.
• Staffing for supervision headcount instead of autonomous responsibility. The tell is wide spans of low-authority roles where automated or knowledge work actually needs fewer, more empowered people.
• Treating the knowledge worker as an ordinary cost rather than a resource whose productivity must be built. The tell is educated people whose knowledge never converts to paid performance.
• Neglecting to replenish the management team because it looks stable. The tell is a team built over years that suddenly hollows out — depletion is fast and invisible until it hits.

• ▸Target result — the specific output this resource must produce
• ▸Scarcest resource named — the most expensive/perishable input at risk here
• ▸Investment carried — education + job investment tied up in this resource
• ▸Strength-to-task match — the strength each person is assigned to apply
• ▸Weakness neutralized — how the assignment makes each weakness irrelevant
• ▸Phase check — size/complexity signal that structure must change (300–1,000 line)
• ▸Span & autonomy — people per manager and decision power granted
• ▸Opportunity vs. defense — share of resource aimed at opportunity vs. protecting the existing
• ▸Replenishment plan — how this team gets rebuilt before it depletes

1. 1Define the specific purpose and mission of your institution before measuring anything — for a business, that purpose is to create a customer and generate profit sufficient to cover risks and secure the future.
2. 2Set performance against that purpose, not against the absence of discontent; do not accept satisfaction (no complaints) as evidence you are performing.
3. 3Study the work itself when you scale — expansion of magnitude is qualitative change, not more of the same, so re-organize the work rather than only adding people.
4. 4Keep knowledge work lean and err toward understaffing, because overstaffed middle-management destroys motivation, accomplishment, and ultimately performance.
5. 5Treat quality-of-life and individual-fulfillment demands as opportunities to convert into profitable business, not as social obligations sitting outside your main function.
6. 6Generate and direct human energies, not just capital: contribute management, since development is a consequence of management energies, not economic wealth alone.
7. 7Pay for contribution, not position — let star performers out-earn their managers where results depend on individual skill, effort, and knowledge.
8. 8At the first economic setback, force a correction: think through what the work is and what it needs before you cut, so the reduction improves performance rather than only headcount.

When Pierre S. du Pont and Alfred P. Sloan, Jr. attempted in 1920 to bring order into the chaos of General Motors, they first set the same salary for the heads of the operating divisions as for the president, Pierre du Pont. Then Sloan, at his own request, took substantially less as the operating vice-president to whom the division heads reported. This inverts the usual assumption that the 'superior' must earn more: the division heads whose contribution drove results were paid at the top, while the coordinating manager took less. The precedent shows organizational performance depends on rewarding the contribution that fulfills the enterprise's purpose, not on rank in the reporting line. The same logic lets a star salesperson out-earn the regional sales manager and a lead researcher out-earn the lab head. Performance, not hierarchy, sets the pay.

• If a unit shows only absence of discontent but no measurable achievement, then you have satisfaction, not performance — raise the demands.
• If you are growing at fast rates, then assume you are overshooting and overstaffing, and study the work before adding more people.
• If middle-management work feels comfortable and unstretched, then it is overstaffed — make it lean and demanding.
• If a person's contribution depends on individual skill and results (star salesperson, lead researcher), then pay for the contribution even when it exceeds the manager's pay.
• If you have supplied only capital and economic factors to a venture, then expect no development — supply management energies instead.

• Mistaking the absence of complaints for performance — the tell is that human relations reports 'satisfaction' while output, achievement, and motivation stay flat.
• Treating fast growth as pure addition of quantity — the tell is duplicated effort and organizational obesity because no one re-studied the work.
• Overstaffing middle management because times are good and it's easier to accede than to fight — the tell is falling motivation and accomplishment despite more people.
• Tying higher pay strictly to promotion into a manager's job — the tell is confused, ambiguous, dissatisfied professional contributors leaving or feuding.
• Treating quality-of-life and individual fulfillment as social responsibility outside the main task — the tell is these demands are handled as restraints rather than converted into profitable business.

• ▸Specific purpose/mission: state the institution's reason to exist in one sentence.
• ▸Customer created: name who you exist to satisfy and how.
• ▸Profit-adequacy test: state the profit level needed to cover risks and secure the future.
• ▸Performance measure: name the achievement metric beyond 'no discontent.'
• ▸Human-energy source: identify where management, not just capital, drives your development.
• ▸Staffing posture: mark each unit understaffed / lean / overstaffed and the action.
• ▸Contribution-based pay: list roles where a performer may out-earn the manager.
• ▸Quality-of-life opportunity: name one fulfillment demand you can convert to profitable business.
• ▸Correction trigger: define the setback signal that forces a re-study of the work.

1. 1State the two entrepreneurial purposes as measurable targets, not slogans: for marketing, define who the customer is and what economic satisfaction you must create; for innovation, define what new and better satisfaction you will provide. Both come before internal efficiency.
2. 2Run a potential-vs-actual gap: ask what the theoretical optimum result for this business is, and where the limiting factors hold it below that optimum. Innovation success is measured against that gap, not against last year.
3. 3For each function's manager, spell out its contribution to marketing and innovation in the objectives, even when the contribution is small — and when a unit contributes nothing to prosperity and survival, state that fact explicitly.
4. 4Apply vulnerability analysis: list the small changes in product, technology, process, or market that would materially alter economic results, ranking them by yield rather than effort.
5. 5Concentrate resources on the small core of worthwhile activities capable of extraordinary results, and neutralize or abandon the large penumbra of busy-ness that cannot yield high returns no matter how well executed.
6. 6Balance short-range and long-range objectives so marketing wins do not starve innovation and vice versa; management by 'crisis' and 'drives' rules out the balanced stress both functions need.
7. 7Treat management as the organ that exists only in contemplation of performance — measure marketing and innovation output against the customer created and the new satisfaction delivered, not against internal activity or delegation from a boss.

Take the Ford-versus-GM controlled experiment. Ford held about 60 percent of the market by 1920 and a billion dollars in reserves, yet by 1927 it was a poor third, losing money for roughly twenty years. The founder refused managers, believing an owner and his 'helpers' sufficed, and fired anyone who acted as a manager — proving the hypothesis wrong. In the same early twenties, Sloan at GM, then a weak number two with no winning car and no dealer organization, thought through what the business and structure should be and converted autonomous barons into a management team; within five years GM led the industry. When Henry Ford II took over a near-bankrupt company in 1946, he built a management structure and team and within five years regained growth and profit, even outstripping GM in the fast-growing European market. The lesson: sustained marketing leadership and renewal require management as the specific organ, not personal will backed by cash.

• If an activity, however well done, cannot yield extraordinarily high results, then neutralize or abandon it and redeploy resources to the worthwhile core.
• If a manager's unit contributes to no area that affects prosperity and survival, then say so explicitly rather than pretend a contribution exists.
• If a minor change in product, technology, process, or market would significantly alter economic results, then pursue it before any large innovation program.
• If the organization drifts into management by crisis and drives, then reimpose balanced short- and long-range objectives across every function.
• If technical excellence, moral responsibility, or human relations is offered alone as the answer, then reject it — the entrepreneurial functions require them made one, not any single dimension.

• Believing the business 'evolves' without managers, as the first Ford did; the tell is a single owner making every decision and sidelining anyone who acts independently.
• Confusing activity with results — pouring effort into the large penumbra of transactions; the tell is high busy-ness with results stuck far below theoretical potential.
• Measuring against last year instead of against the optimum; the tell is celebration of incremental gains while the potential gap stays unexamined.
• Overemphasis on one key area, letting empire-building and clannish jealousies of functions distort the balance; the tell is one function's metrics dominating every review.
• Treating management as an end in itself rather than the organ of the institution; the tell is bureaucracy that serves the structure instead of the customer created or the satisfaction delivered.

• ▸Customer defined: who you are creating and what economic satisfaction they buy.
• ▸New satisfaction: the specific new or better economic result innovation will provide.
• ▸Theoretical optimum: the maximum yield resources are inherently capable of.
• ▸Limiting factors: what holds results below that optimum right now.
• ▸Minor high-yield changes: small shifts in product/technology/process/market that alter results.
• ▸Worthwhile core: the few activities capable of extraordinary results — keep.
• ▸Penumbra to neutralize: well-done activities that cannot yield high results — cut.
• ▸Contribution by function: each unit's stated contribution to marketing and to innovation.
• ▸Time balance: matching short-range and long-range objectives for both functions.

1. 1Inventory the social impacts your operations create — the passages point to areas like the environment, worker attitudes, and the quality of life. List each impact your institution causes on people and community, whether or not it relates to your economic mission.
2. 2Separate impacts (harm your activity causes as a byproduct) from problems (dysfunctions in the surrounding society). Manage them differently: impacts you are responsible for minimizing; problems you convert only where you have competence.
3. 3For each identified impact, ask Rathenau's founding questions: what is the place of this large enterprise in society, what impact does it have, and what are its fundamental contributions and responsibilities. Assign accountability for each.
4. 4Minimize the harm from your own impacts first — this is the non-negotiable baseline before any conversion into opportunity.
5. 5Screen social problems against manageability and legitimacy: only take on problems where your systematic knowledge lets you create value (Towne's test) rather than overreaching into activity that does not belong in the enterprise.
6. 6Convert the qualifying problems into performance opportunities — turn the social problem into a task where solving it also advances the institution's contribution and improves quality of life.
7. 7Bound the effort with the limits of social responsibility: recognize that business is one power center among government and unions, and refuse tasks beyond your competence or legitimacy.
8. 8Build this into the management structure, not into exhortation — the passages warn that speeches and programs change little; responsibility mirrors management's actual competence and structure.

Frederick Taylor's work is the passages' clearest case of converting a social problem into a performance opportunity. The social problem was the laborer's lack of a decent livelihood. Taylor did not treat it as charity or as separate from the business; he attacked it through the enterprise's own core function — the productivity of work. By raising productivity of work, he made it possible to give the laborer a decent livelihood, a hope the passages note has largely been fulfilled in the developed countries. The social problem and the performance goal became the same task: better work, higher output, higher pay. This is managed social impact done right — the contribution to quality of life is produced through, not alongside, the institution's economic performance.

• If an impact is a byproduct your own operations cause, then you are responsible for minimizing it — do not wait to be forced.
• If a social problem can be solved by using your systematic knowledge to create value, then convert it into a performance opportunity; if not, then it is beyond your legitimacy — leave it.
• If an activity does not belong within the large enterprise on grounds of manageability, then do not absorb it in the name of responsibility.
• If you are relying on speeches, programs, and expensive gadgets to signal responsibility, then assume nothing is changing — check the structure and competence instead.
• If the task exceeds your competence or authority as one power center among government and unions, then decline it rather than overreach.

• Confusing exhortation with action — the tell is a steady barrage of speeches, programs, and advice while the actual structure and competence never change.
• Treating social responsibility as unlimited — the tell is absorbing problems the enterprise has no competence or legitimacy to solve (Chapter 30's limits of social responsibility ignored).
• Failing to distinguish your own impacts from society's problems — the tell is either dodging harm you cause or claiming credit for problems you merely touch.
• Bolting responsibility on as separate charity rather than converting problems through core performance — the tell is an initiative that adds cost with no link to the institution's contribution (contrast Taylor).
• Ignoring manageability limits — the tell is an enterprise grown too big and complex to actually govern its impacts, so plans fail to turn into action.

• ▸Impact or problem: name one item and mark whether it is an impact you cause or a societal problem
• ▸Source: which operation, function, or byproduct generates it
• ▸Harm-minimization step: the specific action that reduces the harm you cause
• ▸Competence test: does your systematic knowledge let you create value here (yes/no)
• ▸Legitimacy test: is this within your authority as one power center among government and unions (yes/no)
• ▸Conversion opportunity: how solving it also advances the institution's performance
• ▸Quality-of-life contribution: the concrete improvement to people's lives
• ▸Accountability: who owns this and how they are held to it in the management structure

1. 1Wait for the size and complexity trigger: once you cross the range between 300 and 1,000 employees, or once varied tasks must be performed in cooperation, synchronization, and communication, the 'hard skin' of boss-driven control fails and you must install the objectives system.
2. 2Sit down superior and subordinate together and jointly identify the common goals of the unit — start from what the institution as a whole must perform, not from the individual's convenience.
3. 3Define each individual's major areas of responsibility strictly in terms of the results expected, not activities or effort; write down what the person is accountable to produce.
4. 4Convert those expected results into measures that can actually be read — since the management task is 'making the institution perform,' every responsibility area needs a yardstick.
5. 5Hand those same measures back to the individual for self-control: they operate their own unit against the measures, so performance rather than 'the favor of the boss' governs behavior.
6. 6Use the measures at review time to assess each member's contribution against the results agreed, and to re-set objectives for the next cycle.
7. 7Repeat the setting-objectives / organizing / staffing / measuring-results / communicating cycle continuously — these are the specific work of management in every institution, business or not.

Henry Ford is the negative case the passages hand you. Ford 'wanted no managers' — he tried to keep running a company that had long crossed the size and complexity line on personal boss-power alone. Without jointly set objectives and agreed measures of expected results, there was nothing for people to steer by except Ford himself. The result: he 'mismanaged, misdirected, and misorganized his company and stunted or broke management people.' Contrast the transcontinental railroad, the first genuinely 'managed' enterprise, which had to synchronize the engineering task of building a railbed, the financial task of raising capital, and the political task of obtaining charters — tasks impossible to run on favor, requiring shared objectives across many hands. The lesson: at that scale the choice is only between management and mismanagement, and objectives-and-measures are how you avoid the second.

• If a business has passed 300–1,000 employees or has varied tasks needing cooperation and synchronization, then stop relying on boss-power and install jointly set objectives.
• If different parts of the plan run at different speeds, times, and goals, then your responsibility areas are not defined in terms of shared results — redefine them.
• If 'the favor of the boss' has become more important than performance, then your measures are missing or unused — restore self-control against agreed yardsticks.
• If a responsibility cannot be stated as a result and given a measure, then it is an activity, not an objective — rewrite it.
• If you cannot say how a person contributed to the unit's common goal, then you set the goal individually rather than jointly from the institution's task — reset it.

• Trying to run on personal 'hard skin' past the size line, like Ford — the tell is a business that floods with able, dedicated people yet begins to flounder and stagnate.
• Defining jobs by activity and effort instead of expected results — the tell is reviews that discuss how hard someone worked, not what they produced.
• Setting objectives top-down as commands rather than jointly identifying common goals — the tell is subordinates who steer to please the boss instead of to hit the measure.
• Setting objectives but never measuring results — the tell is plans that 'fail to turn into action' with no yardstick to expose it.
• Starting from the individual's convenience rather than the institution's task to be performed — the tell is a set of personal goals that don't add up to the unit performing.

• ▸Common unit goal: the shared objective this person's superior and they jointly identified
• ▸Major responsibility area: the one area of results this person owns
• ▸Expected result: what performance looks like, stated as an outcome not an activity
• ▸Measure/yardstick: the specific figure or signal used to read that result
• ▸Self-control check: how the individual will read this measure themselves without waiting for the boss
• ▸Cooperation/synchronization point: which other roles this result must sync with
• ▸Review finding: actual result vs. expected, and the contribution assessed
• ▸Next-cycle objective: the reset goal carried forward

1. 1Start staffing decisions with the question 'What can this person do?' — not 'What weaknesses must we screen out?' The passage is explicit: fill positions and promote to maximize strength, not to minimize weakness.
2. 2Design the job before you fill it. The trap is 'staffing to suit personality'; you avoid it by making sure the job is well designed and independent of the individual you happen to have in mind.
3. 3Make each job demanding and big. A large, demanding job forces the relevant strength to show and to carry the work, so that whatever the person cannot do becomes secondary to what they can.
4. 4Match the job's central demand to the one strength the candidate demonstrably has. Grant was chosen for one proven capability — winning campaigns — not for a balanced profile.
5. 5Decide to tolerate the accompanying weakness once the strength fits the central task. 'To get strength often means tolerating weaknesses'; the weakness is accepted, not excused, because it does not touch performance.
6. 6Use all available strengths, not just subordinates' — draw on the strengths of associates, of superiors, and your own; 'managing the boss' is part of making strength productive.
7. 7Structure the work so a real weakness cannot reach results. When the job is designed around the strength, the weakness is rendered irrelevant to performance rather than corrected.

Lincoln is told his new commander-in-chief, General Grant, is fond of the bottle. Having grown up on the Kentucky and Illinois frontier, Lincoln knows exactly what drinking and its dangers mean. But of all the Union generals, Grant alone had consistently proved capable of winning campaigns. So Lincoln keeps him — reportedly offering to send a barrel of Grant's brand to his other generals — because he is choosing for the one strength the central task requires: the ability to win battles. He does not choose for the absence of a weakness. Grant's appointment became the turning point of the Civil War. The effectiveness came precisely from making the strength productive and the drinking irrelevant to the result demanded.

• If a candidate has one strength that matches the job's central demand, then appoint — even with a known weakness attached.
• If you are screening primarily to avoid a weakness, then stop: you are minimizing weakness instead of maximizing strength, and will hire mediocrity.
• If a job seems to require a person with no significant weaknesses, then the job is mis-designed — redesign it to be demanding around a clear strength.
• If you find yourself tailoring the job to fit a specific person's personality, then you have fallen into the personality trap; design the job first, independent of the incumbent.
• If the weakness a strong performer carries does not touch the results the job demands, then tolerate it rather than trying to fix it.

• Staffing to minimize weakness — the tell is a candidate scorecard dominated by disqualifiers and 'no red flags,' producing safe hires who excel at nothing.
• Staffing to suit personality — the tell is that the job description shifts to match whoever is favored, rather than the person being matched to a fixed job.
• Designing timid, narrow jobs — the tell is that no single strength is decisive, so weaknesses become visible and dominant.
• Trying to correct the tolerated weakness after appointment — the tell is management effort spent 'fixing' Grant's drinking instead of exploiting his campaigns.
• Ignoring the strengths of superiors and yourself — the tell is a manager who only appraises subordinates and never 'manages the boss,' leaving available strength unused.

• ▸Central demand of the job: the one result this position must produce
• ▸Strength required: the specific capability that produces that result
• ▸Candidate's proven strength: evidence they have done exactly this
• ▸Job design check: is the job demanding and big, defined independent of any person? (Y/N)
• ▸Personality-trap check: am I reshaping the job to fit this person? (Y/N)
• ▸Known weakness: state it plainly, no euphemism
• ▸Weakness-vs-results test: does this weakness touch the central demand? (Y/N)
• ▸Tolerate/redesign decision: if weakness is irrelevant, tolerate; if it touches results, redesign or reject
• ▸Strengths to draw on: associates, superiors, and self relevant to this appointment

1. 1Start from key activities, not the org chart. Ask what work the organization must do to perform and contribute, then place that work in relation to the whole and its parts — this is the analysis before any boxes get drawn.
2. 2Apply a design principle deliberately. Fayol's functional principle organizes by kind of work (manufacturing, sales, engineering); know it is one option with strengths and limits, not the default.
3. 3Separate the manager definition from the professional-contributor definition. Establish parallel paths of opportunity so a person is paid for professional work without being forced into responsibility for the work of others to earn more.
4. 4Design for flexible assignment. Build task forces and teams where a traditional manager may serve as junior to a nonmanager, and a career professional may lead. Do not lock every relationship into a fixed boss/subordinate line.
5. 5Set pay to contribution, not to rank. Allow a star salesperson, researcher, or specialist to out-earn the manager they report to, on the performer model (athlete/prima donna needs a manager but earns more).
6. 6Study the work before staffing it, especially in middle management. Keep knowledge work lean; err toward understaffing because overstaffing destroys motivation, achievement, and performance.
7. 7Give the entrance job to knowledge workers room to plan their own work. Do not divorce planning from doing; the one best way is temperamental and individual, not fixed by an outside expert.
8. 8Name where the professional contributor sits so title, pay, and function stop being ambiguous — the traditional line definition is what creates that friction.

When Pierre S. du Pont and Alfred P. Sloan, Jr., set out in 1920 to bring order into the chaos of General Motors, the structural question was who ranks and who earns what. They first set the same salary for the heads of operating divisions as for the president, Pierre du Pont. Then Sloan — the operating vice-president to whom the division heads reported — asked, at his own request, to receive substantially less than the people who reported to him. The structure kept a clear reporting line (division heads to Sloan) while divorcing pay from that line. This is clarity of role without the friction of assuming the superior must always earn more. It models the performer principle: contribution, not organizational position, justifies the money.

• If someone is the pacesetter or leader in their field within the enterprise, then apply performer rules — pay for contribution — and accept that they may out-earn their manager.
• If the work is knowledge work, then keep the unit lean and err toward understaffing; if you cannot state what the work is and what it needs, do not add headcount.
• If a piece of work does not fit a line organization, then form a task force or team and assign leadership by fitness for the task, letting managers serve as juniors where appropriate.
• If a professional contributor's title, pay, and function feel ambiguous or are causing friction, then that is a structural signal to define parallel paths of opportunity rather than force promotion into management.
• If you are designing the entrance job, then build in the worker's own planning; if planning is stripped out and handed to an outside expert, the design will fail for knowledge work.

• Drawing the org chart first, then fitting people into it — the tell is job descriptions and appraisals that describe boxes, not the key activities the organization must perform.
• Tying all higher pay to promotion into a manager's job — the tell is dissatisfied, high-value professionals with no way up except supervising others.
• Assuming the superior must always earn more than the subordinate — the tell is a star salesperson capped below the regional sales manager, or a lead researcher who cannot out-earn their unit head.
• Overstaffing middle management during good times because acceding to demands for people is easier than fighting them — the tell is duplication of effort and 'organizational obesity,' with motivation and achievement quietly eroding.
• Treating structure as fixed line-only relationships — the tell is an inability to run task forces because no one can act as junior to a nonmanager or lead without a manager's title.

• ▸Key activity: name one activity the organization must do to perform
• ▸Contribution: state what result this activity must produce
• ▸Decision authority: who decides, and at what level, for this activity
• ▸Relationships: which other activities this depends on and feeds
• ▸Design principle applied: which principle organizes this work and why
• ▸Role type: manager (responsible for others' work) or professional contributor
• ▸Assignment mode: fixed line, or task-force/team with rotating leadership
• ▸Pay basis: rank-based or performer/contribution-based (justify)
• ▸Staffing check: is this unit lean — what work justifies each added person?

1. 1Start from the output the job must contribute to the enterprise, not from the motions available to be divided. Ask Rathenau's question of each role: what are its fundamental contributions and responsibilities to the whole?
2. 2Size the job as a large, demanding whole. Where the assembly-line foreman supervised fifty people doing fragmented motions, structure the automated-plant model: a team of two or three, each carrying greater autonomy, more responsibility, and far more decision-making power.
3. 3Build the job around making the incumbent's strengths productive and their weaknesses irrelevant — the specific job of management applied to job design itself. Match scope to the person's abilities and temperament rather than shrinking scope to the lowest common denominator.
4. 4Integrate multiple varied contributions into a central thrust, as the Sears story demonstrates: the job should require the holder to mold several inputs toward one organizational result, not to repeat one isolated step.
5. 5Load the job with challenge deliberately — the thrill of achievement and self-fulfillment come from a demanding integrated whole, so raise the bar to the level of the knowledge worker's capacity rather than de-skilling the task.
6. 6Push effectiveness (doing the right things toward contribution) over efficiency (doing fragmented things faster), reflecting the shift from laborers to knowledge workers.
7. 7Locate the job in relation to the entire organization and its parts — identify the work needed, then place it so its contribution to the central thrust is visible to the incumbent.

Take the automated oil refinery Drucker cites as already existing. The traditional design would fragment work into semi-skilled machine-operator motions under a foreman supervising fifty. The contribution-based redesign eliminates most operators and builds jobs for a few highly skilled technicians and professionals plus many managers — but each manager runs a team of only two or three, and each member holds greater autonomy, more responsibility, and far more decision-making power than the old foreman. The job is now a large integrated whole tied to plant output rather than a repetitive motion. Contrast this with the Ford story, Drucker's 'controlled experiment in mismanagement,' where the failure was refusing to structure genuine management jobs at all. The Sears story shows the positive test: the design succeeds when multiple varied contributions are molded into a central thrust. The measure is not motions saved but contribution made.

• If you can describe the job only as a set of repetitive motions, then you have not yet designed it — return to the contribution question before staffing.
• If a supervisor is overseeing a large span of people doing fragmented work, then the work is under-designed; integrate it into fewer, larger, more autonomous jobs.
• If the job holds no genuine decision-making power, then it will not develop a knowledge worker — add authority to match the demand.
• If the design optimizes efficiency (speed of a fragment) at the cost of effectiveness (contribution to the whole), then choose contribution.
• If varied contributions are not being molded toward one central thrust, then the job's scope is mis-cut and needs re-integration.

• Designing from the motions available rather than the contribution required — the tell is a job description that lists tasks but cannot name what the enterprise gains from the role.
• Breaking work into the smallest repetitive pieces to gain efficiency, then wondering why capable people stagnate — the tell is high span-of-control with low autonomy per person.
• Treating the knowledge worker like a semi-skilled operator — the tell is educated, expensive people given no decision-making power and no integrated whole.
• Confusing efficiency with effectiveness — the tell is metrics that measure how fast a fragment is done, never whether the right result is contributed.
• Assuming management jobs will emerge on their own as an operation grows, the Ford error — the tell is an organization that added scale but never deliberately structured autonomous, contribution-focused jobs.

• ▸Role name: the job being designed
• ▸Contribution to the whole: what the enterprise gains from this role (Rathenau's question)
• ▸Central thrust served: the one organizational result this job feeds
• ▸Integrated inputs: the varied contributions this holder must mold together
• ▸Decision authority: the specific decisions this holder owns
• ▸Autonomy/span: team size and independence granted vs. the old foreman baseline
• ▸Strengths made productive: what capacity of the incumbent this design uses
• ▸Effectiveness measure: how you'll judge right-things-done, not fragment-speed
• ▸Challenge level: why this job stretches a knowledge worker rather than de-skilling

1. 1Define the economic and performance objectives before assigning the work: management's first task is to make work productive and the worker achieving, so state what result the job must deliver, not what activity it must perform.
2. 2Translate organizational objectives down to each worker's contribution — the Sears principle of molding multiple, varied contributions into a central thrust applies at the individual level, so the worker sees how their output feeds the whole.
3. 3Give the worker the measurements that let them judge their own performance against the pre-agreed objectives, so managerial controls become self-controls rather than figures on paper used by a boss to police.
4. 4Widen autonomy and decision-making power as automation reduces supervision: in automated plants the span drops to two or three people, each with greater autonomy and responsibility, so structure the job to expect self-direction.
5. 5Have the worker set targets in their own terms, then confirm them against the enterprise's needs — objectives are agreed, not imposed, which is what makes the discipline internal.
6. 6Review results against the agreed measures, not against activity or presence, so the feedback loop reinforces self-correction rather than external command.
7. 7Treat the educated worker as an expensive resource ($40,000+ in education per college graduate, $50,000–$500,000 in the managerial job) whose productivity comes from self-direction, not close supervision.

Consider the shift Drucker describes from the traditional mass-production plant to the automated plant. On the assembly line, a foreman supervises fifty semi-skilled machine operators through direct command: the foreman tells each operator what to do and checks that they do it. In the automated oil refinery, the same manager has only two or three people, and each of them holds greater autonomy, more responsibility, and far more decision-making power than that foreman ever had. Command-and-control cannot scale down to two or three highly skilled people doing non-repetitive work — there is nothing routine to police. So the worker must direct their own work and measure it against clear objectives, because the manager is no longer standing over the task. The control that used to sit with the foreman now sits inside the worker, expressed through pre-agreed performance measures rather than supervision.

• If the work is non-repetitive or knowledge-based, then replace supervision with self-control by agreeing objectives and giving the worker their own measurements.
• If the worker cannot state how their contribution feeds the organization's central thrust, then the objectives are not yet clear enough to substitute for command.
• If you find yourself checking activity and presence rather than results, then you have reverted to external control and undermined self-control.
• If the objective was imposed rather than agreed, then expect compliance without internal discipline — re-negotiate so the worker owns the target.
• If automation or high skill has widened the worker's decision-making power, then push responsibility and measurement outward to match, or the resource is wasted.

• Handing over autonomy without handing over the measurements — the tell: the worker asks the boss 'how am I doing?' because they have no way to judge themselves.
• Setting objectives that management dictates and calling it self-control — the tell: targets read like orders and the worker has no share in defining them.
• Measuring the wrong dimension — controls stay as figures on paper instead of molding commitment to results; the tell is reporting that describes effort, not economic performance.
• Applying assembly-line supervision spans to knowledge work — the tell: a manager tries to oversee a large team of professionals the way a foreman oversaw fifty operators, and the professionals stall waiting for direction.
• Forgetting the resource cost — treating the educated worker as interchangeable labor rather than a $40,000–$500,000 investment whose return depends on self-direction; the tell is over-supervision that depreciates the resource faster.

• ▸Worker/role: whose work this covers
• ▸Central thrust link: the organizational objective this contribution feeds
• ▸Agreed objective: the result to deliver, stated as outcome not activity
• ▸Self-measurement: the specific number or signal the worker uses to judge own performance
• ▸Decision scope: what the worker decides without approval
• ▸Review cadence: when results (not activity) are compared to the objective
• ▸Agreement check: mark that the worker helped set this, not just received it
• ▸Resource note: the investment this role represents, to justify autonomy over supervision