Communication in Science

By the end, the learner can

• Team communication: relays scheduling changes and protocol updates to study team members through email and verbal briefings
• Hydrologic findings summary: drafts written summaries of basic water quality or flow data for internal review using standard report templates
• Stakeholder terminology: uses accessible language when introducing watershed concepts to community members during initial public meetings

Session plan

1. 10 minThe sceneWhere this shows up: engineering offices and labs, working with managers, engineers, technicians. Conditions to expect: analytical, precision-driven, project-based. Entry roles this maps to: Engineering Technologists and Technicians, Except Drafters, All Other, Non-Destructive Testing Specialists, Aerospace Engineering and Operations Technologists and Technicians.
   • translates client requirements into preliminary written technical briefs for internal team review
   From Architectural and Engineering Managers (11-9041.00)
2. 25 minRun itPairs. One plays the managers, one plays the Engineering Technologists and Technicians, Except Drafters, All Other. Run the scene for four minutes, then swap. The observer scores against the criteria before anyone discusses it.
   • Tools in play: Data base user interface and query software, Analytical or scientific software, Computer aided design CAD software.
3. 15 minObserver scores itScored live against the four levels. The scorer marks what they saw, not what they assume the learner could do on a better day. Emerging is the target for this point in the program: Just beginning to learn or acquire the skill.
4. 15 minSwap and re-runClose the loop: what changed between the first attempt and the last, and what would have to be true for communication to hold up on a bad day.