Outcome 1.2 Study Notes: Leadership and Communication Skills for Health Science & Technology Workplaces

Verbal, nonverbal, and active listening skills for effective communication (1.2.3)

Communication in health science and technology settings is more than “being polite” or “speaking clearly.” You often exchange information that affects safety, quality of care, timelines, compliance, and trust—so your communication has to be accurate, respectful, and understood the first time.

Verbal communication: what you say and how you structure it

Verbal communication is the spoken content of your message—your words, tone, pacing, and clarity. In workplaces like clinics, labs, pharmacies, and health IT teams, strong verbal communication prevents errors because it makes the “what, who, when, and next step” explicit.

A practical way to make verbal communication reliable is to organize it:

• Purpose first (why you’re speaking)
• Key facts (what the listener needs to know)
• Request/next action (what you need from them)
• Confirmation (check understanding)

This matters because healthcare environments are busy and interrupted. If you lead with background (“So earlier today…”) you may lose the listener before you deliver the critical point.

Example (clear verbal handoff):

“I’m calling about the specimen you just received. The label has two identifiers, but the requisition is missing date of birth. Can you hold processing until I fax the corrected requisition? I’ll send it in five minutes—can you confirm the fax number?”

Nonverbal communication: what your body and environment communicate

Nonverbal communication includes facial expression, posture, eye contact, gestures, personal space, appearance, and even your physical setup (standing over someone vs sitting at eye level). Nonverbal signals can reinforce your message—or quietly contradict it.

In health settings, nonverbal cues can:

• Build trust (open posture, calm tone)
• Reduce anxiety (steady pace, attentive eye contact)
• Prevent escalation (relaxed hands, respectful distance)

A key trap is assuming your intent matches your impact. You might feel “efficient,” but if you avoid eye contact and speak quickly, a patient or coworker may read you as dismissive.

Example (nonverbal mismatch):

• Words: “Take your time—I’m listening.”
• Nonverbal: arms crossed, glancing at the computer, foot tapping.
• Likely impact: the speaker feels rushed and stops sharing important details.

Active listening: how you prove understanding (not just hearing)

Active listening is a set of behaviors that ensure you accurately receive and interpret a message—and that the speaker feels heard. In technical and clinical environments, active listening is a safety skill.

Active listening typically involves:

1. Attending: face the speaker, reduce distractions, don’t multitask.
2. Clarifying: ask focused questions when information is incomplete.
3. Reflecting/paraphrasing: restate key points in your own words.
4. Summarizing and confirming: align on decisions and next steps.

One of the most effective tools is closed-loop communication—the receiver repeats back the instruction or information, and the sender confirms correctness.

Example (closed-loop):

• Sender: “Please store this sample at 2–8 °C immediately and log it under accession 3472.”
• Receiver: “Storing at 2–8 °C now and logging under accession 3472.”
• Sender: “Correct.”

What commonly goes wrong

Communication failures are often not about vocabulary—they’re about assumptions:

• You assume the other person shares your context.
• You assume silence means agreement.
• You assume your message was understood because you said it once.

A simple fix is to make understanding visible through paraphrase and confirmation.

Exam Focus

• Typical question patterns:
  • Identify whether a scenario shows verbal, nonverbal, or active listening skills.
  • Choose the best response that demonstrates clarification and confirmation.
  • Explain how a nonverbal behavior could change the meaning of a message.
• Common mistakes:
  • Treating “active listening” as just being quiet rather than paraphrasing and confirming.
  • Ignoring tone, posture, and eye contact in scenario questions.
  • Giving vague advice (“communicate better”) instead of specific behaviors (repeat-back, clarify, summarize).

Negotiation and conflict-resolution skills to reach solutions (1.2.4)

Conflict is normal in workplaces—especially where resources are limited, priorities differ, and tasks are interdependent. The goal is not to “avoid conflict,” but to manage it in a way that protects relationships, quality, and safety.

Negotiation vs conflict resolution

Negotiation is a structured conversation to reach agreement when parties want different outcomes (schedule, resources, roles, priorities). Conflict resolution is the process of addressing a disagreement or tension so work can continue effectively. Negotiation can be part of conflict resolution, but conflict resolution may also involve repairing trust and clarifying expectations.

A practical conflict-resolution process

A reliable process prevents you from reacting emotionally or making the conflict personal:

