High Output Management
In this legendary business book and Silicon Valley staple, the former chairman and CEO of Intel shares his perspective on how to build and run a company. A practical handbook for navigating real-life business scenarios and a powerful management manifesto with the ability to revolutionize the way we work. "An organizational Baedeker for managers at all levels.... A highly credible handbook for organizing work and directing and developing employees." —The New York Times The essential skill of creating and maintaining new businesses—the art of the entrepreneur—can be summed up in a single word: managing. Born of Grove’s experiences at one of America’s leading technology companies (as CEO and employee number three at Intel), High Output Management is equally appropriate for sales managers, accountants, consultants, and teachers, as well as CEOs and startup founders. Grove covers techniques for creating highly productive teams, demonstrating methods of motivation that lead to peak performance. "Generous enough with advice and observations to be required reading." —The Wall Street Journal
Stats for nerds
116recommend
193mentions
161people
2009–2026years
73% recommend27% neutral1% critical
Mentions per year
What Hacker News says
- You might like these too:
High Output Management (Andrew Grove) https://vectree.io/c/high-output-management-andrew-grove
Never Split the Difference (Chris Voss) https://vectree.io/c/never-split-the-difference-chris-voss
Influence: The Psychology of Persuasion (Robert Cialdini) https://vectree.io/c/influence-the-psychology-of-persuasion-...
Hooked: How to Build Habit-Forming Products (Nir Eyal) https://vectree.io/c/hooked-how-to-build-habit-forming-produ...
Thinking in Systems (Donella Meadows) https://vectree.io/c/thinking-in-systems-donella-meadows
- You’re describing a real coordination problem: over-polished, abstraction-heavy “AI voice” increases cognitive load and reduces signal. Since you don’t have positional authority—and leadership models the behavior—you need norm-shaping, not enforcement. Here are practical levers that work without calling anyone out:
1. Introduce a “Clarity Standard” (Not an Anti-AI Rule) Don’t frame it as anti-AI. Frame it as decision hygiene. Propose lightweight norms in a team doc or retro:
TL;DR (≤3 lines) required
One clear recommendation
Max 5 bullets
State assumptions explicitly
If AI-assisted, edit to your voice
This shifts evaluation from how it was written to how usable it is. Typical next step: Draft a 1-page “Decision Writing Guidelines” and float it as “Can we try this for a sprint?”
2. Seed a Meme That Rewards Brevity Social proof beats argument. Examples you can casually share in Slack:
“If it can’t fit in a screenshot, it’s not a Slack message.”
“Clarity > Fluency.”
“Strong opinions, lightly held. Weak opinions, heavily padded.”
Side-by-side: AI paragraph → Edited human version (cut by 60%)
You’re normalizing editing down, not calling out AI. Typical next step: Post a before/after edit of your own message and say: “Cut this from 300 → 90 words. Feels better.”
3. Cite Credible Writing Culture References Frame it as aligning with high-signal orgs:
High Output Management – Emphasizes crisp managerial communication.
The Pyramid Principle – Lead with the answer.
Amazon – Narrative memos, but tightly structured and decision-oriented.
Stripe – Known for clear internal writing culture.
Shopify – Publicly discussed AI use, but with expectations of accountability and ownership.
You’re not arguing against AI; you’re arguing for ownership and clarity. Typical next step: Share one short excerpt on “lead with the answer” and say: “Can we adopt this?”
4. Shift the Evaluation Criteria in Meetings When someone posts AI-washed text, respond with:
“What’s your recommendation?”
“If you had to bet your reputation, which option?”
“What decision are we making?”
This conditions brevity and personal ownership. Typical next step: Start consistently asking “What do you recommend?” in threads.
5. Propose an “AI Transparency Norm” (Soft) Not mandatory—just a norm:
“If you used AI, cool. But please edit for voice and add your take.”
This reframes AI as a drafting tool, not an authority. Typical next step: Add a line in your team doc: “AI is fine for drafting; final output should reflect your judgment.”
6. Run a Micro-Experiment Offer:
“For one sprint, can we try 5-bullet max updates?”
If productivity improves, the behavior self-reinforces.
Strategic Reality If the CEO models AI-washing, direct confrontation won’t work. Culture shifts via:
Incentives (brevity rewarded)
Norms (recommendations expected)
Modeling (you demonstrate signal-dense writing)
You don’t fight AI. You make verbosity socially expensive.
If helpful, I can draft:
A 1-page clarity guideline
A Slack post to introduce it
A short internal “writing quality” rubric
A meme template you can reuse
Which lever feels safest in your org right now?
- One that would've helped is "Founders at Work: Stories of Startups' Early Days" which is a collection of interviews with startup founders by Jessica Livingston. Even though this was a non-profit it effectively sounds like it was a tech startup (he was building an app that was based on, at the time (late 2000s), cutting edge machine learning technology). I think by hearing other founders' stories building other tech products, he would've learned about how they structured their organizations and led their teams. I liked the book personally, but the interviews will be hit or miss depending on the participant.
Here's the book on Amazon: https://amzn.to/3N47TG3
Here's a podcast summary of it: https://businessbooksandco.com/episode/1127af729a0d4aec/foun...
But frankly even just a basic textbook or video course on leadership/management would've helped or something like High Output Management by Andy Grove (Amazon https://amzn.to/3NCAZME, podcast summary https://businessbooksandco.com/episode/095f226633d34496/high...).
In terms of dealing with all of the personal conflict between team members, Radical Candor may have helped (Amazon https://amzn.to/4qNa7bf, podcast summary https://businessbooksandco.com/episode/938d044a/radical-cand...).
- The boring answer is meetings. Chapter 3 of High Output Management has a great treatment on the topic, and it covers both middle management and the executive level, including a timetable from one of Andy Grove's days. Here is a quote where he summarizes:
> As you can see, in a typical day of mine one can count some twenty-five separate activities in which I participated, mostly information-gathering and - giving, but also decision-making and nudging. You can also see that some two thirds of my time was spent in a meeting of one kind or another. Before you are horrified by how much time I spend in meetings, answer a question: which of the activities -- information-gathering, information-giving, decision-making, nudging, and being a role model—could I have performed outside a meeting? The answer is practically none. Meetings provide an occasion for managerial activities.
- This is a great answer. Three things to add:
1. OP didn't say what they wanted to achieve, except for generally improving their career. It's worth trying to make that specific. OP's idea of that will be different from yours, and different from mine. Each person has different objectives.
2. In most situations, your manager is trying to make you successful, for some definition of successful. This is a joint endeavour. It's worth trying to understand what your manager sees as success, even if there is not 100% overlap with what you see as success. 'High Output Management' has good sections on both effective 1:1s and delegation. They are only a couple of pages each. Worth reading and re-reading.
3. Good 1:1s require some effort (including preparation and follow up) but the investment should be worthwhile. (Of course, it's possible that the majority of people have regular 1:1s that are close to useless. But this doesn't have to be you.)
- A colleague asked me for advice on being a manager. Amongst other advice, I suggested he read High Output Management.
He came back a few days later and said that chatGPT knew what was in the book - was it okay if he just read the summary?
I wasn’t sure what to say. It’s probably true that chatGPT can summarize all the main points from the book. But it has always been easy to find the key points from books on line. The hard part of being a manager is figuring out how to take the obvious instructions and act on them consistently.
Maybe some people can do that just be reading the summary. For me though, reading the whole book is important. I find myself thinking back to the examples used to illustrate the points. And I find that repeating ideas in different ways as I read the book helps make them part of my mental framework. I read lots of interesting ideas in quick articles, but they rarely stick with me unless there is a specific translation to action.
I ended up telling my colleague that it was up to him to decide how to learn best. If it was me, I need the book. But he needs to know his own learning system.
Related
Effective Executive
48 recommend · 70
Topgrading
7 recommend · 15
Mastering the Rockefeller Habits
1 recommend · 3
Only the paranoid survive
30 recommend · 86
Inspired
42 recommend · 49
Peopleware
276 recommend · 637
High performance habits
3 recommend · 3
