Interpersonal and team
Interpersonal and team is a technique for analyzing how people interact, collaborate, and make decisions in a project environment. It uses observations, feedback, and facilitation to identify strengths, issues, and actions that improve team performance and stakeholder engagement.
Key Points
- Focuses on communication patterns, decision making, trust, and psychological safety within and around the team.
- Uses qualitative data from observations, conversations, surveys, and team artifacts to diagnose collaboration issues.
- Results in concrete actions such as working agreements, conflict resolution steps, coaching, or process adjustments.
- Applicable across predictive, agile, and hybrid approaches to enhance delivery and value.
- Should be iterative, time-boxed, and respectful of privacy and cultural norms.
- Findings inform updates to plans like stakeholder engagement, communications, and resource management.
Purpose of Analysis
To understand how interpersonal dynamics and team practices affect delivery outcomes, identify root causes of collaboration challenges, and choose targeted interventions that improve performance, engagement, and decision quality.
Method Steps
- Define focus and criteria: clarify what dynamics to examine (communication flow, roles, conflicts, decisions) and what good looks like.
- Collect data: observe meetings, review chat/email threads, run brief surveys, hold one-on-ones, and examine artifacts like the team charter.
- Synthesize insights: map patterns, cluster themes, and distinguish symptoms from root causes.
- Co-create actions: facilitate the team to agree on experiments or changes (working agreements, cadences, decision rules, coaching).
- Implement and monitor: time-box actions, define simple measures, and inspect results regularly.
- Adapt and institutionalize: keep what works, adjust or drop what does not, and update relevant plans and documents.
Inputs Needed
- Team charter and working agreements.
- Stakeholder register and engagement information.
- Communications plan and meeting cadences.
- Observation notes, survey results, and feedback from retrospectives.
- Issue and risk logs related to people, process, or collaboration.
- Performance indicators such as cycle time, rework, handoff delays, or defect trends.
Outputs Produced
- Interpersonal and team analysis summary with key findings and root causes.
- Action plan or improvement backlog with owners, time boxes, and simple measures.
- Updated working agreements, team charter sections, or decision rules.
- Adjustments to stakeholder engagement and communications approaches.
- Updates to risk, issue, and lessons learned repositories.
Interpretation Tips
- Triangulate evidence from multiple sources before drawing conclusions.
- Consider context such as culture, remote/hybrid constraints, and organizational policies.
- Look for trends over time, not one-off events.
- Separate behaviors and processes from personalities to avoid bias.
- Prioritize issues with high impact on delivery, safety, or stakeholder outcomes.
- Protect confidentiality to encourage honest input and sustainable change.
Example
A project experiences frequent rework due to unclear handoffs. The manager observes meetings, reviews chat threads, and runs a short survey. Analysis shows decisions are made in side channels and roles are ambiguous. The team co-creates new working agreements, defines a simple RACI for key deliverables, and adds a 10-minute daily sync for cross-functional handoffs. Within two iterations, rework and delays drop noticeably.
Pitfalls
- Jumping to solutions without validating root causes.
- Over-focusing on individuals instead of systems and processes.
- Ignoring quieter voices or remote team members.
- One-size-fits-all interventions that do not match the team context.
- Lack of follow-up, measures, and reinforcement after initial changes.
- Breaching confidentiality and eroding trust.
PMP Example Question
During a review, the team reports that key decisions are being made in private chats, leading to confusion and rework. What should the project manager do first?
- Escalate the issue to the sponsor and request a formal directive.
- Add more status reports to increase transparency.
- Analyze communication patterns with observations and facilitate new working agreements on decision visibility.
- Replace team members who made decisions outside formal meetings.
Correct Answer: C — Analyze communication patterns with observations and facilitate new working agreements on decision visibility.
Explanation: Interpersonal and team analysis identifies the root cause and co-creates practical team agreements to improve collaboration. Escalation or punitive actions are premature and may harm trust.
HKSM