1. Pause and define the problem: describe the issue as observable facts, not accusations.
2. Identify needs and interests: what does each person truly need (time, clarity, respect, safety)?
3. Generate options: brainstorm without committing.
4. Evaluate options using criteria: fairness, policy, safety, workload.
5. Agree and document next steps: who does what by when.
6. Follow up: confirm the solution worked.

This works because many conflicts are “position battles” (“I need Friday off”) that hide underlying interests (“I have a childcare issue”). When you negotiate interests, you usually find more solutions.

De-escalation and respectful language

A common reason conflict worsens is the use of blame language (“You always…”, “You never…”) which triggers defensiveness. Instead, use I-statements and behavior-based descriptions.

Example (escalating vs de-escalating):

• Escalating: “You’re careless with documentation.”
• De-escalating: “I noticed the last two entries were missing times. I’m concerned because it affects the next shift. Can we review the checklist together?”

Handling disagreement in teams: separating people from the problem

A powerful mindset is: You and the other person are on the same side against the problem. The “problem” might be unclear roles, unrealistic timelines, missing training, or a broken process.

Example (process-focused):

“It seems like the handoff step isn’t clearly owned. Let’s map the workflow and decide who confirms each step.”

What commonly goes wrong

• Winning over solving: aiming to “be right” instead of reaching a workable agreement.
• Mind reading: assuming motives (“They don’t care”) instead of asking.
• Avoidance: delaying until resentment builds.

Exam Focus

• Typical question patterns:
  • Pick the best conflict-resolution response in a workplace scenario.
  • Distinguish positions from interests in a negotiation prompt.
  • Identify an appropriate next step (clarify, propose options, document agreement).
• Common mistakes:
  • Jumping straight to solutions without defining the problem and needs.
  • Using accusatory language rather than behavior-and-impact statements.
  • Forgetting follow-up—agreements often fail without clear responsibilities and deadlines.

Communicating for an intended audience and purpose (1.2.5)

Effective communication is not one-size-fits-all. The same information may need to be delivered differently to a patient, a supervisor, a lab partner, an external vendor, or a community stakeholder.

Audience and purpose: the two questions that shape everything

Before you communicate, ask:

• Audience: Who will receive this? What do they already know? What do they need?
• Purpose: What should happen after they receive it (decide, act, understand, comply)?

This matters because a mismatch causes predictable failures:

• Too technical for the audience → confusion, noncompliance.
• Too vague for the task → errors, rework.
• Wrong tone for the relationship → damaged trust.

Choosing the right level of detail

Think in layers:

• High-level summary for decision-makers
• Procedural steps for people doing the work
• Technical detail and evidence for audits, troubleshooting, or compliance

Example (same issue, different audiences):

• To a patient: “This test checks how your blood sugar has been trending over the last few months.”
• To a lab colleague: “We need the correct specimen type and collection time to ensure validity.”
• To a manager: “We’re seeing repeat collections due to labeling errors; I recommend retraining and a checklist.”

Channel choice: speaking, email, chat, formal report

The channel should match urgency, privacy, and complexity.

• Face-to-face/phone: fast clarification, sensitive topics, de-escalation.
• Email: durable record, non-urgent coordination.
• Secure messaging/work platform: quick updates, short tasks.
• Formal documents: policies, incident reports, compliance.

A common professional skill is knowing when to move from chat to a call: if the discussion becomes emotional, confusing, or high-stakes, real-time conversation prevents misunderstanding.

Plain language and health/technical literacy

In health settings, people vary widely in health literacy and comfort with technical terms. Communicating clearly is not “dumbing down”—it is translating expertise into usable understanding.

Technique: teach-back (audience verification)
After explaining, ask the listener to restate in their own words:

“Just to make sure I explained it clearly, can you tell me how you’ll take this medication when you get home?”

This checks understanding without implying the listener is at fault.

Exam Focus

• Typical question patterns:
  • Identify the best communication method for a given audience and purpose.
  • Revise a message to be appropriate for a patient vs a technical colleague.
  • Explain why a chosen channel (email vs call) is appropriate.
• Common mistakes:
  • Using jargon without defining it.
  • Providing background but not stating the purpose or action needed.
  • Choosing a channel that doesn’t fit urgency or confidentiality needs.

Proper grammar and expression in workplace communication (1.2.6)

