Effective Executive Drucker Full

1. 1Separate the two acts: first analyze to shape and inform, then decide. Analysis alone produces no action—name explicitly where analysis ends and the courageous choice begins.
2. 2Build a full list of priorities AND posteriorities. Posteriorities—the tasks you choose NOT to tackle—are the harder half; without them you cannot focus on the few that matter.
3. 3Run each candidate task through Drucker's four tests: Does it pick the future over the past? Opportunity over problem? Your own direction over the bandwagon? A high aim over the safe and easy?
4. 4Slough off an old activity before starting a new one. Ask of every existing program, 'Is this still worth doing?'—and if not, kill it to free capacity for the high aim.
5. 5Convert the decision into a Monday difference. Refuse to end at 'a wonderful meeting'; state specifically what you will do differently, and what you will stop doing.
6. 6Build in the means to bail out the new endeavor when it gets into trouble, since nothing new is easy—courage without a rescue mechanism becomes recklessness.
7. 7Resist the pull to keep getting smarter. Accept that a smarter list is always theoretically possible; the deadly sin is aiming first to be smart instead of acting.

Drucker himself is the worked case. As a young man fleeing totalitarianism, he did not create the discipline of management because it was a smart idea—he created it because he had the courage to ask what he could do to strengthen the institutions of society against the horrors of the twentieth century. That single choice runs all four tests: he picked society's future possibilities over its past tragedies, focused on the opportunities management created rather than the problems it solved, chose his own direction by advocating a humanistic practice of management rather than climbing on a bandwagon, and aimed high—to make society both more productive and more humane. Contrast this with the German General Staff after Schlieffen: his successors were technicians rather than decision-makers, and lacking the courage to drop an outflanked plan, they kept it while making its attainment impossible, producing confused improvisation instead of a decision. The difference between the two is not intelligence but courage—the willingness to choose the future, the opportunity, one's own direction, and the high aim.

• If a task defends the past or mops up yesterday rather than making the future, then it is heroics, not effectiveness—move it to posteriorities.
• If you find yourself refining the analysis to get smarter rather than choosing, then the analysis is finished and the missing ingredient is courage, not data.
• If the boundary conditions of a past decision no longer hold (as with Schlieffen), then abandon the decision outright—do not keep it while quietly making its attainment impossible.
• If you cannot name what you will do differently on Monday and what you will stop doing, then no decision has actually been made.
• If a proposed aim is chosen because it is safe and easy, then reject it in favor of one that will make a difference.

• Aiming first to be smart—treating brilliant analysis as the endpoint. The tell: endless studies that are a cover-up for unwillingness to face a decision.
• Setting priorities but never posteriorities. The tell: a long list of things you 'should' do with nothing explicitly abandoned, and no capacity to start the new.
• Adding the new without sloughing off the old. The tell: organizational obesity—controls that control nothing and staff proliferation, the loss of shape and cohesion.
• Climbing on the bandwagon instead of choosing your own direction—'Druckerizing' rather than 'Jonesizing.' The tell: borrowing generic effectiveness instead of carrying out your own distinctive mission.
• Keeping an outflanked commitment out of technician's timidity. The tell: confused improvisation, impassioned rhetoric, and hopes for miracles replacing a coherent strategy.

• ▸Decision at hand: state the single choice in one sentence.
• ▸Analysis done: what the data now tells you (mark this as complete, not to be extended).
• ▸Future vs. past: how does this pick the future over defending the past?
• ▸Opportunity vs. problem: what opportunity does it pursue rather than what problem it merely solves?
• ▸Own direction vs. bandwagon: how is this your distinctive path, not the borrowed trend?
• ▸High aim vs. safe: what difference will it make that a safe, easy option would not?
• ▸Posteriority sloughed off: which old activity you will stop to make room for this.
• ▸Bail-out built in: the mechanism to rescue the new endeavor when it gets into trouble.
• ▸Monday action: exactly what you will do differently, starting Monday.

