Logo

Hackathons: a fast, collaborative route to staff development

Traditional approaches to staff development can struggle to keep up with an industry undergoing rapid transformation. Here’s how a hackathon can help to turn uncertainty into practical, classroom-ready ideas
Susan Smith 's avatar
19 Nov 2026
copy
  • Top of page
  • Main text
  • More on this topic
A group of colleagues sitting around a table on their laptops
image credit: Organic Media/Getty Images.

Created in partnership with

Logo

You may also like

Eight tips for hosting an enterprise hackathon
4 minute read

Popular resources

Academic staff development is often imagined as a slow, reflective process: workshops, reading groups, pilots and incremental curriculum redesign. Yet the current pace of technological change makes that model increasingly unrealistic. Many academics simply do not have the time to explore emerging tools, rethink pedagogical approaches or redesign assessments.

Hackathons – short, intensive, collaborative design sprints – offer a surprisingly effective alternative to more traditional curriculum and learning design processes. Commonly associated with software engineering, they are gaining traction as incubators for infrastructure for staff development in other industries, including higher education. The artificial intelligence in analytical disciplines hackathon held at our university demonstrates how this format can support meaningful professional learning and experimentation under pressure.

Why hackathons work for time-poor academics

Hackathons are deliberately time bound. Rather than stretching development work across weeks or months, they compress it into a few focused hours.

Three features make hackathons particularly suited to academic development:

  • Minimal preparation, maximum engagement: Participants arrive with their disciplinary expertise, not pre-prepared materials. The structure does the heavy lifting.
  • Collective problem solving: Hackathons create temporary communities of practice that cut across departments and seniority levels.
  • Rapid prototyping: Early ideas are made tangible quickly, enabling rapid feedback and iterative refinement.

For academics juggling teaching, research and administrative responsibilities, this format fosters creativity, experimentation and collaboration, allowing staff to produce something tangible quickly.

Our event brought together educators, students and disciplinary experts from a range of analytical disciplines – statistics, economics, accounting, data science, maths, physics, engineering, and related fields – to explore how AI is transforming graduate labour markets and how institutions can equip students with the agility to navigate an increasingly uncertain future. Like many hackathons, it took place outside participants’ home departments and institutions, a feature that research has identified as important for freeing people from local constraints.

Participants self‑selected into groups, each facilitated by a member of the organising team and a student partner. Student partners came from different levels of study and disciplines and provided valuable insight into student perspectives to inform the ideation and development activity. This ensured that groups remained on topic and that outputs were recorded on the shared Padlet.

The structure was deliberately simple but disciplined.

  • Orientation and challenge framing: Groups identified the skills they wished to develop in their students.
  • Rapid ideation: Participants collaborated to develop teaching activities that would develop the selected skills.
  • Short pitches to other teams: These feedback loops helped to refine ideas.
  • Focused development sprint: Teams produced early-stage teaching artefacts leveraging AI tools.
  • Plenary sharing and discussion: Outputs were uploaded to a shared Padlet and discussed collectively.

Crucially, the event had no prizes, winners or competitive framing. The goal was collaborative learning, not performance.

Rapid prototyping as a learning mechanism

Rapid prototyping is well established in instructional design. In education development, this approach has an additional benefit: it forces tacit pedagogical assumptions into the open.

In this way, prototyping became both a creative process and an epistemic checking process. Educators were not only building resources; they were negotiating the boundaries of disciplinary knowledge under GenAI conditions.

Why hackathons avoid ‘innovation theatre’

A common criticism of hackathons is that they produce attractive prototypes that never get implemented. To reduce this risk, you can:

  • focus on a teaching challenge participants already face
  • engage a group of experienced facilitators
  • encourage outputs that can be adapted for classroom use across disciplines and institutions
  • foreground pedagogical legitimacy over novelty.

Tips for running effective hackathons

Hackathons are not a replacement for deeper curriculum work, but they can be effective catalysts. Here’s my advice:

  • Be clear about the focus and what is realistic in the time available.
  • Plan the timings of the day – strictly.
  • Use countdown timers to help create a sense of urgency.
  • Build in lightning presentations, elevator pitches and other opportunities for rapid feedback and iteration.
  • Try to have one facilitator per group.
  • Follow up output development post-hackathon.

Susan Smith is professor of accounting and deputy director (student experience) at UCL School of Management.

If you would like advice and insight from academics and university staff delivered direct to your inbox each week, sign up for the Campus newsletter.

You may also like

sticky sign up

Register for free

and unlock a host of features on the THE site