Grammar and expression are not just “English class” skills—they protect your credibility and reduce ambiguity. In health science and technology, unclear wording can lead to mistakes, delays, or misinterpretation.

What “proper grammar and expression” means in professional settings

Proper grammar and expression means your message is:

• Clear (the reader understands the point quickly)
• Correct (spelling, punctuation, word choice)
• Complete (includes necessary context and action)
• Professional (tone, respect, appropriate formality)

Even small errors can change meaning. For example, missing punctuation can make instructions unclear, and vague pronouns (“it,” “they”) can hide responsibility.

Clarity tools that matter most

You don’t need fancy vocabulary—you need precision.

• Use specific nouns instead of pronouns when confusion is possible.
• Put the action and owner in the sentence: “I will submit the form by 3 pm.”
• Prefer active voice when responsibility matters: “The technician verified the identifier.”

Tone and professionalism

Tone comes from word choice, formality, and structure. A professional tone is direct without being harsh.

Example (tone shift):

• Too casual: “Hey, can you send that thing ASAP?”
• Professional: “Could you please send the updated inventory list by 2 pm so we can finalize the order?”

Common grammar issues in workplace writing

• Run-on sentences: break into shorter units.
• Comma splices: use a period or conjunction.
• Inconsistent tense: keep timelines clear.
• Unclear antecedents: ensure “this/it/they” clearly refers to something.

A useful habit is to proofread specifically for: (1) the ask, (2) deadlines, (3) names and numbers.

Exam Focus

• Typical question patterns:
  • Edit a short message for clarity, tone, and correctness.
  • Choose the best rewritten sentence that reduces ambiguity.
  • Identify why a message could be misunderstood.
• Common mistakes:
  • Focusing only on spelling while leaving the request unclear.
  • Using passive voice that hides responsibility (“It was done”).
  • Writing emotionally (venting) instead of professionally documenting facts.

Leadership styles and how they influence workplace relationships (1.2.9)

Leadership is not only a job title—it is the ability to influence how work gets done and how people work together. In health science and technology organizations, leadership affects internal relationships (team morale, coordination, safety culture) and external relationships (patients, vendors, community partners, regulators).

What a leadership style is

A leadership style is a pattern of behaviors a leader uses to guide, motivate, and make decisions. Styles influence:

• How safe people feel speaking up
• How quickly decisions are made
• How conflict is handled
• How stakeholders perceive the organization

No single style is “best” in every situation. Good leaders adapt while staying ethical and respectful.

Common leadership styles (and their relationship effects)

Below are widely used categories you’ll see in workplace training and scenario questions:

Choosing a style based on context (situational thinking)

In many health settings:

• Emergencies often require directive leadership to coordinate fast.
• Quality improvement benefits from participative leadership to gather frontline insights.
• Training and mentorship align well with servant leadership.

A common misunderstanding is thinking “directive” automatically means “rude.” You can be directive while still being respectful:

“We need to stop this process now for safety. Please step back while I verify the identifiers.”

Internal vs external relationships

• Internal relationships are affected by how leaders handle fairness, recognition, workload, and psychological safety.
• External relationships depend on credibility, transparency, responsiveness, and ethical behavior.

For example, a leader who communicates clearly and follows through builds trust with vendors and community partners—missed deadlines or inconsistent messaging damages reputation.

Exam Focus

• Typical question patterns:
  • Match a scenario to a leadership style and justify the choice.
  • Explain how a leader’s approach affects teamwork or stakeholder trust.
  • Identify which style is most appropriate in a given situation (urgent vs collaborative work).
• Common mistakes:
  • Claiming one style is always best instead of considering context.
  • Confusing “laissez-faire” with empowerment—hands-off without support is not empowerment.
  • Ignoring how leadership affects external partners, not just internal teams.

Interpersonal skills for group leadership, collaboration, and teamwork (1.2.10)

Teams in health science and technology are interdependent—one person’s work becomes another person’s input. Interpersonal skills help you coordinate, influence, and support others so the group meets its goals.

What interpersonal skills include

Interpersonal skills are learnable behaviors such as:

• Respectful communication and active listening
• Empathy and professionalism under stress
• Giving and receiving feedback
• Accountability and reliability
• Cultural awareness and inclusion

These matter because teams don’t fail only due to lack of technical knowledge—they fail due to miscommunication, unclear roles, and unresolved conflict.

Providing group leadership without “being the boss”

