Collaboration & Leadership

By the end, the learner can

• Vendor collaboration: works with external security vendors or managed service providers to configure tools, resolve issues, and align service delivery with internal security standards
• Cross-functional coordination: aligns computational research milestones with the schedules of hardware engineers, domain scientists, or UX researchers on joint projects
• Conflict navigation: surfaces and mediates technical disagreements between team members regarding algorithm selection or system design using evidence rather than hierarchy

Session plan

1. 10 minHow these are scoredWhere 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.
   • aligns IT project schedules and resource commitments with the delivery expectations of business unit partners
   From Computer and Information Systems Managers (11-3021.00)
2. 20 minSituationsWork 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.
3. 10 minWhere the group splitCompare answers before the debrief. Where the room split is the useful part — the split usually marks a real judgment call rather than a knowledge gap.
   • Where did two people read the same situation differently, and what did each notice?
   • Which answer would survive a supervisor asking "why did you do it that way?"
4. 10 minThe pattern behind the answersClose the loop: what changed between the first attempt and the last, and what would have to be true for collaboration to hold up on a bad day.