I read The 48 Laws of Power, and It Changed How I See Every Workplace Interaction

I never thought a book written about 16th-century court politics would make me rethink how I handle Slack messages, support tickets, and one-on-ones. But here I am.

A friend recommended The 48 Laws of Power by Robert Greene a while back. I kept putting it off. The title sounded aggressive, almost manipulative. I pictured some hustle-culture playbook about crushing your enemies and climbing the corporate ladder. I was wrong.

It’s not a book that tells you to be ruthless. It’s a book that tells you the world already is, and you’re better off understanding how it works than pretending it doesn’t exist.

Let me walk you through what actually stuck with me.

What is this book really about?

Robert Greene studied 3,000 years of history, from Chinese emperors to Renaissance artists to French diplomats, and pulled out 48 patterns of how power works. Each law comes with historical examples of people who followed it and won, and people who broke it and paid for it.

The 48 Laws of Power is a New York Times bestseller with over 1.2 million copies sold in the US alone. Greene isn’t guessing. He’s documenting what worked for people like Bismarck, Kissinger, Michelangelo, and Napoleon.

Some of the laws sound harsh on the surface. Take credit for others’ work. Crush your enemy completely. Seem like a friend, but be a spy. But when you read the context, the historical examples, and Greene’s analysis, you realize these aren’t instructions. They’re observations about human nature.

And honestly, once I started reading, I couldn’t stop seeing these patterns everywhere.

The laws that hit me the hardest

Out of 48 laws, maybe a dozen completely rewired how I think about work and relationships. Here are the ones I keep coming back to.

Law 1: Never upstage the boss

This one hit close to home. Greene explains it through the story of Nicolas Fouquet, King Louis XIV’s finance minister. Fouquet threw an extravagant party to impress the king. The party was so good that people couldn’t stop talking about it, which made the king feel outdone. Fouquet was arrested the next day and imprisoned for life.

The lesson isn’t never do good work. The lesson is to make your boss feel like the success is theirs. In a remote work environment, this is subtle but critical. When you solve a hard problem, frame it as a team win, not a personal victory lap. The people who get promoted aren’t always the loudest. They’re the ones who make their leads look good.

I used to rush to share solutions in broader channels, tagging everyone. Now I think about who should get the visibility first. It sounds political, and it is. But it is also just being smart about relationships.

Law 4: Say as little as possible

Greene uses the example of Andy Warhol, who became more powerful the less he spoke. Interviewers would struggle to interpret his vague, ambiguous answers, convinced there was deep meaning behind them. In reality, Warhol had figured out that silence creates mystique.

This one changed how I handle disagreements. I used to feel the need to explain myself thoroughly every time someone questioned a decision. Now I say less. I state my position clearly once and let it sit. People who are used to you over-explaining get uncomfortable when you stop. That discomfort isn’t a bad thing. It means they’re actually thinking about what you said instead of waiting for you to finish.

In support too, I noticed that shorter, clearer replies get better outcomes than long walls of explanation. The customer reads the whole thing. They understand it faster. They trust it more.

Law 9: Do not argue; demonstrate

This is my favorite law in the entire book. Greene tells the story of Michelangelo carving the statue of David. The mayor of Florence looked at it and said the nose was too big. Michelangelo didn’t argue. He invited the mayor up the scaffolding, pretended to chisel the nose, and asked for another look. The mayor said it was perfect. Michelangelo hadn’t changed a thing. He just changed the mayor’s vantage point.

I think about this constantly. When a merchant tells me something is broken in WooCommerce, I don’t argue that it’s working as expected. I show them. I set up a test, reproduce the scenario, and let them see the result. The conversation shifts from “you’re wrong” to “oh, I see what’s happening”.

Arguments create resentment even when you win. Demonstrations create understanding.

Law 10: Misery is contagious

Greene is blunt about this one. Some people are perpetually miserable, and they spread it like an infection. He says to avoid them the way you’d avoid a plague.

I’ve been in situations where one consistently negative person in a group chat or a team channel dragged the whole mood down. Everyone starts complaining. Energy drops. Output drops. And the miserable person never changes. They just keep pulling others into their orbit.

Greene’s advice isn’t cruel; it’s practical. You can’t fix someone who creates their own misery. You can only protect yourself by limiting exposure and surrounding yourself with people who bring energy, not drain it.

Law 11: Be needed

This one is about making yourself indispensable. Greene uses the example of Bismarck, who served weak Prussian kings and made himself so essential to their operations that they couldn’t function without him. He got whatever he wanted by simply threatening to resign.

In tech, this translates directly. The person who understands the legacy codebase, the person who knows how the payment gateway integration actually works, the person who can untangle a subscription renewal issue that has everyone else stuck. That person has leverage. Not because they hoard knowledge, but because they invested the time to deeply understand something complex.