You often need to lead a task even if you aren’t the formal supervisor. Informal leadership looks like:

• Clarifying goals: “What does ‘done’ look like today?”
• Assigning/confirming roles: “Who will verify the inventory? Who will update the log?”
• Managing time: setting checkpoints and priorities
• Encouraging participation: drawing out quieter members
• Protecting psychological safety: inviting questions and concerns

A useful phrase for collaboration is:

“Let’s pause and make sure we agree on the next step.”

Promoting collaboration: feedback that improves performance

Feedback is most effective when it is specific, timely, and focused on behavior and impact.

Example (effective feedback):

“When the specimen log is completed at the end of the shift, it prevents delays for the next team. Could you complete it before you clock out? I can show you the fastest way.”

This works better than general criticism (“Be more responsible”) because it gives a clear action.

Working in a team: roles, norms, and accountability

Healthy teams make expectations explicit:

• Roles: who does what
• Norms: how we communicate (response times, meeting etiquette)
• Accountability: how we track tasks and handle errors

A common team failure is “role ambiguity”—everyone assumes someone else is handling a step. Prevent this by naming owners and deadlines.

Exam Focus

• Typical question patterns:
  • Choose actions that demonstrate collaboration and team leadership.
  • Identify interpersonal behaviors that improve teamwork (feedback, inclusion, clarification).
  • Analyze why a team conflict occurred (unclear roles, poor communication).
• Common mistakes:
  • Equating leadership with authority rather than coordination and support.
  • Giving feedback that attacks character instead of focusing on behavior and impact.
  • Avoiding accountability conversations until problems become severe.

Professional correspondence, documents, job applications, and resumes (1.2.11)

Professional writing is a career skill: it represents you when you are not in the room. In health science and technology fields, your written communication may also become part of an official record.

Professional correspondence: emails and letters

Professional correspondence includes emails, memos, and letters. Strong correspondence is purposeful and easy to act on.

A practical email structure:

1. Clear subject line (topic + action)
2. Greeting appropriate to relationship
3. Purpose in the first sentence
4. Key details in short paragraphs or bullets
5. Specific request and deadline
6. Professional closing and signature

Example (professional email):

Subject: Request: Updated SDS List for Lab Storage (Due Wed)

Hello Ms. Rivera,

Could you please send the current Safety Data Sheet (SDS) list for the reagents stored in Room 214? We are updating the binder and need the latest versions by Wednesday at 3:00 pm.

If any SDS documents are unavailable, please let me know which items are pending and when they will be updated.

Thank you,
Jordan Lee
Health Science & Technology Intern

Job applications: tailoring and professionalism

A job application is a set of documents (often online) that must be accurate, consistent, and complete. Employers look for reliability—missing information can signal poor attention to detail.

Key principle: consistency across documents. Dates, job titles, and certifications should match between your application, resume, and any cover letter.

Resumes: translating skills into evidence

A resume is a concise marketing document summarizing your qualifications. It is not a life story; it is an evidence-based snapshot.

Strong bullet points usually include:

• An action verb
• A task
• A result (what improved, what was achieved)

Example (stronger bullet points):

• Weak: “Responsible for filing.”
• Strong: “Organized and filed patient intake documents to support accurate record retrieval and reduce delays during check-in.”

Avoid exaggeration. If you “assisted,” say assisted—credibility matters.

Cover letters (when required)

A cover letter explains fit: why you want the role and how your skills match the employer’s needs. It should complement, not repeat, the resume.

Exam Focus

• Typical question patterns:
  • Identify the best subject line, tone, or structure for a professional email.
  • Revise resume bullets to be specific and results-oriented.
  • Spot errors or inconsistencies in application materials.
• Common mistakes:
  • Writing vague correspondence with no clear request or deadline.
  • Using overly casual language or slang in professional documents.
  • Listing duties on a resume without showing impact or skills demonstrated.

Technical writing for forms and reports (1.2.12)

Technical writing is different from persuasive or creative writing. In health science and technology environments, technical writing aims to produce a clear, accurate record that someone else can follow, verify, or audit.

What makes technical writing “technical”

Technical writing is:

• Objective: focuses on facts and observations
• Precise: correct terms, units, identifiers, and timelines
• Structured: uses standardized formats
• Traceable: supports accountability and follow-up

This matters because forms and reports often become official documentation. Ambiguity can create compliance issues or make root-cause analysis impossible.

