Key Takeaways
Own the outcome, not merely the project plan or status
Management tracks; leadership delivers. Pham distinguishes managing things, such as schedules and resources, from leading the people who make a project succeed. A project leader accepts responsibility for the full result, including work outside a narrow job description. That can mean taking notes, testing a feature, clearing a blocker, or helping the team understand its purpose. The standard is not whether every task was tracked, but whether the team reached its goal.
Ownership without ego. Pham’s model combines accountability, helping people do their best work, and connecting the team across gaps in communication or process. It is especially useful in matrixed organizations, where a project lead may have little formal authority. The role is less a title than a commitment to do what the project needs.
The useful distinction is between responsibility for activity and responsibility for outcomes. In complex work, no single person controls every input, but someone can still take responsibility for making dependencies visible and coordinating a response. That resembles the systems view in safety-critical fields, where failures often arise between roles rather than inside one person’s task. The caveat is important: ownership should not become a license for organizations to dump unlimited work on the most conscientious person. Strong leadership includes making capacity and authority problems visible, not quietly absorbing them.
Give first, and make every teammate easier to approach
Rapport is practical. At Ticketmaster, Pham began offering candy to engineers on a dark, quiet office floor. The small daily ritual gave her a natural reason to talk with colleagues, helped them see her as approachable, and made later requests for help feel less transactional. The point is not that every leader needs a candy bowl. A coworker shared video games, another gave away fruit, and a baker brought treats.
Notice the person. Learn how colleagues pronounce their names, what they prefer to be called, and how they like to communicate. Offer specific help before an overloaded teammate has to delegate it. Thank people for what they actually did, and create low-pressure chances for the team to connect. These gestures build familiarity and make it easier to raise questions or concerns.
These small practices function as relationship infrastructure. Familiarity lowers the social cost of asking for help, while specific appreciation signals that effort is noticed rather than taken for granted. The idea also fits reciprocity, the social tendency to return help, though it should not be reduced to a ledger of favors. Giving is most credible when it is sincere and freely offered. Leaders should also make room for different personalities and cultural preferences: an invitation to connect should feel welcoming, not like a demand to socialize.
Treat every meeting as a small project with a deliverable
Protect the room’s time. Pham cites an estimate that workers spend 62 hours a month in meetings and regard about half that time as wasted. Before scheduling, decide whether a meeting is the best way to deliver an update, check progress, or collaborate on a decision. If it is, name the purpose clearly, invite the people needed, and share an agenda so attendees can prepare.
Facilitate toward closure. Open with brief context, guide discussion, and capture decisions and owners. If a side topic threatens the agenda, record it for later rather than ignoring it. If the group agrees that another issue matters more, change course deliberately. Reserve time to confirm next steps, and end early when the work is done. A useful meeting leaves people clearer than when they arrived.
A meeting is a coordination technology, not a neutral container. Its value depends on whether the right people exchange information, resolve uncertainty, and leave with shared commitments. The book’s emphasis on agenda, context, and closure addresses common sources of cognitive friction: attendees arrive with different assumptions, conversations drift, and decisions remain implicit. Still, structure should not become performance theater. A meeting that follows every procedural step but avoids a difficult decision is no more productive than an unstructured one.
Turn uncertainty into action with questions people can answer
Curiosity creates influence. A new project leader need not wait for subject-matter expertise before contributing. Follow-up questions such as asking someone to explain further show attention and uncover details others may have skipped. Asking a colleague what they recommend can also give them a meaningful role in solving the problem, rather than treating them as a pair of hands.
Make commitments concrete. At the end of a discussion, establish the next action, its owner, and a target date. If nobody can estimate a completion date, ask what must happen before an estimate is possible, then date that smaller step. When requesting help, address a specific person, say exactly what is needed, explain when it is needed, and give the reason. If an open question gets no reply, offer a reasonable assumption that the expert can correct.
Well-formed questions reduce ambiguity while preserving the other person’s agency. The progression from task to owner to date turns a general intention into something observable, which is central to accountability in distributed work. Offering a tentative answer can help because correcting a proposal often takes less effort than inventing one from scratch. But the tactic depends on psychological safety: if corrections are punished, people will simply accept a flawed assumption. A leader must make it easy to disagree as well as easy to respond.
Capture decisions, then connect facts others hold separately
Notes are shared memory. Pham argues that useful meeting notes are not transcripts. They make decisions, action items, owners, and relevant context easy to find. A note-taker who is still learning can record the team’s own terminology, then read back decisions and tasks before the meeting ends so participants can correct mistakes. Sending a concise recap promptly gives absent colleagues a reliable account and keeps commitments visible.
Synthesis finds the missing link. Synthesis means combining separate facts into a coherent understanding, then checking the conclusion. Pham caught a collision between two website projects because she connected plans discussed by different teams. She recommends summarizing information, arranging it in sequence, and asking what the combined facts imply. The inference may be wrong; inviting correction is part of the method.
The chapter treats note-taking as both an operational tool and a way to learn. Reorganizing information requires active processing, while a shared record reduces dependence on individual memory. Synthesis adds a further layer: it turns the project lead into a boundary-spanner who notices when locally reasonable plans conflict at the system level. That capacity is valuable, but interpretation must be kept distinct from fact. Explicitly labeling what is confirmed, inferred, or still unknown protects trust and makes the resulting analysis easier to challenge.
Align sponsor, team, and daily work around one exact result
Start with the sponsor’s reason. Find the person who funds or can stop the project, then ask why the work matters and keep an open channel for decisions and risks. Their intent helps the project lead make sound choices when the sponsor is absent. Next, turn the broad ambition into a result that specifies what counts and by when.
Test the wording. Pham’s goal to launch 30 clients in 30 days sounded clear until teams disagreed about when the clock started, what “launch” meant, and whether the target meant new clients or total clients. The goal was refined to specify the audience, feature, number of additional clients, and deadline. Share it with team leads, test whether they interpret it identically, then connect daily tasks back to the purpose.
A shared goal is a coordination device: it lets specialists make local decisions without constantly waiting for central approval. The example shows how ordinary words can conceal incompatible definitions, especially across functions. Asking people to explain the goal in their own language is a simple form of alignment testing. Precision has limits, though. A measurable target can still reward the wrong behavior if it ignores quality or user impact. The sponsor and team need both a clear finish line and a shared understanding of why it matters.
Use the lightest plan and process that helps this team deliver
Planning is a tool, not proof of control. Pham says a project needs a clear goal and an accountable team, but not always a detailed schedule. Use milestones when they make a large goal feel manageable, a roadmap when the team needs to see work streams and dependencies, and a detailed task list when tightly coordinated work demands it. Retire heavy plans when they stop helping.
Fit the process to the people. The CALM method is Pham’s approach of staying closely aligned on goals and priorities while giving teams room to manage their work. Working agreements let teams decide practical conventions, such as meeting times, communication channels, and task statuses. Review those agreements as needs change. On a fast website redesign, a visible task board, short daily check-ins, and clear goals proved sufficient where a comprehensive plan might have slowed the work.
This is a strong argument for matching coordination costs to actual interdependence. When teams already have reliable workflows, imposing a second layer of tracking can create administrative drag without adding control. Conversely, loosely coordinated work with many dependencies may need more explicit planning. The central question is not whether process is good or bad, but what failure it is meant to prevent. Team autonomy also requires visibility: light management works when priorities, ownership, and emerging problems remain observable.
Rehearse failure early, and protect the people doing the work
Look for trouble before it arrives. A premortem asks a team to imagine that a project has failed at a future date and identify plausible causes. Pham used the exercise to surface concerns and overlooked groups, including people who would support the work after launch. Record the risks, assign them to people with relevant expertise, and revisit them as the project develops.
Build resilience into the work. Redundant skills can prevent one overloaded specialist from becoming a bottleneck. For changes to a live product or process, phased releases or a fallback path can limit damage. Protect people too: sustained emergency effort invites burnout. Explain why an intense push matters, support the team during it, and allow recovery afterward. Heroic effort is most defensible when it produces a meaningful result, not when it compensates for avoidable planning failures.
The premortem uses prospective hindsight: imagining failure can make risks easier to name than asking people to criticize a project that is still socially protected. Pairing that exercise with redundancy and staged releases reflects a broader resilience principle: do not rely on one person or one irreversible move. The human safeguards matter just as much. A team that repeatedly succeeds through exhaustion may appear effective while accumulating fragility. The book’s approach is strongest when leaders also treat workload as a project risk that can be measured and renegotiated.
Projects gain speed at handoffs, not just through faster specialists
Watch the transitions. A relay team can lose a race through a clumsy baton pass even if each runner is fast. Projects lose time similarly when one group finishes but the next does not know the work is ready, or when two teams interpret “done” differently. The project leader can translate between groups, state the dependency plainly, and confirm that both sides understand the timing and meaning of the handoff.
Keep work moving. Identify who receives the next task and alert them before the transfer. When work stalls, find the person or decision causing the delay, clarify the priority, and ask for a committed date. Escalate only if direct coordination fails. If a gap appears and the leader has the skill, they can help fill it or find someone who can. The aim is to reduce idle time between tasks.
This insight shifts attention from individual productivity to flow through the whole system. Queueing theory offers a useful lens: work can accumulate before a constrained stage even when every other specialist is busy. That means adding effort upstream may make delays worse unless the handoff or bottleneck is addressed. The leader’s role is not to monitor every movement, however. Proactive routing is most valuable at high-risk transitions; applied to every task, it can feel intrusive and weaken the team’s ownership.
Trade scope before casually spending time, money, or team stamina
Make trade-offs explicit. When a project changes, its main levers are scope, time, and resources, including people and money. Pham cautions against treating deadline extensions as painless: they can trigger further delay and added cost. First ask whether lower-priority work can move to a later phase or whether a simpler implementation can meet the essential need. The team can compare options by speed and likely impact rather than arguing over preferences alone.
Negotiate toward a workable decision. Listen to each party’s concerns, capture them without judgment, and identify assumptions that allow discussion to proceed. Then list possible solutions and their advantages and drawbacks. Seek agreement where possible; use the sponsor as a tie-breaker when necessary. If a mandate must stand, acknowledge objections honestly before asking the team to collaborate on the least damaging way forward.
The three-lever model makes hidden costs visible. A deadline extension consumes more than calendar time; it can affect budgets, confidence, and the team’s willingness to keep investing. Negotiation is more productive when parties first feel accurately represented, because disagreement often reflects different constraints rather than bad faith. Still, scope cuts are not automatically wise. Removing testing, accessibility, or maintenance can defer risk rather than remove it. The decision should preserve the purpose of the project, not merely protect its launch date.
Lead change by revising the shared map, not defending the old one
Expect the project to move. Pham compares projects to caring for a growing child: a plan may work briefly, then changing needs make it obsolete. People join or leave, assumptions fail, and priorities shift. The project leader’s task is not to prevent every change, but to stay calm enough to help the team respond.
Rebuild clarity. When conditions change, find out why, identify who and what are affected, and revise the goal with the sponsor and team leads. Reassess scope, resources, timing, and risk; negotiate a path forward; then communicate the new priorities to each audience. Executives need the concise implications, while contributors need clear task-level guidance. Watch for signs of confusion, overload, or declining team energy, and ask what support is needed.
Adaptation is not simply flexibility; it is the disciplined replacement of outdated assumptions with a new shared understanding. That resembles feedback control: observe what is happening, compare it with the intended outcome, and adjust the response. The emotional tone of the leader matters because uncertainty spreads through teams, but calm should not be confused with minimizing real problems. Naming what has changed, what remains uncertain, and who can decide the next move gives reassurance without pretending that the situation is under control.
Count team trust and joy as deliverables, not office decorations
Work is done with people. Pham’s motivation comes less from a company slogan than from loyalty to coworkers and the bonds built through shared projects. After her father died, colleagues offered practical help, companionship, and room to grieve. Their support made the workplace more than a place to complete tasks. She argues that leaders can cultivate this culture through appreciation, empathy, celebration, and attention to people who might otherwise go unnoticed.
Measure the human result. The book cites Gallup findings that only 30 percent of employees have a best friend at work, while those who do are reported to be more engaged. The practical lesson is not to force friendship, but to create conditions for trust and mutual support. A successful project should deliver its intended outcome and leave the people who delivered it able to feel proud of their work together.
The strongest version of this claim treats connection as a condition for coordination, not a substitute for it. People who trust one another can raise risks sooner, ask for help, and recover from setbacks with less defensiveness. Social connection can also make difficult work feel worthwhile. Yet friendship cannot be mandated, and a warm culture does not excuse unfair workloads or weak management. The meaningful standard is whether people feel respected, supported, and free to participate in ways that suit them.
Analysis
Glue is a practical leadership book built around a memorable shift: project delivery is not mainly the maintenance of plans, but the work of connecting people, decisions, and tasks. Its narrative moves from small acts of rapport to alignment, execution, negotiation, change, and team belonging. The examples make this progression concrete, especially the candy bowl, the ambiguous client-launch target, the project collision, and the high-pressure redesign organized with a visible board and short meetings.
The book’s strongest contribution is its account of influence without formal authority. A project lead gains leverage through useful service, accurate synthesis, clear commitments, and credible relationships with sponsors and team leads. These practices connect operational discipline with social intelligence. Notes become shared memory; meetings become decision systems; handoffs become the points where system flow is won or lost. The advice is therefore more integrated than a catalog of project-management techniques.
Its limitation is also close to its strength. Pham’s model depends heavily on a leader who notices needs, remembers preferences, organizes social rituals, fills task gaps, and protects team morale. In some workplaces, this invisible relational and administrative labor may be undervalued or concentrated on a few conscientious people. Ownership should not mean absorbing structural understaffing, and care should not make excessive work seem virtuous. The book is most sustainable when leaders pair personal initiative with transparent limits, shared responsibility, and sponsor accountability.
The approach is especially suited to cross-functional technical projects, where dependencies and shifting requirements are common. Its broader lesson applies elsewhere, but not every team needs the same degree of facilitation or social closeness. The central test remains practical: does the chosen structure help this particular group deliver a meaningful result, learn from change, and remain capable of working together afterward? That question captures both the book’s operational method and its human purpose.
Review Summary
Glue receives mostly positive reviews, praised for its practical advice on project management and leadership. Readers appreciate the author's clear writing style, relatable examples, and focus on human aspects of project work. Many find it valuable for both new and experienced managers. Some criticisms include repetitiveness, basic information, and controversial advice on work-life balance. Overall, reviewers recommend it as an accessible guide for project leaders, with a few caveats regarding certain sections.
People Also Read
Glossary
CALM method
Aligned priorities, flexible executionA planning approach that keeps a team aligned on the goal and the most important priorities while allowing members to use their existing workflows and judgment. Pham presents it as a way to reduce unnecessary oversight when teams are already capable of managing their work. It depends on clear priorities, visible progress, and trust, rather than detailed control of every task.
working agreements
Team-designed work conventionsA written set of conventions that a team creates together for how it will work. Agreements can cover meeting schedules, communication tools, response expectations, task tracking, workflow stages, and document storage. Because the team helps choose the practices, the agreements are more likely to fit its actual needs. They should be revisited when the team or project changes.
premortem
Imagine failure before launchA facilitated exercise conducted near the beginning of a project. Team members imagine that the project has failed at a future point and independently propose plausible reasons. Discussing these causes can reveal risks, overlooked stakeholders, and concerns that may be difficult to raise through ordinary planning. The resulting risks can be documented and assigned to people best positioned to address them.
information radiator
Visible project progress boardA shared display that makes project tasks, owners, and due dates visible to the team. In Pham’s example, it was a whiteboard populated with task notes and placed in a common work area. The board helped team members see progress and dependencies at a glance, reducing the effort needed to find out what was happening.
fuzzy roadmap
Work grouped by rough timingA high-level roadmap that places work into broad time categories, such as now, soon, and later, rather than assigning exact dates. It gives a team more structure than a simple priority list while preserving room to adjust sequencing. It is useful when the work needs direction but detailed timelines would imply more certainty than the team has.
implementation scope
Extra work embedded in solutionsWork added through the way a team chooses to implement a feature, even when that extra work is not essential to its immediate purpose. A solution may be more extensive or future-proofed than the current goal requires. Asking whether a simpler short-term approach can meet the need can reduce delivery effort, with deferred improvements tracked separately.
roadkill
Deferred project featuresPham’s informal label for lower-priority items removed from a project’s immediate scope, particularly near a launch. The items are not necessarily abandoned; they can be collected for a later phase or follow-up release. Naming and recording them makes it easier to protect the launch goal without pretending that every proposed feature will fit.
synthesis
Connect facts into understandingThe practice of combining information from conversations, notes, and observations into a coherent account, then drawing and checking conclusions. It can involve inferring consequences, sequencing work to expose missing steps, or describing events as a cause-and-effect story. In project leadership, synthesis helps identify dependencies and risks that may remain invisible when each team focuses only on its own work.
FAQ
What's "Glue: How Project Leaders Create Cohesive, Engaged, High-Performing Teams" about?
- Focus on Project Leadership: The book emphasizes the transition from project management to project leadership, highlighting the importance of leading people rather than just managing tasks.
- Building Cohesive Teams: It provides strategies for creating cohesive, engaged, and high-performing teams by fostering strong emotional connections and a shared sense of purpose.
- Practical Guidance: Anh Dao Pham offers actionable advice and real-world examples to help project leaders effectively guide their teams to success.
- Comprehensive Approach: The book covers various aspects of project leadership, including communication, negotiation, risk management, and change management.
Why should I read "Glue: How Project Leaders Create Cohesive, Engaged, High-Performing Teams"?
- Enhance Leadership Skills: The book provides insights into becoming a more effective project leader by focusing on people and relationships.
- Actionable Strategies: It offers practical, step-by-step recommendations that can be immediately applied to improve team dynamics and project outcomes.
- Real-World Examples: Anh Dao Pham shares her extensive experience and lessons learned from leading numerous projects, making the advice relatable and applicable.
- Broaden Perspective: The book encourages readers to think beyond traditional project management paradigms and embrace a more holistic approach to leadership.
What are the key takeaways of "Glue: How Project Leaders Create Cohesive, Engaged, High-Performing Teams"?
- Ownership and Accountability: Project leaders should take full ownership of project delivery and empower their teams to do the same.
- Building Rapport: Establishing strong relationships and open communication with team members and sponsors is crucial for project success.
- Adaptability and Flexibility: Effective project leaders tailor processes to fit their team's needs and are willing to adapt to changing circumstances.
- Focus on People: Leading projects is about leading people, and fostering a positive team culture is essential for achieving high performance.
How does Anh Dao Pham define a "project leader" in "Glue"?
- Beyond Management: A project leader goes beyond managing tasks and focuses on leading people by inspiring and motivating them.
- Ownership of Delivery: Project leaders take full responsibility for the success of the project, ensuring that all aspects are aligned and moving forward.
- Empowering Teams: They strive to bring out the best in their teams by creating an environment where individuals feel valued and connected to the project's goals.
- Acting as Glue: Project leaders serve as the glue that binds the team together, facilitating communication and collaboration across different roles and functions.
What is the "CALM method" mentioned in "Glue"?
- Closely Aligned, Loosely Managed: The CALM method emphasizes aligning the team with clear goals and priorities while allowing them the autonomy to manage their workflows.
- Trust in Teams: It relies on trusting team members to use their expertise and existing processes to achieve desired outcomes without micromanagement.
- Focus on Priorities: The method involves setting clear priorities and ensuring that the most important tasks are addressed first.
- Encourages Accountability: By giving teams the freedom to manage their work, the CALM method fosters a sense of ownership and accountability.
How does "Glue" suggest handling project risks?
- Preemptive Planning: The book advises building additional time and budget into project plans to account for unknowns and potential risks.
- Premortem Technique: Conducting a premortem helps identify potential risks by imagining a future scenario where the project has failed and brainstorming possible causes.
- Creating Redundancy: To prevent bottlenecks, project leaders should ensure that team members have overlapping skills and can support each other when needed.
- Incremental Changes: For projects involving live features, rolling out changes gradually can reduce the risk of negative impacts on users.
What are some effective communication strategies from "Glue"?
- Tailor Communication: Adjust communication style and content based on the audience, whether it's executives, sponsors, team leads, or individual contributors.
- Consistent Messaging: Regularly communicate the project's goals, priorities, and risks to keep everyone aligned and focused on what's most important.
- Nonverbal Cues: Pay attention to nonverbal communication, such as body language and tone, to better understand team dynamics and potential issues.
- Act as a Conductor: Like an orchestra conductor, project leaders should guide their teams by clearly signaling when it's time for each member to act.
How does "Glue" address the concept of "scope creep"?
- Negotiable Scope: The book emphasizes that scope is always negotiable and can be adjusted to accommodate changes without extending timelines or increasing budgets.
- Prioritization Framework: Use a decision-making framework to prioritize tasks based on speed and impact, ensuring that the most critical items are addressed first.
- Implementation Scope: Encourage teams to explore simpler solutions that meet project goals without unnecessary complexity or additional work.
- Phase Planning: Place lower-priority items in a queue for future phases, allowing the team to focus on delivering the most important features first.
What role does "synthesis" play in project leadership according to "Glue"?
- Combining Information: Synthesis involves merging separate pieces of information to form a coherent understanding of the project and its challenges.
- Deepening Understanding: By synthesizing information, project leaders can identify gaps, infer missing details, and draw conclusions that guide decision-making.
- Connecting Dots: Effective synthesis allows leaders to connect interrelated facts and create a comprehensive narrative that informs project strategy.
- Enhancing Influence: By demonstrating a deep understanding of the project, leaders can build trust and influence among team members and stakeholders.
What are some of the best quotes from "Glue" and what do they mean?
- "Project leaders take full ownership of project delivery." This quote emphasizes the importance of accountability and responsibility in ensuring project success.
- "You manage things, you lead people." It highlights the distinction between managing tasks and leading individuals, underscoring the human aspect of project leadership.
- "Be the glue that binds teams together." This quote captures the essence of a project leader's role in facilitating communication and collaboration across different functions.
- "The best way to know what will work is to actually work with the team to define it." It advocates for a collaborative approach to process development, ensuring that team needs are met.
How does "Glue" suggest building rapport with team members?
- Learn Names and Preferences: Quickly learn team members' names and communication preferences to make them feel valued and respected.
- Be Approachable: Encourage open communication by being approachable, smiling, and making yourself accessible to the team.
- Take Initiative: Proactively offer help and support to team members, demonstrating a willingness to contribute beyond assigned responsibilities.
- Show Appreciation: Regularly express gratitude and acknowledge team members' efforts to strengthen relationships and foster a positive team culture.
What is the significance of "working agreements" in "Glue"?
- Customized Processes: Working agreements allow teams to collaboratively define processes and rules that best suit their unique needs and preferences.
- Avoiding One-Size-Fits-All: By tailoring processes to the team, project leaders can avoid imposing rigid structures that may hinder productivity.
- Empowering Teams: Involving team members in the creation of working agreements fosters a sense of ownership and commitment to the project's success.
- Continuous Improvement: Regularly revisiting and refining working agreements ensures that processes remain effective and aligned with the team's evolving needs.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.