Глава 1
The Transformative Power of Authentic Partnership
When Peter Block's "Flawless Consulting" first appeared in 1981, it revolutionized how we think about the consulting relationship. Four decades later, this seminal work remains essential reading for anyone who influences without direct control-which, in today's collaborative world, means virtually everyone. The book has become the bible for consultants worldwide, with Oprah Winfrey reportedly keeping it on her desk and companies like McKinsey recommending it to new associates. What makes this work so enduring? In a world obsessed with technical expertise, Block dared to suggest that the relationship between consultant and client matters more than technical knowledge. His radical proposition: authenticity and partnership create more lasting change than clever manipulation or pure expertise ever could. As organizations continue struggling with complexity and uncertainty, Block's insights about influencing without authority have become more relevant than ever-whether you're a formal consultant, a team leader, or simply someone trying to create change in a resistant system.
Глава 2
The Consulting Relationship: Where True Value Emerges
Consulting isn't just about providing expert advice-it's about creating a relationship where expertise can be effectively transferred and used. The fundamental dilemma of consulting is wanting to influence without having direct control over implementation. This tension exists whether you're an external consultant or an internal staff person (like HR, finance, or planning) trying to influence line managers. The challenge becomes particularly acute when dealing with resistant stakeholders or complex organizational dynamics.
Most consulting failures stem not from technical inadequacy but from relationship problems. When consultants focus exclusively on technical content while ignoring the emotional and interpersonal dimensions of their work, they set themselves up for failure. For example, a brilliant solution might fall flat if key stakeholders feel excluded from the process, or if cultural sensitivities are overlooked. The relationship side provides crucial information about client concerns and possibilities for working together, including unspoken organizational dynamics, power structures, and historical context that might affect implementation.
Consultants must develop comfort with four key elements: responsibility (ensuring a 50/50 balance with clients, where both parties actively contribute to solutions), feelings (recognizing both the client's and your own emotional responses, including resistance, anxiety, and enthusiasm), trust (addressing doubts openly and creating safe spaces for difficult conversations), and your own needs (acknowledging that consultants have legitimate requirements rather than adopting a pure service mentality, including the need for access to information and key stakeholders).
Three core assumptions underpin effective consulting: problem-solving requires valid data (both objective facts and subjective feelings, including quantitative metrics and qualitative feedback), effective decision-making requires free and open choice (people support decisions they help shape, necessitating genuine involvement rather than token participation), and implementation requires internal commitment (people commit to what furthers their interests and aligns with their values). These assumptions guide how consultants structure their engagements and interact with clients.
The consultant's primary goals flow from these assumptions: establish collaborative relationships to maximize resources, solve problems so they stay solved by addressing root causes rather than symptoms, and ensure attention to both technical problems and relationship issues. Since consultants lack direct control over implementation, they must build client commitment throughout the process, removing obstacles that block clients from acting on advice. This might involve addressing organizational politics, resource constraints, or capability gaps.
As consultant Ed Schein identified, consultants work with managers in three ways: as experts (delegated full authority to solve specific problems), as pair-of-hands (implementing manager-defined plans while following detailed instructions), or as collaborators (joining specialized knowledge with the manager's organizational understanding to co-create solutions). While each approach has its place, collaboration typically produces the most sustainable results-though many managers initially prefer expert solutions and may see collaboration as indecisiveness. The key is helping clients understand when each approach is most appropriate.
Authentic behavior-putting into words what you're experiencing with the client as you work-builds trust and client commitment far better than being clever or manipulative. When clients minimize your work's importance, exclude you from decisions, or try to control the process, authenticity means naming what's happening directly. For instance, saying "I notice I'm being left out of key meetings" rather than harboring resentment. These simple statements create balance in the relationship and prevent either side from exerting total control, while modeling the kind of honest dialogue that leads to better outcomes.
Глава 3
The Art of Contracting: Building the Foundation for Success
The contracting phase offers maximum leverage for consultants, as it sets the tone for the entire project. A contract is simply an explicit agreement about expectations and working methods-usually verbal for internal consultants, often written for externals. The term "contract" emphasizes specific expectations and incorporates two relevant legal elements: mutual consent (both sides enter freely) and valid consideration (both parties receive something of value).
Many organizational forces coerce people into starting projects together-whether it's pressure because "everybody is doing it" or direct commands from higher-ups. When consultants work under coercion, they don't have a valid contract, which often leads to problems later. Similarly, underplaying consultant needs at the beginning undermines leverage and creates an imbalanced relationship.
To contract flawlessly means behaving authentically and completing the business of the contracting phase. This includes negotiating wants, coping with mixed motivation, surfacing concerns about exposure and loss of control, clarifying the contract, and giving affirmation to the client. The hard part isn't the actions themselves but valuing their importance-direct discussions about control, vulnerability, wants, and success chances make the difference between average and excellent contracting.
Written contracts should be brief, direct and conversational. The real value is in clarifying understanding before a project begins. Key elements include: boundaries of your analysis (what you'll focus on and what you won't), objectives of the project (expected organizational improvements), information you seek (what data you need access to), your role (how you want to work with the client), the product you'll deliver (what form your feedback will take), support needed from the client (what you want to make the project successful), time schedule (starting time, milestones, completion date), confidentiality (who gets what report), and feedback to you later (how you'll learn about results).
The personal interaction during initial contracting meetings accurately predicts how the project will proceed. Every action carries a message about what the project and relationship will be like. The meeting can follow a logical sequence: make a personal acknowledgment, communicate understanding of the problem, explore client wants and offers, express consultant wants and offers, reach agreement, ask for feedback on control and commitment, give support, and restate actions.
One critical skill is directly expressing what you need from the client to make the project successful. Many internal consultants resist this, believing their pure service role means only satisfying client needs. This self-defeating attitude ignores that your wants-adequate time, access to people and information, client support during difficult moments, agreements on confidentiality-are essential to project success.
Even with careful planning, contracting meetings can reach impasses. When stuck, trust nonverbal cues over words-we have sophisticated verbal defenses but less sophisticated physical ones. If you're explaining something for the third time, experiencing fatigue or irritation, or observing contradictory body language, you're probably stuck. After two unsuccessful attempts at agreement, shift focus to how the meeting itself is going: "I think we're stuck" or "How do you feel we're doing in reaching agreement?"
Despite perfect consulting, some projects simply aren't meant to be. Accept this early rather than hoping for later miracles. When irreparably stuck, directly state: "We're having a hard time reaching agreement. Perhaps now is not a good time to do this work." Ending unviable projects is not about consultant pickiness but about avoiding failure and wasted resources.
Глава 4
Understanding and Managing Resistance: The Gateway to Change
Resistance is the most challenging aspect of consulting. Despite clear, logical presentations and good intentions, clients often resist our expertise. This resistance isn't irrational stubbornness but a natural emotional reaction to being helped and facing difficult organizational problems. Rather than an obstacle, resistance is actually a necessary part of the learning process that must be expressed before clients can genuinely accept and use a consultant's expertise.
Resistance manifests in many subtle forms: clients demanding excessive detail, flooding consultants with irrelevant information, claiming time constraints, questioning practicality, responding with "I'm not surprised" to deflate the consultant's contributions, attacking directly, expressing confusion after multiple explanations, remaining silent, intellectualizing, moralizing, complying too readily, questioning methodology excessively, claiming problems are resolving themselves, or pressing for immediate solutions without examining problems thoroughly.
Clients aren't defending against consultants but against difficult choices, unpopular actions, or uncomfortable realities they've been avoiding. Organizations typically need consultants precisely because they're emotionally too close to see their problems clearly. Client resistance typically stems from concerns about either control or vulnerability. Control is the organizational currency, valued even above effectiveness. Many managers maintain control even when it demonstrably reduces performance. Concern about vulnerability is the second major source of resistance-organizations are competitive political systems where staying ahead of peers, maintaining favor with bosses, and keeping subordinates' loyalty is crucial.
The phrase "overcoming resistance" mistakenly frames resistance as an adversary to be subdued through clever logic. This approach fails because resistance is an emotional process, not a rational one. You cannot talk clients out of their feelings. Instead, the effective strategy is to let resistance naturally dissipate by encouraging direct expression of underlying feelings. When clients authentically express concerns, resistance diminishes.
Handling resistance effectively requires a three-step process: identify what form the resistance is taking by recognizing cues from the client's behavior, name the resistance using neutral, unpunishing language that describes what you observe happening, and be quiet to let the client respond to your observation. This approach helps clients move from indirect expressions of reservations to direct statements of their real concerns.
Client resistance is not a reflection on you as a consultant. Many consultants habitually analyze what they did wrong, quickly listing their weaknesses while struggling to identify their strengths. This self-criticism interferes with keeping the resistance focused where it belongs-on the client. Remember that resistance often signals you've touched something important, and most questions are actually statements in disguise.
Глава 5
From Diagnosis to Discovery: Finding Strengths and Possibilities
The discovery phase serves two primary purposes: developing an independent perspective on the situation and creating a process that builds client commitment and ownership. While traditional diagnosis follows a medical model where consultants identify problems and prescribe solutions, a more effective approach focuses on possibilities rather than problems-looking at strengths and assets rather than deficiencies.
One of the consultant's most important contributions is redefining the problem. Most consulting projects begin because managers feel pain, but their explanations for that pain are often inaccurate. The "presenting problem" that clients initially describe is rarely the real underlying problem. A technical organization example illustrates this perfectly: management thought employees were leaving due to low salaries, housing costs, and unrealistic expectations-factors beyond their control. But consultants discovered the real issues were lack of meaningful work, insufficient feedback, and minimal supervisor attention-all factors within management's control.
How clients manage their technical problems is critical yet often overlooked. Consultants typically focus on business issues while privately discussing management styles and politics with colleagues after hours. This is a mistake. The management approach powerfully affects how expertise will be used. Every discipline faces both technical and organizational problems, but clients usually only present the technical side. Though riskier, addressing management issues is essential-most managers actually want this feedback but rarely get it from subordinates.
While traditional consulting takes a third-party approach, where consultants analyze and recommend solutions separately from those who implement them, whole-system discovery offers a powerful alternative. This approach involves representatives from all parts of the client system in collectively redefining problems, envisioning desired futures, and planning actions. The significance is profound: the people doing the discovery are the same ones who will implement the change.
Since the previous edition, the most interesting development in discovery is the growing interest in examining a system's gifts, capacities, and possibilities rather than just problems. This approach-known variously as asset-based community development, positive deviance, appreciative inquiry, and others-focuses on what works and what the system wants to create. This perspective compensates for limitations in problem-solving approaches, which can imply something is wrong, overly focus on the past, create resistance through "selling" change, and emphasize rational analysis at the expense of engaging hearts and spirits.
Positive deviance, developed by Monique and Jerry Sternin, has successfully addressed seemingly unsolvable problems like child malnutrition and hospital infections. Their approach finds "observable exceptions"-people who have solved problems using the same resources as everyone else. Rather than teaching solutions, they create structures where community members share, demonstrate, and help others practice what works. Community members themselves measure progress, creating ownership and sustainability.
Глава 6
Preparing for and Managing Feedback: Creating Conditions for Action
After collecting data during discovery, consultants must prepare to deliver findings that will lead to action. While clients want recommendations, presenting a clear picture of the situation is 70% of the consultant's contribution. The primary task is presenting a fresh perspective on what's been discovered-this constitutes most of the value. By focusing attention on areas expertise identifies as likely causes or opportunities, consultants can influence the direction of the work regardless of the assignment.
When preparing feedback, consultants must avoid collusion-never supporting stances that reduce the organization's ability to solve problems. This means not developing explanations that place solutions outside client control or downplaying difficult relationships. Consultants shouldn't project their own anxieties onto clients-they deserve all information collected. They should support client expectations by confirming perceptions that match theirs and acknowledging what's working. And they must confront areas needing improvement, even when painful-that's why clients need consultants.
The most effective guideline for conveying feedback is behaving assertively-stating directly what's observed without infringing on others' rights. Consultants must avoid aggressive language that implies incompetence and nonassertive behavior that withholds important observations. The goal is being authentic and assertive, using descriptive rather than evaluative language. Specific observations about behaviors are more useful than vague stereotypes or judgmental labels.
In consulting, various courtroom roles illustrate approaches to avoid. The consultant shouldn't be a judge (interpreting policy, determining penalties), jury (deciding right/wrong), prosecutor (presenting irrefutable evidence for "conviction"), or defendant (overexplaining when questioned). Instead, consultants should be witnesses-presenting accurate information without vested interest in the outcome, offering a clear picture of observations.
The meeting for action represents the moment of truth where the consultant's work can trigger decisions, further discovery, or learning. This meeting should be approached as an opportunity to get action, not just present data-it's the beginning of implementation that will solve a problem or change the status quo.
When presenting findings, focus on a few central aspects rather than sharing all data. Keep presentations short and simple-the longer and more complex, the more you invite methodological questions. Structure presentations around just four categories: analysis of the technical problem, what's working and possible, how the situation is being managed, and recommendations. Limit issues to fewer than ten, remembering the goal is action, not research.
The meeting follows a structured timeline with specific time allocations for each step. For a 60-minute meeting: restate the original contract and state the agenda (5% of time), present the picture and recommendations (15%), ask for client reactions (30%), halfway through ask if the client is getting what they want (10%), discuss decision to proceed (30%), and close with testing for concerns about control and commitment, asking yourself if you got what you wanted, and giving support (10%).
Every meeting is part of the client's discovery process. The crucial skill is staying focused on the here-and-now process rather than just content. Many issues explored during discovery will be acted out in this meeting. The way out is to verbalize what's happening in real time. Resistance means you're on target with something important-move toward it rather than away.
Глава 7
Implementation Through Engagement: Making Change Stick
Implementation-the point of consultation-often fails despite good contracting, accurate diagnosis, and sound recommendations. We've traditionally focused too much on analysis and too little on translating answers into action, mistakenly treating implementation as a rational process. The gap between knowing what to do and finding the right way to do it is substantial.
Change cannot simply be installed like machinery. The engineering mindset works for mechanical problems but falls short with living systems. Implementation requires both tangible shifts (methods, structures) and intangible ones (relationships, commitments). Successful implementation demands thinking like a social architect and community organizer, focusing on engagement rather than installation.
Our belief in executive decisiveness often becomes an obstacle to change. We mistakenly think that once a leader decides, action follows. The truth is that change in human systems depends more on the consent of the governed than the will of those who govern. No single person runs a business or delivers a product, yet we cling to the magical belief that leadership and decisiveness are sufficient.
Traditional installation approaches focus on articulating vision, setting standards, and defining measures. While these elements have legitimate roles, they become problematic when misused as forms of coercion rather than neutral management tools. When consultants and managers impose centrally created visions and standards to maintain control, they interfere with implementation by inviting compliance rather than commitment.
The myth that change grows from a leader's vision leads to laminated mission statements that hang on walls but lack meaning. When top management's vision becomes the only one that counts, it drains energy rather than mobilizing it. Most vision statements are interchangeable platitudes about customers, teamwork and excellence. What matters is the act of creating vision, not its content.
Implementation ultimately depends on whether people at multiple levels take responsibility for the change's success. The nature, tone, and structure of meetings serve as samples people use to determine the credibility of any strategy. Each consulting event must embody the principles we wish the larger change to follow-each moment becomes an example of the destination.
Eight ways to engage include: opening with transparent purpose and a level playing field, renegotiating expectations about participation, rearranging the room to signal peer participation matters, creating a platform for openness and doubt, asking "what do we want to create together?", creating new conversations, choosing commitment and accountability, and focusing on gifts rather than weaknesses.
The redistribution of power needs to be present in how we live, not just in how we decide. These engagement structures are designed to shift power in practice, not just restrain it through rules.
Глава 8
The Heart of the Matter: Learning Over Teaching
Consulting is fundamentally a relationship business. No matter how technical or research-based a project may be, its success ultimately depends on the quality of relationships with clients-the conduit through which expertise passes. Whether coaching individuals, working with teams on strategy, or conducting training, our practice is defined by beliefs about relationships, learning, and the nuances of change.
Despite claims about helping clients learn, most consulting efforts focus more on teaching than learning. The dominant model, borrowed from traditional education, positions the consultant as the central figure who supervises learning while clients passively absorb information. This approach stems from our need for predictability and control, but it's also reinforced by clients conditioned to be passive learners who will "revolt" if asked to define their own agenda or evaluate their performance.
To truly serve clients, consultants must prioritize learning over teaching. This means designing experiences that incorporate surprise, discovery, and not-knowing. We must allow risk, raise stakes, engage in caring confrontation, offer strong support, and affirm what each person knows. Packaging answers and putting them online interferes with genuine learning. While such approaches are faster, more predictable, and more marketable, they ultimately fail because "if high-control, predetermined thinking is the client's problem, we cannot fix it with high-control, predetermined answers."
Most persistent organizational problems have no clear right answer but involve paradoxical tensions: more control or less? Centralization or local autonomy? Freedom or structure? Truth-telling or political awareness? Technology or human development? The consultant's task isn't to choose one side or even find middle ground, which loses "the benefit of the unique ideas at the two poles." Instead, we must "evoke an exploration of the polarity, postpone the quick answers, and make sure that the complexity of the question is acknowledged before action is chosen."
We must learn to trust questions and recognize how the way we ask them determines the answers we develop. We get stuck by asking the wrong questions-typically "how" questions that focus on methodology and technique rather than purpose or meaning. "How" questions merely lead to trying harder at what we're already doing. To create meaningful change, we must question what we're doing and why, choosing depth over speed and consciousness over action.
The real transformative power lies in embracing tension rather than avoiding it. When clients push for quick action plans and comfortable solutions, consultants make their worst mistakes by yielding too soon. The pressure to be practical often masks deeper resistance to necessary conversations about boundaries, trust, and collaboration. The very tension in the room points to where insight resides.
In the end, our authenticity, self-management, and connection to clients constitute our true methodology, marketing strategy, and the fruit of our labor. The briefcase, resume, and conceptual frameworks are more habit than necessity. Simply showing up authentically is enough-but this requires an act of faith, which may be the heart of the matter.
