Communication in Information Technology

By the end, the learner can

• Stakeholder briefing: presents project status updates and risk summaries to department heads using clear, jargon-free language in scheduled reviews
• IT policy documentation: drafts procedures, standards, and user guides that translate technical requirements into actionable instructions for end users
• Active listening in problem resolution: captures and reflects back concerns from managers and supervisors during conflict or workflow-disruption discussions to ensure shared understanding

Session plan

1. 10 minThe sceneWhere this shows up: technology teams and corporate it environments, working with managers, technical teams, users. Conditions to expect: analytical, system-dependent, problem-solving intensive. Entry roles this maps to: Computer Systems Analysts, Computer Systems Engineers/Architects, Computer User Support Specialists.
   • presents project status updates and risk summaries to department heads using clear, jargon-free language in scheduled reviews
   From Computer and Information Systems Managers (11-3021.00)
2. 20 minRun itPairs. One plays the managers, one plays the Computer Systems Analysts. Run the scene for four minutes, then swap. The observer scores against the criteria before anyone discusses it.
   • Tools in play: Development environment software, Web platform development software, Data base user interface and query 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. Developing is the target for this point in the program: Moving in a positive direction in a professional career. Still learning, with room to grow around the skill.
4. 10 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.