Misaligned Implementations
A connected system meets the technical spec but misses the operating workflow. Teams inherit rework and new points of friction.
Communication
in Context.
Technical proficiency is essential. Graduates also need to connect their expertise to the people, systems, and decisions that depend on it.
The educational gap
Technical skill. A missing connection.
What technical education builds
- Clean code
- Network configurations
- Working prototypes and control systems
- Solutions that meet isolated specifications
Where the handoff breaks
- Explaining tradeoffs to clinicians
- Coordinating changes with operations teams
- Connecting decisions to business needs
- Navigating compliance with other teams
Students need practice translating technical expertise into shared decisions—especially where digital systems meet physical operations.
Take it into your classroom
Ready-to-use resources for educators.
Modular project briefsA 10-minute exchange, a 30-minute seminar, or a review of an existing project.Open the briefs →Discussion promptsQuestions for cross-department planning and student conversations.Explore the prompts →Assessment rubricAdaptable criteria for context, perspectives, tradeoffs, and reflection.View the rubric →
Download the full resource pack (HTML) · One-page discussion brief (PDF)
Open any resource to print or save it as a PDF. Teaching materials are drafts you can adapt to your course.
The cost of siloed learning
When the connection is missing.
Stalled Rollouts
A rollout overlooks equipment constraints, training, or time needed for a safe change. Implementation stalls while teams resolve competing priorities.
Security Workarounds
A security procedure is unclear or does not fit daily operations. People may bypass it to keep work moving.
Illustrative risks—not inevitable outcomes or failures caused by learning alone.
Communication in Context responds to this gap by bringing those conversations into the learning experience—around shared problems with real people, constraints, and consequences.
Download the one-page discussion brief PDF · Framework + sample rubric
A working definition
Communication in Context brings people from different disciplines into conversation around a shared problem, so students can connect technical knowledge with the setting in which it is used.
02 / Where it began
Experience gives knowledge a setting.
Faculty externships helped shape this idea: understanding a workplace means seeing how people work together, what decisions they face, and why a technical task matters. Kyle Jones’s NCyTE Faculty Externship annual reports document these connections across the 2023, 2024, and 2025 program years.
From workplace insight to classroom conversation.
The 2023 report describes plans for team-based capstones and collaboration with a speech department. The 2024 report highlights collaborative planning, documentation, and oral and written deliverables. In 2025, communication, governance, and structured decision-making emerge as recurring priorities.
Read the examples: 2023, pp. 8–10 · 2024, pp. 9–11 · 2025, pp. 8–10.
The IT/OT connection
When systems converge, expertise must connect.
The paper Bridging the IT/OT Cybersecurity Skills Gap places the educational gap in a concrete setting: information technology (IT) manages data and networks; operational technology (OT) monitors or controls physical processes, such as production equipment. As these systems connect, the paper argues that workforce preparation must connect their disciplines too.
Understand the other team’s context.
A network decision can also be an operations decision. Students need to ask what a change means for equipment, continuity, people, and the organization.
Make the decision understandable.
The paper identifies clear communication with technical and nontechnical audiences as a core competency. Explaining consequences belongs alongside configuring a system.
Paper: IT/OT convergence, pp. 7–8 · communication and curriculum, pp. 15–17.
Communication in Context carries these insights into a teaching question: how can students practice connecting their expertise with other people’s needs before entering the workplace? The shared problem, different perspectives, and decision brief below are a proposed classroom response.
Explore the paper and annual reports →03 / Guiding principles
Four ideas to build on.
01
Start with a shared problem.
Begin with a workplace need: connect equipment, support care, or improve a process. Let that purpose guide the technical work.
02
Bring different perspectives.
Bring IT, operations, business, and other relevant disciplines into the same decision. Ask what each team knows that the others need to understand.
03
Make the context visible.
Make equipment limits, workflows, security needs, costs, and human consequences part of the assignment—not background information.
04
Use conversation to connect.
Ask students to explain a recommendation to another role, clarify unfamiliar language, and document what changed after the conversation.
04 / In practice
A 30-minute cross-disciplinary seminar.
Use a shared workplace problem inside an existing course. The clinic example below explores how technical choices affect care and workflow; the manufacturing variation applies the IT/OT paper’s emphasis on communication across connected systems.
Try the IT/OT variation: connect a production machine
Prompt: A manufacturer wants production data from an existing machine to appear on a shared dashboard. What must the team understand before recommending how to connect it?
- IT: What connections, data, and support will be needed?
- Operations: How does the machine support production, and when can changes be considered?
- Cybersecurity: What access and risk questions need investigation?
- Business: What benefit justifies the cost and disruption?
- Communication & design: Can operators and decision-makers understand the plan and their responsibilities?
Use the same 30-minute rhythm: assign roles, negotiate a tradeoff, and deliver one shared brief. Include the recommendation, an unresolved question, who must answer it, and one revision prompted by another role.
An illustrative classroom prompt informed by the paper’s competencies and curriculum discussion, pp. 13–17.
The 30-minute rhythm
Groups of five take the Technology, Healthcare, Business, Communication & Design, and Cybersecurity perspectives. Use the clinic prompt and matrix below; capture the decision in one shared document.
- Min 0–3
Frame
One shared problem statement.
- Min 3–8
Pick Role
One priority and one question per role.
- Min 8–16
Negotiate
One decision and its cross-disciplinary tradeoff.
- Min 16–23
Draft Brief
A recommendation, benefit, tradeoff, and revision.
- Min 23–30
Exit Ticket
One change in thinking after peer feedback.
Use assigned perspectives in a single-program class or disciplinary knowledge in a mixed group. Students label assumptions and questions for real stakeholders.
Classroom simulation prompt
A clinic wants to introduce a digital check-in system.
What would make the system useful, understandable, and appropriate for the people who rely on it?
Choose a perspective. Notice how the questions change.
- TechnologyHow will the system connect, work reliably, and support its users?
- HealthcareHow will it fit patient needs and the daily flow of care?
- BusinessWhat resources, training, and process changes will it require?
- Communication & designWill patients understand what to do, including when they need help?
- CybersecurityWhat information is needed, who should access it, and how will it be protected?
Students compare these perspectives, identify tradeoffs, and explain a proposed approach together.
A proposed classroom activity for faculty to adapt; not a report of a tested seminar.
See the ripple across disciplines.
Read each row across, then select a decision to explore its tradeoff. These are illustrative possibilities to discuss, not measured outcomes.
On smaller screens, scroll the table sideways to compare all five disciplines.
| Decision to explore | Technology | Healthcare | Business | Design | Cybersecurity |
|---|---|---|---|---|---|
| Plan synchronization and recovery. | Keep arrivals moving during outages. | Budget for maintenance and support. | Explain when information is saved. | Protect locally stored information. | |
| Provide an appropriate staff interface. | Fit assistance into the care workflow. | Plan staffing and training time. | Make the help option easy to find. | Define staff access and audit needs. | |
| Limit scope and gather reliability data. | Choose a representative care setting. | Set a budget and review criteria. | Gather feedback from varied patients. | Review safeguards before wider rollout. | |
| Change forms and validation rules. | Confirm essential care information remains. | Review rework and support demands. | Use clear language and fewer steps. | Reconsider which data must be collected. | |
| Implement and maintain permissions. | Check access fits care responsibilities. | Plan onboarding and role-change processes. | Explain unavailable actions and help paths. | Limit access and review permissions. |
Selected decision · Healthcare
Offer staff-assisted check-in.
Assistance can improve access, but the team must coordinate workflow, staffing, and information access.
Discuss: Who provides help, and what should that person be able to see?
05 / From idea to learning
Begin with a small, shared experience.
A first experiment could pair an IT course with manufacturing, engineering, business, or healthcare around one challenge. Keep the technical learning goals, and add a shared explanation of the decision and its consequences.
The IT/OT paper also argues for industry partnerships and faculty externships to keep curriculum connected to workplace needs. Invite an employer or advisory-board member to help frame the problem, identify realistic constraints, and review the students’ recommendations (pp. 18–20).
Shared problem→Different perspectives→Shared understanding
Walk through a possible learning experience.
- Frame the situation. Describe the people, setting, and problem without prescribing the answer.
- Surface the questions. Let each discipline identify what it needs to understand.
- Develop an approach. Ask students to negotiate priorities and explain their choices.
- Reflect on the connections. Identify how another perspective changed the proposed solution.
- Use what emerges. Consider what the experience suggests for future assignments, partnerships, or program development.
06 / Publications & reports
The work behind the framework.
A paper on the IT/OT skills gap and three faculty externship annual reports by Kyle Jones connect workforce needs with teaching. Explore the original documents and the classroom conversations they suggest.
Bridging the IT/OT Cybersecurity Skills Gap
Leveraging Community Colleges, Industry Partnerships, and Government Resources to Develop a Future-Ready Workforce
Connected systems need connected expertise.
This paper examines workforce preparation where information technology and operational technology meet. It argues for integrated curricula, hands-on experience, and partnerships that develop technical capability alongside communication and collaboration.
Connection to the classroom
Use a shared scenario: a manufacturer wants to connect an existing production machine to its network. Assign IT, operations, cybersecurity, and business perspectives. Ask each group to explain its priorities, then draft one recommendation addressing security, continuity, and cost.
Compare what the team first proposed with what changed after hearing the other roles. This is a suggested application of Communication in Context, informed by the paper’s discussion of communication and curriculum (pp. 15–17) and faculty externships (p. 20).
NCyTE Faculty Externship Program: 2025 Annual Report
Reasoning, communication, and governance.
Across ten faculty placements, the report identifies documentation, cross-team communication, governance, and structured decision-making as recurring priorities. Faculty describe plans for scenario labs, policy work, and assessment of professional deliverables.
Connection to the classroom
Ask students to explain a recommendation, document its tradeoffs, and revise it after peer critique. This extends the report’s emphasis on actionable reporting and professional judgment.
Suggested teaching application, informed by report pp. 8–10.
NCyTE Faculty Externship Program: 2024 Annual Report
Collaboration belongs inside the technical work.
Eleven faculty externships reveal the importance of teamwork, business context, documentation, and compliance across varied workplaces. Proposed course changes include collaborative planning, after-action reviews, and projects with oral and written reports.
Connection to the classroom
Use distinct team roles and a shared deliverable within an existing assignment. A short after-action discussion can reveal how another perspective changed the team’s plan.
Suggested teaching application, informed by report pp. 9–11.
NCyTE Faculty Externship Program: 2023 Annual Report
The starting point: bring industry into learning.
The inaugural cohort’s twelve faculty externships connect current industry practice with curriculum plans and continuing partnerships. Examples include peer-tested documentation, real-world team capstones, and collaboration with a speech department.
Connection to the classroom
Have students exchange instructions and test whether a peer can use them. Pair a technical project with a presentation for an audience outside the student’s field.
Suggested teaching application, informed by report pp. 8–10.
The IT/OT paper presents workforce and curriculum recommendations; the annual reports synthesize participant accounts and program records, including planned changes. Together they inform the framework’s development. The classroom activities here are proposed applications, not evaluated interventions in these publications.
Turn the insights into a classroom conversation →07 / Questions to develop
Keep the concept open.
These questions can guide the next version of the framework.
What does “context” need to include?
People, purpose, workplace practices, disciplinary language, constraints, and consequences are starting points. For an IT/OT problem, include the physical process, equipment limitations, continuity needs, and the roles responsible for a change. What would a purely technical specification leave out?
What should students be able to do differently?
Possible outcomes include explaining a technical idea to another discipline, asking better questions, recognizing tradeoffs, and adapting a solution to its setting.
How will we recognize meaningful learning?
Look for evidence that students can explain how another perspective changed their thinking. Develop criteria that value both disciplinary knowledge and the connections between disciplines.
How can faculty externships inform the experience?
Explore how faculty can turn workplace observations into shared problems, teaching examples, and conversations with colleagues in other disciplines.
What is the first experiment worth trying?
Choose a manageable problem, a small group of collaborators, and one clear learning goal. Use the results to refine the concept before expanding it.