Key Takeaways
You can't know it all, so lead across what you can't master.
A different kind of leadership. Julia built her reputation as a risk expert, then was asked to lead an agile technology project spanning data scientists, IT architects, and other specialists. She had little authority over them and could not learn every field they knew. Her old formula, become the most knowledgeable person in the room, could not work in this role.
Wallace calls leadership across groups with different knowledge bases spanning leadership, or S-leadership. It is not becoming a shallow generalist. It means understanding enough to connect specialties, set direction, and help people work together. Leadership still requires three kinds of work: deciding how you add value, organizing how work gets done, and interacting with people. The balance shifts as the role changes.
The useful distinction is not expert versus non-expert, but whether a leader's knowledge is the main engine of the group's work. In a tightly specialized unit, depth can accelerate judgment and credibility. Across disciplines, the leader's job is more like integration: making sure valuable pieces add up to a coherent result. That does not make expertise obsolete. It makes expertise distributed. A spanning leader still needs enough substance to ask incisive questions and notice inconsistencies, while resisting the fantasy that personal mastery is the only route to authority.
Expertise catches hidden risks, but can make every new idea look dangerous.
Strength and liability share a source. Lionel, a deeply knowledgeable CFO, senses a flaw in an acquisition's risk calculations. His persistent questioning uncovers a serious exposure in the target company's pension plan, saving the company from a costly surprise. His judgment comes from years of detailed financial knowledge, not a lucky guess.
Yet the same protective instinct makes Lionel attack an innovative proposal by drilling into its forecasts, even when the board is trying to encourage early ideas. He sees weak assumptions and misses the value of allowing an idea to develop. Expert leaders add enormous value through precision, quality control, and direct problem-solving. But their standards can turn caution into the default, and their ability to do the work themselves can make others' limits hard to understand.
Lionel's two responses show why leadership strengths can become liabilities without changing at all. The same sensitivity that detects a hidden financial risk can also overweight what is measurable and underweight what is still emerging. This is not an argument for ignoring scrutiny. It is a prompt to match scrutiny to the decision: a near-final acquisition deserves different treatment from an early experiment. Teams benefit when leaders make that distinction explicit, rather than treating every uncertainty as proof that an idea is unsound.
Treat promotion as a new value equation, not merely a higher rank.
The job changes beneath the title. Sonia was promoted from leading real-estate investments she knew intimately to running teams across ten Latin American countries. She assumed her success would still come from superior analysis and clear instructions. Instead, people expected her to understand unfamiliar groups, consult them, and coordinate their work. Her predecessor Aaron earned the technologists' respect not by knowing their craft, but by spending time learning what made it difficult.
Wallace recommends taking stock of what a role actually asks for, what the leader can do well, and what work the leader wants more of. Her assessment is a structured reflection, not a scientifically validated test. It can reveal a mismatch: someone may be skilled at expert work but uninterested in spanning responsibilities, or eager for a broader role without yet having its capabilities.
A promotion changes the source of value, not just the size of the platform. That shift can feel like incompetence because familiar signals of competence, fast answers, technical command, and personal output, become less central. The assessment is useful precisely because it separates three questions that often get blurred: what the role demands, what the person can do, and what the person wants. Its limitation is equally important: self-perception cannot substitute for feedback from people who experience the leader's work.
Shift from proving your expertise to improving the whole business.
Value becomes less visible. In an expert role, a leader can point to a problem solved or a piece of work delivered. In a spanning role, value may lie in connecting teams, securing resources, setting priorities, and helping others gain credibility. Anthony, a structured-finance expert promoted to lead a broader group, initially felt irrelevant when his former team no longer needed his technical input and a new group knew more than he did.
He began to see his contribution differently: focus the team on what mattered, find support from senior stakeholders, and create opportunities for people to lead. Wallace also urges leaders to look beyond their specialty toward customers, competitors, market trends, and how the company makes money. The test is not whether the leader can do every task, but whether the whole organization performs better because of the leader's contribution.
Intangible value is not imaginary value. A leader who removes a cross-team bottleneck or wins a needed resource may enable results that no single person could produce alone. The risk is that broad influence can become hard to evaluate, inviting vague claims of being strategic. Wallace's commercial lens offers a useful discipline: connect coordination and relationship-building to customer outcomes, competitive position, or financial performance. If the link cannot be explained, the activity may be networking for its own sake rather than leadership.
Delegate the thinking, not just the task, to grow team capacity.
Let others own the route. A leader who assigns work only after deciding every step is still controlling the work, merely through another person. Wallace recommends delegating through questions that help an employee reason through goals, stakeholders, timing, and risks. The manager stays informed without supplying every answer, while the employee gains judgment as well as responsibility.
This approach requires a capable team and a few clear ways to monitor progress. Karen, a lawyer promoted into a wider regulatory role, reviewed nearly every document and email herself. Work slowed, her team felt distrusted, and senior leaders received delayed advice. She shifted to concise updates, paired colleagues to review each other's work, and brought team members into important meetings. The goal is a group that can depend on one another, rather than a set of spokes that all run through the manager.
Delegation is often framed as a time-saving tactic, but its deeper purpose is to build organizational capability. Questions expose how a person is thinking and where judgment needs development, which gives a manager better information than simply receiving a finished product. Still, inquiry is not a universal substitute for direction. In a crisis, a novice employee may need clear instructions; in routine work, too many questions can feel like a test. Effective leaders adjust the amount of guidance to the task, the person's readiness, and the consequences of error.
Make a timely, revisable call instead of waiting for perfect certainty.
Progress often creates information. Spanning leaders face issues with incomplete facts, competing priorities, and no single technically correct answer. Karen, accustomed to the precision of legal work, struggled with a regulatory role where procedures were less settled. She tried to control every detail, lost time to back-to-back meetings, and found it hard to make decisions.
Wallace draws on Herbert Simon's idea of satisficing: choose an option that is good enough to meet the need, rather than exhaustively searching for the ideal one. A decision can move work forward and reveal what further information matters. Leaders can test their own habits by making a tentative choice partway through an analysis, then asking whether additional work actually changed it. This is not permission to be careless. It is a reminder that delay has costs too, and that many decisions can be adjusted as circumstances become clearer.
The key distinction is between reversible and hard-to-reverse decisions. A small, adjustable choice can be made with less information because action itself produces feedback. A decision with severe, lasting consequences warrants more analysis and safeguards. The book's emphasis on momentum is strongest when leaders identify which kind of decision they face, rather than applying speed as a virtue everywhere. A useful call is not simply a quick one. It is proportionate to the stakes, informed by the best available evidence, and paired with attention to what would justify changing course.
Build trust across differences before you need influence.
Authority cannot replace relationships. Spanning leaders work with people whose expertise, priorities, and styles differ from their own. They need a wider network to learn what is happening beyond their team, test assumptions, and find allies. Wallace describes practical ways to build it: discover common interests, share useful information, and connect people who could help each other.
Trust grows through several channels, including credible work, consistent behavior, reputation, shared experience, fair processes, and personal connection. Carl, a scientist and strong technical leader, made sound acquisition recommendations but often bypassed finance and other executives. His colleagues felt excluded, so his evidence did not earn their support. Relationships are not a decorative layer around decisions. They help leaders understand what others need and make collaboration possible before a high-stakes meeting.
Networks are most valuable when they move information and capability, not merely access. A leader who shares knowledge, makes thoughtful introductions, and seeks others' views creates reciprocal relationships that can improve decisions. Trust, however, should not be confused with effortless rapport. Similarity can make people feel comfortable even when a colleague has not earned confidence, while unfamiliar styles can be wrongly read as untrustworthiness. Clear commitments, fair processes, and evidence of competence help keep relationship-building from collapsing into favoritism.
Treat emotions as information about what facts alone cannot reveal.
People react to meaning, not just evidence. Carl relied on analysis to persuade senior executives, but failed to notice that the finance leader felt bypassed when Carl presented a deal analysis without inviting finance's input. The disagreement was not only about the numbers. It was also about recognition, trust, and who had been included in the decision.
Wallace argues that emotions affect judgment even when people prefer to call their decisions purely rational. Leaders can learn to notice their own reactions, pause before responding, ask what others are experiencing, and restate a different viewpoint before arguing for a solution. This does not mean accepting every emotional claim as accurate or avoiding hard choices. It means treating emotion as evidence about concerns, status, or perceived risk that may otherwise remain hidden.
Emotion is a signal, not a verdict. Anger may point to a perceived injustice, fear to an uncertain consequence, or disengagement to a sense that participation is pointless. Asking about the signal can reveal information that a spreadsheet cannot supply. But leaders should avoid diagnosing another person's feelings as if they know them with certainty. A question asked with genuine curiosity is safer than an assumption dressed up as empathy. The aim is to understand the human stakes well enough to address them, not to let the strongest reaction dictate the outcome.
Inspire people with a shared future, not your superior expertise.
Give the work a human direction. In a spanning role, followers may not be learning the leader's specialty or relying on the leader to produce the answer. They need other reasons to commit: a credible goal, useful support, recognition, and a sense that their work matters. Carl began to influence his executive team when he connected a proposed acquisition to the company's ambition to shorten drug-development time, rather than presenting it only as a technically sound deal.
Wallace treats executive presence as learnable behavior: communicate clearly, adapt the message to the audience, stay composed under challenge, and listen closely. Inspiration does not require theatrical charisma. It requires a meaningful destination and an honest account of why the work matters. Leaders can also learn what motivates individuals, such as belonging, recognition, helping others, or having authority to act.
A shared future gives people a reason to coordinate beyond compliance, but purpose becomes hollow when it is disconnected from daily work. The strongest message links an ambitious direction to a concrete problem, the people affected by it, and the team's particular contribution. Tailoring that message to different motivations need not be manipulation; it can make the same goal legible to people with different concerns. The ethical boundary is whether the leader is clarifying real value or disguising costs and uncertainty with inspirational language.
Don't mistake flawless execution for readiness to lead the business.
The ladder changes its rules. Sarah-Jane excelled as a high-performing marketing deputy, turning ambiguous assignments into polished results. Her boss praised her as an exceptional number two, but the company chose someone else to lead the function. At that level, the job increasingly involved setting direction, developing others, and influencing beyond one's specialty. Her execution record alone did not show those capabilities.
Wallace argues that women can be rewarded for expertise and dependable delivery while being overlooked for strategic leadership. That pattern combines organizational bias with the understandable comfort of staying where success is familiar. Sarah-Jane's mentor helped her see that an operational assignment, though it felt like a step down, would build the commercial and leadership experience she needed. Stretch projects, mentoring, and support from advisers, mentors, advocates, and sponsors can help make broader capability visible.
The account usefully shifts attention from women's confidence alone to the interaction between career choices and how organizations interpret performance. Yet the prescription cannot be simply that women should take more risks. Organizations also need to offer consequential assignments, explain their selection criteria, and reward strategic contributions rather than quietly depending on women to execute others' ideas. A stretch role is valuable only when it carries real scope and support. Otherwise, it can transfer the risk of a biased system onto the person seeking advancement.
In unfamiliar expert territory, earn traction by solving the team's real pain point.
Content knowledge is not the only asset. Zack was placed in charge of a consulting practice he did not know. His team resisted him, he could not show how he added value, and performance fell. Alice took a similar leap into finance without being an accountant, but her assignment had a clear purpose: turn finance into a more useful partner to the business.
Alice admitted the limits of her technical knowledge, then listened for a shared problem. Her team was buried in reports that business groups kept requesting. Together, they redesigned the service, freeing time for more useful analysis and giving the team a reason to trust her. Wallace identifies conditions that improve the odds: a technically strong team, active backing from the leader's boss, a clear reason for the appointment, and coaching. The leader must still verify advice and build a collaborative unit.
Alice's success was not a triumph of generic management over expertise. It depended on a capable team, a mandate that matched her strengths, and a problem she could help resolve without pretending to know finance better than the specialists. That distinction matters for organizations designing development assignments: unfamiliarity can broaden a leader's perspective, but it can also create avoidable risk. A coherent purpose, technical competence on the team, and visible sponsorship are not optional courtesies. They are part of the job's design.
Analysis
Wallace's central contribution is a more realistic map of modern leadership than the familiar climb from specialist to all-purpose general manager. In knowledge-heavy organizations, expertise remains valuable at senior levels, but it cannot carry every assignment. Leaders are asked to move between deep technical judgment and coordination across people who possess knowledge the leader cannot acquire in full. The practical challenge is not abandoning expertise. It is recognizing when expertise should lead, and when it should support a broader role.
The book's case studies make this shift tangible. Lionel's precision protects an acquisition but can choke off uncertain innovation. Sonia's confidence in her real-estate judgment fails to establish trust with technologists. Anthony learns that relevance can come from setting priorities and opening doors, while Alice gains credibility by addressing a shared operational burden rather than faking financial mastery. Across the stories, leadership is less about having the answer than about making the right knowledge usable.
The framework is strongest when it links role demands to observable behavior: who makes decisions, whose knowledge is consulted, how work is delegated, and whether the leader can move among different perspectives. Its limitation is that spanning can sound like a personal skill problem when organizations themselves create the difficulty. Vague mandates, inadequate preparation, weak sponsorship, and overloaded calendars cannot be repaired by better listening alone. Nor should every specialist be pushed toward broader leadership; some organizations need deep experts, and some people prefer that work.
The gender discussion sharpens this point. Women may be praised for execution and then judged as insufficiently strategic, while men and organizational norms help define which assignments count as leadership. Individual stretch and sponsorship matter, but fair access and credible evaluation matter too. The most useful lesson is therefore both personal and institutional: leaders can learn to create value through others, while organizations must clearly define, support, and reward that work. A capable spanning leader does not know everything. The organization must know what it expects that leader to do instead.
Review Summary
You Can't Know It All explores the transition from expert leadership to spanning leadership in modern organizations. Readers find it insightful, practical, and relevant to their careers. The book offers valuable frameworks, examples, and exercises for developing spanning leadership skills. Many appreciate its focus on adapting to diverse teams and complex business environments. Reviewers highlight the book's emphasis on becoming comfortable with not knowing everything and leveraging team expertise. Overall, readers find it helpful for navigating leadership transitions and understanding the evolving nature of corporate hierarchies.
People Also Read
Glossary
E-leadership
Leadership through expertiseWallace's term for leadership grounded in deep knowledge of a particular field and the ability to apply it directly to the work. E-leaders often add value by solving technical problems, protecting quality, managing risk, and teaching others. Their authority commonly rests on being able to understand or perform the specialist work themselves.
S-leadership
Leadership across specialtiesWallace's shorthand for spanning leadership. An S-leader guides groups with different knowledge bases without needing to become the expert in every area. The leader connects perspectives, sets priorities, builds trust, and enables people with specialized skills to deliver results together. It is a different mode of leadership, not a rejection of expertise.
spanning leader
Leader across knowledge boundariesA leader whose responsibilities cross teams, functions, or specialties with distinct expertise and interests. Rather than relying mainly on personal technical authority, a spanning leader integrates information, builds relationships, guides shared work, and connects the team to the wider organization. The role can coexist with expert responsibilities rather than replacing them entirely.
wisdom of depth
Insight from deep expertiseThe judgment that comes from extensive knowledge and experience in a specific domain. It helps an expert leader recognize subtle problems, understand technical details, and identify practical solutions. Wallace contrasts this with breadth of perspective, which helps a leader understand how different areas and decisions fit together across an organization.
wisdom of breadth
Insight across the organizationThe ability to see connections among different specialties, functions, and business priorities. It helps a spanning leader understand how choices in one area affect others, identify what matters most to the organization, and coordinate expertise without attempting to personally master every technical detail.
satisficing
Choosing a sufficient optionA decision approach associated in the book with economist Herbert Simon. Instead of searching indefinitely for the optimal choice, a decision-maker selects an option that meets the important requirements and moves forward. In spanning leadership, this supports timely action when complete information is unavailable, while leaving room to adjust as new evidence emerges.
executive presence
Credible, composed communicationA learnable set of behaviors that helps a leader's message carry weight. Wallace describes clarity, audience awareness, composure, confident body language, preparation, attention, and the ability to handle disagreement. Executive presence is not simply charisma or polish. It includes communicating what one knows and does not know, while remaining focused on people and issues.
hub-and-spoke
Team centered on its leaderA team pattern in which members primarily communicate with the leader rather than with one another. This can work in an expert-led group where the leader's knowledge is the main resource, but it can restrict collaboration in a diverse team. Wallace contrasts it with a more interdependent group where members exchange ideas and rely on each other's strengths.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.