Key Takeaways
Treat project management as work through people, not just plans
The work is relational. Anthony Mersino opens with his own reversal: after being passed over for promotion, he recognized that a task-first style had left his team relationships weak. As he learned to notice emotions and invest in people, he moved from leading a 12-person team to managing 75 people across the United States and internationally.
Skills compound through others. A study of 400 projects cited in the book found that emotional competencies were strongly associated with project success, while IQ showed little or no relationship. The book’s point is especially relevant to project managers: projects are temporary, teams change, and managers often lack direct authority. Technical methods matter, but they cannot substitute for the ability to earn cooperation and make sound decisions with people.
The opening argument reframes project management as a coordination problem, not merely a planning problem. Schedules describe work; trust, communication, and conflict determine whether people can carry it out together. That distinction connects with organizational research on coordination costs: as interdependence rises, misunderstandings and weak relationships become operational risks. The cited project study supports the case, but association does not establish that EQ alone causes success. Project complexity, organizational support, and resources also matter. The practical claim remains strong: interpersonal competence is not decoration around the work. It is part of the infrastructure that lets the work happen.
Name the feeling before it starts writing your email
Feelings are clues. Mersino uses SASHET, a mnemonic for six broad feeling families: sad, angry, scared, happy, excited, and tender. It is not necessary to identify a precise emotion every time. Recognizing the family can still reveal what is happening. A missed deliverable may bring anger to the surface, while fear about a slipping deadline sits underneath it.
Build the noticing habit. Emotions also show up in bodily sensations, facial expression, and patterns in what keeps bothering someone. The book suggests journaling, taking a physical inventory, backtracking through the day, or recording feelings on a tally sheet. Mersino recommends keeping a feelings journal for 30 days to spot recurring triggers and emotions that are being avoided or missed.
This approach turns vague introspection into observation: identify a feeling, notice its context, and look for patterns. That resembles emotional granularity, the ability to distinguish among emotional states rather than labeling every discomfort as simply stress. Greater precision can support better choices because fear, anger, and sadness may call for different responses. Bodily cues can help, but they are not a universal dictionary. A tight chest may mean anxiety, exertion, or illness. The useful discipline is to treat sensations as evidence to investigate, not as proof of a single interpretation.
Protect your judgment by spotting the conditions that make you reactive
Catch the escalation early. The book calls an uncontrolled emotional reaction an emotional hijacking: a stimulus prompts an immediate response before deliberate thought has time to intervene. Mersino recounts sending a terse, angry email to a team lead after pressure had built. The message escalated to his manager and led to a formal investigation lasting two months. The email was a symptom; the damaged relationship and stress were already in place.
Check your risk level. HALT means Hungry, Angry, Lonely, and Tired, four conditions the book presents as warning signs of reduced resilience. Other risks include anticipating disaster, obsessing over a slight, and interpreting one setback as proof that everything always goes wrong. Naming the trigger, pausing, and checking the evidence can create room for a chosen response.
The practical insight is that self-control often begins before the tense conversation, through noticing fatigue, rumination, and threat interpretation. This is compatible with cognitive reappraisal, the practice of reconsidering what an event means before acting on it. A pause is not avoidance if it leads to a clearer response; it is a way to restore choice. HALT is a useful quick check, not a complete diagnostic tool. Hunger or tiredness may increase vulnerability, but workplace pressure, authority, or unfair treatment can be the underlying problem and should not be reduced to an individual's mood.
Listen for the need beneath a stakeholder's position
Understand before persuading. Empathy means trying to understand another person's emotions and perspective, rather than assuming they see the project as the manager does. The book's empathetic listening practice is concrete: give full attention, let the speaker finish, summarize what was heard, and tentatively name the emotion. A team member who says a colleague dismisses their work may need recognition or a chance to explain the impact, not an instant solution.
Read the organization too. Organizational awareness means noticing informal influence, political realities, and unwritten rules. Mersino advises identifying who actually approves decisions, what behavior earns rewards, and whether an organization's stated values match what happens in practice. For instance, a workplace that celebrates last-minute rescues may reward crises more than steady planning.
Empathetic listening slows the familiar reflex to defend, advise, or redirect. In conflict research, accurately reflecting another person's account can reduce the sense of being misunderstood, even when the listener disagrees with the conclusion. Organizational awareness adds a valuable systems lens: a stakeholder's resistance may reflect incentives or hidden authority, not stubbornness. Still, emotion-reading is fallible. Body language and tone can be misinterpreted, especially across cultures or in remote meetings. Strong practice pairs observation with verification: ask whether the interpretation fits, rather than treating a manager's intuition as privileged access to another person's mind.
Keep empathy warm, but leave other people's emotions with them
Care without taking over. Emotional boundaries describe the distinction between understanding another person's feelings and treating those feelings as one's own responsibility. A manager can recognize that a team member is angry without becoming angry too, or trying to fix the person simply to restore personal comfort. The book recommends stating one's own feelings and requests clearly, while allowing others to have their reactions.
Own your contribution. Mersino calls co-creation the idea that both people contribute to a relationship's outcome. He illustrates the risk of ignoring one's part with the story of his father, who repeatedly blamed supposedly foolish bosses across many jobs while carrying the same critical, sarcastic approach into each new relationship. The principle supports reflection, but it does not mean both parties hold equal power or blame.
The distinction between empathy and emotional absorption is essential for leaders who must remain steady while attending to a team's distress. The co-creation idea can also interrupt helplessness by directing attention toward actions that remain within one's control. Its limit matters: responsibility is not always symmetrical. Bullying, discrimination, or coercion can make a relationship unsafe, and an individual should not be told to share blame simply because a conflict is recurring. The strongest use of this model combines honest self-examination with an assessment of power, conduct, and available protections.
Map stakeholders before they become the surprise that derails delivery
Make relationships deliberate. Mersino describes stakeholder relationship management as a practical cycle: identify who can affect or be affected by the project, learn their position and objectives, plan how to engage them, and maintain the relationship. A useful stakeholder record can include priority, role, attitude toward the project, communication preferences, and what success means to that person. The goal is not to collect everything about everyone, but to focus scarce attention where it can protect delivery.
Build contact before crisis. In one example, a disengaged executive sponsor became more involved after the project manager scheduled regular briefings. In another, the manager's relationship with a vendor's business contact helped surface service problems and bring the vendor's support team into the discussion. Regular one-on-ones, concise tailored updates, and follow-up on agreed actions can keep these relationships active.
A stakeholder map makes social work visible and easier to prioritize, much as a risk register makes uncertainty discussable. It also counters a common bias: focusing on the immediate team while overlooking sponsors, resource managers, or vendors who can block progress. The method has an ethical edge. Notes about people can become surveillance or a tool for manipulation if personal details are collected without purpose. Work-relevant interests and communication needs are usually enough. A relationship plan should help both parties coordinate, not turn every human interaction into a sales funnel.
Tell the useful truth early, before silence hardens into resentment
Choose a third option. Difficult conversations can feel like a choice between staying silent and exploding. Mersino draws on the idea of a sucker's choice: pause to clarify what outcome is wanted and what outcome must be avoided, then look for a more constructive response. When a manager ended a meeting about a serious network problem abruptly, Mersino left without addressing it. A better move would have been to state the need for an action plan and arrange a workable follow-up.
Be direct and specific. The book recommends naming the behavior, one's response, the reason, and the requested change. It also encourages saying no when needed and addressing small hurts before they accumulate. These practices make expectations clearer and reduce the resentment that can follow a yes given out of fear or people-pleasing.
Directness is most effective when it is paired with respect and a concrete request. That combination resembles nonviolent communication, which separates observable behavior from judgment and makes needs explicit. The point is not radical candor for its own sake; bluntness can humiliate or escalate. Nor is silence always cowardice: in situations involving retaliation or danger, careful documentation and support may be safer than immediate confrontation. The useful test is whether a conversation improves shared understanding or merely discharges the speaker's anger. Truth is a relationship tool when it serves clarity, accountability, and repair.
Set team norms, then reward and enforce what you actually value
Leaders shape the climate. A project manager influences team morale through everyday signals: whether rules are enforced, conflict is addressed, promises are kept, and good work is noticed. Mersino recommends establishing team values and expectations early, then recognizing people who demonstrate them. In a class he taught, students agreed to return from lunch after 30 minutes, but many came back late. Discussing the broken commitment made clear that agreements applied to everyone and that lateness affected the whole group.
Do not bury conflict. The book distinguishes collaboration, which brings disagreement into the open and searches for its cause, from approaches such as smoothing, forcing, or withdrawal that can leave the issue unresolved. A short pause or withdrawal can help people cool down, but persistent avoidance often pushes conflict underground. Recognition, accountability, and honest discussion make the team's stated values credible.
Norms become real through repeated enforcement, not through a polished team charter. This connects with procedural justice: people are more likely to accept decisions when expectations are clear and applied consistently. Recognition also tells a group which contributions matter, often more powerfully than slogans do. There is a caution in the book's emphasis on enforcement: rigid rules can silence dissent if leaders confuse disagreement with misconduct. A healthy team distinguishes standards of respect and reliability from pressure to agree. Accountability works best when it protects the work while preserving room to challenge the plan.
Change leadership style with the team's needs, not your habits
Use more than one gear. The book presents six leadership styles: visionary, coaching, affiliative, and democratic styles tend to support connection, while pacesetting and commanding styles can create strain when used too often. Each has a place. A directive approach may suit an emergency; coaching can help someone develop; a shared vision can reconnect people to the purpose of a project. Mersino describes a manager whose weekly goal-setting and confidence helped him find a way to meet a milestone without delaying the project.
Scale by delegating. Large projects add layers of staff and make the manager's role less about personal task control and more about coordination, coaching, and stakeholder relationships. Virtual teams need deliberate contact too. The book recommends face-to-face interaction when possible and relationship-building outside formal conference calls, where emotional cues and informal trust are harder to develop.
Leadership flexibility is more useful than searching for one universally ideal style. The situational leadership idea is that the right degree of direction and support depends on the task, the team's experience, and the conditions. That does not mean changing style arbitrarily; consistency in values can coexist with flexibility in method. Delegation is especially revealing because it tests whether a leader trusts others to own outcomes. In virtual work, contact frequency is not the same as connection. A meeting can transmit information while leaving people isolated, so managers need space for questions, context, and informal exchange.
For Agile teams, replace control with service and genuine trust
Support self-organization. In Agile work, the team is expected to plan and coordinate much of its own activity. The Scrum Master or coach should remove impediments and help the group work together, rather than dictate each task. Mersino recounts a program manager who demanded that an Agile team produce the same detailed schedule and reports as traditional teams because he did not trust its approach. The Agile team was the only one of five that delivered on time and under budget.
Practice positive regard. The book uses this term for treating people as capable of learning and solving problems, then resisting the urge to supply unsolicited answers. A useful coaching question is to ask what the team thinks it should do. Silence can give members room to reason together. The leader remains responsible for support and organizational barriers, not for taking every decision back.
This is a shift in where control lives: the leader creates conditions for coordination, while the team owns the work. The idea aligns with autonomy-supportive management, which gives people meaningful choice while keeping goals and constraints clear. Trust is not passivity. A team still needs transparent commitments, feedback, and intervention when risks exceed its capacity. Nor does one successful Agile team prove that Agile practices always outperform traditional planning. The more general lesson is to match oversight to the work, rather than imposing familiar reporting rituals simply because uncertainty makes leaders uncomfortable.
Analysis
The book's strongest contribution is its translation of emotional intelligence from an abstract leadership virtue into behaviors a project manager can practice: name a feeling, check an assumption, listen without rushing to fix, map stakeholders, and address conflict directly. Its structure follows a useful sequence from understanding oneself to working with others and leading a team. The personal narrative gives that sequence stakes. Mersino's movement from task-focused manager to leader of larger teams makes the argument more persuasive than a list of competencies alone.
The framework also has important limits. Emotional intelligence is used here as an umbrella for skills, habits, and dispositions, while measurement varies across ability tests, self-reports, and competency assessments. The book itself notes that assessment validity is contested. Its cited project studies are suggestive, but they do not establish that emotional intelligence independently causes project success. An emotionally skilled manager cannot compensate indefinitely for impossible deadlines, inadequate staffing, or an organization that rewards crisis behavior.
Some advice needs careful handling. Reading emotion from a face or body is an inference, not a fact, and the claim that irritation at others reveals one's own hidden flaw can turn useful reflection into projection. Likewise, co-creation can restore agency, but it should not erase unequal authority or excuse abusive conduct. The most reliable interpretation is therefore neither emotional determinism nor self-blame. Feelings offer information to test; relationships are influenced by each participant and by the system around them.
The book is most valuable when its practices are treated as disciplined inquiry rather than scripts. A stakeholder map should support mutual coordination, not manipulation. A direct conversation should seek clarity, not victory. A leader's calm should make room for others, not suppress dissent. In that form, emotional intelligence becomes a practical complement to schedules and budgets: it helps a project manager notice what the plan cannot capture, then act without confusing an emotional signal with the whole truth.
Review Summary
Emotional Intelligence for Project Managers receives mixed reviews, with an average rating of 3.76/5. Many readers find it helpful for understanding and managing emotions in project management, particularly for entry to mid-level managers. The book offers practical advice on team building, leadership, and communication. Some experienced professionals consider it basic or obvious, while others appreciate its clear, precise approach. Critics note a lack of new ideas, but supporters value its insights on relationship aspects and people skills in project management. Overall, it's seen as a useful resource for developing emotional intelligence in a professional context.
People Also Read
Glossary
SASHET
Six families of feelingsA mnemonic for six broad groups of emotion: sad, angry, scared, happy, excited, and tender. The framework helps a person recognize the general kind of feeling present without requiring a precise label. Mersino uses it as a starting point for emotional self-awareness and for considering what a feeling may signal about a project or relationship.
Emotional Intelligence Model for Project Management
Project-focused emotional skillsMersino's adaptation of emotional intelligence concepts for project managers. It organizes development around understanding and managing one's own emotions, reading other people and organizational conditions, building relationships, and leading teams. The model emphasizes practical application to changing project teams, limited managerial authority, stakeholder relationships, conflict, and team climate.
Emotional hijacking
Emotion-driven automatic reactionA rapid response in which an emotional stimulus overwhelms deliberate thought and leads to behavior a person may later regret. Mersino uses the term for reactions such as angry outbursts or hostile emails. Recognizing triggers and slowing down are presented as ways to regain the opportunity to choose a more considered response.
Emotional red flags
Clues to hidden feelingsRecurring behaviors that may point to emotions a person has not recognized or expressed directly. Examples in the book include inappropriate humor, sarcasm, passive-aggressive behavior, victim-like complaints, hostility, and strong reactivity. The behavior is a prompt to examine the underlying feeling, not conclusive evidence of a person's motive.
HALT
Four vulnerability warningsAn acronym for Hungry, Angry, Lonely, and Tired. Mersino presents these states as warning signs that emotional resilience may be low and a person may be more prone to an unhelpful reaction. The check is intended to prompt practical self-care or a pause before a high-stakes interaction, rather than to explain every cause of conflict.
Emotional boundaries
Separating feelings and responsibilityThe distinction between one's own emotional experience and another person's. Emotional boundaries allow a project manager to understand and care about a team member's feelings without taking responsibility for controlling or fixing them. The concept also supports clear limits, direct requests, and acceptance that other people may react differently than expected.
Co-creation
Shared relationship outcomesMersino's term for the idea that participants both contribute to the outcomes of a relationship. It encourages a person to examine their own actions and choices rather than assigning all responsibility to the other party. The concept is not a claim that responsibility or power is always equal, particularly in harmful or coercive relationships.
Resonance and dissonance
Leadership's emotional effectTerms used to describe how a leader's behavior affects a team's emotional climate. Resonant leadership connects with the team and helps direct feelings toward shared goals. Dissonant leadership creates emotional disconnection or discord, often through poor empathy or negative communication. The distinction concerns the effect of leadership, not simply whether the leader is pleasant.
Positive regard
Confidence in others' capacityA stance, associated in the book with humanistic psychologist Carl Rogers, that treats people as capable of growth and problem-solving. Applied to Agile teams, it means offering support without reflexively taking over, criticizing, or providing unsolicited solutions. The leader helps create conditions for the team to learn and act for itself.
Servant leadership
Leadership through team supportA leadership approach in which serving the team's needs is central. For Agile project leaders, this includes removing impediments, helping members collaborate, and protecting the team's ability to organize its work. It does not mean abandoning accountability; it shifts the leader's emphasis from directing every task to enabling the team to deliver.
Choosing Appropriate Project Managers study
Study of 400 projectsResearch by J. Rodney Turner and Ralf Mueller, described in the book, examining 400 projects around the world. The study compared project outcomes with project manager competencies, including IQ, emotional intelligence, and managerial competence. Mersino reports that emotional competencies showed a strong relationship with success, while IQ showed little or no relationship in the study.
Emotional Intelligence and Projects study
Study of 67 project managersResearch by Nicholas Clarke and Ranse Howell, summarized by Mersino, involving 67 project managers. It examined links between emotional intelligence abilities and project management competencies such as communication, teamwork, attentiveness, and conflict management, while considering personality, general intelligence, and certification. The book reports associations between emotional intelligence and several important project competencies.
FAQ
What's Emotional Intelligence for Project Managers about?
- Focus on Emotional Intelligence: The book emphasizes the critical role of emotional intelligence (EI) in project management, highlighting its impact on leadership and team dynamics.
- Practical Application: It offers practical tools and techniques for applying EI in project settings, making it valuable for both novice and experienced project managers.
- Comprehensive Coverage: Topics include self-awareness, self-management, social awareness, and relationship management, all essential for effective project leadership.
Why should I read Emotional Intelligence for Project Managers?
- Enhance Leadership Skills: The book provides insights into developing people skills crucial for leading project teams effectively.
- Improve Project Outcomes: By fostering stronger relationships and communication, the book's techniques can lead to better project results.
- Personal Growth: It encourages self-reflection and personal development, helping you understand and manage your emotional responses in professional settings.
What are the key takeaways of Emotional Intelligence for Project Managers?
- Emotional Intelligence is Crucial: EI is vital for project managers, directly impacting team dynamics and project success.
- Self-Awareness and Self-Management: Understanding and managing your emotions are foundational skills for effective leadership.
- Building Relationships: The book outlines strategies for nurturing strong stakeholder relationships, essential for navigating project complexities.
What are the best quotes from Emotional Intelligence for Project Managers and what do they mean?
- "Emotional intelligence is the key to success.": Highlights that technical skills alone are insufficient; EI is essential for effective project management.
- "Catch them doing something right.": Emphasizes the importance of recognition in building a positive team environment.
- "It’s lonely at the top.": Reflects the isolation PMs may feel, stressing the need for building relationships and seeking peer support.
How does Emotional Intelligence for Project Managers define emotional intelligence?
- Definition of Emotional Intelligence: EI is the ability to monitor and manage one's own and others' emotions to guide thinking and actions.
- Components of EI: Includes self-awareness, self-management, social awareness, and relationship management, each crucial for project management.
- Practical Relevance: EI is presented as a practical skill set that can be developed and applied in real-world project scenarios.
How can I improve my self-awareness as a project manager according to Emotional Intelligence for Project Managers?
- Keep a Feelings Journal: Track your emotions to identify patterns and triggers, enhancing emotional self-awareness.
- Conduct a Physical Inventory: Regularly check in with your body to connect emotional states with physical responses.
- Use Paired Sharing: Engage with a trusted colleague to explore your feelings in a supportive environment for deeper reflection.
What techniques does Emotional Intelligence for Project Managers suggest for self-management?
- Know Thyself: Understand your emotional triggers and patterns to manage them effectively.
- Use HALT: The acronym (Hungry, Angry, Lonely, Tired) reminds you to check in with yourself to avoid emotional breakdowns.
- Take Care of Yourself: Prioritize self-care, including nutrition, exercise, and rest, to support emotional resilience.
How can I develop social awareness as a project manager according to Emotional Intelligence for Project Managers?
- Practice Empathetic Listening: Focus fully on the speaker without judgment to understand others' emotions and needs.
- Track Emotions During Meetings: Use an emotional tally sheet to observe and record team members' emotions, enhancing your ability to read the group's emotional climate.
- Identify Emotional Red Flags: Recognize signs like inappropriate humor or passive-aggressive behavior to address issues before they escalate.
What is the significance of relationship management in project management according to Emotional Intelligence for Project Managers?
- Foundation of Team Success: Strong relationships lead to better collaboration and project outcomes.
- Navigating Authority: Building relationships is essential for influencing team members and stakeholders, especially when lacking direct authority.
- Negotiation and Communication: Relationship management skills enhance negotiation and communication, vital for project success.
How can I apply emotional intelligence in conflict management according to Emotional Intelligence for Project Managers?
- Recognize Conflict Early: Be attuned to signs of conflict to address issues proactively.
- Use Empathy: Understand the emotions and needs of those involved to facilitate resolution and collaboration.
- Choose Appropriate Conflict Resolution Styles: Select the most suitable approach based on the situation and individuals involved.
What role does emotional intelligence play in managing large and complex projects according to Emotional Intelligence for Project Managers?
- Stakeholder Management: High EI is crucial for navigating diverse interests and conflicts among stakeholders.
- Team Dynamics: EI helps build cohesive teams by fostering trust and open communication.
- Adaptability: Allows PMs to adapt leadership styles to meet the needs of different team members and project challenges.
What is the significance of servant leadership in Agile projects as discussed in Emotional Intelligence for Project Managers?
- Supportive Leadership Style: Prioritizes the needs of the team, empowering them to self-organize and take ownership.
- Removing Impediments: Agile leaders identify and remove obstacles to ensure effective team progress.
- Fostering Collaboration: Encourages collaboration and communication, vital for Agile methodologies' success.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.