Communication and Teamwork
This domain tests whether you can make technical work understandable, decision-ready, and traceable across disciplines. It covers technical writing, active listening, stakeholder communication, design reviews, conflict resolution, and records of decisions. The exam favors concise, audience-specific messages with clear actions and owners.
Core rules and concepts
- State purpose, audience, key message, evidence, and requested action early; separate facts from recommendations.
- Use active listening: paraphrase the concern, ask clarifying questions, and confirm agreement before proposing a solution.
- Record decisions, assumptions, actions, owners, and due dates; verbal agreements are not controlled records.
- In design reviews, raise issues with data and impact, not personal blame; track them to closure.
- Escalate unresolved technical disagreements with a clear statement of risk, options, and recommended path.
Worked example
Two teams disagree about a pump selection. The meeting becomes personal. You restate both positions, ask each team to identify the decision criteria, and convert the debate into a weighted decision matrix using head, efficiency, maintenance, and lifecycle cost. The data shows one option is better on lifecycle cost but marginal on head margin. You document the assumptions, recommend the option with adequate margin, assign a verification test, and record the owner and date. The reasoning is that criteria and evidence convert conflict into a traceable decision.
Traps
Sending vague messages such as “please fix”; hiding bad news until the review; relying on verbal decisions that are never recorded; and copying everyone instead of identifying the decision owner.