I witnessed a well-intentioned initiative at a higher-education institution devolve into turmoil. A new academic program—developed in half the usual time—ended up straining students, faculty, and institutional trust. As someone who laboured to salvage the program, I’ve reflected deeply on how this happened and what it taught me about both the value of project management and the dangers of prioritising urgency over process.
A Rush to Innovate
The goal was to create a program aligned with industry needs, and to do it quickly. Leadership saw an opportunity to attract students and increase revenue. In their urgency, they bypassed critical steps that they deemed unnecessary: consulting experienced faculty and assessing feasibility. The program lead outright refused input from colleagues running a similar, long-standing program that had been iteratively refined over two decades. This existing program had already solved many of the challenges the new initiative would face: curriculum structuring, student skill-acquisition rates, and industry collaboration. Yet their battle-tested insights were dismissed as irrelevant in the name of innovation.
This resulted in a misaligned curriculum that may have looked impressive on paper but buckled in practice. Students struggled with concepts they weren’t prepared for. They were pushed too fast and were overloaded. Faculty, already stretched thin, became makeshift counsellors and tutors. The program aimed to prepare graduates for industry, but wasn’t itself prepared to do so.
Who Paid the Price?
While the goal was clear—launch a market-responsive program that produced job-ready graduates—the underlying priorities took precedence: hitting a launch date and accepting new registrations. A baffling blunder was leadership’s choice to ignore the institution’s own history. An existing program, matured from decades of iterative refinements, could have provided a roadmap to guide efforts while avoiding pitfalls. Instead, leadership ineptly reinvented the wheel. Students were promised job-ready skills but received a half-baked curriculum. Faculty, excluded from decision making, became collateral damage, forced to compensate for poor design with unpaid labour and bear the ire of an angry hoard of students who felt swindled.
The stakeholders were in place: leadership, faculty, students, industry. Unfortunately, only the project leader’s voice propelled the plan. When faculty raised concerns about flubbed or missing course content, it was dismissed. When students complained about accelerated, overly advanced content, they were told no one else was struggling. When colleagues from the existing program offered mentorship, they were ignored. The system was never built to listen.
The Missing Project Plan
To undertake such a large project and minimise risk, planning and project management is key. Watt (2014) noted that it’s the vital preservation of balancing the forces of cost, time, and scope—the “triple constraint”—that leads to the most successful projects. In this case, time dominated. The persistent tension between starved time and miscalculated scope resulted in permeating ramifications that diminished quality, strained resources, and exacerbated risk.
If I could redesign this process, I would allow industry input to recommend and influence but not to dictate. I would collaborate with faculty as expert co-designers. Tools like Gantt charts could allow stakeholders to visualise scope, dependencies, and timelines. I would balance time with other forces like quality, scope, and resources. I would also pilot a smaller scale trial of the program to allow for more nimble iteration while mitigating risk.
Why Good Intentions Paved the Wrong Path
The biggest barriers weren’t logistical but cultural:
- Leadership assumed goodwill could replace resources. It couldn’t. Faculty burnout was swift.
- When students and faculty raised alarms, leadership heard complaints, not data. Marsh et al. (2006) emphasised that data-driven decision-making is critical in education. In this case, qualitative feedback from frontline stakeholders was ignored, which compounded risks.
- Industry input matters, but it should be advisory rather than dictatorial. Letting it override academic expertise is like letting a client design the architect’s blueprint. Collaboration, not capitulation, builds sustainable solutions.
- Not-Invented-Here Syndrome (Kathoefer & Leker, 2010) led to bias and division. Rejecting the existing program’s input was a costly misstep. Systems change is about building on history, not discarding it. By dismissing institutional history, leadership wasted decades of valuable lessons and alienated allies who could have been eager co-creators.
From Risks to Turmoil
Risks became dangers, and dangers became costs.
Risk is always present in projects, and balancing different risk types—people, relationships, schedule, scope, financial, and business (Louder Than Ten, n.d.)—is critical. Here, prioritising urgency over process amplified all six:
- People: Faculty burnout and student disenchantment.
- Relationships: Eroded trust between staff and leadership and between students and faculty.
- Schedule: Continual scrambling due to poor planning and under resourcing.
- Scope: Flawed curriculum design.
- Financial: Costs ballooned from reactive fixes (e.g., repairing/replacing flawed content).
- Business: Reputational damage threatened future enrollment and school’s standing.
Risks became dangers, and dangers became costs. This aligns with Watt’s (2014) caution that failure to assess risks upfront assures they will metastasize.
Lessons for The Future
This experience reshaped how I view project management. Here’s what I’ll do differently:
- Start with feasibility, not ambition. I’ll examine early if needed resources are available. I will proceed once a plan involving the right people is in place.
- Design with data, not assumptions. Marsh et al. (2006) showed that data-driven decisions reduce risks. I’ll treat feedback from students and faculty as valuable qualitative data, not complaining.
- Iterate and collaborate. Agile approaches use regular check-ins to identify what is working, what needs help, and what is in the way. Smaller pilots or prototypes could have revealed flaws early.
- Measure student stress levels and faculty workload through each semester.
- Honour institutional knowledge. Historical data and insights are foundational. I will let eager allies share their experience.
This program’s launch taught me that systems change isn’t about speed, it’s about direction. Next time, I’ll advocate for prioritising time: to listen, to co-create, and to iterate. An African proverb provides a good reminder: “If you want to go fast, go alone; if you want to go far, go together.”
Resources
Kathoefer, D. G., & Leker, J. (2010). Knowledge transfer in academia: An exploratory study on the Not-Invented-Here Syndrome. The Journal of Technology Transfer, 37, 658–675.
Louder Than Ten. (n.d.). Project risk analysis. Louder Than Ten. Retrieved February 26, 2025, from https://louderthanten.com/resources/risk-management/project-risk-analysis
Marsh, J., Pane, J., & Hamilton, L. (2006). Making Sense of Data-Driven Decision Making in Education: Evidence from Recent RAND Research. RAND Corporation.
Watt, A. (2014). Project Management. Victoria, BC: BCcampus.
Attributions
Lema, D. (2024). A turtle is walking down a set of stairs [Photograph]. Pexels. https://www.pexels.com/photo/a-turtle-is-walking-down-a-set-of-stairs-27500672/