CBE at KU Updates 10.18.2023


​​​​​​Highlights

  • Upcoming decisions (next 2 weeks)

    • Academic calendar type

    • Term length

    • Pricing structure

  • Longer term decisions (next 2 months)

    • Staffing model

    • CBE technology plan

    • Program approval timeline

 

STRAND UPDATES

Business Processes & Systems

Leader: Nick Stevens nickstevens@ku.edu

Next Meeting: Oct 19

Strand members are reviewing the nonterm calendar proposal and providing pros/cons/concerns for their business area. There will be an additional sample calendar for review in the next 2 weeks. On the Oct 19 meeting, we’ll discuss pros & cons of each in preparation for the final proposal to leadership on Oct 27.

Curriculum & Learning

Leader: Kelli Feldman kfeldman@ku.edu

Next Meeting: Oct 25

The next meeting time will overlap with the Competency Workshop. Members of the Curriculum strand can join to listen in to the introduction & teaching portion.

On November 8, the Curriculum strand meeting time will be extended and repurposed for a Faculty Model Workshop, facilitated by C-BEN. Calendar holds to be sent this week.

Information Technology

Leader: Ed Hudson edhudson@ku.edu

Next Meeting: Oct 19

Updated Unicon timeline:

  • Next 2 weeks – define recommendations rubric

  • December 8 – target date to provide final recommendations

  • December 8-13 – 90-minute readout to review recommendations

  • December 13-early January – make decisions based on recommendations

Policy & Regulatory Compliance

Leader: Jennifer Roberts jaroberts@ku.edu

Next Meeting: Nov 7

Assessing the overall program approval timeline and implications for federal approval and financial aid. This will be a topic at the October 27 Advance and a decision to be made in the next 2 months.

Student Journey Supports

Leader: Misty Chandler misty.chandler@ku.edu

Next Meeting: Oct 23

An initial draft of the CBE Student Support Model is completed.

In upcoming meetings, we’ll continue to build out the model and apply it to one of our inaugural programs and get specific on how we translate into a launch plan.