I’ve been on both sides of this. When I was new, I felt replaceable. As I built deeper expertise in WooCommerce subscriptions and the extension ecosystem, I noticed that conversations started routing through me. That’s not ego. That’s the result of showing up consistently and going deeper than surface-level understanding.

Law 23: Focus your efforts

Greene warns against spreading yourself too thin. Focus your resources and energy where you’ll have the most impact.

This sounds obvious, but I failed at it for years. I used to say yes to everything. Extra projects, side tasks, helping with things that weren’t my responsibility. I thought being helpful everywhere would make me valuable. Instead, it made me average at everything and excellent at nothing.

The shift came when I started asking myself, what is the one thing I can do right now that makes everything else easier or unnecessary? That question, borrowed partly from Greene’s thinking, changed my daily workflow.

Law 29: Plan through the end

Greene says to make detailed plans with a clear ending, accounting for all possible developments. Don’t be tempted off your path.

This applies to everything from writing code to handling a complex support escalation. When I start debugging an issue now, I think about what the resolution looks like before I start. What does done look like? What are the possible outcomes? What if the fix introduces a new problem?

Before reading this, I’d dive into problems reactively. Fix one thing, another breaks; chase that, lose an hour. Planning through the end, even just mentally sketching the path, saves time and keeps you calm when things go sideways.

I can share one that still sticks with me. I was on live chat, and a merchant came in with what looked like a quick fix. I moved fast, made a change I shouldn’t have without asking for confirmation first. My leads handled it well; nothing blew up, but I sat with that mistake for a while.

Even when something looks simple, especially when it involves deleting or closing something, slow down. Ask for confirmation. Better yet, move it to an async conversation where you can think before you act. Speed feels productive in the moment, but one rushed action can undo the trust you spent weeks building.

Law 36: Ignore small problems

Greene uses the example of President Woodrow Wilson, who turned a small border incident with Pancho Villa into a prolonged military embarrassment by overreacting. He sent 123,000 troops into the mountains of Mexico to catch one bandit. Villa’s popularity, which had been fading, exploded.

I see this pattern in codebases and in support. A minor UI inconsistency gets escalated, and suddenly three engineers are debating the right shade of a button border for a week. A customer sends a mildly frustrated message, and instead of a calm reply, the team spirals into a postmortem.

Some problems solve themselves if you leave them alone. Others need attention. The skill is knowing which is which. Greene’s framing helped me get better at making that distinction.

What I disagree with?

I’d be lying if I said I agreed with all 48 laws. Some of them, like Law 7 (take credit for others’ work) and Law 14 (seem like a friend, but be a spy), feel genuinely toxic if applied literally.

Greene is clear that these are observations, not prescriptions. He’s describing what powerful people throughout history actually did. But reading it uncritically, especially if you’re in a competitive mindset, could lead you down a pretty dark path.

I chose to treat the book like a field guide. It describes the terrain. It doesn’t tell you which direction to walk. Some of these laws are useful as defensive knowledge, meaning you recognize when someone is using them on you. Others are worth practicing because they genuinely make you more effective without hurting anyone.

The deeper lesson

The real takeaway for me wasn’t any single law. It was the underlying idea that power dynamics exist in every interaction, and pretending they don’t puts you at a disadvantage.

Greene makes a strong case early in the book that people who loudly claim to be above power games are often the most skilled players. They use moral superiority as a smokescreen. I’ve seen this firsthand in professional settings. The person who says they don’t do politics is often the most political person in the room.

You don’t have to play dirty. But you should understand the game. That’s what this book gave me.

Who should read this?

If you work with people (which is everyone), this book has something for you. It’s especially useful if you:

• Work in a large organization with complex team dynamics.
• Handle customer-facing roles where persuasion and patience matter.
• Want to understand why certain people seem to always get their way.
• Are interested in history and the psychology behind human behavior.

It’s a long book, roughly 450 pages, and some of the historical examples go deep. But Greene is a compelling writer. The stories of Bismarck, Talleyrand, Louis XIV, and even con artists like Victor Lustig read like thrillers.

Final thoughts

The 48 Laws of Power isn’t a book I’d recommend without context. If you read it as a playbook for manipulation, you’ll become a worse person. If you read it as a study of human nature, history, and the invisible forces that shape every organization and relationship, it will make you sharper.

I finished it today, and I’m already thinking about it differently. Not because I’m trying to outsmart anyone, but because it gave me a vocabulary for things I was already experiencing but couldn’t name.

The best thing about reading it was realizing that none of this is new. People have been navigating these dynamics for thousands of years. The game hasn’t changed. Only the setting has.

If you pick it up, read it slowly. Let the stories sink in. And when you finish, look around your own workplace. You’ll start seeing the laws everywhere.

That’s not cynicism. That’s awareness. And awareness is the first step to navigating anything with intention.