The Secrets of Consulting
Gerald M. Weinberg · 1985
Editorial rating
- Evidence
- 4/10
- Actionability
- 8/10
- Originality
- 9/10
The thesis
Consulting is less about possessing the perfect answer than helping people change without becoming trapped by their problem, politics, or dependence on you. The consultant's real tool is a flexible mind that can expose choices while accepting limited control.
Who this is for
Technical consultants, coaches, internal advisors, freelancers, and experienced specialists who are repeatedly asked for answers but need better judgment about influence, pricing, resistance, failure, and when not to intervene.
My favorite quote
Once you eliminate your number one problem, number two gets a promotion.
Why it matters
Solving problems does not create a permanent problem-free state, so consultants must improve a client's capacity rather than promise final rescue.
Do this
Ask whether your current project removes a bottleneck or merely promotes the next one, then prepare the client for what follows.
Start here
Act as a jiggler rather than a savior. Introduce a small question, observation, price, boundary, or alternative that helps the client see the situation differently, then let the organization do work it could not begin while trapped in its original framing.
Critical summary
Gerald Weinberg presents consulting as the practice of influencing people who have requested help, then immediately complicates that definition with paradoxes. His First Law says that regardless of what the client reports, there is always a problem; the Second says that whatever its surface appearance, it is always a people problem. Technology, structure, and economics still matter, but people define the problem, protect existing arrangements, interpret advice, and decide whether anything changes. Weinberg therefore casts the consultant as a jiggler who gets a stuck system moving through a useful disturbance rather than a heroic expert who permanently fixes it. The book packages this in devices: the Law of Raspberry Jam warns that influence becomes thinner as it is spread wider; the Ten Percent Promise discourages humiliating clients with grand claims of easy transformation; the Orange Juice Test separates what is technically possible from what the client is willing to pay for; and Rudy's Rutabaga Rule reminds readers that the next problem is already waiting behind the current one. Later chapters address fees, marketing, trust, negotiation, survival, overwork, and self-deception.
What it gets right
- Treats resistance, politics, language, and personal incentives as part of the system instead of inconvenient noise around the technical problem
- Uses short laws and paradoxes that remain memorable during messy client situations where a formal methodology would be too slow or rigid
- Encourages consultants to preserve client capability, accept failure, price consciously, and avoid solving problems they were not invited to solve
What it overstates or misses
- The aphorisms are built from anecdotes and experience, with almost no systematic evidence showing where one rule outperforms another
- Several stories, idioms, and assumptions reflect American consulting culture in the early 1980s and can feel dated or opaque outside that context
- Deliberately contradictory advice develops judgment only when the reader already has enough experience to recognize which principle fits the situation
Weinberg offers no linear delivery process, maturity model, or research program. The evidence is decades of pattern recognition compressed into stories that are valuable precisely because they resist mechanical use. Some readers will find the whimsy excessive, and others will mistake a clever law for an explanation. Still, few books describe the emotional absurdity of advisory work this honestly. Read it after learning a formal consulting method, because it teaches what the method cannot tell you when the client, consultant, and problem refuse to behave.
Key concepts
Jiggler
Create a small disturbance that helps a stuck client perceive new choices instead of attempting to carry the entire system to a solution.
People Problem
Examine incentives, identity, fear, communication, and ownership even when the assignment is presented as purely technical.
Law of Raspberry Jam
Influence becomes thinner as it is spread more widely, so narrow the audience, message, and commitments until they retain substance.
Ten Percent Promise
Promise modest improvement that clients can absorb without feeling exposed, then let larger gains emerge without making humiliation part of the sale.
Orange Juice Test
When asked for something difficult, separate impossibility from price by explaining what it would take and allowing the buyer to choose.
Core insights
-
Every Solution Reveals Another Problem
Design engagements that strengthen the client's ability to handle the next constraint rather than creating dependence on repeated rescue.
-
Permission Defines the Assignment
Unrequested help is often experienced as interference, so confirm that the client wants influence before solving the problem you notice.
-
Change Requires Tradeoffs
Make time, risk, money, certainty, and quality tradeoffs explicit because hidden tradeoffs return later as resistance or disappointment.
-
Pricing Changes Behavior
Fees influence whether clients pay attention, commit resources, respect boundaries, and take responsibility for acting on advice.
-
Consultants Need Survival Systems
Humor, limits, self-awareness, and willingness to fail are not luxuries in work where control is low and expectations are high.
Implementation steps
Today
- Write the presenting problem for one assignment, then add the people behavior that may be creating or protecting it.
- Identify one unrequested solution you are tempted to deliver and ask for permission before investing further effort.
This week
- Use a jiggling question in one stuck meeting, such as asking what would happen if the current constraint disappeared tomorrow.
- Apply the Orange Juice Test to one difficult request by stating the real conditions, cost, and tradeoffs instead of saying yes or no too quickly.
This month
- Review your offers, messages, and commitments for Raspberry Jam and remove one audience, service, or obligation that has made your expertise too thin.
- Create a consultant survival kit containing trusted peers, recovery practices, financial boundaries, warning signs, and a process for reviewing failures.
Ongoing
- Prefer interventions that leave clients more capable of solving future problems without you.
- Collect your own consulting laws from repeated situations, then test where each law fails before treating it as wisdom.
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Select one live client problem and write separate technical, interpersonal, political, and incentive explanations for why it persists.
- Day 3
Ask the client what influence they actually want from you and remove any work that falls outside that permission.
- Day 7
Introduce one small jiggler and observe whether the system produces movement without a complete solution from you.
- Day 14
Make the assignment's tradeoffs explicit and renegotiate one expectation that depends on hidden time, cost, or risk.
- Day 21
Review your fee, boundaries, and client behavior to see whether the commercial arrangement supports serious participation.
- Day 30
Document three personal consulting laws, one example supporting each, and one situation where each rule would be dangerous.
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.