1. 1Start by naming which of the four realities is currently pushing you toward nonresults: time captured by others, forced operating, dependence on sideways/superior people, or inside-insulation from outside reality. You have no control over the conditions—only over your response.
2. 2For the time reality, stop expecting to protect time reactively. You cannot, like the physician, tell the nurse 'no one for half an hour.' Instead schedule large, continuous, uninterrupted units in advance—three or four hours—because people-decisions and organizational problems only get solved in that block, not in fragments.
3. 3For the operating reality, take positive action to change what you do; if you were promoted out of marketing or the plant, deliberately slough off the operating habits or you will keep running the function instead of directing the whole.
4. 4For the dependence reality, map who must use your output—usually people sideways or above you, not your direct reports. Ask what they need from you in a form they can actually use, and make your contribution effective in their work, or you have no effectiveness at all.
5. 5For the inside-insulation reality, treat every report as an already-predigested abstraction that imposes organizational relevance criteria. Deliberately go to where results actually are—the customer, the patient—because there are no results inside the organization.
6. 6Audit for the tells of these realities biting: a time log showing meetings at a quarter of your time or more signals malorganization; nonstop standing meetings signal work spread across components that belongs in one.
7. 7When a structural cause is found (as with the energy divisions), fix the structure, not the symptom—consolidate the diffused responsibility under one manager so the meetings collapse rather than continuing to referee them.

A large company's turbine (pre-1900), jet-engine (WWII), and atomic-energy divisions had become substitutes and complements for one another in a single market—electric power for the same customers—yet each stayed 'carefully shielded from the others by layers of organization,' with its own folkways, rituals, and career ladders, each certain it would capture 75 percent of the next decade's business. Because the three reported to different members of management, they were locked in a nonstop meeting for years that 'sucked in the entire top group.' This is three realities at once: top executives' time belonged to everyone; they were trapped operating and refereeing; and the inside abstraction blinded them to the one-market outside reality. The fix was structural: cut the three loose from their original groups and put them under one manager. Infighting and the big strategy decisions remained, but top management no longer had to chair every meeting and total meeting-time dropped to a fraction. The lesson: the reality could not be changed, but the response—reorganizing to match the outside market—converted futility into direction.

• If people who must use your output sit sideways or above you rather than under you, then design your contribution around their work, not your convenience—reaching them is the whole of your effectiveness.
• If your time log shows meetings at 25 percent or more, then treat it as evidence of malorganization—work misallocated across jobs and components—not as a personal scheduling problem.
• If information reaches you only as reports and computer-ready facts, then assume you are insulated; make a conscious effort to perceive the outside event (perception) before it becomes after-the-event fact.
• If a body exists to meet (a board like DuPont's or Standard Oil's), then keep its members from also operating anything—as judges cannot also be advocates—but never let meetings become an operating executive's main demand on time.
• If two or more components are trapped in a permanent meeting, then the responsibility is diffused across them—consolidate under one manager rather than continuing to referee.

• Trying to defend time reactively like a physician saying 'no one for half an hour'—the phone rings with the best customer or the boss, and the block is gone; the tell is a calendar of fragments and zero uninterrupted stretches.
• Continuing to run the function you were promoted out of; the tell is a president still running marketing or the plant while the whole business goes undirected.
• Building contribution around subordinates you control instead of the sideways and superior people who must actually use it; the tell is polished output that no one downstream converts into their own results.
• Mistaking the organizational abstraction for reality—forgetting that mathematically it is a point with no results inside it; the tell is 'computeritis,' becoming contemptuous of any stimulus that won't reduce to computer logic.
• Fixing symptoms instead of structure—adding meetings to coordinate work that belongs in one component; the tell is an epidemic of meetings that grows rather than the consolidation that ends it.

• ▸Reality in play: which of the four (time / operating / dependence / insulation) is pushing me toward nonresults now?
• ▸Time capture: list this week's largest uninterrupted block actually protected in advance.
• ▸Operating drag: name the function/habit I still run that I should have sloughed off.
• ▸Users of my output: name the sideways and superior people who must use it, and the form they need it in.
• ▸Outside reality check: what result outside the organization (customer, patient) am I actually producing?
• ▸Meeting load: percent of my time in meetings—flag if 25 percent or more.
• ▸Structural cause: what diffused responsibility or misplaced work is generating the meetings?
• ▸Consolidation move: which components/responsibilities should sit under one manager?
• ▸Insulation guard: what firsthand outside perception did I seek this week beyond reports?

