Turning what you did here into what you can say

By the end, the learner can

• Technical documentation authorship: produces comprehensive firewall configuration logs, encryption protocol records, and access control change documentation with audit-ready precision
• 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

Session plan

1. 10 minThe methodWhere 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. 15 minWorked exampleDemonstrate executive technology briefing as a computer and information systems manager would do it. The technique is yours to teach — this plan covers the judgment around it, so narrate the decision points out loud and name which parts were judgment and which were procedure.
   • Do it once at working pace so the shape is visible.
   • Do it again, stopping at each point where a different call was possible.
   • Name the one mistake that costs the most here, and why it's tempting.
   From Computer and Information Systems Managers (11-3021.00)
3. 15 minYou try itWork the task on your own first. Support is available, but ask for it out loud so the group hears what got you stuck.
   • Tools in play: Development environment software, Web platform development software, Data base user interface and query software.
4. 10 minCheck and correctClose 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.