elliot-stack 1.0.29 → 1.0.33

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (128) hide show
  1. package/LICENSE +21 -21
  2. package/README.md +5 -0
  3. package/bin/install.cjs +981 -950
  4. package/hooks/repo-search-nudge.js +32 -32
  5. package/package.json +1 -1
  6. package/skills/estack-active-learning-tutor/SKILL.md +339 -339
  7. package/skills/estack-better-title/SKILL.md +64 -64
  8. package/skills/estack-better-title/scripts/rename.sh +55 -55
  9. package/skills/estack-chris-voss/SKILL.md +80 -80
  10. package/skills/estack-chris-voss/references/elliot-notes.md +120 -120
  11. package/skills/estack-chris-voss/references/voss-principles.md +210 -210
  12. package/skills/estack-customer-discovery/SKILL.md +60 -60
  13. package/skills/estack-flight-planner/SKILL.md +332 -332
  14. package/skills/estack-flight-planner/references/config_schema.md +156 -156
  15. package/skills/estack-flight-planner/references/flight_history_schema.md +97 -97
  16. package/skills/estack-flight-planner/references/shuttle_schedules.md +98 -98
  17. package/skills/estack-flight-planner/scripts/check_setup.sh +89 -89
  18. package/skills/estack-flight-planner/scripts/fetch_flights.py +99 -99
  19. package/skills/estack-flight-planner/scripts/filter_flights.py +265 -265
  20. package/skills/estack-flight-planner/scripts/pair_shuttles.py +173 -173
  21. package/skills/estack-github-issue-tracker/SKILL.md +322 -322
  22. package/skills/estack-github-issue-tracker/bin/tracker-tools.cjs +1358 -1358
  23. package/skills/estack-github-issue-tracker/references/gh-cli-patterns.md +124 -124
  24. package/skills/estack-github-issue-tracker/references/result-file-schema.md +156 -156
  25. package/skills/estack-github-issue-tracker/references/tracker-schema.md +96 -96
  26. package/skills/estack-github-issue-tracker/tracker-template.md +58 -58
  27. package/skills/estack-leadership-coach/SKILL.md +235 -0
  28. package/skills/estack-leadership-coach/adding-references.md +280 -0
  29. package/skills/estack-leadership-coach/frameworks/delegation/flows/post-mortem.md +120 -0
  30. package/skills/estack-leadership-coach/frameworks/delegation/flows/pre-delegation.md +138 -0
  31. package/skills/estack-leadership-coach/frameworks/delegation/phases/1-intake.md +145 -0
  32. package/skills/estack-leadership-coach/frameworks/delegation/phases/2-trm-assessment.md +119 -0
  33. package/skills/estack-leadership-coach/frameworks/delegation/phases/3-enrollment.md +132 -0
  34. package/skills/estack-leadership-coach/frameworks/delegation/phases/4-build-brief.md +171 -0
  35. package/skills/estack-leadership-coach/frameworks/delegation/phases/5-monitoring.md +134 -0
  36. package/skills/estack-leadership-coach/frameworks/delegation/phases/6-reverse-delegation.md +118 -0
  37. package/skills/estack-leadership-coach/frameworks/delegation/phases/7-diagnose.md +200 -0
  38. package/skills/estack-leadership-coach/references/.source-files/deci-ryan_self-determination-theory__deci-olafsen-ryan-2017-self-determination-theory-in-work-organizations.md +1881 -0
  39. package/skills/estack-leadership-coach/references/.source-files/deci-ryan_self-determination-theory__gagne-deci-2005-self-determination-theory-and-work-motivation.md +2058 -0
  40. package/skills/estack-leadership-coach/references/.source-files/deci-ryan_self-determination-theory__selfdeterminationtheory-org-theory-overview-page.md +61 -0
  41. package/skills/estack-leadership-coach/references/.source-files/gallup_engagement-research__gallup-3-key-insights-into-the-global-workplace-2024.md +57 -0
  42. package/skills/estack-leadership-coach/references/.source-files/gallup_engagement-research__gallup-managers-account-for-70-percent-of-variance-in-employee-engagement-2015.md +40 -0
  43. package/skills/estack-leadership-coach/references/.source-files/gallup_engagement-research__gallup-state-of-the-global-workplace-2026-global-data-summary.md +73 -0
  44. package/skills/estack-leadership-coach/references/.source-files/gallup_engagement-research__gallup-state-of-the-global-workplace-2026-report-landing.md +42 -0
  45. package/skills/estack-leadership-coach/references/.source-files/hormozi-leila_4-stages__leila-hormozi-the-art-of-delegation-blog-post.md +91 -0
  46. package/skills/estack-leadership-coach/references/.source-files/oncken-wass_monkeys-hbr-1974__oncken-wass-management-time-whos-got-the-monkey-hbr-classic-1974.md +969 -0
  47. package/skills/estack-leadership-coach/references/.source-files/sanchez_main-street-millionaire__codie-sanchez-afford-anything-podcast-ep-565-show-notes.md +89 -0
  48. package/skills/estack-leadership-coach/references/.source-files/sullivan_who-not-how__dan-sullivan-impact-filter-tool-and-guide-booklet.md +565 -0
  49. package/skills/estack-leadership-coach/references/.source-files/van-edwards_cues__vanessa-van-edwards-lewis-howes-school-of-greatness-ep-1231-show-notes.md +122 -0
  50. package/skills/estack-leadership-coach/references/.source-files/van-edwards_cues__vanessa-van-edwards-roger-dooley-cues-interview.md +194 -0
  51. package/skills/estack-leadership-coach/references/deci-ryan_self-determination-theory.md +166 -0
  52. package/skills/estack-leadership-coach/references/doerr_measure-what-matters.md +154 -0
  53. package/skills/estack-leadership-coach/references/ferriss_4hww.md +189 -0
  54. package/skills/estack-leadership-coach/references/gallup_engagement-research.md +105 -0
  55. package/skills/estack-leadership-coach/references/gerber_e-myth-revisited.md +118 -0
  56. package/skills/estack-leadership-coach/references/grove_high-output-management.md +95 -0
  57. package/skills/estack-leadership-coach/references/hormozi-alex_followthrough.md +152 -0
  58. package/skills/estack-leadership-coach/references/hormozi-leila_4-stages.md +146 -0
  59. package/skills/estack-leadership-coach/references/oncken-wass_monkeys-hbr-1974.md +128 -0
  60. package/skills/estack-leadership-coach/references/sanchez_main-street-millionaire.md +196 -0
  61. package/skills/estack-leadership-coach/references/sullivan_who-not-how.md +137 -0
  62. package/skills/estack-leadership-coach/references/van-edwards_cues.md +189 -0
  63. package/skills/estack-migrate-claude-session-history/SKILL.md +226 -0
  64. package/skills/estack-migrate-claude-session-history/references/path-encoding.md +55 -0
  65. package/skills/estack-migrate-claude-session-history/references/troubleshooting.md +96 -0
  66. package/skills/estack-migrate-claude-session-history/scripts/migrate-claude-history.js +1123 -0
  67. package/skills/estack-migrate-claude-session-history/scripts/test-append-note.js +48 -0
  68. package/skills/estack-migrate-claude-session-history/scripts/test-validate-migration.py +326 -0
  69. package/skills/estack-migrate-claude-session-history/scripts/validate-migration.py +493 -0
  70. package/skills/estack-pdf-to-md/SKILL.md +180 -0
  71. package/skills/estack-pdf-to-md/scripts/pdf_to_md.py +596 -0
  72. package/skills/estack-productivity-prioritization-coach/SKILL.md +124 -0
  73. package/skills/estack-productivity-prioritization-coach/sources/01-tony-robbins-rpm.md +39 -0
  74. package/skills/estack-productivity-prioritization-coach/sources/02-justin-sung-task-prioritization.md +34 -0
  75. package/skills/estack-prompt-builder-coach/SKILL.md +81 -81
  76. package/skills/estack-prompt-builder-coach/definition-of-done-generator.md +42 -42
  77. package/skills/estack-prompt-builder-coach/prompt-builder.md +37 -37
  78. package/skills/estack-prompt-builder-coach/task-shaper.md +36 -36
  79. package/skills/estack-prompt-builder-coach/vague-ask-auditor.md +37 -37
  80. package/skills/estack-read-claude-session-history/SKILL.md +204 -204
  81. package/skills/estack-read-claude-session-history/references/jsonl-schema.md +126 -126
  82. package/skills/estack-read-claude-session-history/references/modes.md +423 -423
  83. package/skills/estack-read-claude-session-history/references/recipes.md +271 -271
  84. package/skills/estack-read-claude-session-history/scripts/lib/__init__.py +1 -1
  85. package/skills/estack-read-claude-session-history/scripts/lib/parser.py +460 -460
  86. package/skills/estack-read-claude-session-history/scripts/lib/paths.py +234 -234
  87. package/skills/estack-read-claude-session-history/scripts/lib/search.py +179 -179
  88. package/skills/estack-read-claude-session-history/scripts/lib/subagents.py +88 -88
  89. package/skills/estack-read-claude-session-history/scripts/lib/tools.py +144 -144
  90. package/skills/estack-read-claude-session-history/scripts/read_transcript.py +1776 -1776
  91. package/skills/estack-read-claude-session-history/scripts/tests/conftest.py +40 -40
  92. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/README.md +20 -20
  93. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/all-noise.jsonl +4 -4
  94. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/basic-session.jsonl +2 -2
  95. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/engagement-gaps.jsonl +9 -9
  96. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/engagement-noise.jsonl +7 -7
  97. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/engagement-parallel-a.jsonl +3 -3
  98. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/engagement-parallel-b.jsonl +3 -3
  99. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/engagement-waiting.jsonl +5 -5
  100. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/interrupted.jsonl +2 -2
  101. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/multi-compact.jsonl +8 -8
  102. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/pending-user.jsonl +2 -2
  103. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/subagent-no-meta/subagents/agent-aaa.jsonl +2 -2
  104. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/subagent-no-meta.jsonl +2 -2
  105. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/subagent-parent/subagents/agent-xyz123.jsonl +2 -2
  106. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/subagent-parent/subagents/agent-xyz123.meta.json +1 -1
  107. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/subagent-parent.jsonl +4 -4
  108. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/time-spread.jsonl +6 -6
  109. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/timeline-day-test.jsonl +5 -5
  110. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/tool-zoo.jsonl +10 -10
  111. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/truncated.jsonl +2 -2
  112. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/unicode.jsonl +2 -2
  113. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/with-advisor.jsonl +3 -3
  114. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/with-compact.jsonl +5 -5
  115. package/skills/estack-read-claude-session-history/scripts/tests/fixtures/with-thinking.jsonl +2 -2
  116. package/skills/estack-read-claude-session-history/scripts/tests/test_backup_roots.py +56 -56
  117. package/skills/estack-read-claude-session-history/scripts/tests/test_engagement.py +239 -239
  118. package/skills/estack-read-claude-session-history/scripts/tests/test_json_format.py +201 -201
  119. package/skills/estack-read-claude-session-history/scripts/tests/test_modes.py +199 -199
  120. package/skills/estack-read-claude-session-history/scripts/tests/test_parser.py +195 -195
  121. package/skills/estack-read-claude-session-history/scripts/tests/test_paths.py +133 -133
  122. package/skills/estack-read-claude-session-history/scripts/tests/test_search.py +78 -78
  123. package/skills/estack-read-claude-session-history/scripts/tests/test_subagents.py +43 -43
  124. package/skills/estack-read-claude-session-history/scripts/tests/test_timeline.py +179 -179
  125. package/skills/estack-read-claude-session-history/scripts/tests/test_timezone_and_project.py +212 -212
  126. package/skills/estack-read-claude-session-history/scripts/tests/test_tools.py +80 -80
  127. package/skills/estack-repo-search/SKILL.md +65 -65
  128. package/skills/estack-vscode-file-recovery/SKILL.md +188 -0
