The first two weeks

By the end, the learner can

• Conference paper authorship: produces peer-reviewed manuscripts that clearly present novel algorithms, experimental design, and empirical results for expert audiences
• Executive technology briefing: delivers concise, data-supported presentations on infrastructure strategy, budget needs, and risk posture to senior leadership and board-level audiences
• Disaster recovery communication: authors and executes communication plans that notify all stakeholder tiers of system failures, recovery timelines, and preventive actions

Session plan

1. 5 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.
   • delivers concise, data-supported presentations on infrastructure strategy, budget needs, and risk posture to senior leadership and board-level audiences
   From Computer and Information Systems Managers (11-3021.00)
2. 10 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. 10 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. Proficient is the target for this point in the program: Has functional knowledge of the skill and can apply it properly in specific on-the-job settings.
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.