change-management

2 posts

grammarly

The Trust Question: How Higher Education Is Really Navigating AI (opens in new tab)

Higher education’s AI challenge is fundamentally a question of trust, not simply technology adoption or resistance. Based on interviews with educators and administrators, institutions are balancing competing views about innovation, evidence, ethics, and practical outcomes. The central conclusion is that credible AI governance must make these differences visible and build shared understanding rather than rely on blanket rules or binary narratives. ## AI Policy Is a Campus-Wide Negotiation - Four recurring orientations shape institutional responses: - **Innovators** favor responsible adoption before reactive governance becomes necessary. - **Strategists** want stronger evidence before committing to change. - **Resisters** prioritize ethics, academic integrity, and institutional reputation. - **Pragmatists** focus on student success, equity, and workable implementation. - These perspectives often coexist within the same institution. - Differences between administrators, writing center leaders, and faculty can create productive debate or direct conflict. - Recognizing these mindsets helps institutions engage stakeholders more effectively. ## Institutions Need Alignment, Not More Tools - Leaders consistently asked for alignment with institutional priorities, constraints, and values—not additional technology. - Effective partners should help institutions understand trade-offs rather than impose preselected solutions. - Skeptics need language that allows them to raise concerns constructively. - Advocates for adoption must recognize that resistance often reflects responsibility rather than fear of change. - AI is forcing institutions to clarify long-standing tensions such as: - Speed versus rigor - Access versus control - Innovation versus stability ## Academic Integrity as a Trust Problem - The common starting question—how to prevent students from misusing AI—is too narrow. - Academic integrity also asks whether institutions trust students and whether students trust their institutions. - Excessive restrictions can communicate distrust, while a lack of governance can appear negligent. - K–12 and higher education face different accountability structures, but both must create guidelines that reflect their actual educational values. - Many educators are shifting: - From detection to judgment - From surveillance to discernment - From punishment to responsibility - Integrity policies therefore communicate what an institution believes learning is for. ## Governing Under Uncertainty - Leaders are tired of portraying AI as either an existential threat or a universal solution. - They need principled language for discussing uncertainty with students, faculty, families, and governing boards. - Every AI decision sends a message about institutional values and credibility. - Maintaining trust requires thoughtful governance, shared understanding, and honest engagement with uncertainty—not stricter rules alone. Institutions should treat AI governance as an ongoing process of alignment and trust-building. Rather than beginning with enforcement or technology procurement, they should clarify their values, acknowledge competing perspectives, and develop policies that support informed judgment and shared responsibility.

figma

An Insider’s Guide to a Seamless Figma Migration | Figma Blog (opens in new tab)

Migrating to Figma is presented as an organizational change—not merely a software switch. Success depends on careful planning, cross-functional communication, advocacy, training, and adaptation of existing workflows and cultural norms. The article argues that treating migration as a strategic investment can produce long-term gains in collaboration, transparency, and productivity. ## Planning the Migration - Begin by identifying the reasons for adopting Figma, such as: - Better collaboration - Greater transparency - Streamlined processes - Treat migration as a change-management initiative involving the entire organization. - Plan around team commitments and existing tool-expiration dates. - Use resources such as Figma’s Migration Toolkit for guidance when moving from other design platforms. ## Building a Cross-Functional Advocacy Team - Create a core team with representatives from design, development, product management, and stakeholder groups. - Give the team responsibility for: - Gathering balanced feedback - Configuring the Figma workspace - Managing communications - Coordinating library transfers - Successful examples include: - Wells Fargo’s “Figma Jedis,” combining experts and enthusiastic users - Uber’s integration of Figma training with an existing design-system workshop - JPMorgan Chase’s advocates, nominated by leadership and cross-functional groups - The strongest advocates are engaged, representative of different departments, and connected to existing initiatives. ## Securing Organization-Wide Support - Obtain buy-in from developers, product managers, leadership, and other stakeholders—not only designers. - Present a clear proposal outlining the benefits and drawbacks of migration. - Build support through: - Workshops and demonstrations - Best-practice sharing - Early access to libraries and components - Training and practical guidance - Dropbox’s migration shows the value of sustained outreach and creative engagement, including extensive internal promotion and Figma-themed incentives. ## Learning from Other Organizations - Contact teams that have already completed large-scale migrations. - Their experience can provide: - Training plans - Deployment playbooks - Cover pages and workspace conventions - Warnings about common mistakes - Examples from Wells Fargo, Uber, and Dropbox demonstrate how peer advice can improve rollout planning and reduce avoidable problems. - Large migrations benefit from studying proven approaches rather than designing every process from scratch. ## Establishing a Migration Timeline - Build a schedule that accounts for: - Team availability - Existing project commitments - Expiration dates for current tools - A defined timeline helps coordinate the transition and gives teams a clear path from planning to adoption. The practical recommendation is to manage a Figma migration as a coordinated organizational program: assemble advocates, involve every relevant function, learn from experienced teams, and create a realistic timeline before moving work and libraries.