Management Tasks Drucker

1. 1Start from the outside, not the inside: ask what result your institution owes society, community, and individual—since organs are defined by contribution, not by what they do or how. Write your mission first, then list impacts second.
2. 2Separate the two categories of impact management: negative impacts your operations create incidentally, and social problems in your community you might address. Handle them differently—the first you are responsible for minimizing, the second is optional opportunity.
3. 3Inventory every impact your activities cause on the surrounding community—not just those you intend. Because you are responsible for your impacts whether or not you meant them, list the incidental spillovers, not only the mission-driven outputs.
4. 4Rank impacts by whether you can eliminate them without damaging your mission. Where an impact can be minimized without impairing the function you exist for, minimize it; treat that as an obligation, not a discretion.
5. 5Screen each social problem for whether it can be converted into a business opportunity—a service, product, or process that both relieves the problem and pays. Where conversion is possible, that is the highest-value response.
6. 6Keep the craftsman's discipline first: perform the mission—goods, service, learning, patient care—before assuming impact responsibility. Impact management is added onto competent performance, never a substitute for it.
7. 7Treat impact management as culture-conditioned: read the values, beliefs, and commitments of your specific society and community, because management is a social function embedded in a tradition of values, and impacts land differently in different cultures.
8. 8Assume leadership responsibility beyond your institution's specific and limited mission, because in a society of institutions the managers are the leadership groups and someone must think through society's values and commitments.

General Motors is the passage's own case. Measured as a technocrat—by market standing, profit, or productivity—GM in the post-World War II period was an outstanding success: it did the first duty of a manager, making its institution perform its mission of producing goods and service. Yet at the same time GM was a resounding failure in public opinion, in politics, and in public esteem, and was forced onto the defensive instead of reaping rewards for its business success. The lesson the passage draws is that performing the mission is necessary but not enough: because any institution exists for the sake of society and within a community, it has impacts, and one is responsible for one's impacts. GM's defensive position shows what happens when a manager masters the craft of business performance but neglects the second task—managing social impacts and discharging social responsibilities. The remedy the passage points to is that the leadership group must think through the values, beliefs, and commitments of its society and assume responsibility beyond the discharge of its specific and limited mission.

• If an impact can be minimized without impairing your mission, then you are obligated to minimize it—minimizing is not optional where the mission is unharmed.
• If a social problem can be converted into a business opportunity, then treat that conversion as the preferred response over mere charity or containment.
• If you are succeeding as a technocrat but losing standing in public opinion, politics, and esteem, then read it as the GM signal that impact and responsibility are being neglected—not that performance needs more of the same.
• If the mission itself would be damaged by removing an impact, then the impact cannot simply be minimized away; it requires a responsibility judgment, not an operational fix.
• If you manage a public-service institution rather than a business, then apply the same impact task anyway—managing social impacts is a managerial task shared across mission types, not a business-only concern.

• Defining the institution by what it does or how it does it rather than by its contribution—the tell is a mission statement full of activities and outputs with no account of results owed to society.
• Treating business performance as sufficient and stopping at the craftsman's first duty—the tell is the GM pattern: rising profit and productivity alongside falling public esteem and a defensive posture.
• Counting only intended, mission-driven effects and ignoring incidental spillovers onto the community—the tell is that your impact list mirrors your product list exactly.
• Applying value-free, 'businesslike' technique to impacts while ignoring that management is culture-conditioned—the tell is a standardized impact program that reads identically across very different societies and communities.
• Confusing responsibility with rights and slogans—doing your own thing or demanding autonomy without accepting the corresponding impacts—the tell is language about entitlement replacing language about performance and accountability.

• ▸Institution's contribution: the needed result you owe society, community, and individual (not what you do)
• ▸Impact identified: a specific social/community consequence of your activities
• ▸Intended or incidental: mark whether this impact is mission-driven or a byproduct
• ▸Minimizable without harming mission? yes/no — and the operational step if yes
• ▸Convertible to business opportunity? describe the product/service/process that both relieves and pays
• ▸Cultural context note: values, beliefs, or community expectations that change how this impact lands
• ▸Responsibility owner: which manager/leadership group is accountable for this impact
• ▸Public-standing check: current standing in opinion/politics/esteem on this impact (the GM test)

1. 1Assign each worker responsibility for their own job AND for the performance of the work group — do not stop at task assignment; make the group's output a shared accountability.
2. 2Study the work itself before you assign it, following Taylor's break: do not take work for granted, look at it and analyze it so productivity gains are real, not assumed.
3. 3Make contribution visible: define the specific result the worker's effort feeds into (economic performance, student learning, patient care) so each person can see how their work connects to the institution's output.
4. 4Build in continuous learning by treating the job as a site where knowledge becomes productive — give the worker access to make a contribution through knowledge, not just execute a fixed task.
5. 5Measure performance where you can and use opinion where you cannot: business has profitability as a measure; if your unit lacks one, name explicit result-standards so satisfaction in performance has something to attach to.
6. 6Ground the worker's responsibility in performance, not rank or ownership — apply Shibusawa's principle that the essence is responsibility, extending it from managers down to every worker.
7. 7Frame the alternative honestly: autonomous, performing responsibility is the safeguard against imposed regimentation, so tie the ask for responsibility to the worker's own autonomy and dignity.

Robert Owen at his textile mill in Lanark in the 1820s became, in Drucker's account, the first manager because he was the first to tackle the relationship of worker to work, worker to enterprise, and worker to management as concrete problems rather than abstractions. He did not treat productivity and motivation as given; he attacked them directly on the shop floor. Taylor extended this in the 1880s by refusing to take work for granted — he looked at it and studied it, and his motivation was social: to free the worker from toil destructive of body and soul and to break the Iron Law of wages that condemned workers to poverty. His hope, largely fulfilled in developed countries, was to give the laborer a decent livelihood by raising the productivity of work. The lesson for building worker achievement: you raise both output and the worker's stake by studying the actual work and connecting higher productivity to the worker's own livelihood and fulfillment.

• If a unit has a genuine result-measure (like profitability), tie achievement to it; if it has only opinions, define explicit performance standards first — opinions are 'hardly an adequate foundation.'
• If you are tempted to assign a task and walk away, then instead study the work itself before assigning, because taking work for granted forfeits the productivity Taylor's method captures.
• If a worker's responsibility rests on rank or ownership, then reground it in responsibility for performance — those are incidental to the function.
• If people cannot see how their work contributes to the institution's needed result, then make the contribution explicit before expecting satisfaction in performance.
• If your only tool for engaging workers is imposed control, then reverse course — regimentation is the tyranny alternative, and only autonomous performing responsibility protects dignity.