1. 1Start from output, not input: define the specific contribution your position makes to the performance of the whole organization, then work backward to what you must do this week.
2. 2Build two lists—priorities and posteriorities. Posteriorities (tasks you deliberately choose not to tackle) will be the longer list; treat the act of abandoning as the real work.
3. 3Convert each priority into a concrete next action by finishing the sentence: 'On Monday I will do X differently.' If you cannot name a changed action, the priority is still just an insight, not effectiveness.
4. 4Direct your attention outward, away from your own specialty, department, and 'authority I should have,' and toward the results the organization needs—results occur outside, not inside.
5. 5Apply the courage test to your priority list before you finalize it: does each item pick the future over the past, opportunity over problem, your own direction over the bandwagon, and a high aim over the safe and easy?
6. 6Guard against inside-only data: recognize that the computer and reports quantify internal events (costs, production, patient stats) but the relevant outside events arrive late and unquantified—go find them yourself.
7. 7Cap meetings and interruptions; too many meetings signal poor job structure. Protect blocks of time so insight can become achievement through 'hard systematic work.'
8. 8Review results, not efforts: judge yourself and others on the right things gotten done, not on busyness, hours, or how brilliant the discussion felt.

Don Keough, then president of Coca-Cola, was a consulting client of Drucker's. After every session Drucker refused the usual pleasantry: 'Don't tell me you had a wonderful meeting with me. Tell me what you are going to do on Monday that's different.' This forced Keough away from admiring insight and toward action—the only place effectiveness lives. In the passage it proves 'deceptively tough,' because naming a different Monday requires first deciding not only what you should do but what you should stop doing. A parallel case is Edward Jones, which retained Drucker from 1980 to 2003: rather than becoming a generically 'effective' or 'Druckerized' company, Drucker told the Managing Partner to 'Jonesize'—to apply the discipline toward Jones's own distinctive mission of democratizing investing. Over that period the firm grew from 200 offices in 28 states to more than 9,000 across the U.S., Canada, and the U.K. In both cases effectiveness came from converting knowledge into a specific, contribution-focused action, not from the intelligence itself.

• If a task advances your specialty or protects your authority but not the performance of the whole, then move it to posteriorities.
• If you cannot state what you will do differently on Monday, then you have an insight, not a priority—do not count it as work done.
• If a candidate priority is 'safe and easy' rather than aimed at something that makes a difference, then drop it; safe-and-easy is a tell of avoidance, not analysis.
• If deciding between two priorities, then choose the one that picks the future, the opportunity, and your own direction over the bandwagon.
• If the data supporting a decision is all internally quantified, then treat the important outside reality as still missing and seek the qualitative signal before acting.

• Confusing effort with results: being 'occupied with efforts rather than with results'—the tell is worrying about what the organization 'owes' you and what authority you 'should have.'
• Mistaking brilliance for achievement: the strikingly ineffectual smart person who never learned that insight becomes effectiveness only through hard systematic work. Tell: frenzy and busyness confused with creativity while the plodder gets there first.
• Aiming first to be smart: endlessly refining the priority list because you could 'always be smarter.' Tell: analysis substitutes for action and no decision ever gets made—the deadly sin of preferring analysis over courage.
• Turning inward as the organization succeeds: inside events engage the executive's energy 'to the exclusion of his real tasks,' aggravated by the computer feeding only quantifiable internal data. Tell: decisions made entirely from reports, outside change noticed only after it's too late (the thalidomide pattern).
• Refusing to abandon: setting priorities without setting posteriorities, so attention scatters across too many items. Tell: too many meetings and no exquisite clarity about the small number of things that matter.

• ▸Contribution: the one result my position must produce for the whole organization
• ▸This week's priorities: the small number of right things (list 1–3 max)
• ▸Posteriorities: tasks I am deliberately choosing NOT to do now (make this list long)
• ▸Monday action: the specific thing I will do differently on Monday for each priority
• ▸Courage check: does each priority pick future/opportunity/own-direction/high-aim? (yes/no per item)
• ▸Outside signal: the qualitative, unquantified external change I must go verify myself
• ▸Meeting/interruption cap: hours I am protecting for systematic work this week
• ▸Result review: how I will judge this by results done, not effort spent

1. 1Locate results outside the organization. Ask: who converts our costs and efforts into value? For a business it is the customer who exchanges purchasing power for products; for a hospital it is the patient. Name that outside decision-maker before you measure anything.
2. 2Strip the organizational filter. Recognize that you see the outside through reports—predigested, abstract, tagged with internal criteria of relevance. Go get firsthand contact with customers or patients so outside reality is not lost in translation.
3. 3Shift every knowledge worker's aim from effort to contribution to the performance of the whole. Have each person state what result outside their own specialty or department their work must produce, and for whom.
4. 4Reach the 'sideways' and superior people whose work depends on your output. Ask what they need from you to make your contribution effective in their work; if you cannot make it usable to them, you have no effectiveness.
5. 5Redefine the work by results, not by size, cost, or headcount. A two-hundred-person market research group and a one-person one owe the same contribution; judge by insight and quality delivered outside, not by how many people report to you.
6. 6Fix information flow so results-relevant facts reach the people who act. Trace where a fact is known (floor nurse) versus where it is needed (admissions), and add the missing channel.
7. 7Anchor performance to your distinctive mission, not generic effectiveness. Define what your organization uniquely does for the outside (Edward Jones: democratizing investing) and make that the standard for 'doing the right things.'
8. 8Reserve large, uninterrupted blocks of time for people-decisions and structural fixes, since people are 'almost fits' and these choices determine whether the organization can perform, adapt, and renew its human capital.

