case study

U of Illinois

University of Illinois: De-Risking Enterprise CMS Migration Through Stakeholder Alignment and Workflow Architecture

profiles

personas

Research

Interviews

stakeholder management

Strategic Value & Governance Outcomes

Empowered Department Autonomy

  • Designed a strategic blueprint that eliminates daily reliance on IT staff
  • Returning operational speed and autonomy to individual departments

De-Risked Enterprise Migration

  • Transformed a high-risk technical overhaul verified with user data and cross-functional stakeholder buy-in
  • Created a structured, step-by-step transition

Operational Cost Reduction

  • Mitigated long-term security and maintenance costs
  • Standardized governance roadmap for the university's future web ecosystem
Executive Summary

The University of Illinois operated on an outdated, legacy Content Management System (CMS) that created severe operational friction. The system possessed critical security vulnerabilities, lacked modern publishing flexibility, and required constant, manual IT intervention for basic content updates.

Fragmented departments operating in silos and a bottlenecked IT department, the university faced a high-risk migration. I focused on identifying the bottlenecks for users and support staff to transition to a modern CMS.

I led user research, discovery, and experience strategy across multiple university system touchpoints. I mapped current workflows and translated technical backend liabilities into high-impact visual narratives. I established a unified governance roadmap that empowered non-technical departments with publishing autonomy while drastically reducing IT operational overhead.

Strategic Product Decisions & Trade-offs

Total Decentralization vs. Strict System Governance

Tension Point

Individual university departments demanded absolute independence:

  • Independence to manage and customize their own web properties without waiting on IT
  • Decentralization leads to fractured brand identities, poor accessibility compliance (WCAG breaches), and long-term security vulnerabilities

design decision

I Designed a Controlled Self-Service Framework:

  • I architected a user-centric workflow that gave departments the flexibility, and autonomy
  • All while locking down core global code components and security protocols at the systemic level.

the trade-off

I balanced department freedom with heightened data security considerations:

  • We limited the absolute design and structural freedom of individual departments
  • Campus-wide system compliance, security, and a unified digital footprint highest priority
My Role

Senior UX Consultant / Experience Architect

responsibilities

User Profiles, User Research, User Interviews, Stakeholder Interviews

collaborations

Solution Architects, U of I IT Lead, U of I Cybersecurity lead, Business Analyst, Business Process Consultant, User Researcher, Engagement Manager, Internal Leadership, Subject Matter Experts

timeline

1.5 months to deliverables

touchpoints

Enterprise CMS/LMS Migrations, Corporate Intranets, System Governance, Workflow Optimization

The Discovery & Architecture Loop

step 1 > Cross-Departmental Qualitative Research

To capture the reality of the university's fragmented ecosystem, I conducted deep-dive user interviews across a diverse array of academic and administrative departments.

I focused on uncovering how non-technical staff interacted with the legacy CMS, mapping out the hidden manual workarounds and identifying exactly where workflows stalled due to forced IT dependencies.

step 2 > Translating Statistics into Human Personas

Following the research phase, my team organized hundreds of qualitative responses into structured, macro-level operational themes. We isolated and categorized common friction points, creating a definitive index of:

  • Workflow inefficiencies (e.g., multi-day delays for basic text updates)
  • Common security liabilities caused by outdated system workarounds
  • Usability barriers preventing departmental independence

step 3 > Driving Executive Buy-In & Trust

To ensure our multi-disciplinary consulting team projected a unified, trustworthy message to the client, I established a strict stakeholder communication framework.

I designed highly accessible graphic presentations that clearly illustrated the "before and after" of the proposed CMS architecture, giving university leadership a crystal-clear, risk-mitigated roadmap for implementation.

The Takeaways

Things I learned throughout this process.

Be Conversational

Keep the interviewing light hearted to get the most honest data from the potential users

Unified Message

Make sure the team has a unified message in order to instill trust from client

Visuals = Clarity

Create accurate and engaging visuals for stakeholders to be able to 'see' their problem