Key Takeaways
Integrate expertise instead of merely referring clients across silos
Integration creates the value. Smart collaboration is the deliberate combination of specialists’ knowledge to solve a client’s complex problem or tailor an answer to its particular needs. It involves repeated interaction, so different perspectives can shape a unified solution. It is not simply dividing tasks and assembling the pieces, passing work from one specialist to another, or introducing a colleague to sell an extra service.
Begin with a reason. Collaboration carries startup and coordination costs, so adding people is not automatically smart. A nineteenth-century mill owner hired an architecture firm to handle brick repairs, then discovered the project involved public agencies and local groups because the mill stood beside a navigable river. The firm’s broader experience helped address that context. The lesson is not “use a team for everything,” but “match expertise to the real shape of the problem.”
The useful distinction is between a team as a sales bundle and a team as a problem-solving instrument. That difference matters because clients can often detect when extra specialists serve the firm’s internal revenue goals more than the client’s needs. The idea also resembles systems engineering: parts must be coordinated around the behavior of the whole system, not simply assembled. A practical test is whether each person changes the quality, relevance, or speed of the answer. If not, the added coordination may be overhead dressed as collaboration.
Cross-practice teams can multiply revenue while making client work more valuable
Broader service, bigger accounts. In data from three law firms, clients served by two practice groups generated roughly three times the revenue of clients served by one group in one firm. Average revenue continued to rise as more practices served a client. Each participating group, including the original one, tended to earn more. Broader teams could identify additional needs, reach senior executives, and take on complex work that was less easily compared with a standard service.
Profit matters, too. Clients sometimes pressed for discounts as relationships expanded, but discounting tended to level off as the work grew. Across the firms studied, profit margins generally stayed within a few percentage points, so higher revenue usually meant higher total profit. The pattern does not mean that every extra specialist pays off; routine, low-cost tasks may not justify a multidisciplinary team.
The central economic insight is that expertise can be complementary: one specialist’s contribution may make another’s advice more useful, rather than merely adding a separate billable service. That is a stronger case than simple cross-selling. Still, the revenue patterns are associations across client accounts, not proof that adding practices alone caused growth. Larger, more sophisticated clients may both need more specialists and spend more. Firms should test their own data, including costs and client outcomes, rather than treat a rising revenue curve as a mandate to expand every team.
Spread client relationships across partners before one departure puts them at risk
One contact is a fragile bridge. In an accounting firm’s study of its 300 largest clients, about three-quarters of clients served by a single lead partner said they would consider another provider if that partner left. Among clients served by multiple partners, 90 percent said they would remain with the firm. Broader relationships also reduce the chance that a departing partner can take the client away alone.
Build continuity deliberately. Cross-practice relationships are more protective than simply adding several partners from the same unit. Direct contact between client and firm specialists also matters, since it avoids making one partner the gatekeeper for every opportunity. Succession plans and “laddering,” which pairs professionals with client counterparts at similar career levels, help establish future contacts before a handover becomes urgent.
A firm’s relationship with a client is a form of organizational memory. When knowledge and trust sit with one individual, they are portable; when they are distributed across a capable team, the institution has a better chance of preserving continuity. This resembles resilience planning in infrastructure, where dependence on a single component creates a point of failure. But retention should not be confused with trapping a client through switching costs. The durable goal is to make the wider team useful enough that clients freely prefer continuity.
Share your client work to grow your own business, not just the firm’s
Collaboration can compound for specialists. Gardner compared two similar law partners who billed about the same number of hours. One involved six partners in his client work; the other involved more than thirty, mostly from outside his practice. The second partner’s client revenue was more than four times greater. Across multiple firms, partners who referred work to colleagues, especially across practices, tended to grow their own business in subsequent years.
The mechanism is practical. Delegating suitable work gives a specialist more room to develop clients. Collaborating also teaches what other experts notice, helping the specialist recognize issues that once sat outside their field of view. A tax adviser, for instance, can learn from employment and real estate colleagues, then spot when a client’s broader business problem calls for their input. The effect is not instant expertise; it is better questions and better connections.
This challenges the assumption that sharing work necessarily means surrendering status or revenue. In network terms, the specialist gains access to capabilities and information that would be costly to build alone. The crucial condition is reciprocal value: the introduced expert must deliver well, while the original partner remains meaningfully involved in understanding the client. Otherwise, delegation becomes a handoff, and the relationship may weaken rather than grow. The book’s findings support trying collaboration as a business-development strategy, while leaving room for differences in practice, client type, and compensation design.
Explain the client problem before asking clients to pay for a team
Clients reject irrelevant add-ons. They may see an unsolicited specialist introduction as a sales maneuver, especially when no one has explained why the added expertise matters. They are more receptive when the problem is genuinely multifaceted and the team is formed early, with clear roles and a reason for each person’s involvement. A client may even welcome a short expert consultation if it saves hours of unnecessary research.
Make the value visible. A company’s procurement team may issue a narrow request for proposal, yet clients sometimes accept a broader proposal when it clearly addresses a larger business need. One supplier proposed an offshore pilot that went beyond the original request, explaining how success could support a wider company initiative. Clients may pay for collaboration that improves the outcome, but not for duplicated work, rework, or internal coordination that produces no benefit.
The client’s test is not whether a provider has many experts, but whether the proposed team reduces uncertainty or improves a decision. That makes timing and explanation part of the service itself. The idea parallels informed consent: people are more willing to accept a process when its purpose, trade-offs, and participants are made clear. There is also a discipline for providers here. If an adviser cannot describe the client benefit before expanding the team, the proposal may be premature. A collaborative team must earn its place, not assume it.
Make lateral hires collaborate in both directions within eighteen months
Integration has a short window. Gardner’s analyses found that successful lateral partners needed both to work on incumbent clients and to involve established colleagues in work they brought or developed. If only one of those experiences occurred, the hire faced a greater risk of leaving; if neither occurred, the partner was likely to be gone within three years. Other firms reported that the critical period could be as short as six months.
Treat hiring as a joint plan. Before making an offer, assess whether the expertise is truly missing and whether the firm can support the newcomer. After arrival, name a peer mentor, arrange introductions to specific clients and colleagues, and assign leaders responsibility for progress. Assess collaborative behavior during hiring rather than relying only on a candidate’s existing client portfolio. A large book of business is not proof that someone can build relationships inside a new firm.
Lateral hiring is often treated as acquiring an asset, but the asset’s value depends on its integration into a social and operating system. This is similar to acquiring technology without redesigning workflows: the purchase alone does not create capability. The two-way requirement is especially revealing. Newcomers need access to the firm’s established relationships, while incumbents need a reason to trust and involve them. The book’s timetable is a useful warning, though the exact window will vary by firm. Accountability should focus on meaningful collaboration, not ceremonial introductions.
Give contributors visible chances to learn, earn referrals, and advance
Supporting roles can build careers. Contributors are specialists who help deliver work originated by another partner. Working on cross-practice projects can teach them how different expertise solves client problems and help them develop relationships with colleagues. Gardner’s analyses found that collaboration predicted later business development and referrals. In one set of findings, each additional partner in a collaborator’s network was associated with about 0.5 percent more billings the following year; the average lawyer who added one partner a month could gain about $22,000 in billings.
Make the work worthwhile. Contributors also need fair recognition, useful feedback, and opportunities to take on challenging tasks. Collaborative experiences can strengthen belonging and expose junior professionals to clients and senior colleagues. That matters for retention, especially when younger staff want autonomy, development, and meaningful work. Yet service work can become a trap if a contributor spends nearly all available time on other people’s clients and has no time to build an independent practice.
This section widens the definition of career progress beyond the visible rainmaker. It treats collaboration as a learning environment where people gain both technical context and social credibility. That is an important corrective to organizations that praise teamwork but reward only individual sales. Still, development opportunities cannot substitute for fair workload allocation or credit. A contributor who gains experience but repeatedly loses time, recognition, and advancement prospects is not being developed; that person is subsidizing the system. Leaders need to make the exchange explicit and equitable.
Measure collaborative outcomes and behaviors, not only individual hours
Metrics steer attention. A firm may reward collaboration in its compensation plan and still discourage it through performance measures that celebrate individual billings or office-level utilization. One lockstep firm’s partners hoarded work locally to protect office figures, even when cross-office expertise could better serve clients. The lesson is that people respond to the measures they see, not just the values leaders announce.
Design a balanced scorecard. Set specific, measurable objectives tied to client and firm priorities. Track outcomes such as account growth, retention, and client satisfaction, alongside behaviors such as mentoring, sharing expertise, and contributing to joint pitches. Avoid making billable hours the dominant test, since time spent building a team can then look like lost productivity. Compensation matters, but abrupt changes are costly and politically difficult. Fix contradictory measures first, then adjust rewards where needed.
This is a problem of organizational design, not simply individual motivation. A metric acts like a rule in a game: it defines what counts, even when leaders verbally praise different behavior. The most robust system therefore pairs results with the behaviors that plausibly produce them, while checking for gaming and unintended consequences. There is a trade-off, however. Behavioral measures can become box-ticking too, especially when counts replace judgment. A sensible approach uses transparent goals and evidence, then leaves room to evaluate context and the quality of collaboration.
Make distance manageable through shared context before pressure narrows communication
Remote teams lack everyday knowledge. Colleagues in different offices may have little sense of one another’s workloads, work styles, local constraints, or client expectations. This “mutual knowledge problem” can encourage an us-versus-them mindset. Regular brief meetings, shared project goals, and personal context help distant colleagues interpret one another more accurately. A short virtual tour of a workspace or a note about likely interruptions can prevent minor surprises from becoming judgments about competence.
Pressure makes this harder. Under high stakes, professionals may retreat to familiar methods, reduce communication, and reject unfamiliar ideas. Teams can counter this by identifying likely pressure points, giving members support, inviting junior voices into discussions, and showing clients ideas early enough for feedback. A global team is not automatically better than a local one. Its benefits must justify the extra coordination, and its members need routines that make information flow reliably.
Distance is not merely a scheduling inconvenience; it changes what teammates know and how they interpret silence, delay, or disagreement. The remedy is not to manufacture constant intimacy, but to supply enough shared context for people to coordinate without guessing. This connects to distributed cognition: a team’s working knowledge lives partly in its members and partly in the channels they maintain. More communication is not always better, though. The aim is useful, symmetrical information, with clear norms that prevent remote work from becoming an endless stream of messages.
Institutionalize collaboration with clear roles, project gates, and accountable resources
A star cannot build the system alone. At Dana-Farber Cancer Institute, leaders created integrative research centers to bring specialists together around cancer research and measurable goals. The Center for Nanotechnology in Cancer was led by an eminent scientist, Charlie Woods, whose technical vision was strong but whose administrative and collaborative work lagged. He pursued a large commercial opportunity that partly fell outside the center’s cancer mission, while the center lacked staff, project controls, and communication with other researchers.
Redesign before giving up. Leaders paired Woods with a more institutionally minded coleader and hired a research scientist to coordinate projects. The center introduced project review, budgets, milestones, and a public platform for sharing work. It ultimately completed 23 projects and had 35 more underway. The case shows that collaboration needs infrastructure: clear responsibilities, appropriate management skills, transparent intake, and accountability to a shared purpose.
The Dana-Farber example makes collaboration tangible as an operating model rather than a personality trait. It also shows why leaders cannot simply appoint a brilliant specialist and hope that leadership skills appear on demand. The redesign preserved scientific expertise while adding complementary roles and decision processes. That is a general lesson in team composition: a group needs both domain insight and the capacity to coordinate execution. Formal controls can feel restrictive, so they should protect the shared mission without smothering experimentation. The center’s turnaround suggests that structure can enable creativity when its purpose is clear.
Analysis
The book’s central contribution is to recast collaboration from a virtue statement into a strategic capability with measurable consequences. Its argument follows a useful chain: specialization distributes expertise, client problems cross those specialist boundaries, and firms that integrate expertise can create more valuable work, deeper relationships, and stronger internal networks. The most memorable evidence is not a single revenue chart, but the recurring contrast between isolated individual performance and durable, multi-person capacity.
The book also avoids treating collaboration as effortless. It names the human and organizational costs: distrust, coordination, workload conflict, credit, local autonomy, and metrics that reward the opposite behavior. Its role-based structure is effective because the same intervention does not suit a solo specialist, an experienced account leader, a contributor, and a firm executive. The Dana-Farber case gives the argument a useful stress test outside professional services: expertise alone did not make a center collaborative; roles, project intake, and accountability had to change.
The evidence is persuasive but should be read carefully. The book reports extensive longitudinal data across eight firms, interviews, and client accounts, yet many business outcomes remain observational. Bigger clients may attract more practices and also generate more revenue. Nor does client retention always prove superior value; it can reflect switching costs. The strongest application is therefore not to maximize team size or lock clients in, but to test whether integration improves outcomes clients recognize and willingly renew.
The deeper managerial lesson is architectural. Collaboration becomes reliable when relationships, incentives, information systems, and decision rights reinforce one another. A firm cannot proclaim teamwork while measuring only individual hours, nor can software compensate for mistrust. Leaders must design conditions in which people can contribute expertise without surrendering all autonomy or credit. Smart collaboration is selective, client-centered integration, not universal group work.
Review Summary
Smart Collaboration receives mixed reviews, with an average rating of 3.61/5. Positive reviews praise its insights on improving client service and profits through collaboration in professional services firms. Critics note its narrow focus on consulting and law firms. Readers appreciate the research-based findings and practical examples, but some find it less applicable to broader organizational contexts. The book is seen as valuable for managers and partners in professional services, offering strategies to overcome silos and enhance teamwork. Some readers found it informative but challenging to finish due to its research-heavy content.
People Also Read
Glossary
Smart collaboration
Integrated expertise for complex workThe deliberate integration of specialists’ knowledge to produce a high-quality, customized answer to a complex client problem or to adapt an existing approach to a client’s context. It involves repeated interaction that lets perspectives shape a coherent solution. It is distinct from merely dividing tasks, handing work between experts, or cross-selling an additional service.
Solo specialist
Expert who relies on individual practiceA professional whose reputation and client work rest mainly on deep expertise in a particular niche. Solo specialists may delegate to junior colleagues but often see little reason to involve peer experts unless a client problem demands it. Gardner argues that they can benefit from collaboration by expanding client relationships, learning other specialties, and developing broader business opportunities.
Seasoned collaborator
Experienced leader of collaborative workA professional who already understands the value of collaboration and has experience building client work with colleagues. This person seeks to improve the scale or quality of collaboration, often across practices, offices, or countries. The role requires assembling a committed team, aligning peer leaders, managing local priorities, and maintaining coordination under pressure.
Contributor
Specialist who supports others’ client workA professional who contributes expertise to a client project originated or led by someone else. Contributors may be developing their careers or balancing service work against building their own clients. Collaboration can help them gain skills, relationships, referrals, and reputation, but firms need to recognize their contributions and prevent service work from consuming all their development time.
Ringmaster
Leader who shapes collaborative conditionsGardner’s metaphor for a firm leader responsible for aligning talented, autonomous professionals around shared work. A ringmaster creates conditions that support collaboration through clear goals, appropriate measures, compensation, and technology. The role is not to control every interaction, but to make collaborative behavior practical, accountable, and consistent with the firm’s strategy.
Expertise dissensus
Disagreement about who knows whatA mismatch among team members’ beliefs about one another’s knowledge and expertise. People may assume a colleague knows more, less, or something different from what is actually true. Such mistaken assumptions can create conflict and weaken performance. A clear team launch, explicit purpose, and discussion of each member’s knowledge can reduce this problem.
Collaborative technology platform
Social system for sharing expertiseA digital platform that helps colleagues find one another, share work in progress, respond to specific requests, and build visible records of expertise and contribution. Unlike a static knowledge repository, it supports direct interaction and user-generated content. Gardner presents it as a way to lower search and coordination costs, while emphasizing that leadership and adoption matter more than software alone.
Pain barrier
Early costs before benefits accumulateThe initial period in which collaboration feels more costly than beneficial. Startup work, coordination, uncertainty, and risk are immediately visible, while gains in client value, revenue, and trust take time to develop. With repeated successful experience, coordination can become easier and benefits can accumulate, but firms must sustain the effort long enough to learn.
After-action review
Structured reflection after team workA facilitated review in which team members compare what they intended to do with what actually happened, examine why, and identify lessons for future work. Gardner recommends using it to strengthen learning from both mistakes and successes. Its purpose is improvement rather than blame, so the discussion should make it safe to surface difficult facts.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.