A large company's energy business had steam turbines, jet engines, and atomic energy as three separate divisions—each with its own staff, folkways, career ladders, and each confident it would own 75 percent of the next decade's business. But the three power sources had become substitutes and complements serving one market with one end product: electric power for the same customers. Because each reported to a different member of management, they were locked in a nonstop meeting for years that sucked in the entire top group. Management finally cut the three loose from their original groups and put them under one manager expressing the reality of one energy market. Infighting continued and big strategy decisions remained, but top management no longer had to referee every meeting and total meeting-time fell to a fraction. The lesson for organizational performance: structure must mirror the outside reality—one market, one customer, one result—not internal history.

• If a person or unit produces no result usable by someone outside the organization, then their activity is cost, not performance—count it as effort until proven otherwise.
• If someone whose work depends on your output cannot use what you produce, then you have no effectiveness regardless of your title or authority; fix the handoff first.
• If a fact needed to serve the outside is known in one place but not where the action happens, then add the missing information channel rather than adding a meeting.
• If people spend a quarter or more of their time in meetings, then the structure is wrong—responsibility is diffused and work that belongs in one job is spread across many.
• If a knowledge worker is measured by quantity, cost, or number of subordinates rather than by results delivered outside, then you are measuring the wrong thing and will grow ineffectual.

• Managing to internal efficiency metrics—turning out beautiful blueprints for the wrong product. Tell: the department is busy and well-run but nothing it makes reaches or satisfies an outside customer.
• Mistaking the report for reality. Tell: leaders 'know' the outside only through predigested abstractions and are surprised when customers or patients behave against the internal picture.
• Chasing generic effectiveness instead of your distinctive mission. Tell: people talk about becoming an 'effective' or 'Druckerized' organization rather than about what they uniquely do for the public.
• Occupation with efforts, authority, and what the organization 'owes' you. Tell: conversations center on turf, entitlements, and 'authority I should have' rather than on contribution to the whole.
• Letting structure follow internal history rather than outside market reality. Tell: separate divisions serving one customer stay walled off, spawning an endless meeting that pulls in top management.

• ▸Outside decision-maker: name who converts our effort into value (customer/patient/public)
• ▸Result they receive: the specific outcome delivered to them, stated in their terms
• ▸Firsthand contact: how you verify this outside reality without the report filter
• ▸Distinctive mission: what we uniquely do for them that 'effective in general' would miss
• ▸Contribution beyond specialty: the whole-organization result each key worker must produce
• ▸Sideways/superior dependency: who needs our output and what form makes it usable to them
• ▸Information gap: fact known where vs. needed where, and the channel that closes it
• ▸Structure vs. market check: does our org chart mirror one outside market or internal history?
• ▸Monday action: the one different thing you will do to move a result on the outside

1. 1Record your time in real time, not from memory: log each event at the moment it happens, either yourself or through a secretary who captures it for you.
2. 2Run the log continuously and review it monthly; at minimum, run it on yourself for three to four weeks at a stretch, twice a year, on a fixed schedule.
3. 3After each sample, rethink and rework your schedule against what the record actually shows—not what you assumed it showed.
4. 4Identify time-wasters and cut back unproductive demands: eliminate what need not be done at all, and delegate what someone else can do as well or better.
5. 5Consolidate the discretionary time you free up into the largest possible continuing units, because significant knowledge work requires large uninterrupted blocks.
6. 6Treat time as the limiting factor: the scarcest resource sets the output ceiling, and time is totally inelastic—you cannot rent, hire, or buy more of it.
7. 7Repeat the cycle indefinitely; expect that six months later you will have drifted back into trivia, so re-record and re-diagnose on schedule.

