The 36 Laws of Quiet Power: Book Review and How It Changed My Approach to AI Work — Omkar Vijay Ghate
The 36 Laws of Quiet Power: Book Review and How It Changed My Approach to AI Work
By Omkar Vijay Ghate · 2026-08-10 · LinkedIn · All Articles
I read a lot of books about strategy, persuasion, and power — partly because they are fascinating, and partly because the work I do (building AI systems for Indian businesses) is as much about human dynamics as it is about technology. You can build the most sophisticated AI agent in the world and watch it fail because the people who needed to adopt it felt excluded from the decision to deploy it.
The 36 Laws of Quiet Power arrived in my reading list through a recommendation from a mentor who prefaced it with: "This is not about manipulation. It is about understanding." I am glad I picked it up.
What the Book Is (And Is Not)
The 36 Laws of Quiet Power is not a self-help book in the conventional sense. It does not promise to make you more likeable, more charismatic, or more persuasive in the crude sense. It is more accurately described as a study of subtle authority — the kind that operates without loud assertion, that builds without confrontation, that endures without dependency on position or title.
The "quiet" in the title is its defining feature. The book's thesis is that the most durable forms of power are understated: the reputation built slowly through consistent delivery, the influence that comes from being genuinely useful, the authority that others grant rather than the authority you demand.
This immediately distinguishes it from books like Robert Greene's 48 Laws of Power, which tends toward a more cynical and manipulative frame. Quiet Power is interested in something subtler and, I think, more sustainable — the kind of influence that works over years and across relationships rather than in single tactical moments.
The Laws That Stayed With Me
I am not going to summarise all 36 laws (that would defeat the purpose of reading the book). But let me share the ones that genuinely changed how I think:
Law 7: Speak Last
The person who speaks first in any group sets the frame. The person who speaks last shapes the conclusion. This law is about the strategic value of restraint — waiting until you understand the terrain before committing to a position. In technical discussions, I used to jump in early with opinions. Now I ask more questions first. The quality of my conclusions has improved significantly.
Law 12: Scarcity of Presence
People value access to you roughly in inverse proportion to how available you make yourself. This is not about artificial unavailability or game-playing — it is about the genuine scarcity of deep attention. When I am with a client, I am fully with them. I do not schedule back-to-back calls. The experience of talking to someone who is genuinely present is now rare enough that it registers.
Law 19: Let Them Take Credit
This one is counterintuitive and difficult to follow. When a good idea you introduced gets adopted and the person who adopted it receives credit for implementing it, the book argues that this is actually the best outcome — because now the idea is theirs, which means they will defend and advance it. I have tested this in practice. An AI system that a client's team feels ownership over gets better support, more budget, and faster adoption than one that is seen as "the consultant's thing."
Law 23: The Power of the Unfinished
Leaving something open — a question unanswered, a thought incomplete, a space for the other person to contribute — creates engagement more effectively than delivering a complete package. In presentations, I now deliberately leave space. "Here is what we know. Here is what we are uncertain about. What do you see from your side?" This transforms a monologue into a collaboration.
Law 31: Know When to Withdraw
Strategic withdrawal is not defeat. Sometimes the most powerful move is to step back, let a situation evolve, and re-enter at a better moment. I have lost clients by pushing too hard at the wrong time. I have won them back by demonstrating patience and returning when the timing was right.
The Criticism Worth Voicing
I want to be honest about where I think the book is limited:
Some of the laws work better for people who already have baseline credibility — professional track record, network, cultural capital. For someone starting out without those advantages, "speak last" can result in being spoken over. "Scarcity of presence" can result in being forgotten. The book's wisdom assumes a level of recognised competence that, once established, allows the subtle plays to work. Without that foundation, the approach can backfire.
The book is also somewhat culturally located in a Western professional context. Indian workplace dynamics — relationships with seniority, the role of family connections, the difference between Mumbai and Chennai professional cultures — add dimensions the book does not explicitly address. Some laws require adaptation for the Indian context; a few need to be significantly modified.
And finally, some of the laws edge toward manipulation, even if the book frames them otherwise. "Let them take credit" can be generosity or can be calculated self-effacement for strategic gain. The difference matters, and the book is not always careful to maintain it.
How It Changed My AI Work
The most surprising application of this book has been in how I think about AI deployment in organisations.
Building an AI agent is 30% technical and 70% organisational. You have to understand who is threatened by the change, who stands to benefit, who controls adoption, and how to bring each stakeholder along without triggering defensive resistance. The laws in this book are, in effect, a guide to navigating that organisational landscape.
Law 7 (speak last) means I now do a lot more listening in initial client conversations before presenting what the AI can do. I understand the political terrain first.
Law 19 (let them take credit) means the AI systems I build are presented as the client team's systems, not mine. Their name is in the documentation. Their ideas shaped the design. They demo it to their leadership. I am the technical partner in the background.
Law 31 (know when to withdraw) has saved me from several bad projects. When the organisational readiness is not there, the most powerful move is to delay. A forced AI deployment into a resistant organisation creates lasting damage to AI credibility that takes years to repair.
The most important insight I took from this book: the technical quality of an AI system matters far less than the trust of the people who have to live with it. Building that trust requires exactly the kind of quiet, patient, relationship-sensitive work that the 36 Laws describe.
Who Should Read This
This book is particularly valuable for:
Consultants and advisors who need to influence without hierarchical authority
Technical professionals who are good at their craft but find organisational navigation difficult
People early in their careers who are learning how trust and credibility work
Anyone managing up — working with or influencing people above them in the hierarchy
AI and technology professionals deploying systems into human organisations
It is less useful for people who already have strong political instincts, or for very junior professionals who need to first establish basic visibility before playing the long game.
My Rating: 4/5
This is a thoughtful, nuanced book about a topic that most professional development writing treats superficially. It is not perfect — the cultural specificity is limited, the ethical line between influence and manipulation is sometimes blurry, and some laws assume a level of established credibility that beginners do not have.
But its core insight — that sustainable power is built quietly, through usefulness, patience, and genuine attention — is both true and undervalued in a culture that rewards loud self-promotion.
I have returned to several of these laws repeatedly in the two years since I read it. That is probably the best endorsement I can give a business book.
Further Reading
If you find this book valuable, these complement it well:
Influence: The Psychology of Persuasion by Robert Cialdini — the scientific foundation for much of what Quiet Power teaches
Never Split the Difference by Chris Voss — tactical negotiation skills that pair well with the strategic framing here
The Trusted Advisor by David Maister — specifically about building trust in professional service relationships, highly relevant for consultants
Deep Work by Cal Newport — about the value of depth over performance, which resonates strongly with the quiet power thesis
Want to Build an AI Agent for Your Business?
Omkar Vijay Ghate has built 16+ live AI agents across automotive, real estate, finance and retail in India. Let's talk about what's possible for you.
Frequently Asked Questions
What is The 36 Laws of Quiet Power about?
The 36 Laws of Quiet Power is a guide to subtle influence and understated authority — the kind of power that is built over time through genuine usefulness, patience, and attention rather than through loud assertion or manipulation. It argues that the most durable forms of influence are quiet ones, and lays out 36 principles for developing them.
How does The 36 Laws of Quiet Power differ from The 48 Laws of Power by Robert Greene?
The 48 Laws of Power is often cynical and tactical, presenting power as a game played for dominance. The 36 Laws of Quiet Power is more interested in sustainable influence rooted in trust and usefulness. It is less about winning individual exchanges and more about building a long-term reputation and the kind of authority others grant voluntarily rather than what you seize.
Is this book applicable to professionals in India?
Yes, with some adaptation. The core principles — patience, usefulness, restraint, letting others take credit, strategic withdrawal — translate well to Indian professional contexts. Some laws need adjustment for hierarchical workplace cultures where seniority matters more and direct disagreement with seniors is less acceptable. The book is worth reading critically and adapting rather than applying wholesale.
What is the most useful principle from the book for technical professionals?
Law 19 (Let Them Take Credit) is probably the most counter-intuitive and most valuable for technical professionals who often want their work recognised. For anyone deploying AI or technical systems into organisations, making the client team feel ownership over the system dramatically improves adoption and reduces resistance. The technical excellence fades into the background; the organisational relationship is what endures.
Should I read this book if I am early in my career?
Conditionally yes. The quiet power approach works well when you have established baseline credibility — a track record, a reputation, some recognised skill. Very early in a career, being too quiet can mean being overlooked. Read it with that caveat in mind: the principles become more powerful as your credibility grows. Start by reading the laws about building reputation and usefulness, then layer in the subtler ones as your career develops.
Related Articles
Originally published at omkar-portfolio-ydov.onrender.com
📚 Books by Omkar Ghate
The Human Pattern — A modern guide to understanding human behaviour, patterns and decision-making in the age of AI.
The 36 Laws of Quiet Power — A modern framework of influence, restraint and strategy.
Both available on Amazon India 👆
— Omkar Ghate | Agentic AI Architect | Mumbai
Top comments (0)