Designing a new CS degree
In higher education, change often comes at a glacial pace. Butin 2022, our team at Kibo had the rare opportunity to design a computer science degree from the ground up. This is the story of how we balanced innovation with regulation, and ambition with practicality, to create a degree fit for the modern tech landscape.
The Challenge: Constraints and Goals
Designing an accredited degree program meant working within strict regulatory requirements—credit hour requirements, types of assessments, and a required balance between computer science and general education. But meeting regulatory standards was just the basic requirement. We aimed to create a program that was not only credible but also cutting-edge, and equipping students with skills for immediate employment and lifelong success.
The Structure: An Intensive, Three-Year Journey
We opted for an intensive three-year program with four 10-week terms per year. This structure allowed for faster iteration and created room for industry experience at the end of each academic year. However, this accelerated pace posed challenges, especially for students new to computer science. The rigorous schedule led us to explore transitioning to a four-year model—though Kibo’s closure came before we could implement that change.
Crafting the Curriculum
Our curriculum development process was thorough. We started by defining the broad learning outcomes we wanted our graduates to achieve. We then consulted experts in academia and the tech industry to ensure our courses aligned with both theoretical knowledge and the practical demands of the workplace.
What Set Kibo Apart
There were two primary ways Kibo’s degree differed from traditional university programs:
More Technical Courses: our program included 20+ courses that covered computer science theory, software development practice, and non-technical skills
Integrated Course Design: We separated course design from instruction, and spent a significant amount of time designing courses with strong narratives, projects, and practical experience. Moreover, each course was designed with a holistic view of the entire program. Rather than treating each course as an isolated experience, we design strong connections between courses.
Kibo’s degree wasn't static. We continuously iterated based on student feedback, performance data, and faculty insights. This ongoing refinement allowed us to adjust course content, add new courses, and even consider structural changes.
Challenges and Lessons Learned
No innovation is perfect out the gate, and a new degree is no different. We grappled with balancing rigor and pacing, managing student workload, and providing flexibility within regulatory constraints. And, once students began learning, we saw many opportunities to evolve the degree.
While Kibo's journey has concluded, our experience offers insights for others looking to reimagine higher education. As Ope observed, “Too often in higher ed, we think it's been this way forever, and it therefore is immovable, but it truly isn't. And I want to see more people take a shot."
Rob Cobb, Kibo’s Chief Product Officer, added: “Even within the constraints, there’s a lot you can do to make positive change.”
The skills students need for success in the 21st century are evolving, and so must university programs. While Kibo’s journey has ended, we hope our experience inspires others to take up the challenge of designing the next generation of university degrees.
To dive deeper into our degree design approach, watch the full reflection video: Designing a CS degree from scratch
Note: This post is part of a series exploring lessons learned from Kibo School. Click here to read the series overview and access related posts.