Leadership, Change Management, and Organizational Strategy
Strategy and change
Informatics leaders align technology with organizational strategy: mission, quality goals, financial sustainability, and regulatory obligations. Governance including executive sponsorship, clinical informatics committees, prioritization, and portfolio management prevents project sprawl. A business case includes benefits, costs, risks, and alternatives; ROI may be financial or clinical. Change management is deliberate: Kotter's eight steps (urgency, coalition, vision, communication, empowerment, short wins, consolidation, anchoring) and ADKAR (awareness, desire, knowledge, ability, reinforcement) are common frameworks.
People and execution
Stakeholder analysis maps influence and interest; communication should be tailored and repeated. Resistance is data about the system, not merely a personality problem. Leaders build coalitions, set clear decision rights, and sponsor training and support. They also manage competing priorities, vendor relationships, and benefits realization after go-live. Psychological safety and just culture support reporting and learning.
Traps
Questions often reward technology-first thinking, skipping stakeholder engagement, or confusing leadership with project management. Another trap is assuming a go-live communication plan equals change management. Benefits rarely appear without workflow redesign and reinforcement.
Worked example / rule of thumb
A CPOE rollout stalls because residents do not trust order sets. An ADKAR diagnosis shows awareness and desire, but limited ability due to poor training. The fix is hands-on practice, local champions, and reinforcement, not another email. Rule of thumb: diagnose the change gap before choosing the intervention; communicate vision, remove barriers, and reinforce.