• Treating management as practicing behavioral science or quantification rather than managing the worker toward achievement — the tell: metrics multiply but no one owns the group's result.
• Taking work for granted instead of studying it — the tell: you assign jobs and blame motivation when productivity stalls, never having looked at the work itself.
• Defining the job by what the worker does or how, rather than by contribution — the tell: activity is busy but no one can state the result the effort exists to produce.
• Grounding responsibility in rank or ownership instead of performance — the tell: authority is claimed by position while accountability for output goes unassigned.
• Imposing regimentation to force output — the tell: goods get produced 'fitfully, wastefully' at high cost in humiliation and frustration, and workers withdraw rather than take responsibility.

• ▸Job studied? — describe what you actually observed about the work, not what you assumed.
• ▸Individual responsibility — the specific job outcome this worker owns.
• ▸Group responsibility — the work-group performance this worker shares accountability for.
• ▸Visible contribution — the institution result (economic/learning/care) this work feeds.
• ▸Performance measure or standard — the profitability-like measure, or the explicit standard used in its absence.
• ▸Learning path — how this job lets knowledge become productive and grow.
• ▸Basis of responsibility — confirm it rests on performance, not rank or ownership.
• ▸Autonomy granted — the discretion the worker holds, as the alternative to regimentation.
• ▸Satisfaction check — how the worker will see and take satisfaction in performance.

1. 1Define the enterprise's business first — answer 'What is our business?' as Theodore Vail did for American Telephone. Until this is settled, unity has nothing to unite around. Every unit must be able to trace its work to this answer.
2. 2Distinguish performance from work. Passages insist there are no 'functional' results — only business results. Force every functional head to state how their work contributes to the whole enterprise's revenue, mission, or survival, not to their department's internal excellence.
3. 3Set both a present and a future object of common effort. Management 'always has to consider both the short run and the long run.' Make the time-balance explicit so specialized units don't optimize their piece against the enterprise's survival.
4. 4Translate the common mission into each unit's specific work. Since 'work and effort are always specific,' the tension between whole-enterprise performance and specialized work must be resolved deliberately — assign each unit contributions phrased in enterprise terms.
5. 5Build the top-management function that carries the vision, as Georg Siemens did at Deutsche Bank — 'first thinking through the top-management tasks, and first tackling the basic problems of communications and information in the large organization.' Unity fails without a structure that thinks through communication.
6. 6Add the social-impact and social-responsibility dimension. The manager's 'first duty is to make his institution perform the mission,' but the institution 'exists for the sake of society and within a community.' Include impacts in the common goal or you replicate General Motors' split.
7. 7Test every decision against results, not logic or effort. 'Its only authority is performance.' Judge unity by whether dispersed efforts converge on the mission, not by whether people feel aligned.

General Motors in the post-World War II period shows unity of effort achieved on one axis and lost on another. Measured technocratically — market standing, profit, productivity — GM was an outstanding success: its units clearly directed effort toward company performance. But it was 'a resounding failure in public opinion, in politics, in its standing in the public esteem,' and was 'forced on the defensive.' The vision uniting GM's units was too narrow: it covered mission (make cars, produce results) but not impacts and social responsibility. The passages draw the lesson directly — an institution 'exists for the sake of society and within a community,' so 'it is not a plant that pollutes; it is Consolidated Edison, Union Carbide, the paper industry.' Real unity of vision would have made responsibility for impacts part of the common goal that every GM unit understood and served, not an afterthought the technocrat treats as external.

• If a unit reports 'functional' results but cannot state its contribution to enterprise performance, then its effort is not yet unified — redefine its object in whole-business terms.
• If a proposed action improves present results by 'paying out capital' or endangering long-range survival, then reject it — present and future must both be satisfied, not traded.
• If the common mission covers performance but ignores social impacts and responsibility, then treat unity as incomplete — the GM failure mode is latent.
• If the organization has grown large but no one has 'thought through the top-management tasks' and communication, then vision cannot propagate — build that function before scaling further.
• If a manager produces startling results personally but 'leaves behind nothing but a sinking hulk,' then his unity was around his person, not the shared mission — that result is fictitious.

