Ethics, communication and team decisions

Concept and mechanism

PMI presents responsibility, respect, fairness and honesty as guiding values for professional conduct. Public guidance identifies a code update effective 17 November 2025. In a scenario, begin by recognizing the relevant fact and applicable procedure.

If a rule prohibits gifts during selection, postponing use of a gift does not satisfy that rule. If a conflict requires disclosure and a prior participation decision, urgency does not authorize someone to approve their own safeguards. Also avoid assuming that every relationship automatically requires exclusion: apply the conditions actually stated and the corresponding authority.

Honesty includes representing uncertainty, correcting errors and acknowledging contributions. A forecast with dependencies should not be presented as a guarantee. A note disclosing AI use does not establish that references were checked.

Confidentiality requires attention to purpose, access and information circulation. Encrypting transport does not authorize the recipient; when fictional data suffices for a demonstration, avoid unnecessary exposure of real records. These examples exercise professional decisions and do not establish universal legal rules.

Guided application

A team can produce correct information and still communicate poorly. A sponsor deciding funding needs impact, options and a deadline linked to evidence; twenty pages of logs do not necessarily provide that summary. Also confirm the meaning received.

A receipt establishes message delivery, not understanding or approval. Ask recipients to describe the expected action, clarify differences and update the shared record. In distributed teams, distinguish real urgency from scheduling convenience.

Asynchronous input with context and a deadline can support participation that an immediate meeting would exclude. When simultaneous attendance is necessary, distribute scheduling costs and prepare the decision in advance. Do not infer intent from a short message or silence; check meaning before judging commitment.

During conflict, explore interests and constraints instead of automatically choosing a midpoint between positions. A manager can recognize a defensive reaction, pause and return to facts. This supports accountability without turning difficulty or disagreement into public exposure.

Choose and facilitate the session

Before scheduling a session, identify whether you need alternatives, understanding of experience or a decision. During idea generation, separate exploration from evaluation so immediate rejection does not suppress contributions. If a few people dominate conversation, individual collection and turn-taking can reveal other perspectives.

A focus group helps explore themes; it does not automatically provide a representative estimate for all customers. For a decision meeting, confirm criteria, data and authority. If prerequisites are missing but time remains, use the session to prepare options and schedule the decision when conditions are met.

A short daily meeting can identify a blocker and arrange later analysis with the necessary people. It need not require the whole team to observe every technical detail. At the end, distinguish discussion minutes, authorized decisions and follow-up actions.

Record an owner and deadline, plus a signal that allows the outcome to be observed. A retrospective with many suggestions and no followed-up actions has not yet demonstrated improvement. If a report involves intimidation or another situation requiring specialist handling, use the appropriate channel and confidentiality boundaries; public confrontation does not replace that process.

Analyze problems and make decisions reproducible

A cause diagram organizes hypotheses; team participation does not turn every hypothesis into a demonstrated cause. Define observations distinguishing competing explanations and seek counterexamples too. A complaint distribution can guide investigation but does not prove a future intervention’s effectiveness.

If tooling, training and task difficulty changed together, reduced rework cannot be attributed entirely to tooling. Distinguish count from rate: six cases instead of twelve represent half as many cases, but the rate requires work volume. For collective decisions, state population and rule before counting votes.

Twelve favorable votes among fifteen responses are 80% of respondents; if the rule requires 80% of twenty holders, sixteen favorable votes are needed. Silence is not automatically approval. In weighted comparison, check mandatory requirements first.

With continuity weighted at 70% and speed at 30%, scores of 4 and 2 produce 3.4; scores of 2 and 5 produce 2.9. Changing weights after seeing results changes the decision rule and should be handled through the agreed process.

Common pitfalls

Treating delivery as understanding; using silence as consent; confusing knowledge with authority; exposing more information in the name of transparency; inferring population percentages from a focus group; performing every technical analysis in the coordination meeting.