Drucker describes a company chairman who did not keep his own time log but had his secretary record it for him. The record was made in real time, at the moment of each event, rather than reconstructed later from memory—which Drucker treats as the non-negotiable requirement. Effective executives like him keep such a log continuously and look at it every month, and at minimum run it for three to four weeks twice a year on a regular schedule. After each sample, they rethink and rework their schedule based on what the record reveals. But Drucker notes the recurring result: six months later they invariably find they have 'drifted' into wasting their time on trivia. This is why the practice is a repeating cycle, not a one-time audit.

• If you are tempted to start with planning your work, then stop—start instead by finding out where your time actually goes, because plans without time-diagnosis stay on paper as good intentions.
• If an activity need not be done at all, then eliminate it before you try to do it more efficiently.
• If someone else could do a task as well or better, then delegate it and reclaim the block for work only you can do.
• If your discretionary time is scattered in fragments, then consolidate it into the largest continuing units, because significant results demand uninterrupted stretches.
• If six months have passed since your last time sample, then re-run the log regardless of how well you think you are managing time, since drift into trivia is predictable.

• Reconstructing the log from memory instead of recording in real time—the tell is a tidy, flattering account that omits the small interruptions memory discards.
• Starting with task planning rather than time-diagnosis—the tell is polished plans that never turn into achievement.
• Treating the audit as a one-time event—the tell is that trivia has quietly reclaimed the calendar within six months.
• Optimizing the efficiency of activities that should be eliminated or delegated entirely—the tell is doing unnecessary work faster instead of not at all.
• Leaving freed time in small scattered pieces instead of consolidating it—the tell is a calendar full of gaps too short for any significant work.

• ▸Sample period: the fixed 3-4 week stretch you are logging (dated now, repeated twice a year)
• ▸Event (real-time entry): what you actually did, recorded at the moment it happened
• ▸Duration: how long it took
• ▸Eliminate?: mark activities that need not be done at all
• ▸Delegate?: mark activities someone else could do as well or better, and to whom
• ▸Drift check: trivia that reappeared since your last review
• ▸Consolidated block: the largest uninterrupted unit you can now protect for significant work
• ▸Next review date: the scheduled month you will re-run and re-diagnose

1. 1Ask the governing question before starting any task: 'What can I and no one else do which, if done really well, would make a real difference to this organization?' Write the answer down.
2. 2Turn attention away from your own specialty, department, and narrow skills; state the performance of the whole you are aiming at, not the effort you plan to expend.
3. 3Force direct contact with the outside. Because the inside is what touches you constantly (relations, problems, gossip), schedule deliberate exposure to results and to the customer, who holds final veto power.
4. 4Convert your specialty output into usable input for others by asking colleagues, superiors, and subordinates directly: 'What contribution from me do you require to make your contribution? When do you need it, how, and in what form?'
5. 5Set posteriorities alongside priorities: decide the small number of things you will do and, with equal clarity, the tasks you refuse to tackle so effort concentrates on contribution.
6. 6Act on the answer, don't just record it — install yourself where the contribution happens (as the retail CEO literally walked the personnel department to make development get done).
7. 7Close each week by naming what you will do differently on Monday, not by admiring the analysis. Working on the right things, not effort, is what makes knowledge work effective.

A sixty-year-old financial man became CEO of a nationwide retail chain after twenty years in the second spot, expecting never to lead. His strength was figures — costing, purchasing, inventory, financing new stores, traffic studies — and people were 'a shadowy abstraction' to him. Rather than working harder at what he knew, he asked: 'What can I and no one else do which, if done really well, would make a real difference to this company?' He concluded the one significant contribution was developing tomorrow's managers, noting that the company's celebrated executive-development policy 'does nothing by itself.' So his contribution became making sure it actually got done — and for the rest of his tenure he walked through the personnel department to ensure it happened. He redirected the relative weight of his value dimensions instead of leaning on his existing specialty.

• If you find yourself worrying about what the organization or your superiors 'owe' you or what authority you 'should have', then stop — that focus renders you ineffectual; redirect to contribution.
• If your output (knowledge, ideas, blueprints) cannot be used by another person as their input, then it is meaningless data — reframe it in the user's language, not your specialty's.
• If attention is drifting inside-focused (the higher you rise, the stronger this pull), then make a special effort to reach outside reality where results live.
• If a task doesn't answer 'what can I and no one else do that makes a real difference', then make it a posteriority and refuse it.
• If you're aiming first to be smart rather than to act, then correct course — priorities require courage, not more intelligent analysis.