Completing forms correctly: accuracy and completeness

When completing workplace forms (intake forms, inventory logs, incident reports, maintenance checklists), your goal is to ensure the form can stand alone—someone reading it later should not need to track you down to interpret it.

Best practices:

• Follow required fields and instructions exactly.
• Use approved abbreviations only (if your workplace has a list).
• Record dates and times clearly.
• Avoid blank fields; if a field truly doesn’t apply, follow workplace policy for indicating that.
• If you correct an error, follow the organization’s correction procedure rather than scribbling over it.

Writing reports: structure and readability

Reports vary by workplace (quality reports, incident reports, lab reports, project updates), but strong reports usually include:

• Purpose (why this report exists)
• Background/context (only what’s needed)
• Method/what happened (chronological, factual)
• Findings/results (what was observed)
• Actions/recommendations (next steps, owners, timelines)

A helpful habit is to separate:

• Observations (what you saw)
• Interpretations (what you think it means)
• Actions (what you did or will do)

Example (incident-style writing):

• Observation: “Label on vial showed two patient identifiers; requisition lacked date of birth.”
• Action: “Specimen held; supervisor notified; requesting corrected requisition.”

What commonly goes wrong

• Opinionated language (“The nurse was careless…”) instead of factual description.
• Missing identifiers (which device, which lot, which patient, which time).
• Unclear chronology (events out of order, no timestamps).

Exam Focus

• Typical question patterns:
  • Identify which report statement is objective vs opinion.
  • Choose the best way to document an event with clear facts and next steps.
  • Determine missing information needed to complete a form accurately.
• Common mistakes:
  • Writing narratives without structure, making key details hard to find.
  • Omitting dates/times/locations/identifiers that make documentation actionable.
  • Using informal language or unapproved abbreviations in official records.

Stakeholders: identifying them and soliciting opinions (1.2.13)

A stakeholder is anyone who is affected by a decision or can influence it. In health science and technology, stakeholders often have different priorities—patients may value comfort and clarity, clinicians may value speed and accuracy, administrators may value cost control, and regulators may value compliance.

Who counts as a stakeholder

Stakeholders can be internal or external:

• Internal: staff, supervisors, department leaders, IT teams, quality/safety teams
• External: patients and families, suppliers/vendors, community partners, accrediting/regulatory bodies, payers/insurers (depending on context)

Identifying stakeholders matters because solutions fail when the “right people” weren’t included early. A workflow change that ignores frontline staff input may look good on paper but break in practice.

How to identify stakeholders systematically

A simple method is to ask:

• Who uses the process/product?
• Who provides inputs (data, specimens, equipment)?
• Who is responsible for outcomes?
• Who approves or funds it?
• Who is affected if it fails?

You can also categorize stakeholders by:

• Influence/power (can they approve or block?)
• Interest/impact (how much are they affected?)

This helps you prioritize engagement. High-influence, high-impact stakeholders need early, ongoing communication.

Soliciting opinions: getting useful input (not just “feedback”)

To solicit opinions effectively, you need the right method and the right questions.

Methods include:

• Short interviews (good for depth)
• Surveys (good for breadth)
• Focus groups (good for comparing perspectives)
• Pilot testing and observation (good for seeing real behavior)

The key is to ask actionable questions:

• Instead of: “Do you like the new form?”
• Ask: “Which fields are unclear?” “Where do delays occur?” “What would make this easier to complete accurately?”

Closing the loop: trust is built by what you do with feedback

Stakeholder engagement fails when people feel their input disappears. A best practice is to summarize what you heard and what will happen next:

• What themes emerged
• What changes will be made
• What will not change (and why)
• When stakeholders will hear back

Example (closing the loop message):

“Based on staff feedback, we’re moving the checklist to the top of the packet and adding examples for two fields that were confusing. We are not removing the identifier section because it is required for verification. We’ll pilot the revised form next week and collect feedback again on Friday.”

Exam Focus

• Typical question patterns:
  • Identify stakeholders for a described workplace change or project.
  • Choose the most appropriate method to collect stakeholder input.
  • Explain why a plan failed due to missing stakeholder engagement.
• Common mistakes:
  • Listing only obvious stakeholders (e.g., manager) and missing end users (frontline staff, patients).
  • Asking vague questions that don’t produce actionable information.
  • Failing to communicate outcomes of feedback, reducing future participation and trust.