Peter Drucker’s 1967 classic still has the sharpest answer to why smart, hardworking people produce so little.
Is Your Boss Actually Effective? (Be Honest.)
Let me ask you something, and I want you to think carefully before answering: Is your manager an effective person?
I’m guessing you already have a list forming.
“My boss schedules meetings about meetings. Nothing ever actually gets decided.”
“My manager takes all the credit when things go right and vanishes the moment something goes wrong.”
“My boss never talks to me directly. I find out what’s happening through the rumor mill.”
“My manager is always impossibly busy — and I genuinely cannot tell you what they’re busy with.”
Sound familiar? I heard versions of these complaints constantly during my years in academic research labs. And what always struck me wasn’t that these managers were lazy or incompetent. Most of them were genuinely intelligent, genuinely hardworking, and genuinely knowledgeable in their fields. They cared about their work. And yet — they were producing almost nothing that mattered.
That gap between effort and impact is exactly what The Effective Executive by Peter Drucker is about. Published in 1967, it’s one of those rare management books that hasn’t aged a day. The core argument is quietly radical: effectiveness is not a personality type, not a leadership style, not a gift some people are born with. It’s a set of learnable practices. And almost anyone who works at them can become effective.
I picked this book up when I was trying to make sense of something I kept observing — why some researchers seemed to produce outsized impact with the same hours everyone else had, while others spun their wheels despite working just as hard. The answer, as I eventually understood it, had almost nothing to do with talent. It had everything to do with how they managed their own time, attention, and decisions.
What follows is what I took from this book — the ideas that stuck, the ones I’ve tried to apply, and the ones I think matter most regardless of whether you have a title or not.
What Every Effective Executive Has in Common (And It’s Not Charisma)
Here’s the thing that trips most people up: effective executives look nothing alike.
They range from extroverted to nearly reclusive, from easygoing to relentless, from warm and generous to cold and demanding. Some are scholars. Some barely read outside their domain. Harry Truman — widely considered one of the most effective chief executives in U.S. history — was famously charisma-free. Yet he reshaped postwar American foreign policy more decisively than almost any president before or since.
So if effectiveness isn’t personality-driven, what is it?
Eight specific practices separate the effective executives from the merely busy ones:
- They asked “What needs to be done?” — not “What do I want to do?”
- They asked “What is right for the enterprise?” — not what’s politically safe
- They built action plans from those answers
- They took personal responsibility for decisions
- They took personal responsibility for communicating those decisions
- They focused on opportunities rather than problems
- They ran productive meetings
- They thought and said “we” rather than “I”
The first two practices give you knowledge. The next four convert knowledge into action. The last two make the organization feel accountable rather than just the person at the top.
Jack Welch didn’t walk into GE asking “what do I want to build?” He asked what needed to be done — and realized the answer was cutting every business unit that couldn’t be number one or number two in its industry, even profitable ones he personally liked. That’s an uncomfortable call. But it’s the kind of call that comes from asking the right question first.
Why Even Smart Executives Stay Stuck: The Four Realities
Before getting into the practices, there’s something worth sitting with: the environment executives operate in is structurally designed to make them ineffective. Not because organizations are poorly run — but because four specific realities are built into the job itself, and unless you actively fight them, they will win.
Your time belongs to everyone else. The moment you carry any kind of responsibility in an organization, your calendar stops being yours. Your boss, your best client, a direct report with an emergency, a colleague who needs a signature — everyone can walk in and take a piece. If you don’t manage your time deliberately, the organization will consume all of it, and you’ll finish every week with the feeling that you worked constantly but accomplished almost nothing you actually intended to.
You’ll keep doing your old job unless you stop yourself. There’s a relentless gravitational pull toward what you were good at before. The former scientist who becomes a lab director or even a department director and still wants to run experiments. The salesperson promoted to VP who keeps personally working deals. This isn’t nostalgia — it’s what the flow of events will drag you toward if you don’t redirect deliberately. Events don’t tell you what’s important. They tell you what’s urgent. Those are very different things.
Your effectiveness depends on people you can’t control. In any organization, your output only matters when someone else uses it. The people most critical to whether your work lands are usually lateral or above you — not the people who report to you. An executive who can’t make their contribution relevant to peers and cross-functional colleagues is largely ineffective, regardless of how much effort they’re putting in.
You see the inside of the organization, but results only exist on the outside. Every result — every customer outcome, every patient treated, every policy implemented — lives in the external world. But what’s visible to you is entirely internal: reports, meetings, office politics, internal dynamics. The higher you go, the more your attention gets pulled toward inside problems. This is one of the most insidious patterns I saw in research environments: brilliant scientists who became administrators and progressively lost touch with the actual science because the internal machinery of running a lab consumed everything.
These four realities can’t be eliminated. They’re structural features of organizational life. But knowing they exist is the first step to not being destroyed by them.
Know Where Your Time Actually Goes (Before You Try to Manage It)
Most productivity advice starts with planning. I’ve come to think that’s exactly backwards.
Planning assumes you know where your time currently goes. Almost no one does. Our memories are unreliable narrators when it comes to time. I’ve tested this on myself more times than I’d like to admit — I’d have a confident sense of how I’d spent a week, and then the actual log would tell a completely different story. The writing I thought I’d done a lot of turned out to be a few fragmented hours. The email I thought was a minor background task had actually consumed two mornings.
The practice that changes this is embarrassingly simple: keep a real-time log of where your time goes, for three to four weeks, then look at it honestly. Not what you planned to do. Not what you remember doing. What you actually did, recorded as it happened.
Once you have that data, the diagnostic questions become useful:
What on this list would nothing happen without? Activities that leave no trace when dropped entirely are pure waste — and almost everyone has more of them than they realize.
What on this list could someone else handle just as well, or better? This isn’t about laziness. It’s about recognizing that if you’re spending time on things others could do, you’re not spending it on the things only you can do.
What am I doing that wastes other people’s time? This one hurts. In my research lab days, I watched senior scientists call everyone into meetings to discuss things that directly involved only two or three people in the room. Everyone sat through it, nobody said anything, and an hour evaporated for eight people. The scientist running the meeting genuinely thought it was useful. It wasn’t.
After trimming, the next step is consolidating what’s left into large blocks. Real work — the kind that moves something forward — doesn’t happen in fifteen-minute fragments between interruptions. It requires chunks of ninety minutes to three hours where you can actually think. A report that needs six hours of sustained focus doesn’t get written in twelve thirty-minute sessions. It gets started twelve times and finished never.
Time is the one resource you cannot buy, borrow, or recover once spent. Until you know where it’s actually going, you’re managing nothing.
From Activity to Contribution: The Question That Changes Everything
Here’s a question I started asking people I worked with, adapted from the book’s framing: What do you do that justifies your being on the payroll?
The answers I got were almost always descriptions of activity. “I manage the bioinformatics pipeline.” “I run the lab’s sequencing operations.” “I coordinate between the wet lab and the computational team.”
What almost nobody said — and what I had to consciously train myself to say — was anything about results. Not what I did, but what changed because I was there. What decisions got made better. What bottlenecks got removed. What the organization could do tomorrow that it couldn’t do yesterday.
The shift from activity-thinking to contribution-thinking is more disorienting than it sounds. It means turning your attention away from your specialty, your department, your immediate tasks — and toward the performance of the whole. It means asking not “am I doing my job well?” but “is this organization better because of what I’m producing?”
Every organization needs three kinds of performance from its people:
Direct results — the measurable outputs that justify the organization’s existence. Revenue for a business. Patient outcomes for a hospital. Publication and discovery for a research lab.
Values reinforcement — a commitment to what the organization stands for and why. Without this, organizations drift into incoherence. They start optimizing for the wrong things and lose the thread of what they were built to do.
People development — building the human capacity to perform tomorrow. An organization that can’t reproduce its own competence is already declining, even if it looks healthy today.
Focusing on contribution isn’t just a mental reframe — it actually changes the quality of relationships at work. The teams I’ve seen operate with the most trust and the clearest communication were almost always oriented around a shared output they cared about. Warm feelings are nice. But productivity comes from people who understand what they’re collectively trying to produce and who take responsibility for their piece of it.
Build on What’s Already Strong — Stop Trying to Fix Everything That Isn’t
I spent years in environments where the implicit performance model was: identify your weaknesses, develop them, become more well-rounded. Annual reviews reinforced this. Feedback conversations reinforced this. The whole apparatus of professional development was built around the assumption that the goal was a person with no significant gaps.
The problem is that this model produces mediocrity. Not because self-improvement is wrong, but because it optimizes for the absence of weakness rather than the presence of strength. Those are completely different targets.
Strong people almost always have strong weaknesses. If you’ve spent time around genuinely exceptional people — in any field — you know this. The most incisive analytical minds are often terrible at reading a room. The most creative thinkers often can’t execute. The best operators often struggle to imagine anything they haven’t seen work before. Peaks and valleys come together.
Lincoln spent three years appointing generals to lead Union forces based on who had the fewest obvious flaws. He got three years of stalemate despite overwhelming material advantages. Then he appointed Grant — a man with a well-known drinking problem and a personality that rubbed many people the wrong way — and the war turned. The question was never whether Grant had weaknesses. The question was whether Grant could win campaigns. He could.
The practical rules I’ve taken from this:
Make roles demanding enough that only genuine strength can succeed in them. If you design a job that anyone moderately competent can do, you’ll attract moderately competent people. If you design it around what matters most and make it large, you attract people who want to rise to it.
Ask “what can this person do exceptionally well?” before asking “what are their limitations?” The limitations are always there. The question is whether the strength is relevant to the job — and whether the weaknesses interfere with that strength.
Tolerate the weaknesses that come along with the strengths, unless those weaknesses directly undermine the work. A researcher who produces extraordinary insights and is chronically disorganized is a manageable problem. A manager who can’t communicate clearly to their team is a structural failure.
And for your own development — the question isn’t “what am I bad at, and how do I fix it?” The more useful question is “what am I genuinely good at, and am I in a position where that strength is actually being used?”
First Things First: Why Doing One Thing at a Time Is the Real Productivity Secret
The people I’ve watched accomplish the most — in research, in entrepreneurship, in content creation — almost universally share one habit: they concentrate. They pick one thing, give it their full attention, finish it or get it to a stable resting point, and then move to the next.
This sounds so obvious it’s almost embarrassing to write. But watch how most people actually work. They maintain seven ongoing projects simultaneously, context-switch constantly, and generate a lot of motion without much forward progress. I’ve done this myself. It’s seductive because it feels productive — you’re always doing something — but the output rate is terrible.
The insight I keep coming back to: doing one thing at a time doesn’t mean accomplishing fewer things. It often means accomplishing more, because each thing actually gets finished. Time spent is more concentrated. Progress compounds. And you spend less energy managing the overhead of constantly reloading context on a dozen half-finished projects.
The practical question this creates is a hard one: what’s actually first?
A few principles I’ve found useful:
Pick the future over the past. Resources and energy should flow toward what comes next, not defending what already exists. If you’re holding onto a project, a commitment, or a strategy primarily because you’ve already invested in it — not because it’s where opportunity lies — that’s a signal to drop it. The question worth asking regularly: “If we weren’t already doing this, would we start it today?” If the answer is no, it belongs on the stop-doing list.
Treat opportunities as higher priority than problems. Problems are loud and demand attention. Opportunities are quiet and disappear if you don’t pursue them. Most organizations I’ve been part of spend the vast majority of their time and talent on problems and almost none on opportunities. The imbalance is almost never noticed because problems are visible and urgent in a way that opportunities aren’t.
Set priorities deliberately, and then protect them. The enemy of real priority is not laziness — it’s the infinite supply of things that feel urgent. Email, requests, meetings, crises. None of those things will stop coming. The only defense is a prior decision about what matters, combined with the willingness to say no to almost everything else.
How Effective Decisions Actually Get Made
Most people think of decision-making as the moment of choosing. But the choice itself is actually the smallest part. Everything that leads up to it determines whether the choice is sound or not.
There are five elements to a decision that actually works:
First: Is this a recurring pattern or a genuinely unique situation? Most problems that look unique aren’t. They’re specific instances of a general category, and the right response is a policy or system that handles the whole category — not a one-off fix for this instance. Treating a recurring problem as a one-time exception is one of the most common ways organizations waste leadership attention. If you find yourself solving the same crisis every year, the crisis isn’t the problem — the absence of a system that prevents it is.
Second: Define what the decision actually needs to accomplish before generating options. The worst decisions I’ve watched get made started with solutions looking for problems. Someone had an answer and worked backwards to the question. The right sequence is to sit with the problem until you understand what a satisfactory resolution would actually look like — the minimum requirements the solution has to meet. Only then do you evaluate options.
Third: Start with opinions, not facts. This one felt wrong to me the first time I encountered it. But it’s correct. People with experience in an area have formed opinions about it. Asking them to “just look at the data” doesn’t eliminate those opinions — it just makes them invisible and therefore unexaminable. Better to surface the opinion directly, name it as a hypothesis, and then design a process to test it. That’s how science actually works, and it’s how good decision-making works too.
Fourth: Convert the decision into action before the meeting ends. A decision without a named owner, a deadline, and a follow-up mechanism is not a decision — it’s a statement of intent. I’ve watched organizations make the same decision repeatedly because nobody ever converted it into accountable action. The decision has to degenerate, as the book puts it, into work.
Fifth: Build feedback in from the start. How will you know in three months whether this decision was right? If you can’t answer that question when you make the decision, you’ve made it impossible to learn from.
Why Disagreement Is a Feature, Not a Bug
Here’s the counterintuitive piece that I think matters most about decision-making: consensus reached too quickly is usually a warning sign, not a green light.
Decisions involve judgment under uncertainty. If everyone in a room agrees immediately, one of two things is happening. Either the question is so obvious it didn’t really need a formal decision, or people are suppressing their actual views to align with whoever seems to be in charge. Neither situation produces good decisions.
The best decisions I’ve been part of had real disagreement in them — people who saw the situation differently, argued their positions, and forced the group to actually examine what was being decided and why. That friction is uncomfortable in the moment. But it’s what prevents decisions that look sensible at the time from unraveling six months later in ways that were completely predictable.
There’s a related point about how to use the disagreement productively. The goal isn’t argument for its own sake. It’s to have competing interpretations tested against reality before you commit. When two people see the same situation differently, the question isn’t who’s right in the abstract — it’s what evidence would distinguish between their views. That reframe turns conflict into a structured inquiry rather than a power struggle.
And sometimes, after going through all of this, the right answer is to make no decision at all. Not every situation requires action. Sometimes the costs of acting outweigh the costs of waiting. Recognizing that inaction is a legitimate choice — and not just a failure to decide — is itself a form of executive judgment.
What If You’re Not an Executive?
I want to close with the piece I find most useful personally, because my own title has varied a lot over the years.
The word “executive” sounds like it only applies to people with corner offices. But if you step back, the definition is really just: anyone whose decisions significantly affect the performance of the organization they’re part of. By that definition, a senior individual contributor qualifies. So does a research scientist who determines which projects get pursued. So does an independent creator deciding where to focus their output.
And even if none of those categories fit you right now, these practices aren’t really about organizational power. They’re about how to make the most of the time and attention you have.
Knowing where your time actually goes. Asking what you’re contributing rather than what you’re doing. Building on what you’re genuinely strong at. Concentrating on one priority at a time instead of managing a portfolio of half-commitments. Making decisions through structured disagreement rather than premature consensus.
These are applicable to managing a research agenda. To building a side project. To thinking about where your career is heading. To managing ngs101.com or BullishBooks — both of which I’ve found benefit from this kind of regular audit.
The honest version of this is that I don’t always practice any of this well. I drift. I let the urgent crowd out the important. I spread my attention across too many things and wonder why nothing seems to move. The practices aren’t a fixed state you achieve — they’re a direction you keep correcting toward.
But the underlying question — Am I spending my time and attention on what will actually matter? — is one I think is worth asking more often than most of us do.
What’s the biggest effectiveness gap you see in your own work — time, priorities, or something else? Drop a comment below.
