Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the NextGen topic
No spam. Unsubscribe anytime.
Minnesota State pauses CRM purchase as NextGen risk review spotlights tight interdependencies and resource surge
Summary
After a project risk review, Minnesota State leaders paused a planned CRM purchase to reduce integration and staffing risk and prioritized Workday finance/HCM stabilization, identity/access management, modern data architecture and data governance ahead of Workday Student go‑live.
A Baker Tilly review and system project teams told trustees on June 16 that Minnesota State’s NextGen transformation — which includes Workday finance, HCM and student modules plus supporting infrastructure and integrations — has reached a point where sequencing and resource alignment are decisive. The project risk review identified roughly 20 critical building blocks that must align for a successful Workday Student implementation.
Project leaders said Workday finance and HCM stabilization remain foundational. They also flagged identity and access management (IAM), modern data architecture (MDA) and consistent data definitions/governance as essential prerequisites. The chancellor and system leaders said they have paused a separate customer relationship management (CRM) purchase to avoid layering a large, integration‑heavy product onto systems that are still being configured.
Liz Murphy, an executive advisor on the program, summarized the situation to trustees: NextGen is not a single rollout but a large portfolio of interdependent efforts. That makes the sequencing of critical work — IAM, MDA and data governance — and the allocation of scarce IT and campus resources essential to controlling cost and protecting the planned Workday Student go‑live timeline (academic year 2028‑29).
Project leaders presented a resource‑demand chart that showed a summer‑to‑fall surge in interdependent tasks and argued that, with the timeline relatively fixed by contract, the program must either reduce scope or add resource capacity. Trustees and audit staff pressed for clearer, near‑term decisions: lock scope for key elements, finalize staffing assignments, and provide a master integration/architecture plan.
Management agreed. The chancellor said the program’s priority is disciplined execution and stewardship and that the CRM sequencing decision was made to reduce risk, not to abandon long‑term CRM strategy. Project teams said they will return with more definitive scopes, resource assignments and an updated risk profile to the board as the architecture work progresses.