• Occupied with efforts rather than results — the tell: you measure yourself by hours worked and busyness; the failures in wartime Washington 'worked much harder' but never redirected.
• Staying inside your specialty and narrow skills — the tell: like the engineering department turning out beautiful blueprints for the wrong product, your work is polished but unused.
• Barbarian arrogance of the expert — the tell: you talk only to fellow experts and assume laymen should decode you; your knowledge becomes pedantry and uselessness.
• Confusing distinctiveness or a written policy with contribution — the tell: you cite the policy ('we pride ourselves on development') while nothing actually gets done.
• Waiting for more analysis before acting — the tell: brilliant ideas endlessly pondered; without courage knowledge never becomes productive.

• ▸Unique contribution: What can I and no one else do that, done well, makes a real difference here?
• ▸Whole-organization result: the performance of the whole I'm aiming at (not my effort)
• ▸Posteriorities: tasks tied to my specialty/authority/comfort that I will NOT tackle
• ▸Downstream users: who must convert my output into theirs, named
• ▸Their requirement: 'What contribution do you require from me — when, how, what form?'
• ▸Outside reality check: one deliberate contact with customer/results this week
• ▸Courage move: which of pick-the-future / opportunity-over-problem / own-direction / aim-high applies
• ▸Monday action: the specific thing I will do differently, not just decide

1. 1Start with contribution, not authority: ask what results the whole organization needs from your position, then staff and organize backward from that, the way the third stonecutter starts from 'building a cathedral' rather than 'making a living.'
2. 2Locate the strengths that matter for that contribution — in yourself, your superiors, your sideways colleagues, and your subordinates — and match each person to work where their specific skill is decisive rather than where their gaps are least visible.
3. 3Identify the people most important to your effectiveness: they are usually not those you control but those 'sideways' in other areas and your superiors. Design your contribution so their strengths become usable to you and yours to them.
4. 4Render weaknesses irrelevant by organizing the work, not the person: put decision authority with 'whoever is on the spot' who has the knowledge, so the org multiplies individual strength instead of averaging it down.
5. 5Distinguish executives (those with responsibility for direction, content, quality, and decisions of irreversible impact) from mere overseers, and build parallel ladders of reward for individual professional contributors so knowledge strength is recognized, not just positional strength.
6. 6Convert recurring crises into routine so strengths are spent on results, not firefighting; a well-managed operation is 'boring' because anticipated problems no longer consume executive time.
7. 7Force the Monday test: after every plan, name what you will actually do differently, and what you will stop doing, since making strength productive requires deciding posteriorities as much as priorities.

Edward Jones retained Drucker from 1980 through 2003 and grew from 200 offices in 28 states to more than 9,000 across three countries. When the Managing Partner spoke of 'Druckerizing' the firm and read 'very dubious sources,' Drucker refused to help on those terms and insisted they 'Jonesize' instead — build on the firm's own distinctive strength, its mission of democratizing investing, rather than import a generic model. This is making strength productive at the organizational level: the firm staffed and organized around what it uniquely did well rather than trying to correct itself into a copy of someone else. The result was not a generically 'effective' company but one that carried out its own mission more effectively, and it scaled dramatically. The tell of the right approach was that Drucker built on their existing distinctiveness rather than substituting his own.

• If a person's weakness is irrelevant to the required contribution, then ignore it and staff for the strength that is decisive.
• If the people who most affect your effectiveness are 'sideways' or above you, then design your contribution to be usable in their work rather than waiting for control you lack.
• If someone has the knowledge and is 'on the spot,' then place the decision with them and keep only the responsibility — the young captain's rule for guerrilla conditions.
• If a crisis recurs every period, then treat it as a symptom of slovenliness and redesign it into routine rather than praising the heroic scramble.
• If your instinct is to be smart about priorities, then check for courage instead — pick future over past, opportunity over problem, your own direction over the bandwagon, high aim over safe.

• Being occupied with efforts and authority rather than results — worrying over what the organization 'owes' you; the tell is talking about your rights and specialty instead of the performance of the whole.
• Staffing to minimize weakness so you end up with people who have no glaring gaps and no decisive strengths; the tell is an org where nobody is exceptional at anything.
• Confusing overseers with executives — treating anyone who manages others as decisive; the tell is a 'manager' with no responsibility for the direction, content, or quality of the work.
• Copying a model instead of building on your own strength ('Druckerizing' rather than 'Jonesizing'); the tell is importing generic best practices and worn-out copies of someone else's book.
• Prizing dramatic effort over quiet results; the tell is a 'dramatic' factory or organization where exciting crises signal that anticipation failed and strength is being wasted on rework.

