Character & Fortitude

By the end, the learner can

• Transparent communication: discloses limitations in current informatics solutions or personal expertise to clinical stakeholders rather than overstating capabilities
• Violation accountability: addresses security procedure violations directly and constructively with individuals involved, prioritizing organizational integrity over interpersonal comfort
• Documentation honesty: records security test results, system modification logs, and incident details with complete accuracy, including findings that reflect unfavorably on current security posture

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.
   • upholds data security and access control principles even when business pressure favors expediency over protection
   From Computer and Information Systems Managers (11-3021.00)
2. 5 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, Data base user interface and query software, Web platform development 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 character to hold up on a bad day.