The University of Chicago used a two-day hackathon to help staff with no software-development experience put AI coding tools to practical use. The event produced more than a dozen working prototypes, and some are still in use: a useful test of whether AI adoption can get beyond the training session and into everyday work.
Watch Desk analysis
What happened
UChicago held the hackathon in March 2026 after leaders saw that AI tools were available on campus but adoption was lagging. The event drew 81 staff members, organised into 17 teams, and focused on problems participants wanted to solve rather than coding for its own sake. EdTech Magazine reports that teams built their prototypes with Claude Code.
The projects included a tool that drafts job descriptions using the university’s approved templates and language, a synthetic-data generator for developers, and a Chrome extension that swaps selected words on webpages into another language. The HR prototype became the basis of a tool the department now uses, according to the report. UChicago also started a monthly AI user group where staff can demonstrate what they have made.
Why it matters
The practical lesson is that adoption may need more than access to software and another round of training. UChicago put staff members’ own workplace problems at the centre of the event, gave teams guidance and mentoring, and set clear data rules. Participants had no access to production systems or test environments; structured data had to be sanitised, with student, health and personal information excluded.
That makes this more than an upbeat tale of prototypes. It is a concrete example of how an organisation tried to make experimentation useful while limiting what participants could put into AI tools. The results are specific, but they do not prove that a hackathon will work everywhere: UChicago’s vendor agreements, security arrangements and policies formed part of the setup.
Our read
The strongest idea here is to begin with people’s actual work, not with a tool looking for a problem. A prototype that becomes an HR tool is a more convincing adoption signal than a roomful of enthusiastic prompts. Just as importantly, the guardrails were part of the exercise, not a footnote discovered after someone pasted in a spreadsheet.
For organisations considering a similar event, the useful takeaway is to pair hands-on experimentation with mentoring, clear data boundaries and a process for turning promising prototypes into supported tools. UChicago plans another event and has created resources for other institutions; the next test is whether those prototypes keep earning their place after the hackathon buzz fades.
What to watch
- Whether UChicago’s HR tool and other prototypes remain in regular use.
- What changes the university makes for its next event, including smaller teams and more time to demonstrate projects.
- Whether other institutions can reproduce the approach under their own security policies and vendor agreements.
Discussion spark: Should employers encourage staff to build AI prototypes around real workplace problems, or is that too risky without formal IT development and approval?
Sources and evidence
- Source update (19 November 2026, 16:54 UTC)
Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.