Key Takeaways
Treat every people problem as your responsibility, not necessarily your fault.
Responsibility starts the repair. A leader may inherit a failing project or discover a problem on the first day. Alan Willett recalls Watts Humphrey taking charge of a project involving more than a thousand people and accepting that its failure was now his responsibility, regardless of who had caused it. The point is not to absorb blame for everything. It is to stop using blame as a substitute for action.
Measure more than delivery. Results still matter: profit, deadlines, and customer value. Exceptional leadership also asks whether top talent stays, conflict improves the work, team energy remains healthy, and people the leader has coached go on to excel. These measures make the leader accountable both for the mission and for the conditions that let others deliver it.
What's useful here is the distinction between fault and responsibility. In systems thinking, a problem can emerge from many interacting causes, while the person with authority still has the best chance to change the system. That makes ownership practical rather than punitive. The distinction needs guarding, however: responsibility should not erase the accountability of people who caused harm, nor let organizations excuse defective processes by blaming one manager. The strongest version is shared diagnosis with clear authority to act. A leader owns the response, then investigates causes without turning the inquiry into a hunt for a scapegoat.
Replace suspicion with curiosity before confronting difficult behavior.
Behavior has a context. Willett urges leaders to begin from the possibility that a troublesome person is trying, however unsuccessfully, to do what seems right. That assumption is not permission to ignore poor work or hurtful conduct. It is a way to ask what is missing before deciding what the behavior means. Differences in background, workplace norms, and communication can also distort what people intend and what others hear.
Separate observation from inference. A leader might know that a team member missed commitments, but not know whether the cause is skill, unclear expectations, or a crisis outside work. In one example, a manager first judged a driver who had behaved dangerously, then discovered the driver was rushing someone to emergency care. The correction is not to suspend judgment forever, but to investigate before acting on it.
Curiosity is not softness. It improves the accuracy of a leader's diagnosis, much as a clinician gathers symptoms before choosing treatment. Attribution errors are common: observers often explain another person's behavior as character while overlooking circumstances they cannot see. Still, a charitable starting point should be paired with boundaries and evidence. Persistent harm cannot be excused indefinitely by an unseen explanation. The productive sequence is to ask, listen, and verify, then respond to both the person's circumstances and the behavior's impact. That approach is especially valuable in diverse teams, where shared words do not guarantee shared meanings.
Build a radar that makes bad news safer to surface.
Look for early signals. Willett recommends listening directly to people, noticing changes in routine, and examining detailed evidence rather than accepting a reassuring headline. A teammate who stops giving regular updates may simply be busy, or may be struggling. A project labeled on track may still contain estimates that make the deadline unrealistic. Ask questions, listen without cutting people off, and follow up on what they disclose.
Expect blind spots. People often withhold problems because they fear blame, conflict, career damage, or being assigned the fix. Leaders can reduce that silence by responding constructively to bad news, learning from other managers, commissioning outside assessments, and seeking candid feedback on their own conduct. Data helps only when it is accurate and connected to decisions. A status report that invites no action is paperwork, not a warning system.
This is a practical account of organizational sensing: leaders need multiple channels because no single report captures the whole system. The emphasis on follow-up matters. Asking for candor while reacting badly to unwelcome answers teaches people to hide information. Psychological safety, meaning the ability to raise concerns without expecting humiliation or retaliation, is therefore operational, not merely interpersonal. But informal listening has limits: people may still fear speaking openly, and leaders can mistake visibility for truth. Anonymous feedback, independent review, and traceable measures can supplement conversations rather than replace them.
Deliver hard feedback privately, briefly, and without a verdict.
Prepare before the meeting. The leader first sorts out personal emotions, distinguishes known facts from assumptions, and drafts a concise message. Willett's two-minute or less rule is meant to keep feedback focused on observable behavior, its effect, and a question that invites explanation. In the case of Carl, a manager described missed commitments and their impact, then asked what had changed instead of labeling him lazy or incompetent.
Listen before prescribing. The conversation took place privately. The manager waited through silence, heard that Carl was facing a divorce, reflected what she understood, and clarified expectations. Carl then acknowledged the impact on his team and asked for help. The situation improved because the leader addressed real performance concerns without treating the person as the problem itself. A concise opening leaves room for the information the leader does not yet have.
The short opening is effective because it limits defensiveness and gives the other person room to speak. It resembles a useful clinical distinction: describe the behavior and impact, not a fixed identity. The case also shows why silence is an active tool; an immediate solution can prevent discovery of the real constraint. Compassion does not mean lowering standards. The manager still makes the impact and expectations clear. In high-risk situations, though, a private conversation may not be sufficient. Harassment, safety threats, or legal violations can require immediate protective steps and formal processes alongside direct communication.
Turn a promising conversation into measured, supported improvement.
A good talk is only a start. Willett's follow-through approach turns an intention to change into a shared plan. The plan should describe the desired future, why it matters to the individual and team, visible signs of progress, and the help required. Hank, a brilliant architect who kept rewriting developers' work, realized he wanted to shape architecture across many projects rather than control each piece of code. His manager and team translated that ambition into clear responsibilities and indicators.
Build support around new habits. The team agreed on a signal for when Hank slipped back into micromanaging. Short check-ins helped catch setbacks early, and peers were coached to give useful feedback. Progress was celebrated when it showed up in results, not merely effort. Willett's point is that stress can revive old habits, so improvement needs repetition, monitoring, and room to recover from mistakes.
The plan works because it links behavior change to a meaningful role, rather than relying on a promise to stop doing something. This resembles behavior design: specify the target, make progress observable, and arrange cues and support in the environment. Team participation also distributes responsibility instead of making the manager the sole monitor. The caution is that measures can become targets that distort behavior. Counting favorable code reviews or meeting attendance is useful only if those indicators reflect the underlying goal. Periodic judgment remains necessary, especially when a metric looks good but trust or quality does not.
Choose improvement or removal by the group's needs, not loyalty.
Use criteria, not impulse. A leader's duty is to the group and its mission, which sometimes means helping a person improve and sometimes means removing them. Willett suggests examining whether the person accepts feedback, how their behavior affects colleagues, whether they enable collaboration, how important their skills are now and later, and how replaceable those skills are. The available options range from changing responsibilities to moving the person or ending their employment.
Consider Sanjay's decision. He delayed addressing a division manager whose poor treatment of staff and customers threatened the business. The manager had rejected prior feedback, and customer trust was eroding. After reviewing the evidence, Sanjay decided to replace him, even though finding a successor would be difficult. The decision was not presented as a punishment. It was a judgment that the division and its employees needed leadership they could trust.
This framework helps leaders resist two familiar distortions: keeping a damaging employee because of history, and firing someone to discharge frustration. Its group-level focus is a strength, particularly when a high performer's behavior harms everyone around them. Yet a scoring table cannot settle a moral or legal question by itself. Context matters, including fairness, due process, disability accommodations, and whether the organization supplied adequate support. The tool is best understood as a disciplined prompt for gathering evidence and comparing options, not an algorithm that turns a complex human decision into arithmetic.
Reward customer results, not visible exhaustion.
Daily signals define excellence. A company cannot claim to value quality while pressuring teams only for earlier dates. TopShelf, a software division, repeatedly delivered late and with defects because managers asked for aggressive schedules and quick handoffs to testing, but rarely asked how teams would ensure quality. When executives clarified that customer value, quality, and credible commitments mattered together, they also invested in better planning and skills. The division began delivering more reliably.
Watch what gets celebrated. Willett contrasts a team that repeatedly fought defects after release with one that prevented problems and delighted customers. The firefighting team looked busier and received more attention, while the quieter team delivered strong results with less rework. When leaders praise crisis response but overlook prevention, they teach the organization to keep producing crises. Expectations must therefore appear in meetings, budgets, project reviews, training, and recognition, not just on posters.
The contrast exposes a measurement problem: effort is visible, prevention is often invisible. Organizations naturally reward what leaders can easily observe, even when that reinforces expensive rework. This connects to the broader principle that incentives shape behavior more powerfully than slogans. Still, a focus on outcomes should not become contempt for effort or bad luck. Some projects face genuine uncertainty, and teams can work responsibly without succeeding. Good evaluation distinguishes disciplined execution from favorable results, while asking whether the organization is learning and whether customers receive value.
Give capable teams a mountain worth arguing toward.
Conflict needs a destination. A successful company in Willett's account had grown from a start-up focused on survival, but its leaders began fighting destructively once survival was no longer the shared goal. They did not need etiquette training as much as a compelling next challenge. Their CEO connected the group's past struggle to an ambitious future and invited leaders to make the goals more meaningful and specific through discussion.
Make the goal vivid and discussable. Willett recommends explaining why the goal matters, describing an inspiring destination rather than only what must stop, and setting a difficult but worthwhile challenge. Leave room for people to interpret how they can contribute. A clear purpose can turn disagreement into productive debate about means. Without it, the same conflict can become a contest over status, resources, or whose priorities win.
A shared purpose gives disagreement a common object: people can challenge proposals while remaining aligned on the destination. This resembles the role of a superordinate goal in group dynamics, where cooperation becomes necessary to achieve something neither faction can accomplish alone. Ambiguity can invite ownership, as Willett argues, but too much ambiguity also allows competing interpretations to masquerade as alignment. Leaders should pair an inspiring direction with concrete boundaries, decisions, and measures. A difficult goal motivates only when people believe the work is meaningful and the organization will provide a plausible path.
Negotiate the project start before urgency turns into rework.
A rushed start can delay the finish. Willett argues that projects often begin badly because leaders want visible progress, key people are busy elsewhere, or sponsors fear saying no. Teams then start without a shared purpose, realistic resources, or agreement about quality and timing. The result can be shortcuts, rework, missed commitments, and declining trust. A strong start defines why the work matters, how it ranks against other projects, and what success requires.
Make commitment a conversation. Select a leader suited to the project's risks, form a small capable team, and let that leader negotiate assumptions before dates become promises. In the Hot Metal project, executives moved an experienced leader from another initiative and accepted the disruption rather than pretending there would be no cost. Detailed planning exposed a conflict around a forceful specialist early, before it could split the working team.
This is a useful antidote to the planning fallacy, the tendency to underestimate time and obstacles when making plans. The insistence on negotiation also gives project leaders permission to surface resource conflicts instead of silently absorbing impossible commitments. The book's account rightly treats a start as organizational design, not a kickoff meeting. At the same time, extensive preparation can become another form of delay. The appropriate level depends on project uncertainty and reversibility: a small experiment can start quickly, while a high-cost, tightly coupled effort deserves more deliberate alignment.
Lead other leaders with explicit standards and room to act.
Leadership needs its own expectations. Senior leaders cannot observe every detail, and a manager's influence reaches more people than an individual contributor's. Willett recommends making expectations explicit: leaders should understand the organization's purpose, consider the long term, grow talent, challenge decisions constructively, manage conflict, and deliver results. New leaders can be asked to listen across the organization, report strengths and weaknesses, and take on a difficult challenge with clear expectations.
Sarah and Tom show why clarity matters. Sarah hired Tom for his ideas, but he began pushing changes in ways that alienated his team. Their conversations revealed that he thought he had been hired to turn around a failing organization. Sarah expected him to accelerate an already successful one. Once they clarified the mission, Tom listened to colleagues and rebuilt trust. The leader of leaders set direction without dictating every method.
Explicit expectations reduce the fog that often surrounds senior performance. They also make autonomy safer: people can choose their methods while being accountable to shared outcomes and norms. Sarah's misalignment with Tom shows that a recruitment decision can fail even when technical credentials are strong, if the mandate remains implicit. The approach should not become a license for constant surveillance. Listening campaigns and demanding assignments are valuable when they reveal support needs and enable learning, not when they are traps designed to catch a new leader failing.
Protect your energy so leadership remains a deliberate choice.
Notice what gives or drains energy. Willett describes a leadership sweet spot as the overlap among work a person finds energizing, work they can do well, and work that provides value to others. Tracking a week's activities can reveal which responsibilities fit and which leave the leader depleted. He also recommends managing energy drains, preserving open time, and planning the week around family commitments, priorities, stakeholders, team needs, and work that can be declined.
Improve deliberately. The book frames leadership as a choice, even when someone entered management through promotion or circumstance. Willett's own turning point came when he stopped viewing his job as an endless slog and began treating his contribution as something he could shape. That shift did not remove responsibility. It helped him focus on valuable work, keep learning, and say no when a request undermined the larger mission.
Self-management is not a private luxury for leaders. Attention, patience, and judgment are limited resources, and chronic depletion makes people more reactive just when their teams need steadiness. The overlap among ability, motivation, and social value also offers a practical way to redesign a role rather than merely endure it. Still, individual energy management cannot solve structural overload. If a leader's calendar is impossible because staffing or authority is inadequate, the answer includes organizational change, not only better planning or more disciplined rest.
Analysis
Leading the Unleadable is a practical leadership book built around a reversal: difficult people are not merely obstacles to manage, they are signals about the team, the work, and the leader's own system. Its narrative moves from a choice to accept leadership, through early detection and direct intervention, into prevention, project design, and self-leadership. The recurring case stories make an abstract obligation concrete: listen before judging, set expectations, act, and stay engaged long enough for change to become observable.
The book's most coherent contribution is its integration of individual conduct with organizational conditions. A cynical employee may need direct feedback, but repeated cynicism across a team may indicate a missing purpose or a leader who punishes bad news. A quality failure may require technical correction, but chronic late delivery across teams points toward the incentives and expectations set by management. This makes the advice more systemic than a typical catalogue of difficult personality types.
Its strongest practical tools are specific: concise private feedback, early listening, detailed project data, planned follow-through, and explicit criteria for retaining or removing someone. Stories such as Carl's personal crisis and Hank's shift from code control to broader architecture demonstrate why curiosity and support can recover valuable talent. The contrasting case of Sanjay's failing division prevents the message from collapsing into unlimited patience.
The evidence is mainly the author's consulting experience and illustrative cases, not controlled comparison. That gives the book texture and practical detail, but readers should treat its success stories as demonstrations, not guarantees. Its insistence that trouble is the leader's responsibility can spur action, yet can also overburden managers if read as personal blame for structural failures. The fairest application combines ownership with shared accountability, formal safeguards, and attention to power. The book is most useful when its humane posture is paired with clear boundaries: understand the person, protect the group, and judge change by sustained behavior and results.
Review Summary
Leading the Unleadable receives mixed reviews, with an average rating of 3.50 out of 5. Some readers praise its practical leadership advice and real-world examples, particularly for those in the tech industry. Others find it too basic or lacking in specific strategies for difficult personalities. Many appreciate the book's focus on self-reflection and continuous improvement for leaders. However, some reviewers feel the title is misleading, as the content covers general leadership principles more than handling truly "unleadable" individuals.
People Also Read
Glossary
Taxonomy of trouble
Map of leadership problemsWillett's broad grouping of recurring leadership difficulties. It includes troubled projects, difficult individual contributors, dysfunctional leaders, and demanding or misaligned stakeholders. The categories help leaders notice that a problem may spread beyond one person or team, and that the source may include unclear expectations, poor incentives, conflict, or the leader's own response.
Troublesome to tremendous conversion rate
Measure of successful turnaroundA leader's informal measure of how often difficult people or failing situations are transformed into strong contributors and successful work. Willett compares it to a batting average: not every attempt will succeed, but tracking successes and failures can encourage learning about which interventions help and where judgment or follow-through needs improvement.
Two-minute or less rule
Keep feedback conciseA technique for preparing corrective feedback as a brief, clear message, ideally under two minutes. The message should identify observable behavior, explain its impact, express the relevant concern, and invite the other person to describe what is happening. Its purpose is to prevent a focused conversation from turning into a long, emotional lecture.
Energy equation
Compare energy given and receivedA project check-in question that asks whether participants gain more personal energy from doing the work than they expend on it. Willett treats a positive answer as one indicator of a healthy, engaging project. It is not a substitute for measures of delivery or quality, but can reveal persistent strain that conventional status reports overlook.
Gelled teams
Teams that own shared workTeams whose members take responsibility for the mission, their working practices, and problems among colleagues, rather than waiting for a manager to solve everything. Leaders build this capacity by setting high expectations, providing guidance, and giving the group room to address issues together. Shared ownership can strengthen trust and reduce unnecessary managerial intervention.
Leadership sweet spot
Energizing, capable, valuable workThe overlap among work that energizes a leader, work the leader has or can develop competence to do, and work that provides value to others. Willett recommends tracking activities to identify this overlap and shaping responsibilities toward it. The concept is meant to help leaders sustain contribution, not simply pursue personal preference at the expense of organizational needs.
Exceptional start
Deliberate project launchA project beginning built on a clear purpose, realistic priorities, capable leadership, appropriate staffing, negotiated expectations, and detailed early planning. Willett argues that rushing into work without these foundations often creates rework, conflict, and unreliable commitments. The idea also applies to restarting an existing initiative when its goals, team, or circumstances change.
Remove or improve
Decision about a person's futureA judgment process for deciding whether to support a person's improvement, alter their responsibilities, move them elsewhere, or remove them from the organization. Relevant considerations include openness to feedback, impact on colleagues and customers, collaborative ability, current and future skills, and replacement difficulty. The framework supports deliberation but does not make the decision automatically.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.