What actually makes someone a good manager, historically speaking
People love to list famous managers like they're all the same. They're not. You pick examples and you'll notice a pattern, but the pattern isn't "be nice" or "work hard." It's more specific than that. I've spent years studying how people ran large operations, from military campaigns to corporate divisions, and the useful examples share a few non-obvious traits. The boring ones don't get remembered. The interesting ones do.
Examples Of Good Managers In History
Here are four you can actually study, not just quote at team meetings. Palmer ran the largest telecom monopoly in the UK during its transition from state-owned utility to competitive market. The job was technically managing infrastructure while preparing the company for privatization. What most people miss is that he didn't try to make the old company faster. He explicitly decided which parts of British Telecom needed to stay slow and careful — the switching networks — and which parts could be pushed aggressively — the customer service and billing divisions. He split performance metrics by division type instead of applying one standard across everything. That's the counter-intuitive part beginners always get wrong. They think good management means raising the bar everywhere. It usually means differentiating the bar by function.
I ran into this exact problem when a client asked me to apply a single KPI framework across their R&D and sales teams. Sales needs velocity. R&D needs depth. Forcing one framework onto both produced exactly the disaster you'd expect — the R&D team started reporting incremental progress on every small task to game the metric, which is called metric gaming and it destroys whatever measurement system you had. The workaround was separating the teams into different review cycles. Sales reviewed weekly. R&D reviewed monthly with milestone gates instead of volume targets. The numbers looked messier at first but accuracy went up because people weren't optimizing for the dashboard anymore.
Get the Full Details
Corporal Robert Johnson in the US Marine Corps, 1944
Not everyone on this list led thousands of people. Johnson commanded a rifle squad of about twelve men during the battle for Peleliu. What makes him worth studying isn't the heroics. It's that after two days of combat, he reorganized a fragmented unit by explicitly telling people what to do instead of asking for volunteers. He assigned roles based on observed capability under stress, not rank or seniority. One man who hadn't spoken in two days turned out to be a competent radio operator. Johnson found out by giving him the radio instead of waiting for him to volunteer. The lesson here is that good managers often make decisions that look authoritarian in calm conditions but are actually information-gathering moves. You assign roles to test competence. You learn who can do what by watching them do it, not by asking them in a meeting.
Margaret Thatcher as Prime Minister, 1979-1990
This is a contentious example and I'm including it because the management story is distinct from the political one. Thatcher's Whitehall reform efforts showed a clear managerial pattern: she refused to let civil servants set the agenda by default. Every proposal that came to her desk without a clear cost estimate or timeline was returned. Not rejected. Returned with a request for specifics. That's a simple move that most managers never make. They accept proposals as-is and then get surprised when delivery takes twice as long as expected. The default assumption in many organizations is that people will come back with better information. They rarely do unless you create a specific mechanism that requires it. The downside of this approach is obvious. It slows down decision-making in the short term and can frustrate staff who feel micromanaged. I've seen it backfire when applied to routine operational decisions where speed matters more than precision. The workaround is threshold-based: require detailed estimates only for decisions above a certain cost or impact level, and delegate the rest.
Hedy Lamarr and George Antheil during WWII
This isn't a traditional management example but it's relevant. Lamarr and Antheil developed frequency-hopping spread spectrum technology. The managerial insight is in how they handled the patent process and military adoption. They assigned the patent to the US government rather than selling it individually. That was a strategic management decision that prioritized impact over personal profit. More importantly, when the military initially ignored their work, they didn't keep lobbying. They accepted that institutional inertia was real and moved on. The technology was rediscovered decades later and became foundational for modern communications. Sometimes the best managerial decision is knowing when to stop pushing against a wall.
What the actual pattern looks like
These examples aren't identical. They operated in different contexts with different constraints. But they share a specific behavior: they adjusted their management style to the structural reality of the situation rather than applying a consistent philosophy across all situations. Palmer adjusted metrics by division. Johnson adjusted leadership style by combat phase. Thatcher adjusted her engagement level by decision type. Lamarr and Antheil adjusted their approach by institutional receptiveness. Most bad managers do the opposite. They apply one management theory everywhere and blame the results on the people executing it.
If you're looking for a practical takeaway, start by identifying where you're applying a uniform standard that shouldn't be uniform. That's usually where the inefficiency lives.