• ▸Required contribution: the result the whole organization needs from this position.
• ▸My decisive strength: the one skill that makes me effective here.
• ▸Superior's strength to feed: what my boss does well that my work should support.
• ▸Sideways strengths I depend on: colleagues whose output I must make usable and vice versa.
• ▸Subordinate placements: each person matched to work where their strength is decisive.
• ▸Weaknesses to render irrelevant: gaps I will organize around rather than fix.
• ▸On-the-spot decision rights: which decisions move to whoever has the knowledge.
• ▸Recurring crisis to routinize: the periodic scramble I will convert into standard procedure.
• ▸Monday difference: the one thing I will do or stop doing this week.

1. 1Reserve a big continuous chunk of time (a half-day, or two weeks of sustained effort) for the one task that contributes most, and defend it with an iron determination to say 'No' to interruptions.
2. 2Review your work program and your associates' programs periodically, asking of each activity: 'If we did not already do this, would we go into it now?' Drop or sharply curtail anything that does not draw an unconditional 'Yes.'
3. 3Pull your first-class resources — especially scarce human strength — out of the tasks of yesterday and redeploy them onto the opportunities of tomorrow.
4. 4Rank all clamoring tasks into a short list of priorities and a large list of posteriorities (tasks you deliberately choose not to tackle) — and decide these yourself rather than letting pressures decide for you.
5. 5Work one thing at a time to completion; do not begin the next until the preceding one is finished or deliberately shelved in the drawer.
6. 6Estimate time generously: assume the unexpected will happen (it always does), add a margin beyond what the task appears to need, and set an easy but steady pace instead of racing.
7. 7Budget time for the most time-consuming and most-neglected part of any task — converting the decision into organizational action, so others accept it as their own daily routine.
8. 8Apply the four courage tests to your priorities: pick future over past, opportunity over problem, your own direction over the bandwagon, and high aim over safe-and-easy.

One chief executive of a major drug company concentrated his entire tenure on a small number of very large tasks, one at a time. He worked out a strategy fit for modern health care as an emerging 'public utility,' where public bodies such as governments, nonprofit hospitals, and Blue Cross pay the bills while the individual physician decides the actual purchase — a strategy perfected only in 1965, shortly before he retired. Doing even one task of that magnitude is unusual for a chief executive; he did three, plus building a strong, worldwide, well-staffed organization. He accomplished this by single-minded concentration on one task at a time, never starting the next until the current one was finished or set aside. As a result he needed much less time in the end than executives who scatter themselves. Contrast DuPont, which refuses to invest scarce people and money in defending yesterday and is 'much too busy making and selling new products' to run seminars on creativity — versus firms clinging to the 'efficient buggy-whip plant.'

• If the answer to 'Would we go into this now if we weren't already doing it?' is anything short of an unconditional Yes, then drop or sharply curtail it and stop feeding it resources.
• If you are trying to do three major tasks at once, then you have no minimum time-quantum for any one, and a single one running into trouble collapses the whole program — cut to one (or at most two with a genuine minimum for each).
• If pressures rather than you are choosing what gets done, then the important tasks are being sacrificed by default — take the decision back yourself.
• If a decision has not yet become part of others' daily routine and behavior, then the task is not complete, no matter how 'finished' it feels.
• If a choice is merely safe, backward-looking, problem-driven, or on the bandwagon, then it fails the courage test — reject it in favor of the future-facing, opportunity-driven, difference-making option.

• Trying to keep many balls in the air: the tell is a juggler's stunt that works for ten minutes, then all the balls drop when it's held longer than a real quantum of time allows.
• Underestimating task time by assuming everything will go right; the tell is a program with no margin that repeatedly collapses when the inevitable unexpected arrives.
• Hurrying to catch up; the tell is that racing puts you further behind, whereas an easy, steady pace keeps going.
• Aiming to be smart before acting; the tell is endless refinement of priority/posteriority lists ('one could always be smarter') with no Monday-different action — the missing ingredient is courage, not more analysis.
• Defending yesterday: the tell is executives sent to creativity seminars and complaints about the absence of new products, while scarce human strength stays trapped in no-longer-productive tasks.

