Project Management

Soft Skills for Project Managers: 7 That Matter Most, With Words You Can Use

Updated October 12, 2026 · 12 min read

Most project managers learn schedules and budgets first, then find that the hard part of the job is people. Soft skills sound vague until you attach them to a real moment: a sponsor who changes the goal, a developer who says a deadline is impossible, two stakeholders who want opposite things. This guide takes seven skills, shows what each looks like in those moments, gives sample wording and a practice drill for each, and ends with a four-week plan.

What “soft skills” means here

Soft skills are the interpersonal and thinking skills that sit beside technical ones: how you communicate, influence, handle conflict and lead. The Project Management Institute (PMI) now prefers the term “power skills,” partly because “soft” sounds optional. We use “soft skills” because that is what most people search for, and mean the same thing.

Technical skills still matter. Our guides to the five phases and the iron triangle cover that side. This page is about the part no software does for you.

What official sources say

The US Bureau of Labor Statistics (BLS) lists seven important qualities for project management specialists in its occupational profile: analytical, communication, critical-thinking, interpersonal, organizational, problem-solving and time-management skills. Most of them are not technical. BLS describes communication as conveying information to staff and getting input from, and presenting results to, clients, and interpersonal skills as establishing trust with clients and responding well to their concerns. It reports a median pay of $102,320 (May 2025) and about 1.1 million jobs in 2025.

PMI’s Talent Triangle, described on its certification page, has three parts: ways of working, power skills and business acumen. It describes power skills as interpersonal skills and lists collaborative leadership, communication, an innovative mindset, for-purpose orientation and empathy. PMI has described the list slightly differently in other documents, which shows that no one list is final. For PMI’s survey figures on how power skills relate to project outcomes, see the evidence section of our project management tips.

The seven skills

1. Clear communication

What it looks like: short, specific updates; saying the bad news early; adapting the message to the listener, so the sponsor gets the decision needed and the engineer gets the detail.

Sample wording (ours): “Status: amber. We are three days behind on testing because the test environment was down. I need a decision by Friday: extend the date by three days, or drop the reporting feature. My recommendation is to drop the feature.”

Practice drill: write your next status update in four lines: status, reason, decision needed, recommendation. Our guide to improving project communication goes further.

2. Active listening

What it looks like: asking before answering, summarizing what you heard, and noticing what people avoid saying.

Sample wording: “Let me check I have this right. You are worried less about the date and more about the launch being visible to customers before support is ready. Is that it?”

Practice drill: in your next three meetings, restate the other person’s point before you give yours.

3. Negotiation and influence

What it looks like: you often lack formal authority over the people whose work you need. Influence means linking your request to their goals, offering trade-offs and agreeing to things in writing.

Sample wording: “I know your team is stretched. If I move two non-urgent items to next month, could you give me two days for the review this week?”

Practice drill: before an important request, write down what the other side cares about and what you can offer. Plan two options, not one demand.

4. Conflict resolution

What it looks like: raising problems early, separating the person from the issue, finding the interests under the positions, and not letting disputes drag on in side conversations.

Sample wording: “It sounds like you both want a stable launch, and you disagree on how many test cycles that takes. Can each of you tell me what risk you are trying to avoid?”

Practice drill: next time two people disagree, ask each for the risk they are trying to prevent before discussing solutions.

5. Empathy and stakeholder awareness

What it looks like: understanding each stakeholder’s pressure, concern and preferred way to be informed. BLS describes establishing trust and responding well to clients’ questions and concerns as a core quality.

Sample wording: “What would make this project a success for you personally?”

Practice drill: list your five most important stakeholders with one line each on their main concern and how often they want updates. Use the planner below.

6. Motivating and leading a team

What it looks like: making goals clear, matching work to strengths, removing obstacles, thanking people specifically and treating mistakes as information. You lead without being the boss of the team. See boss vs leader and team building techniques.

Sample wording: “The migration finished early because Sam found the data problem on Tuesday. That saved us a week. Thank you.”

Practice drill: once a week, give one person specific thanks that names what they did and the effect.

7. Adaptability and composure

What it looks like: staying calm when plans change, re-planning quickly and not showing panic to the team. BLS lists problem-solving as handling difficult or unexpected situations and finding effective solutions.

Sample wording: “The vendor has dropped out. Here are three options with the time and cost of each. I will confirm a choice by tomorrow noon.”

Practice drill: after every surprise, write a three-line summary of what happened, the options and what you chose. It trains a calm routine.

Project moments and the skill each needs