• Uniting effort around efficiency instead of effectiveness. The tell: everyone asks 'How do we do this better?' and no one asks 'which product, market, or opportunity should we serve?' — focus on costs signals the wrong common goal.
• Letting specialization fragment the whole. The tell: departments defend technical accomplishment (Towne's warning) while enterprise results stagnate — 'value set in the marketplace' loses to 'technical accomplishment.'
• Technocrat's blind spot. The tell: strong performance numbers alongside collapsing public standing and defensiveness, exactly as at General Motors — the shared vision omitted impacts.
• Present-future imbalance. The tell: 'startling economic results' during one leader's tenure followed by decline — capital was paid out and dressed up as profit.
• Confusing style or feeling with substance. The tell: talk of alignment and 'style' rather than character and results — but 'style tends to be manner rather than substance,' and management's only authority is performance.

• ▸What is our business? — one sentence answering it as Vail did
• ▸Enterprise mission and object — the common goal all units serve
• ▸This unit's contribution — stated in whole-business results, not functional terms
• ▸Present object — what this effort must achieve short run
• ▸Future object — what long-run health/survival this effort protects
• ▸Social impacts owned — what impacts of our work we are responsible for
• ▸Communication path — how the vision reaches this unit from top management
• ▸Performance test — the result that proves effort converged on the mission

1. 1Reward what you want. People behave as they are rewarded, so audit every reward signal — money, promotion, medals, a pat on the back — and confirm it points at performance and contribution, not at not-alienating constituents or protecting budgets.
2. 2Focus effort on opportunities where performance and results are both needed and attainable; refuse to double the 'missionary effort' on areas that no longer produce contribution.
3. 3Institute organized abandonment: treat everything you do today as a candidate for abandonment within a fairly short period, and stop putting your best and ablest people on defending what no longer serves a purpose.
4. 4Make strengths productive by placing high-cost, high-knowledge people (managers, researchers, planners, designers, innovators) where their knowledge is applied, not misapplied — knowledge misapplied is totally unproductive.
5. 5Attack idle time: there is nothing less productive than idle expensive equipment or wasted time of able people. Track whether men and machines are utilized steadily.
6. 6Build integrity into people decisions — appraise and promote for contribution to performance, never for participation in voluntary or community activities, which must stay voluntary.
7. 7Where no market feedback exists (governance-type activities), install organized, independent audit of promises, assumptions, and performance as the substitute discipline for results feedback.

Drucker describes a company whose marketing services staff audits the marketing standards and performance of every unit. Roughly eighteen to twenty divisional and territorial managers use the internal marketing staff, eleven or twelve use outside consultants, and about a dozen use no service staff at all. The marketing results show no correlation to method — the best and the poorest performers are spread across all three approaches. The point of the spirit of performance shows up in what happens even among the weakest: 'Even the poor performers in this company have remarkably high standards and good marketing results.' The staff itself is among the best in effectiveness, performance, and in its spirit and enthusiasm. So the culture of high standards, not the choice of tooling, is what carries results across the whole organization.

• If an activity no longer produces contribution, then abandon it and redeploy your ablest people — do not fund it as a redoubled missionary effort.
• If a reward (pay, promotion, recognition) is attached to anything other than performance and contribution, then it is misdirecting behavior and must be changed.
• If an institution is paid by budget or monopoly rather than by satisfied customers, then it is rewarded for what it deserves, not what it earns — install independent audit of objectives, priorities, and results.
• If community or voluntary activity is being appraised, rewarded, or forced, then stop: pressuring managers into it is illegitimate abuse of organizational power.
• If expensive equipment or highly paid, able people sit idle, then treat that idle time as the biggest productivity loss and act before chasing visible cost cuts.

• Clinging to yesterday: doubling effort to defend what no longer makes sense. Tell — the best people are assigned to protecting obsolete programs rather than to opportunities.
• Managing for absence of discontent (satisfaction) instead of energy and performance. Tell — human/industrial relations aimed at 'no complaints' with no rise in contribution.
• Measuring only visible, direct costs the accountant tracks. Tell — decisions ignore knowledge misapplied and wasted time because they never surface as cost figures.
• Carrying parasitic overhead born of mismanagement — high-priced personnel needed only because of mal-organization, poor spirit, or confused objectives. Tell — headcount justified by internal disorder, not by contribution.
• Letting budget-based logic define performance as 'what will produce the budget.' Tell — success is reported as programs launched and constituents not alienated, not as results delivered.

• ▸Activity/unit: name the function under review
• ▸Contribution: what result it produces, and whether that result is still needed and attainable
• ▸Reward signal: what behavior current pay/promotion/recognition actually reinforces
• ▸Best-people placement: are your ablest assigned to opportunity or to defending yesterday?
• ▸Abandonment candidate: what here would you not start today, and by when do you drop it?
• ▸Idle-resource check: where is expensive equipment or able people's time being wasted?
• ▸Integrity flag: any appraisal/promotion tied to something other than performance?
• ▸Feedback source: market results, or (if none) the independent audit that substitutes for it
• ▸High-standard test: do even weak performers here still hold remarkably high standards?

1. 1State the institution's specific mission first: for a business, economic performance; for a hospital, church, or university, economics is a restraint, not the purpose. Do not blur these.
2. 2Define your business by answering 'What is our business?' in terms of the customer to be satisfied, not the product you make or the internal jobs you supply. DLJ answered it as 'provide financial services, financial advice, and financial management to the new capitalists, the institutional investors.'
3. 3Ground performance in the two economic functions: marketing (identifying and satisfying a customer) and innovation (technical and social). Assign explicit responsibility for both.
4. 4Test the result by profitability: confirm you supply goods/services the customer desires at a price the customer will pay, and that you at least maintain the wealth-producing capacity of the resources entrusted to you.
5. 5Run the existing managerial organization and a new innovative organization simultaneously, since in existing large firms both the trained people and the money for the new are already concentrated there.
6. 6For a public-service institution, refuse the shortcut of making management 'businesslike.' Instead perform the four managerial tasks against that institution's own mission: perform the function it exists for, make work productive and the worker achieving, manage social impacts, and discharge social responsibilities.
7. 7Judge everything by results, not logic or style: management's only authority is performance. If it fails to produce the specific economic results, the management has failed regardless of intentions.

Donaldson, Lufkin, and Jenrette (DLJ) was founded by three men out of business school with little except an idea, yet rose within five or six years to seventh place among Wall Street houses. Their performance came from answering 'What is our business?' correctly: to serve the new institutional investors—pension funds and mutual funds—which by 1950 were becoming the dominant force in the American capital market. This answer went counter to everything the rest of Wall Street then knew, but 'right answers always are' obvious in retrospect. DLJ then became the first Wall Street firm to sell its shares to the public and began the long-overdue broadening of Wall Street's capital base that thoughtful people had seen needed for thirty years. Here performance is not size but the creation of a satisfied customer (institutional investors) through both marketing (spotting the dominant channel of savings) and innovation (going public, opening the exchange from private club to service institution). The firm's rapid rise to a leadership rank is the visible test that the mission was fulfilled.

• If the institution is a business, then put economic performance first in every decision; if it is a hospital, church, university, or armed service, then treat economics as a restraint, not the purpose.
• If you cannot name the customer whose desire your goods or services satisfy, then you have not yet defined your business and cannot measure performance.
• If a decision does not improve or at least maintain the wealth-producing capacity of the resources entrusted to you, then it fails the profitability test even if it looks active.
• If the new opportunity requires developing and applying new technology or social innovation, then locate it inside the existing organization, because the trained people and money are concentrated there.
• If someone proposes curing a public-service institution's ills by making it 'businesslike,' then reject it and instead apply the four managerial tasks against that institution's own mission.

• Treating size as performance. Standard Oil's daughters grew fourfold yet only three became major companies—growth is not the same as fulfilling the mission. Tell: reports lead with headcount, capital, or sales rather than customers satisfied.
• Defining the business by the product in the garage rather than the customer. The tell: the founder never asks 'What is my business?' once he must hire people and choose channels, and drifts as the product catches on.
• Forgetting the institution exists to contribute outside itself. Running a business to supply jobs to workers and managers, or a hospital for the sake of doctors and nurses, is mismanagement. Tell: internal stakeholders' comfort dominates the agenda over the nonmember it serves.
• Copying business methods into a public-service institution. The tell: a hospital or agency adopts profit-style metrics that fit no mission it actually has, and the managerial ills persist.
• Running only the existing organization and starving innovation. Tell: management is competent at operations but has no innovative organization running alongside, so new technology and social innovation happen elsewhere.

• ▸Institution type: business (economic performance = purpose) or non-business (economics = restraint)
• ▸Mission statement: the one function this institution exists to perform
• ▸What is our business?: answer stated as the customer to be satisfied
• ▸Marketing: who the customer is and what desire is being satisfied at what acceptable price
• ▸Innovation (technical and social): the new thing being developed and applied inside this organization
• ▸Profitability test: how you confirm wealth-producing capacity is maintained or improved
• ▸Contribution outside itself: the nonmember (customer, patient, student) served
• ▸Existing vs. innovative organization: how both are being run at once
• ▸Performance verdict: results produced (not intentions or style)

1. 1Start by refusing to take work for granted, as Taylor did: look at the actual task and study it rather than assuming the existing method is fixed. Break each task into its component motions and steps before optimizing anything.
2. 2Distinguish effectiveness from efficiency (Towne's question). Ask 'which work should be done at all?' before 'how do we do this work better?' — allocate effort toward extraordinary results, not incremental improvement of the wrong thing.
3. 3Organize the work and separately organize the workers. Towne separated 'organization of the work' from 'organization of the plant community, that is, of the workers' — treat these as two distinct managerial jobs.
4. 4Set the social objective alongside the productivity objective: Taylor sought to free the worker from heavy toil destructive of body and soul, and to raise livelihood by raising productivity. Design work so higher output funds a decent wage.
5. 5Balance all factors of production — capital, physical resources, and human effort (manual and knowledge-based) — to get greatest output for smallest effort, rather than maximizing any single factor in isolation.
6. 6Apply the optimizing lens: ask which products and which markets/end-uses produce or can produce extraordinary economic results, then concentrate resources there rather than spreading effort evenly.
7. 7Lead the worker toward productivity and achievement, not just measure output. Management's shared task everywhere is both to organize work for productivity and to lead people toward it.

Robert Owen at his textile mill in New Lanark in the 1820s became the first manager by tackling productivity and motivation together rather than treating labor as a fixed cost. He confronted the relationships of worker to work, worker to enterprise, and worker to management — the same key questions management still faces. Unlike the abstractions in Say, Fourier, and Hamilton, Owen worked as a real person on a real shop floor, linking how work was organized to how workers were motivated. Decades later Taylor extended the same instinct by studying work itself for the first time, aiming to break the Iron Law of wages that condemned workers to poverty. Taylor's hope — largely fulfilled in developed countries — was that raising the productivity of work would give the laborer a decent livelihood. Both cases show the construct in action: output rises not by demanding more toil but by studying and reorganizing the work so effort yields more.

• If you are asking 'how do we do this better?' before asking 'which results deserve resources?', then stop — decide effectiveness (right work) before efficiency (better method).
• If a task has never been studied and is merely inherited, then examine and break it down rather than assuming the current method is optimal.
• If gains in output come only from harder human toil, then you have not raised productivity — redesign the work so the same or less effort produces more.
• If organizing the task and organizing the workers are treated as one problem, then separate them; they are distinct managerial jobs with distinct approaches.
• If one factor of production is maximized while others are starved, then rebalance — productivity is the balance across capital, physical resources, and human effort.

• Taking work for granted: never studying the task itself. The tell — no one can describe the component steps of a job or why they are done that way.
• Confusing efficiency with effectiveness: polishing the wrong work. The tell — heavy improvement effort on products or markets that cannot produce extraordinary results.
• Treating labor purely as cost to be minimized (the technocrat trap). The tell — productivity numbers rise while the relationship of worker to enterprise deteriorates.
• Chasing productivity through longer or heavier toil rather than better-organized work. The tell — output gains vanish when you account for worker burnout or turnover.
• Optimizing one factor of production in isolation. The tell — capital utilization looks excellent but total output per unit of combined effort is falling.

• ▸Task studied: name the specific task you are examining rather than assuming its method
• ▸Component steps: list the actual motions/steps that make up the task
• ▸Effectiveness check: which result does this work produce, and is that result extraordinary or marginal?
• ▸Right-work decision: keep, redesign, or eliminate — and why
• ▸Factor balance: note current use of capital, physical resources, manual effort, knowledge effort
• ▸Effort-to-output ratio: what output does current effort yield; where is effort wasted?
• ▸Worker relationship: how does this design affect worker-to-work, worker-to-enterprise, worker-to-management?
• ▸Social objective: does the redesign reduce destructive toil and support a decent livelihood?
• ▸Reallocation: where will freed resources and effort be moved to produce extraordinary results?

1. 1Set a minimum growth objective before any expansion target: ask what growth rate the company needs merely to hold viable market standing, because falling below it turns you marginal and, in effect, the wrong size.
2. 2Read the growth minimum off the market, not the ambition — in a fast-expanding market (pharmaceuticals, computers in the fifties/sixties) staying even demands very fast growth; in a flat market (developed-country textiles) minimum growth means identifying and concentrating on the best segments.
3. 3Score growth economically, not physically: track contribution to economy and society, productivity of men/capital/materials, and profitability — treat rising volume alone as irrelevant.
4. 4Organize the innovating task separately from the operating task: decentralization runs an ongoing business but does not answer the demands of innovation, so use a distinct structure (task-force team, simulated decentralization, systems organization) for creating the business of tomorrow.
5. 5Build manager development around adapting the organization to people's needs, aspirations, and potential — not merely adapting the individual to the organization, and not settling for absence of discontent.
6. 6Engineer the management structure for age balance: avoid a job structure focused on rapid promotion, because it produces an age structure overbalanced toward youth and a group of the same age headed for crisis.
7. 7Cap the number of levels a person must traverse to reach top management so an able person entering management at twenty-five can normally reach the top rungs while still effective; audit the structure against the self-renewal specification of producing tomorrow's leaders from within.
8. 8Test each design against the perpetuation/self-renewal specification: can this structure prepare and test a person on each level for the level above, and adapt to new situations, demands, and faces without becoming brittle?

GE's strategic business planning inverts the usual growth question for viability. It does not first ask 'What markets have the greatest growth potential?' It asks instead: 'What is the minimum growth of each market? Can we expect to keep up with it? What market segments — even in the slow-growth markets — offer the best opportunities for us?' This forces each business to first secure its minimum viable standing rather than chase volume. A paper company applying this would reject the Gypsy Moth's logic of using up more wood each year as an inane objective, and measure itself by economic performance instead. The result is a rational growth policy grounded in viability, not the desire or promise to grow that collapsed in the sixties growth craze.

• If the market is expanding domestically or worldwide, then the company must grow with it to maintain viability — a high minimum growth rate is mandatory, not optional.
• If overall market growth is low, then set minimum growth as concentration on the most promising segments rather than as aggregate volume.
• If the task is running an ongoing business with distinct markets for distinct product lines, then use federal decentralization; if the task is innovation, then use a separate innovating structure because decentralization does not fit it.
• If a job cannot make an identifiable contribution and hold its holder accountable (the typical 'assistant to'), then do not create it — such a job corrupts into wire-pulling or toadying.
• If a company is expanding rapidly, then bring in a few seasoned older outsiders, because filling every important post with young insiders creates expectations you must later frustrate.

• Declaring 'we want growth' without a rational growth policy — the tell is targets justified only by the desire or promise to grow, with no stated minimum-viability threshold.
• Measuring growth as volume — the tell is celebrating using up more resources per year (the Gypsy Moth error) rather than contribution, resource productivity, and profitability.
• Treating decentralization as the universal model — the tell is applying the General Motors template (one product line, one national market, manual labor) to service, process, or multi-market institutions where it does not fit.
• Building the structure around rapid promotion — the tell is a management group of uniform age and a job ladder that leaves capable forty-year-olds bored, cynical, and frustrated.
• Confusing simplicity with clarity in structure — the tell is the 'modern office building' organization where no one can find their way without an elaborate manual, versus the complex-but-clear Gothic cathedral where everyone knows where they stand.

• ▸Minimum growth rate: the growth below which this business loses strength or viability
• ▸Market trajectory: is the served market expanding, flat, or contracting — and at what rate
• ▸Priority segments: the best-opportunity segments to concentrate on, even in slow-growth markets
• ▸Economic growth measure: contribution, resource productivity, and profitability targets (not volume)
• ▸Innovation structure: which unit/mechanism creates the business of tomorrow, held separate from operations
• ▸Levels to top: number of levels a 25-year-old must traverse to reach top management
• ▸Age balance check: current distribution — flag if overbalanced toward youth or age
• ▸Outsider intake: seasoned outsiders planned for key posts to prevent frustrated internal expectations
• ▸Self-renewal test: how each level prepares and tests a person for the level above

1. 1Start from the premise that your institution is now the agent for a major social task once handled by the family—economic performance, health care, education, environmental protection. Name explicitly which social task society has entrusted to you, because that entrustment is the source of your social responsibility.
2. 2Treat work itself as your first social contribution. Since work is the primary access to society and community in the employee society and largely determines status ('I am a doctor,' 'I am a plumber'), design jobs so they satisfy the worker's need for belonging and meaningful relationship, not just output.
3. 3Audit your economic rewards through the Herzberg lens: economic rewards no longer motivate as incentives once satiety approaches, but they create deep dissatisfaction if disappointed ('hygiene factors'). Get pay and differentials right so they do not become deterrents that unite the group against the institution.
4. 4Manage pay differentials as power-and-status decisions, not just numbers. Because the organization is a redistributive economy, relative rewards signal the worth of a person or group; misjudge them and you alienate both the recipient and everyone watching.
5. 5Mobilize 'positive dissatisfaction'—impatience with poor methods and the desire to do a better job—rather than only suppressing negative dissatisfaction (frustration, speed-up, poor conditions). Use continuous training, as the Japanese do, to make positive dissatisfaction productive and the workforce receptive to change.
6. 6Set the standard of responsible autonomy: perform the entrusted task on a high level so the institution earns its license to exist. The alternative to institutions that perform responsibly is not freedom but totalitarian tyranny that submerges all institutions in one bureaucracy.
7. 7Anticipate the social-responsibility problems your own reward system creates—for example, managerial carrots that grow 'from small bonuses to massive stock option plans'—and relate the growing demand for 'much more' back to productivity and profitability instead of pretending they are unlimited.

Consider the two vice-presidents in the same company whose salaries are only a few hundred dollars apart. At that level the income tax makes the differential economically meaningless—they are effectively equals. Yet the lower-paid vice-president may be 'eaten up by frustration and envy,' and no matter how good his income it stays a thorn in his side. The lesson is that the reward's power to satisfy has fallen to near zero while its power to demotivate remains high. The same pattern runs all the way down: every trade-union leader's biggest problem is not absolute pay scales but the differentials among kinds of workers within his union. So the social contribution of getting rewards right lies not in paying 'more' but in managing relative worth so the group is not divided against itself and united against the institution.

• If a want (economic or otherwise) is approaching satiety, then stop relying on it as a positive incentive and treat it instead as a hygiene factor you must not disappoint.
• If you are setting relative rewards, then treat them as status and power judgments on a person's worth—and check whether they will unite the group against the system.
• If workers show impatience with poor methods and a desire to do better (positive dissatisfaction), then channel it through training and improvement rather than merely resolving complaints.
• If your incentive structure (e.g., stock options for managers) grows into 'seven-course Victorian meals,' then flag the social-responsibility problem and re-anchor rewards to productivity and profitability.
• If people respond to being driven with learned resistance ('losers' who perfected resistance), then abandon carrot-and-stick and build motivation through achievement and belonging instead.

• Assuming rejection of the work ethic means hedonism. The tell: you dismiss educated young workers as lazy, missing that they assign high positive value to demanding work like teaching and art—work is being reshaped, not abandoned.
• Believing more money always motivates. The tell: rising pay produces rising dissatisfaction and inflationary pressure, because reward's capacity to deter grows even as its capacity to incentivize shrinks.
• Treating pay differentials as mere accounting. The tell: employees just a few hundred dollars apart are consumed by envy, and your union counterpart's hardest fight is internal differentials, not absolute scales.
• Suppressing all dissatisfaction indiscriminately. The tell: you quiet the negative complaints but also kill the positive dissatisfaction—the demand for better, more systematic management—that drives improvement.
• Answering the 'down with organization' revolt by weakening the institution rather than making it perform. The tell: you pursue autonomy without responsibility, and the practical result is not freedom but regimentation.

• ▸Entrusted social task: the major social task society relies on this institution to perform
• ▸Work-as-community check: how do jobs here give status and belonging beyond a paycheck
• ▸Hygiene-factor status: where are economic rewards currently creating dissatisfaction if disappointed
• ▸Differential map: list relative pay gaps and the worth/status message each one sends
• ▸Alienation risk: which reward decisions could unite the group against the institution
• ▸Positive dissatisfaction sources: where do people want to do the job better, and how are you capturing it
• ▸Training-to-change link: how continuous training turns that impatience into productive improvement
• ▸Self-created responsibility problems: which of your own incentives (e.g., outsized manager rewards) need re-anchoring to productivity
• ▸Responsible-autonomy standard: what level of performance justifies this institution's license to exist

1. 1Ask the three questions in sequence, not once but as a discipline: 'What is our business?', 'What will it be?', and 'What should it be?' Treat the last two as forcing questions about change, not restatements of the present.
2. 2Define the business from the customer's perspective, not the producer's. Start by asking what the customer buys, what value they see, and what they consider results — the answer determines what your business actually is.
3. 3Convert the mission answer into concrete objectives before building anything else. The mission is the foundation; objectives, strategy, and organization structure all derive from it, in that order.
4. 4Run the four analyses when structure gets built on the mission — key-activities analysis, contributions analysis, decisions analysis, and relations analysis — so that structure follows the strategy the mission demands rather than 'typical function' or 'staff and line' templates.
5. 5Test every activity against the mission: is it a key, revenue-producing activity for this purpose? If it is (as with product development in an innovation-seeking business), give it standing rather than subordinating it to another function.
6. 6Focus attention on major business decisions, key activities, and results — not on procedure, etiquette, or jurisdiction. Where the mission is clear, people's attention lands on performance; where it is fuzzy, they drift to secondary problems.
7. 7Judge the whole exercise by results, not logic or elegance. The test of clarity of mission is performance: whether the institution delivers the goods, service, learning, or patient care for which it exists.

Take the recurring organization problem of where to place product development. Practitioners keep shuffling it — subordinate it here, attach it there — and it keeps coming back as a problem. That recurrence is the tell: it signals 'lack of thinking, lack of clarity, and lack of understanding' about the mission. In a business that wants innovation, product development is a key, revenue-producing activity central to the purpose of the business. Once you answer 'What should our business be?' as innovation, the placement resolves: product development should not be subordinated to any other activity but organized as a separate innovative component. The clarity of mission dissolves the structural argument that endless box-shuffling could never settle.

• If you cannot state what your business is from the customer's point of view, then you have no foundation for objectives — stop and answer that first.
• If an organization problem returns more than a couple of times, then treat it as evidence of unclear mission, not as a chart problem to solve mechanically.
• If an activity is key and revenue-producing to your defined purpose, then give it separate standing rather than subordinating it to a 'typical function.'
• If your structure directs key people's attention to procedure, etiquette, or jurisdiction, then the mission has failed to drive the design and organization has become a bar to performance.
• If you are choosing structure for symmetry rather than performance, then you are slapping on principles instead of thinking through what the strategy of the business demands.

• Answering 'What is our business?' from the producer's side (what you make) rather than the customer's (what they buy and value) — the tell is objectives that describe your operations, not customer results.
• Treating the mission question as a one-time founding statement rather than a recurring discipline that includes 'what will it be' and 'what should it be' — the tell is a mission that never anticipates change.
• Building structure from 'organization principles' before the mission and strategy are defined — the tell is a recurring problem you keep solving by moving boxes on paper.
• Chasing an elegant, symmetrical organization chart as if the chart were the organization — the tell is pride in the diagram while performance lags; no chart hangs in an art museum.
• Succeeding as a technocrat on internal metrics while losing sight of the wider purpose and impact — the tell is General Motors: outstanding in market standing, profit, and productivity, yet a resounding failure in public standing because mission was read too narrowly.

• ▸Current business definition — state what our business is, phrased in the customer's terms
• ▸Customer and what they buy — name the customer and the value or result they actually purchase
• ▸What it will be — describe how the business changes as the market and customer change
• ▸What it should be — state the purpose you intend to pursue, including new directions
• ▸Key revenue-producing activities — list activities essential to this purpose (flag any wrongly subordinated)
• ▸Objectives derived — write the concrete objectives that follow from the mission above
• ▸Attention check — note where key people's attention currently lands (results vs. procedure/jurisdiction)
• ▸Recurring problems — record any organization problem that has returned more than twice as a clarity signal
• ▸Performance test — define the result that proves the mission is being served

1. 1State the institution's mission and the specific result it exists to contribute to society, the economy, and the individual — organs are defined by contribution, not by activity, so name the outcome (economic performance, student learning, patient care) before naming any objective.
2. 2Translate that mission into the enterprise's overall objectives, then push the translation downward so each unit and each manager holds a share of the whole result rather than a functional silo.
3. 3Have each manager draft his own objectives against those enterprise goals — the manager participates in setting them, so the goals are commitments, not commands handed down.
4. 4Reconcile the manager's proposed objectives with the enterprise's direction: keep them where individual effort demonstrably aligns with the enterprise result; revise where a manager's local optimization would fragment the whole.
5. 5Make the agreed objectives measurable and specific enough to serve as the manager's own standard — the point is that he can read his own performance without waiting to be told.
6. 6Give the manager the information to control himself against those objectives, so appraisal is self-directed first; management directs and the manager self-controls rather than being contained.
7. 7Review results against the stated objectives, treating gaps as data about the objective or the resources, not merely as personal failure — the stress stays on accomplishments and results throughout.

When Canada in the late sixties first combined army, navy, and air force into a single unified military service, its very first conference of generals and admirals was not on strategy — it was on 'management by objectives.' The reason fits the construct: a newly merged institution has one overall mission but three inherited command cultures, so its first task is to translate that shared mission into specific objectives each service branch and each officer can own. Strategy could not be set coherently until the combined leadership agreed on common objectives that would become the standard for each command's self-control. The generals and admirals were, in effect, doing the translation step — turning one mission into aligned unit objectives before deciding how to pursue them. This is why the same tool drew Canadian officers, the Jesuits, the German civil service in Hamburg, and the British civil service: any institution built from formerly separate parts needs objectives to align individual effort with the whole.

• If a manager cannot state his objective as a measurable standard he could check himself against, then it is not yet an objective — keep working it before appraising on it.
• If a manager's local goal would optimize his unit at the expense of the enterprise result, then revise it toward the enterprise contribution — alignment governs.
• If the objective was handed down without the manager's participation, then treat it as a directive, not an MBO objective; self-control requires he helped set it.
• If the institution is newly merged or restructured, then run the objectives conversation before the strategy conversation, as the unified Canadian service did.
• If appraisal depends on someone else reporting the result, then the manager cannot exercise self-control — redesign so he gets the information first.

• Defining units by what they do or how they do it rather than by their contribution; the tell is objectives written as activities ('run more meetings') instead of results.
• Handing objectives down and calling it MBO; the tell is that no manager can recall participating in setting his own goals.
• Treating the practice as control-by-management rather than self-control; the tell is that managers wait to be told their numbers instead of reading them themselves.
• Letting each unit optimize locally so the enterprise result fragments; the tell is strong unit metrics alongside a weak overall contribution.
• Adopting the tool as a technique divorced from mission; the tell is objectives set with no line traced back to the institution's reason for existing.

• ▸Institution mission / result contributed: name the outcome the institution exists to produce
• ▸Enterprise-level objectives: the overall goals mission translates into
• ▸This manager's / unit's share of the result: the piece of the whole owned here
• ▸Manager-drafted objectives: goals the manager himself proposes
• ▸Measurable standard: how the manager will read this objective without being told
• ▸Self-control information source: the data the manager gets to check himself
• ▸Alignment check: how this objective serves the enterprise, not only the unit
• ▸Review point: when results are compared against the stated objective

1. 1Take one factor of productivity — labor — and analyze it into individual pieces of work, following Taylor's method: do not take work for granted, look at it and study it as constituent tasks.
2. 2Synthesize the analyzed pieces back into a production process by applying the principles of production; ask how the separate tasks combine into the most productive sequence, not just how each task is done efficiently in isolation.
3. 3Widen the productivity frame beyond labor: assess land, labor, and capital together, in balance, since productivity is the output of all three factors of production, not one.
4. 4Distinguish the logic of work from the logic of the worker and design to harmonize the two — the process has its own requirements, the person has different requirements, and the job must satisfy both.
5. 5Design each job to be large and challenging: give the worker responsibility for results, not just a fragment of a task.
6. 6Build feedback into the job so the worker gets the information needed for self-control — the worker measures and corrects their own performance rather than waiting to be directed.
7. 7Lead the worker toward productivity and achievement, treating motivation and the relationship of worker to work as management's responsibility, not the worker's alone.
8. 8Judge the design by results and accomplishments — economic performance, output — not by how busy or technically refined the plant is.

Robert Owen at his textile mill in New Lanark, Scotland, in the 1820s became the first actual manager by treating work and worker as a management problem rather than a given. He did not stop at organizing machines or plant; he tackled the problems of productivity and motivation directly, and worked the relationship of worker to work, worker to enterprise, and worker to management. These were not abstractions for him as they were for Say, Saint-Simon, or Hamilton — with Owen the manager emerges as a real person addressing the concrete question of how to make workers productive while sustaining their relationship to the job. The passages note these remain, to this day, the key questions in management. Owen's example shows the two halves of the construct in one place: the work must be organized for productivity, and the worker must be led toward productivity and achievement. It also shows the trap of premature success — Owen had no successors for a long time, because the design questions he raised were harder than the technical ones around them.

• If you are measuring only labor productivity, then you have taken only the first step — bring land and capital into the same balance before claiming a productivity gain.
• If your productivity gains have historically come from moving people out of low-productivity work (e.g., subsistence farming) into high-productivity industry, then once that migration is exhausted you must instead make existing workers more productive in existing jobs.
• If a job gives the worker no feedback, then it cannot support self-control or achievement — redesign it to return performance information to the person doing it.
• If you are optimizing efficiency (doing things right) without asking about effectiveness (doing the right things, value set by the customer), then you are following Towne's warning and organizing the plant instead of the work.
• If the work's logic and the worker's logic conflict, then design to harmonize both rather than sacrificing one — neither the process alone nor the person alone is the unit of design.

• Focusing on one factor — labor — as the whole of productivity; the tell is a productivity report that never mentions capital or land utilization.
• Stopping at analysis (breaking work into pieces) and never performing synthesis; the tell is optimized individual tasks that do not add up to a more productive process.
• Confusing efficiency with effectiveness — organizing the plant and the workers rather than the work itself; the tell, per Towne, is high technical accomplishment with weak value in the marketplace.
• Designing small, fragmented jobs stripped of responsibility and feedback, then blaming the worker for low motivation; the tell is that management treats motivation as the worker's problem instead of a design responsibility.
• Assuming past sources of productivity gains still apply — relying on migration from low- to high-productivity employment after that capacity is exhausted; the tell is flat output with no new job design and the excuse that gains 'used to come easily.'

• ▸Task inventory: list the constituent pieces this work analyzes into
• ▸Process synthesis: describe how those pieces combine into the productive process
• ▸Three-factor productivity check: state current output of land, labor, capital in balance
• ▸Effectiveness vs efficiency: name the result/value the customer sets for this work
• ▸Job scope: describe how the job is made large and challenging (not a fragment)
• ▸Responsibility: state what result the worker owns end-to-end
• ▸Feedback loop: specify the information returned to the worker for self-control
• ▸Work-vs-worker fit: note where the process logic and the person's logic conflict and how you harmonize them
• ▸Achievement path: describe how management leads this worker toward productivity and achievement

1. 1Start with the mission, objectives, and strategy of the enterprise before you draw any boxes — 'structure follows strategy,' so define what the business is and what results it must produce first.
2. 2Identify the key activities that carry the strategy: ask which contributions the organization must perform excellently to achieve its objectives, not which functions are conventional or comfortable.
3. 3Position each key activity where it can perform and where it commands attention — key activities determine and shape management jobs, work, and organization, not the reverse.
4. 4Select a design principle that fits the size and task: functional structure for concentrated single-mission work, federal decentralization for autonomous businesses with their own objectives (the Du Pont/Sloan model), team structure where cross-work coordination dominates.
5. 5Design communication flows so that decision-making, both formal and informal, reaches the people who must act — balance formal structure with the policies that give an organization its 'soul.'
6. 6Test the resulting structure against performance: an organ is defined by its contribution, so ask whether each unit produces a needed result rather than whether it looks tidy.
7. 7Revisit structure whenever strategy shifts — since structure is a means to an end, a change in objectives should trigger redesign, not preservation of what had been.

Alfred P. Sloan, Jr. at General Motors, following Pierre S. du Pont at Du Pont, first developed decentralization as the organizing principle for the new 'big business.' Rather than treating structure as fixed, Sloan and du Pont also developed systematic approaches to business objectives, business strategy, and strategic planning — so structure and strategy were designed together. Decentralization positioned the key activities (running each car division as a business with its own objectives) where they could perform and be measured. This let large scale coexist with local accountability, exactly the problem earlier organizations could not solve. The Unilever architects of the Dutch-English merger applied the same logic to multinational scale, designing what may still be the most advanced structure for the multinational corporation and confronting multinational planning and marketing at the same time. In each case structure followed a strategy that was made explicit first.

• If the mission and objectives are not yet defined, then stop designing structure — without understanding strategy, organizations cannot be designed and managerial jobs cannot be made productive.
• If you are choosing where to place an activity, then ask whether it is a key activity for the strategy; if it is, position it for maximum performance and visibility.
• If the business consists of distinct businesses with their own objectives and markets, then apply federal decentralization (the du Pont/Sloan principle) rather than a single functional pyramid.
• If formal structure is complete but the organization lacks 'soul,' then add the policies Ian Hamilton identified as balancing formal structure — structure alone does not produce performance.
• If strategy has changed but structure has not, then treat the mismatch as the priority: preserving what had been is a restoration, not a design decision.

• Designing from the inside out — starting with the work of the manager or with organization charts; the tell is a technocrat's approach that soon degenerates into bureaucracy.
• Treating structure as an absolute rather than a means; the tell is defending an organ by what it does or how it does it instead of by the contribution it makes.
• Copying conventional functions instead of identifying the strategy's actual key activities; the tell is a structure that mirrors other firms rather than this firm's objectives.
• Balancing only formal structure and ignoring informal organization and decision flows; the tell is clean reporting lines but stalled decisions (the Follett/Barnard blind spot).
• Assuming one universal design fits every case; the tell is applying the same principle regardless of size, mission, or whether the entity is business or public-service — public-service institutions may need structural discipline more, not less.

• ▸Mission and purpose: state in one line what this institution exists to contribute.
• ▸Objectives: list the specific results the strategy must produce.
• ▸Key activities: name the activities on which achieving those objectives depends.
• ▸Placement: for each key activity, state where it must sit to perform and be seen.
• ▸Design principle chosen: functional / federal decentralization / team — and why it fits size and task.
• ▸Communication and decision flows: identify who must act and how the structure gets decisions to them.
• ▸Formal vs. soul balance: note the policies that animate the formal structure.
• ▸Contribution test: for each unit, state the needed result it delivers; flag any unit defined only by activity.
• ▸Review trigger: name the strategy change that would require redesign.

1. 1Define innovation in economic, not technological, terms: ask what new value the customer receives, not what new thing you built. Finding a new use for an old product (selling refrigerators to Eskimos to keep food from freezing) counts as innovation because it creates a new market or new customer reality.
2. 2Structure innovation as a distinct task, run separately from the going concern. Manage two organizations at once: the existing managerial organization that optimizes what exists, and a new innovative organization that creates the new — do not let one absorb the other.
3. 3Practice systematic abandonment: name obsolete products, processes, and policies and retire them deliberately, freeing the trained people and money (concentrated in existing large organizations) to develop the new.
4. 4Set explicit innovation objectives across every function — not just engineering or R&D. Innovation extends across marketing, distribution, resource development, and productivity, exactly as marketing does; it is never a confined single department.
5. 5Aim high and include social/economic innovation, not just technical. Mobilization of purchasing power (bank credit), insurance, limited liability, and installment credit each moved the economy as much as the steam engine — treat social innovation as an equal opportunity.
6. 6Build capability rather than buy it: where the fabrics, techniques, or suppliers you need do not yet exist, develop them — turn quality control into research and design, and cultivate suppliers who can deliver.
7. 7Make the customer the sole judge. Test every innovation against the customer's economic reality, because only the customer knows it; technical accomplishment without customer value is not innovation.

Marks & Spencer treated innovation as an organized business task rather than a lab activity. The clothing and textiles it needed did not exist, so it started with ordinary retailer quality control and rapidly built those labs into research, design, and development centers — developing new fabrics, dyestuffs, processes, blends, designs, and fashions. It then went out and found the right manufacturers, often helping them get started because established old-line makers would not cooperate with the upstart. After World War II it applied the identical innovative approach to a wholly new industry: prepared and processed foods, bakery goods, and dairy. It also set innovation goals in marketing, pioneering consumer research in the early thirties when the techniques did not yet exist and had to be developed in-house. The pattern is the discipline: set innovation objectives, build the missing resources, and judge everything by what reaches the customer.

• If the change alters the customer's economic reality (new market, new use, new value), then it is innovation — even if the product is technically unchanged.
• If both the trained people and the money needed to develop the new sit inside your existing large organization, then that organization must carry the innovation, not wait for an outside inventor.
• If a product, process, or policy has become obsolete, then abandon it systematically to release resources — do not defend it because it once worked.
• If you are running innovation and ongoing operations through the same structure, then separate them: innovation is a distinct task requiring its own organization.
• If the resource or supplier you need does not exist, then develop it yourself and help others get started rather than abandoning the objective.

• Confusing innovation with invention. Tell: the team measures success by technical novelty or patents rather than by new customer value or a new market.
• Confining innovation to engineering or R&D. Tell: no innovation objectives exist for distribution, marketing, or resource productivity — it is treated as one department's job.
• Letting the going concern smother the new. Tell: the innovative work is judged by the same optimization metrics as established operations and always loses the resource fight.
• Ignoring social and economic innovation while chasing only technical breakthroughs. Tell: proposals like new credit, distribution, or organizational forms are dismissed as 'not real innovation.'
• Failing to abandon the obsolete. Tell: old products and policies accumulate, tying up the trained people and money that the new work needs, and nothing is ever deliberately retired.

• ▸New customer value: state the new economic reality the customer gains
• ▸Innovation type: mark technical / social / economic / new-use of existing product
• ▸Function reach: list which functions (marketing, distribution, resources, productivity) must change
• ▸Missing resources to build: fabrics, techniques, suppliers, or skills that do not yet exist
• ▸Abandonment list: obsolete products, processes, policies to retire and resources freed
• ▸Separation plan: how the innovative organization runs apart from ongoing operations
• ▸Objective and measure: the innovation goal plus how you will measure its result
• ▸Customer test: how you will verify the customer's economic reality actually improved