Effective Communication Skills for Project Managers Working with Technical Experts

In the VUCA era, project managers (PMs) often work in matrix‑type environments where they must communicate with senior developers, testers, and other technical experts from different organizations and departments. While many PMs can communicate well in general, they may encounter resistance when dealing with technical experts who respond with jargon, dismissive attitudes, or a "you don't understand" mindset, making the PM feel like a mere progress‑chaser.

To handle this situation, the article recommends several skills. Skill One – “Words of Enlightenment” : PMs should clearly define their own responsibilities. They are not people managers and cannot impose their ideas on others; their authority comes only from the project, organization, and company leadership. A PM does not need to be a technical expert, but must be a communication expert, familiar with common technical terms and basic knowledge, and focus on coordinating senior experts to leverage their strengths toward the project’s correct direction.

PMs should use the management authority granted by the organization to align the team’s goals with the project’s goals. Influence is built through personal charm, establishing rapport, and creating a relaxed communication environment—talking about life, hobbies, or entertainment—not just work matters. This helps team members see the PM’s strengths and be willing to follow their guidance.

Skill Two – “Thoughts Follow” : A PM’s attitude should not be overly rigid. Continuous learning of business knowledge, development terminology, and project‑management practices is essential. When a team member is reluctant to explain, seek help from others, reflect on one’s own questions, and avoid asking vague or irrelevant questions that waste others’ time. Building relationships outside work—such as meals or weekend activities—enhances emotional intelligence and encourages open feedback.

High emotional intelligence is crucial; no one intentionally makes work difficult for others. Understanding the meaning behind professional terms is part of the PM’s growth.

Skill Three – “Shift and Transform” : PMs should practice empathy and consider whether a question is being asked to the right person. Start by consulting junior staff to clarify the problem’s nature and impact, then formulate higher‑level questions for senior experts, involving them in evaluation and reducing dismissive responses.

Often, PMs ask “outsider” questions that frustrate experts, leading them to view the PM as a nuisance rather than a valuable contributor. Therefore, PMs must also care for the team’s emotions to avoid slowing project progress.

Skill Four – “Professional Diagnosis” : PMs should demonstrate professional competence throughout all project phases, not merely act as “chaser”. In the requirements stage, ask about long‑term planning, rapid solutions for key needs, and agile iteration considerations. During design and development, inquire about design universality, compatibility, and impact on other systems. In testing, raise questions about test case dependencies, environment requirements, and data preparation. This proactive questioning showcases the PM’s expertise and guides the team toward comprehensive risk assessment.

Ultimately, a PM does not control people but controls the project. When problems arise, avoid blind questioning; instead, think, learn, summarize, and ask well‑prepared questions.

Welcome to share and discuss: JD.com Technology Management Center, Project Management Department, Liu Ming – WeChat ID: lmlovehot