MomentMain skillWhat to do first
The sponsor changes the goal mid-projectCommunication, negotiationAsk what changed, then show the effect on time and cost and ask for a decision
A team member says the deadline is impossibleListeningAsk what would need to be true for it to work; check the estimate
Two stakeholders want opposite thingsConflict resolutionGet each one’s underlying goal, then take it to the sponsor if needed
A key person is overloadedEmpathy, leadershipCheck real workload; move or drop something with the manager
You must report a delayCommunicationTell the sponsor first, early, with options and a recommendation
A request keeps growing the scopeNegotiationSay yes to the idea and be honest about cost. See scope creep
The team is demoralized after a setbackLeadership, composureName the setback, thank the effort and agree on the next step
Nobody owns a taskLeadership, clarityAssign one owner. See the RACI chart
A decision is stuckInfluenceOffer two options with a recommendation and a deadline. See decisiveness

A stakeholder conversation planner

Fill in a row like this for each important stakeholder. The example is our illustration.

StakeholderMain concernWhat they want from meHow and how oftenRisk if ignored
Finance directorBudget overrunsMonthly forecast with variances explainedOne-page email, monthlyFunding is frozen
Head of salesLaunch date for a big customerEarly warning of any slipShort call, every two weeksPromises a date we cannot meet
Lead developerUnrealistic scopeProtection from last-minute changesDaily stand-upQuits or burns out

Review it every month. Concerns change as the project moves from planning to delivery.

Showing these skills in an interview

Interviewers rarely ask “are you good at communication?” They ask for a story. Use the STAR pattern: situation, task, action, result. A made-up example answer to “Tell me about a conflict on a project”:

Situation. Two team leads disagreed on how many test cycles we needed before launch.

Task. I had to settle it without delaying the date or hurting quality.

Action. I asked each lead what risk they were trying to avoid. One feared customer-facing bugs, the other feared missing the date. I proposed an extra cycle on the three highest-risk areas only and took it to the sponsor.

Result. We kept the date, found two serious bugs in the targeted tests, and both leads agreed to the plan.

Prepare three or four true stories from your own work that cover communication, conflict, influence and a setback. Keep the details honest. Interviewers often probe, and a modest true result is better than an impressive invented one. For more on getting hired, see project manager jobs.

A four-week practice plan

WeekFocusDaily or weekly actions
1Communication and listeningWrite every status update in four lines. In each meeting, restate one person’s point before replying.
2Stakeholders and empathyFill in the planner. Have one “what does success look like for you?” conversation.
3Negotiation and conflictBefore one real request, write what the other side cares about and offer two options. Use the risk question in a disagreement.
4Leadership and composureGive specific thanks once. After a surprise, write the three-line summary. Ask a trusted colleague for feedback on what you did well and one thing to change.

Skills build through repetition in real situations, not through reading. Pick one drill at a time and keep it going for a few weeks before adding another.

Common mistakes

  • Treating soft skills as personality. They can be learned, in the same way as scheduling.
  • Confusing nice with effective. Being liked is not the aim. Being clear, fair and reliable is.
  • Over-communicating. Long, frequent updates train people to ignore you. Keep them short and use them for decisions.
  • Avoiding conflict. Problems that are not discussed tend to grow.
  • Using manipulation as influence. Influence means being honest about trade-offs. Tactics that exploit people destroy trust the first time they are noticed.
  • Neglecting yourself. Composure takes energy. Protect sleep, breaks and boundaries.

Learn more

If you want structured practice, online providers such as Coursera and Udemy list project management courses, some with modules on communication and leadership. We may earn a commission if you sign up, at no cost to you. We are not affiliated with any university. Check the syllabus for these topics before you pay. For the certification side, see our guides to PMI certification and how to prepare for the PMP.

Frequently asked questions

What are the most important soft skills for a project manager?

Communication, listening, negotiation and influence, conflict resolution, empathy, leadership and adaptability. BLS also lists analytical, critical-thinking, organizational and time-management skills.

Are soft skills more important than technical skills for project managers?

Neither is enough alone. Many project problems are about people, but you still need planning and control skills. The mix depends on the project and the role.

What does PMI mean by power skills?

PMI uses “power skills” for interpersonal skills such as collaborative leadership and communication. Its Talent Triangle pairs them with ways of working and business acumen.

Can soft skills be learned?

Yes. They improve with practice, feedback and reflection, like any other skill. Courses help, but real situations teach most.

How do I show soft skills on a resume?

Describe results in plain numbers, such as “resolved a scheduling dispute between two teams and kept the launch date,” instead of listing “strong communicator.”

How do I improve my communication as a project manager?

Write shorter updates that lead with the decision needed, listen before replying, and share bad news early. Ask a colleague what is unclear in your messages.

How do I manage a team I have no authority over?

Link your requests to their goals, agree on expectations in writing, keep your promises and thank people specifically. Influence builds with reliability.

How do I handle conflict between stakeholders?

Ask each what risk or outcome they are trying to protect, look for an option that serves both, and take unresolved disputes to the sponsor with a recommendation.

Ready to compare?

Browse certificate, course and degree programs side by side.

Compare programs →