Ideation workshop: Bridging theory and practice

The idea for an ideation workshop emerged from observing a consistent pattern: students had all the theoretical knowledge and research inputs but couldn’t bridge the gap to actual design execution.

University of Groningen connection and workshop context — The blue highlighted sections are the steps the workshop focuses on.

We drew inspiration from Google Ventures’ well-known Sprint methodology, detailed in Jake Knapp’s book “Sprint”: ‘How to Solve Big Problems and Test New Ideas in Just Five Days.’

However, the traditional Sprint framework assumes resources most students don’t have: five full days, dedicated teams, complete project ownership, and substantial budgets.

The fundamental problem

Students consistently struggled with the same challenge: how do you move from information and constraints to actual design?

Most existing design frameworks assume unlimited time and resources.

The gap from research to prototype — Moving from input to a first prototype.

Workshop constraints in an academic context — In the 'real world' constraints are always very much present.

The mini design sprint

We adapted the Sprint book’s methodology to fit academic realities. Where the original process takes five days (map, sketch, decide, prototype, test), our workshop compressed the critical first three phases (map, sketch, decide) into 2-3 hours.

Jake Knapp's Sprint methodology reference — Reference to the 'Sprint' method from Jake Knapp.

Full sprint vs compressed workshop comparison — Differences between the design sprint and the adjusted process for the workshop.

Design sprint phases adapted for the workshop — The blue highlighted sections are the steps the workshop focuses on.

The systematic process

Working with 10-40 students in small groups, each cycle runs in approximately 30-minute blocks:

Grouping (10 min) — Students organise requirements into roughly five thematic groups using sticky notes in FigJam.

FigJam sticky note grouping exercise — Each horizontal row represents a group (e.g. constraints with similarities).

Sorting (10 min) — Dot voting with 10 votes per member determines priority groups.

Dot voting for prioritisation — Dot Voting could be done with the 'vote' feature in FigJam.

Filtering (5 min) — Teams draw a cutoff line to establish focus.

Filtering exercise with prioritisation line — The easiest step of the workshop, though not irrelevant.

Sketching (8 min) — Crazy 8s: an A3 sheet divided into 8 blocks, one sketch per block under timed pressure.

Crazy 8 sketching method — Sketching under pressure can force ideation.

Presentation (5 min) — Members present sketches; photos get uploaded to FigJam.

Sketch presentation phase — As a neutral observer, this was the most fun step for me.

Evaluation (5 min) — Dot voting identifies the strongest concepts.

Concept evaluation and voting — Applying my favorite 'dot voting' once more.

Evolution through iteration

Early versions of the workshop had significant friction points. Technical setup became the biggest barrier.

The team optimized by printing step-by-step reference sheets, allowing independent work while facilitating across groups. Digital tools handled organization and voting, while analog sketching removed technical barriers during the creative phase.

Pencil and paper sketching materials — Possibly the best tool for the job.

Impact and adoption

Results were immediate and visible. Professors observed sparked creativity; previously stuck students suddenly generated tangible ideas within the session.

The workshop became embedded in regular curriculum, with professors requesting additional implementations across multiple courses. This successfully bridged academic theory with business practice.

Post-workshop follow-up recommendations — Advice on follow-up actions after the workshop.

Strategic outcomes

Approximately five students converted to meaningful connections over two years. A distributed design principles quartet game with contact details and talent newsletter QR code created lasting brand connections.

Talent pipeline tracking in Notion and ActiveCampaign — The talent pool was (temporarily) a Notion webpage with an ActiveCampaign form.

Lessons learned

Professional design processes translate well to academic settings when properly adapted. The key insight: don’t dilute the professional methodology, adapt it. Keep the rigor and structure that make these processes effective in business, but compress timelines and reduce resource requirements.

Time pressure became a feature enabling creative action rather than a limitation.

There’s something special about enthusing people for something you’re passionate about.