• ▸The one priority: the single task that will produce outstanding results this period
• ▸Protected time block: the big continuous chunk reserved for it (and how I'll say No)
• ▸Slough-off list: activities that fail 'Would we start this now?' — drop or curtail
• ▸Freed resources: the first-class people/time pulled out of yesterday's tasks
• ▸Posteriorities: important tasks I deliberately choose NOT to do now
• ▸Time estimate + margin: realistic duration plus a buffer for the unexpected
• ▸Action conversion: who must adopt this as their own routine for it to count as done
• ▸Courage check: future / opportunity / own-direction / high-aim — pass or fail
• ▸Monday-different: the one concrete thing I will do differently this week

1. 1Classify the problem before touching it: ask whether this is generic (a recurring symptom of an underlying pattern) or a true exception. If generic, solve it with a rule or principle, not a one-off fix.
2. 2Set the boundary conditions in writing: name what the decision must accomplish and the minimum objectives it must satisfy. A decision that cannot meet its boundary conditions is worse than one that fails a wrong one.
3. 3Decide what you WON'T do first. Set posteriorities — tasks you deliberately abandon — so a small number of priorities get exquisite focus. This is the harder, more important act than listing priorities.
4. 4Manufacture disagreement. Do not accept the first consensus; require alternatives and dissent so you are choosing between options rather than ratifying the only one on the table.
5. 5Build the action into the decision from the start: name who has to know, who does what, and by when. A decision without a commitment to action is only a good intention.
6. 6Aim the decision outward at contribution to the whole, not at your specialty, department, or authority. Ask 'what does the performance of the whole need from me?'
7. 7Install feedback that lets you see reality directly, not through reports alone, so you learn whether the decision is producing results and can correct it.
8. 8Convert the decision into a Monday difference: state concretely what you will do differently, not what you concluded.

Edward Jones retained Drucker from 1980 to 2003, and its Managing Partner wrote that his team had read Management until 'our copies are literally worn out.' Drucker's one negative comment defined the boundary condition of the whole engagement: 'Stop talking about "Druckerizing" your organization... The job ahead of you is to "Jonesize" your organization—and only if you accept this would I be of any help to you.' The generic problem — becoming a generically 'effective' company — was rejected in favor of the unique one: more effectively carrying out Jones's distinctive mission of democratizing investing. That reframing built action into the decision, because every subsequent choice had to serve the firm's own mission rather than an imported template. Over the engagement the firm grew from 200 offices in 28 states to more than 9,000 across three countries. The decision worked because it was made at the highest conceptual level — mission — rather than as a bundle of tactics.

• If the problem is generic (a recurring symptom), then solve it with a rule or principle; if it is a genuine exception, then treat it as unique — misclassifying it guarantees the wrong fix.
• If you cannot state the boundary conditions the decision must satisfy, then you are not ready to decide; a decision that cannot meet its minimum objectives should not be made.
• If everyone agrees immediately, then withhold the decision and demand alternatives — the absence of disagreement is a signal that no real judgment has occurred.
• If a decision names no action, no owner, and no deadline, then it is a good intention, not a decision.
• If the aim is only to be smart, safe, or self-protective, then reject it and re-aim: pick the future over the past, opportunity over problem, your own direction over the bandwagon, and something that makes a difference over something easy.

• Being occupied with efforts rather than results — worrying over authority 'owed' to you. Tell: you can describe how hard you worked but not what the whole organization performed differently.
• Trying to be smart instead of effective — endless analysis that never sparks action. Tell: brilliant ideas that only 'ponder what might be' because courage never converted knowledge into motion.
• Importing a generic template ('Druckerizing') instead of solving your own unique problem. Tell: your solutions come from 'dubious sources' rather than your organization's distinctive mission.
• Drowning in detail and quantity, mistaking busyness for contribution. Tell: like the market-research manager 'so busy managing' he never asks 'what do we really mean when we say our market?' and misses the change that sinks the company.
• Listing priorities without setting posteriorities. Tell: everything stays on the list, focus is diffuse, and nothing on Monday is actually different.

• ▸Decision in one sentence: state the choice at the highest conceptual level, not the tactic.
• ▸Generic or unique?: mark which, and give the rule if generic or the reason it's an exception.
• ▸Boundary conditions: list the minimum objectives this decision must satisfy to count as right.
• ▸Posteriorities: name what you are deliberately NOT doing so priorities get focus.
• ▸Alternatives considered / dissent heard: record at least one real disagreement or option you weighed.
• ▸Contribution to the whole: state how this serves performance beyond your own department or specialty.
• ▸Action commitment: who must know, who does what, by when.
• ▸Feedback check: how and when you will see for yourself whether it is producing results.
• ▸What I will do differently on Monday: one concrete, observable change.