@@ -0,0 +1,969 @@
1
+ Harvard Business Review 30 DO 15 www.hbrreprints.org
2
+
3
+ HBR CLASSIC
4
+
5
+ The burdens of subordinates
6
+ always seem to end up on the
7
+ manager's back. Here's how to
8
+ get rid of them.
9
+
10
+
11
+ # Management Time: Who's Got the Monkey?
12
+
13
+ by William Oncken, Jr., and Donald L. Wass
14
+
15
+
16
+ Included with this full-text Harvard Business Review article:
17
+
18
+
19
+ ## 1 Article Summary
20
+
21
+ The Idea in Brief-the core idea
22
+ The Idea in Practice-putting the idea to work
23
+
24
+ 2 Management Time: Who's Got the Monkey?
25
+
26
+
27
+ ### 8 Further Reading
28
+
29
+ A list of related materials, with annotations to guide further
30
+ exploration of the article's ideas and applications
31
+
32
+ Reprint 99609
33
+ This document is authorized for use only by Jillian Smith (jsmith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
34
+ <!-- PageBreak [1] -->
35
+
36
+ HBR CLASSIC
37
+
38
+
39
+ # Management Time: Who's Got the Monkey?
40
+
41
+
42
+ ## The Idea in Brief
43
+
44
+ You're racing down the hall. An employee
45
+ stops you and says, "We've got a problem."
46
+ You assume you should get involved but
47
+ can't make an on-the-spot decision. You
48
+ say, "Let me think about it."
49
+
50
+ You've just allowed a "monkey" to leap from
51
+ your subordinate's back to yours. You're now
52
+ working for your subordinate. Take on
53
+ enough monkeys, and you won't have time
54
+ to handle your real job: fulfilling your own
55
+ boss's mandates and helping peers gener-
56
+ ate business results.
57
+
58
+ How to avoid accumulating monkeys?
59
+ Develop your subordinates' initiative, say
60
+ Oncken and Wass. For example, when an
61
+ employee tries to hand you a problem,
62
+ clarify whether he should: recommend
63
+ and implement a solution, take action
64
+ then brief you immediately, or act and re-
65
+ port the outcome at a regular update.
66
+
67
+ When you encourage employees to handle
68
+ their own monkeys, they acquire new
69
+ skills-and you liberate time to do your
70
+ own job.
71
+
72
+ COPYRIGHT @ 2007 HARVARD BUSINESS SCHOOL PUBLISHING CORPORATION. ALL RIGHTS RESERVED.
73
+
74
+
75
+ ## The Idea in Practice
76
+
77
+
78
+ <table>
79
+ <tr>
80
+ <th rowspan="2">How to return monkeys to their proper own- ers? Oncken, Wass, and Steven Covey (in an afterword to this classic article) offer these suggestions:</th>
81
+ <th>direct control and support employees' growth.</th>
82
+ </tr>
83
+ <tr>
84
+ <td rowspan="3">DEVELOP EMPLOYEES' SKILLS Employees try to hand off monkeys when they lack the desire or ability to handle them. Help employees develop needed problem- solving skills. It's initially more time consum- ing than tackling problems yourself-but it saves time in the long run.</td>
85
+ </tr>
86
+ <tr>
87
+ <td>MAKE APPOINTMENTS TO DEAL WITH MONKEYS</td>
88
+ </tr>
89
+ <tr>
90
+ <td>Avoid discussing any monkey on an ad hoc basis-for example, when you pass a subordi- nate in the hallway. You won't convey the proper seriousness. Instead, schedule an ap-</td>
91
+ </tr>
92
+ <tr>
93
+ <td>pointment to discuss the issue.</td>
94
+ <td>FOSTER TRUST</td>
95
+ </tr>
96
+ <tr>
97
+ <td></td>
98
+ <td rowspan="3">Developing employees' initiative requires a trusting relationship between you and your subordinates. If they're afraid of failing, they'll keep bringing their monkeys to you rather than working to solve their own problems. To promote trust, reassure them it's safe to make mistakes.</td>
99
+ </tr>
100
+ <tr>
101
+ <td>SPECIFY LEVEL OF INITIATIVE</td>
102
+ </tr>
103
+ <tr>
104
+ <td>Your employees can exercise five levels of ini- tiative in handling on-the-job problems. From lowest to highest, the levels are: 1. Wait until told what to do.</td>
105
+ </tr>
106
+ <tr>
107
+ <td>2. Ask what to do.</td>
108
+ <td></td>
109
+ </tr>
110
+ <tr>
111
+ <td>3. Recommend an action, then with your ap- proval, implement it.</td>
112
+ <td></td>
113
+ </tr>
114
+ <tr>
115
+ <td>4. Take independent action but advise you at once.</td>
116
+ <td></td>
117
+ </tr>
118
+ <tr>
119
+ <td>5. Take independent action and update you through routine procedure.</td>
120
+ <td rowspan="2"></td>
121
+ </tr>
122
+ <tr>
123
+ <td>When an employee brings a problem to you, outlaw use of level 1 or 2. Agree on and assign level 3, 4, or 5 to the monkey. Take no more than 15 minutes to discuss the problem.</td>
124
+ </tr>
125
+ <tr>
126
+ <td>AGREE ON A STATUS UPDATE</td>
127
+ <td rowspan="2"></td>
128
+ </tr>
129
+ <tr>
130
+ <td>After deciding how to proceed, agree on a time and place when the employee will give you a progress report.</td>
131
+ </tr>
132
+ <tr>
133
+ <td>EXAMINE YOUR OWN MOTIVES</td>
134
+ <td rowspan="2"></td>
135
+ </tr>
136
+ <tr>
137
+ <td>Some managers secretly worry that if they en- courage subordinates to take more initiative, they'll appear less strong, more vulnerable, and less useful. Instead, cultivate an inward sense of security that frees you to relinquish</td>
138
+ </tr>
139
+ </table>
140
+
141
+
142
+ This document is authorized for use only by Jillian Smith (jsmith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
143
+ PAGE 1
144
+ <!-- PageBreak [2] -->
145
+
146
+ The burdens of subordinates always seem to end up on the manager's
147
+ back. Here's how to get rid of them.
148
+
149
+ HBR CLASSIC
150
+
151
+
152
+ # Management Time: Who's Got the Monkey?
153
+
154
+ by William Oncken, Jr., and Donald L. Wass
155
+
156
+ COPYRIGHT @ 1999 HARVARD BUSINESS SCHOOL PUBLISHING CORPORATION. ALL RIGHTS RESERVED.
157
+
158
+ This article was originally published in the
159
+ November-December 1974 issue of HBR and has
160
+ been one of the publication's two best-selling
161
+ reprints ever.
162
+
163
+ For its reissue as a Classic, the Harvard Busi-
164
+ ness Review asked Stephen R. Covey to provide
165
+ a commentary.
166
+
167
+ Why is it that managers are typically run-
168
+ ning out of time while their subordinates
169
+ are typically running out of work? Here we
170
+ shall explore the meaning of management
171
+ time as it relates to the interaction between
172
+ managers and their bosses, their peers, and
173
+ their subordinates.
174
+
175
+ Specifically, we shall deal with three kinds of
176
+ management time:
177
+
178
+ Boss-imposed time-used to accomplish
179
+ those activities that the boss requires and that
180
+ the manager cannot disregard without direct
181
+ and swift penalty.
182
+
183
+ System-imposed time-used to accommo-
184
+ date requests from peers for active support.
185
+ Neglecting these requests will also result in
186
+
187
+ penalties, though not always as direct or
188
+ swift.
189
+
190
+ Self-imposed time-used to do those things
191
+ that the manager originates or agrees to do. A
192
+ certain portion of this kind of time, however,
193
+ will be taken by subordinates and is called
194
+ subordinate-imposed time. The remaining por-
195
+ tion will be the manager's own and is called
196
+ discretionary time. Self-imposed time is not
197
+ subject to penalty since neither the boss nor
198
+ the system can discipline the manager for not
199
+ doing what they didn't know he had intended
200
+ to do in the first place.
201
+
202
+ To accommodate those demands, managers
203
+ need to control the timing and the content of
204
+ what they do. Since what their bosses and the
205
+ system impose on them are subject to penalty,
206
+ managers cannot tamper with those require-
207
+ ments. Thus their self-imposed time becomes
208
+ their major area of concern.
209
+
210
+ Managers should try to increase the discre-
211
+ tionary component of their self-imposed time
212
+ by minimizing or doing away with the subor-
213
+ dinate component. They will then use the
214
+
215
+ HARVARD BUSINESS REVIEW . NOVEMBER-DECEMBER 1999 This document is authorized for use only by Jillian Smith (jsmith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
216
+ PAGE 2
217
+ <!-- PageBreak [3] -->
218
+
219
+ Management Time: Who's Got the Monkey? . HBR CLASSIC
220
+
221
+ William Oncken, Jr., was chairman of
222
+ the William Oncken Corporation until
223
+ his death in 1988. His son, William
224
+ Oncken III, now heads the company.
225
+ Donald L. Wass was president of the
226
+ William Oncken Company of Texas
227
+ when the article first appeared. He now
228
+ heads the Dallas-Fort Worth region of
229
+ The Executive Committee (TEC), an
230
+ international organization for presidents
231
+ and CEOs.
232
+
233
+ added increment to get better control over
234
+ their boss-imposed and system-imposed activ-
235
+ ities. Most managers spend much more time
236
+ dealing with subordinates' problems than
237
+ they even faintly realize. Hence we shall use
238
+ the monkey-on-the-back metaphor to examine
239
+ how subordinate-imposed time comes into
240
+ being and what the superior can do about it.
241
+
242
+
243
+ ## Where Is the Monkey?
244
+
245
+ Let us imagine that a manager is walking
246
+ down the hall and that he notices one of his
247
+ subordinates, Jones, coming his way. When
248
+ the two meet, Jones greets the manager with,
249
+ "Good morning. By the way, we've got a prob-
250
+ lem. You see .... " As Jones continues, the man-
251
+ ager recognizes in this problem the two char-
252
+ acteristics common to all the problems his
253
+ subordinates gratuitously bring to his atten-
254
+ tion. Namely, the manager knows (a) enough
255
+ to get involved, but (b) not enough to make
256
+ the on-the-spot decision expected of him.
257
+ Eventually, the manager says, "So glad you
258
+ brought this up. I'm in a rush right now. Mean-
259
+ while, let me think about it, and I'll let you
260
+ know." Then he and Jones part company.
261
+
262
+ Let us analyze what just happened. Before
263
+ the two of them met, on whose back was the
264
+ "monkey"? The subordinate's. After they
265
+ parted, on whose back was it? The manager's.
266
+ Subordinate-imposed time begins the mo-
267
+ ment a monkey successfully leaps from the
268
+ back of a subordinate to the back of his or her
269
+ superior and does not end until the monkey is
270
+ returned to its proper owner for care and
271
+ feeding. In accepting the monkey, the man-
272
+ ager has voluntarily assumed a position sub-
273
+ ordinate to his subordinate. That is, he has al-
274
+ lowed Jones to make him her subordinate by
275
+ doing two things a subordinate is generally
276
+ expected to do for a boss-the manager has
277
+ accepted a responsibility from his subordi-
278
+ nate, and the manager has promised her a
279
+ progress report.
280
+
281
+ The subordinate, to make sure the man-
282
+ ager does not miss this point, will later
283
+ stick her head in the manager's office and
284
+ cheerily query, "How's it coming?" (This is
285
+ called supervision.)
286
+
287
+ Or let us imagine in concluding a conference
288
+ with Johnson, another subordinate, the man-
289
+ ager's parting words are, "Fine. Send me a
290
+ memo on that."
291
+
292
+ Let us analyze this one. The monkey is now
293
+
294
+ on the subordinate's back because the next
295
+ move is his, but it is poised for a leap. Watch
296
+ that monkey. Johnson dutifully writes the re-
297
+ quested memo and drops it in his out-basket.
298
+ Shortly thereafter, the manager plucks it
299
+ from his in-basket and reads it. Whose move is
300
+ it now? The manager's. If he does not make
301
+ that move soon, he will get a follow-up memo
302
+ from the subordinate. (This is another form of
303
+ supervision.) The longer the manager delays,
304
+ the more frustrated the subordinate will be-
305
+ come (he'll be spinning his wheels) and the
306
+ more guilty the manager will feel (his backlog
307
+ of subordinate-imposed time will be mounting).
308
+
309
+ Or suppose once again that at a meeting
310
+ with a third subordinate, Smith, the man-
311
+ ager agrees to provide all the necessary
312
+ backing for a public relations proposal he
313
+ has just asked Smith to develop. The man-
314
+ ager's parting words to her are, "Just let me
315
+ know how I can help."
316
+
317
+ Now let us analyze this. Again the monkey
318
+ is initially on the subordinate's back. But for
319
+ how long? Smith realizes that she cannot let
320
+ the manager "know" until her proposal has
321
+ the manager's approval. And from experi-
322
+ ence, she also realizes that her proposal will
323
+ likely be sitting in the manager's briefcase for
324
+ weeks before he eventually gets to it. Who's
325
+ really got the monkey? Who will be checking
326
+ up on whom? Wheel spinning and bottle-
327
+ necking are well on their way again.
328
+
329
+ A fourth subordinate, Reed, has just been
330
+ transferred from another part of the company
331
+ so that he can launch and eventually manage a
332
+ newly created business venture. The manager
333
+ has said they should get together soon to ham-
334
+ mer out a set of objectives for the new job,
335
+ adding, "I will draw up an initial draft for dis-
336
+ cussion with you."
337
+
338
+ Let us analyze this one, too. The subordinate
339
+ has the new job (by formal assignment) and
340
+ the full responsibility (by formal delegation),
341
+ but the manager has the next move. Until he
342
+ makes it, he will have the monkey, and the sub-
343
+ ordinate will be immobilized.
344
+
345
+ Why does all of this happen? Because in
346
+ each instance the manager and the subordi-
347
+ nate assume at the outset, wittingly or un-
348
+ wittingly, that the matter under consideration
349
+ is a joint problem. The monkey in each case
350
+ begins its career astride both their backs. All it
351
+ has to do is move the wrong leg, and-
352
+ presto !- the subordinate deftly disappears.
353
+
354
+ HARVARD BUSINESS REVIEW . NOVEMBER-DECEMBER 1999
355
+ This document is authorized for use only by Jillian Smith (smith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
356
+ PAGE 3
357
+ <!-- PageBreak [4] -->
358
+
359
+ Management Time: Who's Got the Monkey? . HBR CLASSIC
360
+
361
+ The manager can now
362
+ see, with the clarity of a
363
+ revelation on a
364
+ mountaintop, that the
365
+ more he gets caught up,
366
+ the more he will fall
367
+ behind.
368
+
369
+ The manager is thus left with another acquisi-
370
+ tion for his menagerie. Of course, monkeys can
371
+ be trained not to move the wrong leg. But it is
372
+ easier to prevent them from straddling backs
373
+ in the first place.
374
+
375
+
376
+ ## Who Is Working for Whom?
377
+
378
+ Let us suppose that these same four subordi-
379
+ nates are so thoughtful and considerate of
380
+ their superior's time that they take pains to
381
+ allow no more than three monkeys to leap
382
+ from each of their backs to his in any one day.
383
+ In a five-day week, the manager will have
384
+ picked up 60 screaming monkeys-far too
385
+ many to do anything about them individually.
386
+ So he spends his subordinate-imposed time
387
+ juggling his "priorities."
388
+
389
+ Late Friday afternoon, the manager is in his
390
+ office with the door closed for privacy so he
391
+ can contemplate the situation, while his subor-
392
+ dinates are waiting outside to get their last
393
+ chance before the weekend to remind him that
394
+ he will have to "fish or cut bait." Imagine what
395
+ they are saying to one another about the man-
396
+ ager as they wait: "What a bottleneck. He just
397
+ can't make up his mind. How anyone ever got
398
+ that high up in our company without being
399
+ able to make a decision we'll never know."
400
+
401
+ Worst of all, the reason the manager can-
402
+ not make any of these "next moves" is that his
403
+ time is almost entirely eaten up by meeting
404
+ his own boss-imposed and system-imposed
405
+ requirements. To control those tasks, he needs
406
+ discretionary time that is in turn denied him
407
+ when he is preoccupied with all these monkeys.
408
+ The manager is caught in a vicious circle. But
409
+ time is a-wasting (an understatement). The
410
+ manager calls his secretary on the intercom
411
+ and instructs her to tell his subordinates that
412
+ he won't be able to see them until Monday
413
+ morning. At 7 PM, he drives home, intending
414
+ with firm resolve to return to the office to-
415
+ morrow to get caught up over the weekend.
416
+ He returns bright and early the next day only
417
+ to see, on the nearest green of the golf course
418
+ across from his office window, a foursome.
419
+ Guess who?
420
+
421
+ That does it. He now knows who is really
422
+ working for whom. Moreover, he now sees
423
+ that if he actually accomplishes during this
424
+ weekend what he came to accomplish, his sub-
425
+ ordinates' morale will go up so sharply that
426
+ they will each raise the limit on the number of
427
+ monkeys they will let jump from their backs to
428
+
429
+ his. In short, he now sees, with the clarity of a
430
+ revelation on a mountaintop, that the more he
431
+ gets caught up, the more he will fall behind.
432
+
433
+ He leaves the office with the speed of a per-
434
+ son running away from a plague. His plan? To
435
+ get caught up on something else he hasn't
436
+ had time for in years: a weekend with his
437
+ family. (This is one of the many varieties of
438
+ discretionary time.)
439
+
440
+ Sunday night he enjoys ten hours of sweet,
441
+ untroubled slumber, because he has clear-cut
442
+ plans for Monday. He is going to get rid of his
443
+ subordinate-imposed time. In exchange, he
444
+ will get an equal amount of discretionary time,
445
+ part of which he will spend with his subordi-
446
+ nates to make sure that they learn the difficult
447
+ but rewarding managerial art called "The Care
448
+ and Feeding of Monkeys."
449
+
450
+ The manager will also have plenty of discre-
451
+ tionary time left over for getting control of
452
+ the timing and the content not only of his
453
+ boss-imposed time but also of his system-
454
+ imposed time. It may take months, but com-
455
+ pared with the way things have been, the
456
+ rewards will be enormous. His ultimate ob-
457
+ jective is to manage his time.
458
+
459
+
460
+ ## Getting Rid of the Monkeys
461
+
462
+ The manager returns to the office Monday
463
+ morning just late enough so that his four sub-
464
+ ordinates have collected outside his office
465
+ waiting to see him about their monkeys. He
466
+ calls them in one by one. The purpose of each
467
+ interview is to take a monkey, place it on the
468
+ desk between them, and figure out together
469
+ how the next move might conceivably be the
470
+ subordinate's. For certain monkeys, that will
471
+ take some doing. The subordinate's next
472
+ move may be so elusive that the manager
473
+ may decide-just for now-merely to let the
474
+ monkey sleep on the subordinate's back over-
475
+ night and have him or her return with it at an
476
+ appointed time the next morning to continue
477
+ the joint quest for a more substantive move
478
+ by the subordinate. (Monkeys sleep just as
479
+ soundly overnight on subordinates' backs as
480
+ they do on superiors'.)
481
+
482
+ As each subordinate leaves the office, the
483
+ manager is rewarded by the sight of a mon-
484
+ key leaving his office on the subordinate's
485
+ back. For the next 24 hours, the subordinate
486
+ will not be waiting for the manager; in-
487
+ stead, the manager will be waiting for the
488
+ subordinate.
489
+
490
+ HARVARD BUSINESS REVIEW . NOVEMBER-DECEMBER 1999
491
+ PAGE 4
492
+ This document is authorized for use only by Jillian Smith (smith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
493
+ <!-- PageBreak [5] -->
494
+
495
+ Management Time: Who's Got the Monkey? . HBR CLASSIC
496
+
497
+ Later, as if to remind himself that there is
498
+ no law against his engaging in a constructive
499
+ exercise in the interim, the manager strolls by
500
+ the subordinate's office, sticks his head in the
501
+ door, and cheerily asks, "How's it coming?"
502
+ (The time consumed in doing this is discre-
503
+ tionary for the manager and boss imposed for
504
+ the subordinate.)
505
+
506
+ When the subordinate (with the monkey on
507
+ his or her back) and the manager meet at the
508
+ appointed hour the next day, the manager ex-
509
+ plains the ground rules in words to this effect:
510
+
511
+ "At no time while I am helping you with
512
+ this or any other problem will your problem
513
+ become my problem. The instant your prob-
514
+ lem becomes mine, you no longer have a
515
+ problem. I cannot help a person who hasn't
516
+ got a problem.
517
+
518
+ "When this meeting is over, the problem
519
+ will leave this office exactly the way it came
520
+ in-on your back. You may ask my help at
521
+ any appointed time, and we will make a joint
522
+ determination of what the next move will be
523
+ and which of us will make it.
524
+
525
+ "In those rare instances where the next
526
+ move turns out to be mine, you and I will de-
527
+ termine it together. I will not make any
528
+ move alone."
529
+
530
+ The manager follows this same line of
531
+ thought with each subordinate until about
532
+ 11 AM, when he realizes that he doesn't have
533
+ to close his door. His monkeys are gone. They
534
+ will return-but by appointment only. His
535
+ calendar will assure this.
536
+
537
+
538
+ ## Transferring the Initiative
539
+
540
+ What we have been driving at in this monkey-
541
+ on-the-back analogy is that managers can
542
+ transfer initiative back to their subordinates
543
+ and keep it there. We have tried to highlight
544
+ a truism as obvious as it is subtle: namely, be-
545
+ fore developing initiative in subordinates, the
546
+ manager must see to it that they have the ini-
547
+ tiative. Once the manager takes it back, he
548
+ will no longer have it and he can kiss his dis-
549
+ cretionary time good-bye. It will all revert to
550
+ subordinate-imposed time.
551
+
552
+ Nor can the manager and the subordinate
553
+ effectively have the same initiative at the
554
+ same time. The opener, "Boss, we've got a
555
+ problem," implies this duality and repre-
556
+ sents, as noted earlier, a monkey astride two
557
+ backs, which is a very bad way to start a
558
+ monkey on its career. Let us, therefore, take
559
+ a few moments to examine what we call
560
+ "The Anatomy of Managerial Initiative."
561
+
562
+
563
+ ## Making Time for Gorillas
564
+
565
+ by Stephen R. Covey
566
+
567
+ When Bill Oncken wrote this article in 1974,
568
+ managers were in a terrible bind. They were
569
+ desperate for a way to free up their time, but
570
+ command and control was the status quo.
571
+ Managers felt they weren't allowed to em-
572
+ power their subordinates to make decisions.
573
+ Too dangerous. Too risky. That's why On-
574
+ cken's message-give the monkey back to its
575
+ rightful owner-involved a critically impor-
576
+ tant paradigm shift. Many managers working
577
+ today owe him a debt of gratitude.
578
+
579
+ It is something of an understatement, how-
580
+ ever, to observe that much has changed since
581
+ Oncken's radical recommendation. Command
582
+ and control as a management philosophy is all
583
+ but dead, and "empowerment" is the word of
584
+ the day in most organizations trying to thrive
585
+ in global, intensely competitive markets. But
586
+ command and control stubbornly remains a
587
+ common practice. Management thinkers and
588
+ executives have discovered in the last decade
589
+
590
+ that bosses cannot just give a monkey back to
591
+ their subordinates and then merrily get on
592
+ with their own business. Empowering subor-
593
+ dinates is hard and complicated work.
594
+
595
+ The reason: when you give problems back
596
+ to subordinates to solve themselves, you have
597
+ to be sure that they have both the desire and
598
+ the ability to do so. As every executive knows,
599
+ that isn't always the case. Enter a whole new
600
+ set of problems. Empowerment often means
601
+ you have to develop people, which is initially
602
+ much more time consuming than solving the
603
+ problem on your own.
604
+
605
+ Just as important, empowerment can only
606
+ thrive when the whole organization buys into
607
+ it-when formal systems and the informal
608
+ culture support it. Managers need to be re-
609
+ warded for delegating decisions and develop-
610
+ ing people. Otherwise, the degree of real em-
611
+ powerment in an organization will vary
612
+ according to the beliefs and practices of indi-
613
+ vidual managers.
614
+
615
+ But perhaps the most important lesson about
616
+ empowerment is that effective delegation-
617
+ the kind Oncken advocated-depends on a
618
+ trusting relationship between a manager and
619
+ his subordinate. Oncken's message may have
620
+ been ahead of his time, but what he suggested
621
+ was still a fairly dictatorial solution. He basi-
622
+ cally told bosses, "Give the problem back!" To-
623
+ day, we know that this approach by itself is too
624
+ authoritarian. To delegate effectively, execu-
625
+ tives need to establish a running dialogue
626
+ with subordinates. They need to establish a
627
+ partnership. After all, if subordinates are
628
+ afraid of failing in front of their boss, they'll
629
+ keep coming back for help rather than truly
630
+ take initiative.
631
+
632
+ Oncken's article also doesn't address an as-
633
+ pect of delegation that has greatly interested
634
+ me during the past two decades-that many
635
+ managers are actually eager to take on their
636
+ subordinates' monkeys. Nearly all the man-
637
+ agers I talk with agree that their people are
638
+
639
+ HARVARD BUSINESS REVIEW . NOVEMBER-DECEMBER 1999
640
+ This document is authorized for use only by Jillian Smith (smith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
641
+ PAGE 5
642
+ <!-- PageBreak [6] -->
643
+
644
+ Management Time: Who's Got the Monkey? . HBR CLASSIC
645
+
646
+ There are five degrees of initiative that the
647
+ manager can exercise in relation to the boss
648
+ and to the system:
649
+
650
+ 1\. wait until told (lowest initiative);
651
+
652
+ 2\. ask what to do;
653
+
654
+ 3\. recommend, then take resulting action;
655
+
656
+ 4\. act, but advise at once;
657
+
658
+ 5\. and act on own, then routinely report
659
+ (highest initiative).
660
+
661
+ Clearly, the manager should be professional
662
+ enough not to indulge in initiatives 1 and 2 in
663
+ relation either to the boss or to the system. A
664
+ manager who uses initiative 1 has no control
665
+ over either the timing or the content of boss-
666
+ imposed or system-imposed time and thereby
667
+ forfeits any right to complain about what he or
668
+ she is told to do or when. The manager who
669
+ uses initiative 2 has control over the timing but
670
+ not over the content. Initiatives 3, 4, and 5
671
+ leave the manager in control of both, with the
672
+ greatest amount of control being exercised at
673
+ level 5.
674
+
675
+ In relation to subordinates, the manager's
676
+ job is twofold. First, to outlaw the use of ini-
677
+ tiatives 1 and 2, thus giving subordinates no
678
+ choice but to learn and master "Completed
679
+ Staff Work." Second, to see that for each
680
+ problem leaving his or her office there is an
681
+
682
+ agreed-upon level of initiative assigned to it,
683
+ in addition to an agreed-upon time and place
684
+ for the next manager-subordinate confer-
685
+ ence. The latter should be duly noted on the
686
+ manager's calendar.
687
+
688
+
689
+ ### The Care and Feeding of Monkeys
690
+
691
+ To further clarify our analogy between the
692
+ monkey on the back and the processes of
693
+ assigning and controlling, we shall refer
694
+ briefly to the manager's appointment
695
+ schedule, which calls for five hard-and-fast
696
+ rules governing the "Care and Feeding of
697
+ Monkeys." (Violation of these rules will cost
698
+ discretionary time.)
699
+
700
+ Rule 1. Monkeys should be fed or shot.
701
+ Otherwise, they will starve to death, and
702
+ the manager will waste valuable time on
703
+ postmortems or attempted resurrections.
704
+
705
+ Rule 2. The monkey population should be
706
+ kept below the maximum number the man-
707
+ ager has time to feed. Subordinates will find
708
+ time to work as many monkeys as he or she
709
+ finds time to feed, but no more. It shouldn't
710
+ take more than five to 15 minutes to feed a
711
+ properly maintained monkey.
712
+
713
+ Rule 3. Monkeys should be fed by appoint-
714
+ ment only. The manager should not have to
715
+
716
+ underutilized in their present jobs. But even
717
+ some of the most successful, seemingly self-
718
+ assured executives have talked about how hard
719
+ it is to give up control to their subordinates.
720
+
721
+ I've come to attribute that eagerness for con-
722
+ trol to a common, deep-seated belief that re-
723
+ wards in life are scarce and fragile. Whether
724
+ they learn it from their family, school, or athlet-
725
+ ics, many people establish an identity by com-
726
+ paring themselves with others. When they see
727
+ others gain power, information, money, or rec-
728
+ ognition, for instance, they experience what the
729
+ psychologist Abraham Maslow called "a feeling
730
+ of deficiency"-a sense that something is being
731
+ taken from them. That makes it hard for them
732
+ to be genuinely happy about the success of oth-
733
+ ers-even of their loved ones. Oncken implies
734
+ that managers can easily give back or refuse
735
+ monkeys, but many managers may subcon-
736
+ sciously fear that a subordinate taking the ini-
737
+ tiative will make them appear a little less strong
738
+ and a little more vulnerable.
739
+
740
+ How, then, do managers develop the inward
741
+ security, the mentality of "abundance," that
742
+
743
+ would enable them to relinquish control and
744
+ seek the growth and development of those
745
+ around them? The work I've done with numer-
746
+ ous organizations suggests that managers who
747
+ live with integrity according to a principle-
748
+ based value system are most likely to sustain an
749
+ empowering style of leadership.
750
+
751
+ Given the times in which he wrote, it was
752
+ no wonder that Oncken's message resonated
753
+ with managers. But it was reinforced by
754
+ Oncken's wonderful gift for storytelling. I got
755
+ to know Oncken on the speaker's circuit in the
756
+ 1970s, and I was always impressed by how he
757
+ dramatized his ideas in colorful detail. Like the
758
+ Dilbert comic strip, Oncken had a tongue-
759
+ in-cheek style that got to the core of managers'
760
+ frustrations and made them want to take back
761
+ control of their time. And the monkey on your
762
+ back wasn't just a metaphor for Oncken-it
763
+ was his personal symbol. I saw him several
764
+ times walking through airports with a stuffed
765
+ monkey on his shoulder.
766
+
767
+ I'm not surprised that his article is one of
768
+ the two best-selling HBR articles ever. Even
769
+
770
+ with all we know about empowerment, its
771
+ vivid message is even more important and
772
+ relevant now than it was 25 years ago. Indeed,
773
+ Oncken's insight is a basis for my own work on
774
+ time management, in which I have people
775
+ categorize their activities according to urgency
776
+ and importance. I've heard from executives
777
+ again and again that half or more of their time
778
+ is spent on matters that are urgent but not
779
+ important. They're trapped in an endless cycle
780
+ of dealing with other people's monkeys, yet
781
+ they're reluctant to help those people take their
782
+ own initiative. As a result, they're often too
783
+ busy to spend the time they need on the real
784
+ gorillas in their organization. Oncken's article
785
+ remains a powerful wake-up call for managers
786
+ who need to delegate effectively.
787
+
788
+ Stephen R. Covey is vice chairman of the Frank-
789
+ lin Covey Company, a global provider of leader-
790
+ ship development and productivity services and
791
+ products. He is the author of The 7 Habits of
792
+ Highly Effective People (Simon & Schuster, 1989)
793
+ and First Things First (Simon & Schuster, 1994).
794
+
795
+ HARVARD BUSINESS REVIEW . NOVEMBER-DECEMBER 1999
796
+ This document is authorized for use only by Jillian Smith (smith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
797
+ PAGE 6
798
+ <!-- PageBreak [7] -->
799
+
800
+ Management Time: Who's Got the Monkey? . HBR CLASSIC
801
+
802
+ In accepting the monkey,
803
+ the manager has
804
+ voluntarily assumed a
805
+ position subordinate to
806
+ his subordinate.
807
+
808
+ hunt down starving monkeys and feed them
809
+ on a catch-as-catch-can basis.
810
+
811
+ Rule 4. Monkeys should be fed face-to-
812
+ face or by telephone, but never by mail.
813
+ (Remember-with mail, the next move will be
814
+ the manager's.) Documentation may add to
815
+ the feeding process, but it cannot take the
816
+ place of feeding.
817
+
818
+ Rule 5. Every monkey should have an as-
819
+ signed next feeding time and degree of initia-
820
+ tive. These may be revised at any time by mu-
821
+ tual consent but never allowed to become
822
+ vague or indefinite. Otherwise, the monkey
823
+ will either starve to death or wind up on the
824
+ manager's back.
825
+
826
+ ...
827
+
828
+ "Get control over the timing and content of
829
+ what you do" is appropriate advice for manag-
830
+ ing time. The first order of business is for the
831
+
832
+ manager to enlarge his or her discretionary
833
+ time by eliminating subordinate-imposed
834
+ time. The second is for the manager to use a
835
+ portion of this newfound discretionary time to
836
+ see to it that each subordinate actually has the
837
+ initiative and applies it. The third is for the
838
+ manager to use another portion of the in-
839
+ creased discretionary time to get and keep
840
+ control of the timing and content of both boss-
841
+ imposed and system-imposed time. All these
842
+ steps will increase the manager's leverage and
843
+ enable the value of each hour spent in manag-
844
+ ing management time to multiply without
845
+ theoretical limit.
846
+
847
+ Reprint 99609
848
+ To order, see the next page
849
+ or call 800-988-0886 or 617-783-7500
850
+ or go to www.hbrreprints.org
851
+
852
+ HARVARD BUSINESS REVIEW . NOVEMBER-DECEMBER 1999 This document is authorized for use only by Jillian Smith (jsmith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
853
+ PAGE 7
854
+ <!-- PageBreak [8] -->
855
+
856
+ HBR CLASSIC
857
+
858
+ Management Time: Who's Got the Monkey?
859
+
860
+
861
+ ### Further Reading
862
+
863
+ ARTICLES
864
+ What Effective General Managers Really
865
+ Do
866
+ by John P. Kotter
867
+ Harvard Business Review
868
+ March-April 1999
869
+ Product no. 3707
870
+
871
+ A gap has existed between the conventional
872
+ wisdom about how managers work and the
873
+ actual behavior of effective managers. Kotter
874
+ explains that managers who limit their inter-
875
+ actions to orderly, focused meetings actually
876
+ shut themselves off from vital information and
877
+ relationships. Seemingly wasteful activities like
878
+ chatting in hallways and having impromptu
879
+ meetings can, in fact, prove quite efficient
880
+ when managers have an agenda on which they
881
+ are always working. Unplanned encounters
882
+ thus provide an opportunity to advance
883
+ the agenda.
884
+
885
+
886
+ ### The Manager: Master and Servant of Power
887
+
888
+ by Fernando Bartolomé and André Laurent
889
+ Harvard Business Review
890
+ November-December 1986
891
+ Product no. 4215
892
+
893
+ When workers' commitment to their jobs
894
+ wanes, or when they allow resentments to-
895
+ ward bosses, direct reports, and others to
896
+ fester, the reason isn't that bosses are
897
+ power-hungry or direct reports rebellious.
898
+ Conflict and misunderstanding usually arise
899
+ because of power dynamics. Many manag-
900
+ ers can't see how their behavior toward di-
901
+ rect reports and superiors alike is distorted
902
+ by hierarchical differences. The result can be
903
+ a lessening of trust between manager and
904
+ subordinate, which inhibits open communi-
905
+ cation and risk taking.
906
+
907
+
908
+ ### Pygmalion in Management
909
+
910
+ by J. Sterling Livingston
911
+ Harvard Business Review
912
+ September-October 1988
913
+ Product no. 88509
914
+
915
+ Further substantiation of the manager's cru-
916
+ cial role in developing initiative. Experiments
917
+ and studies have demonstrated that manag-
918
+ ers'expectations have a direct impact on their
919
+ direct reports' productivity-the "Pygmalion
920
+ effect." High expectations on the part of
921
+ managers lead to the development of a
922
+ "superstaff." Low expectations result in dam-
923
+ aged egos and poor performers. The differ-
924
+ ence in the behavior of these two groups is a
925
+ direct result of how each of them is treated by
926
+ the manager.
927
+
928
+
929
+ ### BOOK Harvard Business Review on Managing People
930
+
931
+ Harvard Business School Press
932
+ 1999
933
+ Product no. 9075
934
+
935
+ The articles in this collection suggest ways to
936
+ build organizations with judicious and effec-
937
+ tive systems for managing people. Although
938
+ each article presents a thought-provoking
939
+ perspective on some aspect of people man-
940
+ agement, two are especially applicable to
941
+ the subject of time spent managing others.
942
+ Writing on empowerment, Chris Argyris
943
+ warns that using it as the ultimate criterion
944
+ for success in an organization may cover up
945
+ deeper problems that need to be addressed.
946
+ Jay Conger argues that persuasion, defined
947
+ as learning from others and negotiating a
948
+ shared solution, is gaining importance as a
949
+ management tool in post-command-and-
950
+ control organizations.
951
+
952
+
953
+ ## Harvard Business Review
954
+
955
+
956
+ ### To Order
957
+
958
+ For Harvard Business Review reprints and
959
+ subscriptions, call 800-988-0886 or
960
+ 617-783-7500. Go to www.hbrreprints.org
961
+
962
+ For customized and quantity orders of
963
+ Harvard Business Review article reprints,
964
+ call 617-783-7626, or e-mai
965
+ customizations@hbsp.harvard.edu
966
+
967
+ This document is authorized for use only by Jillian Smith (jsmith@allinialglobal.com). Copying or posting is an infringement of copyright. Please contact customerservice@harvardbusiness.org or 800-988-0886 for additional copies.
968
+ PAGE 8
969
+ <!-- PageBreak [9] -->