Team communication, leadership and interdisciplinary work

Define roles and the meaning of done

Technical teams combine knowledge of subsystems, disciplines, use and support. Identify who supplies an input, who performs work, who reviews the result and who has authority for a consequential decision. One person can hold several roles, but the responsibilities and relevant independence still need to be clear.

A useful completion statement names the deliverable, configuration, conditions, observations and remaining issues. “Done” without a shared completion criterion can transfer unfinished work to the next team. Agree on the meaning at the boundary and check that the receiving team can use the result. A meeting attendance list is not an allocation of the work.

A record should support the next decision

Our original action record lists unit meaning, physical fit and evidence affected by a change. The first two have named responsible roles; the third has no owner. Leaving that gap visible allows the coordinator to resolve it before acceptance. Hiding it behind an overall green status would conceal required work.

For a consequential request, state the issue, its evidence, effect, proposed action, owner and needed event or date. The receiver can confirm their understanding and raise constraints. Read-back or a written summary helps expose different meanings, but it does not substitute for technical review. Preserve the decision and rationale where later teams can retrieve them.

Make disagreement useful

Encourage people to distinguish observations, assumptions and interpretations. A disagreement about a model can identify an omitted condition or a discipline’s different boundary. Ask what evidence would resolve the difference and involve the people with relevant competence. Seniority or confidence does not make an unsupported prediction accurate.

Plan realistic workloads and opportunities to raise concerns. A specialist shared across projects cannot supply exclusive full-time work to all of them at once. Communicate changed dependencies early and update the plan through its responsible owner. Give credit for contributions, preserve the basis of judgments and ensure that important information reaches the people who must act on it.

Replace a vague status with a usable report

A constructed status says, “Messages work.” A more usable report says that version S2 exchanged the defined nominal messages with catalogue D2 in the controlled test, while interrupted-session reconciliation remains untested. It identifies the result and a limit relevant to the receiving integration team.

The project record then assigns the unresolved reconciliation task to a responsible role with the necessary inputs and review path. This assignment closes an ownership gap, not the technical issue itself. Completion needs the actual work and evidence, and the overall readiness decision must retain any remaining limitation.

Try the reasoning

1. Why can a locally completed task still block the next team?

   Show the answer and reasoning

   The deliverable or evidence may not satisfy the receiving team’s needed interface and completion conditions.

2. Does naming an owner close an engineering finding?

   Show the answer and reasoning

   No. It assigns responsibility; the required work and reviewed evidence still need to be completed.

3. How can a technical disagreement improve the project?

   Show the answer and reasoning

   It can reveal different boundaries or assumptions and guide a discriminating observation or review.

What to carry forward

Give work a clear owner and usable completion evidence, and keep shared meanings and unresolved dependencies visible across the team.