Design Challenge
Event playbook
A practical guide to organising collaborative learning around real green and digital STEAM challenges.
Bring students, educators, researchers and industry partners together. Prepare the event, guide teams through the design process and share their work with the Community of Practice.
Prepare
Challenge selection, participant recruitment and online learning.
Create
Explore, Analyse, Ideate, Prototype, Realise and Evaluate.
Share & sustain
Document solutions, gather feedback and continue the collaboration.
From the first invitation
to the final report.
The guidance and practical toolkit from the GLOBE-STEAMSS Design Challenge Event handbook.
Open a practical tool.
Plan your event
Set the date, define the challenge and allocate responsibilities.
Your event brief
Enter a student count to estimate the number of teams.
Participant targets
Aim for 20–30 students in teams of 4–5, with at least two disciplinary backgrounds where possible. Actively encourage female and underrepresented participation.
The event KPI minima are 12 students, 1 educator, 1 researcher and 4 industry professionals contributing business cases. Record actual attendance.
Agree roles and responsibilities
Preparation checklist
Team formation: the role-card method
Invite students to select a role card, then use the number on its back to form balanced teams. The pilot used Steve Jobs (Visionary), Albert Einstein (Analyst), Barack Obama (Leader / Communicator), and Oprah Winfrey (Connector / Empath).
Push the possibilities.
Bring bold ideas and challenge conventions.
Ask what sits underneath.
Question assumptions and look for patterns.
Build a shared direction.
Connect contributions and communicate clearly. Speak last to make space for others.
Keep people in the picture.
Listen actively and focus on needs and impact.
Invite learners to try, share or change roles. Choose reference figures that work in your local context.
Facilitate the event
Select a phase for instructions, materials, timing and expected outputs.
Explore
Timer pauses when you change phase.
Record the team’s work
Reserve 2–5 minutes after every activity for the team to record its insights, decisions and output. Photograph paper worksheets if you work offline.
Belgian pilot agenda · adaptable one-day example
Adapt this one-day timetable to your venue and participants. Activities can be extended into two days. At 15:00, teams record their videos while the jury deliberates in a separate room.
Online preparation and the pre-event session
Students complete the six online Design Thinking modules before the event. Assign them 2–3 weeks beforehand. Allow about 30 / 30 / 20 / 30 / 30 / 60 minutes for the six steps.
Hold a 60–90 minute pre-event session: welcome, project overview, challenge teasers, CoP registration, module introduction, practical information and questions.
Team design canvas
Choose a note-taker to complete the canvas as your team works. You can also use it to record the results of paper-based activities.
Avoid entering sensitive personal data. A backup contains everything typed into this playbook. Share exported files only with the intended recipients.
Jury assessment
and feedback
Use the seven-criterion rubric to guide scoring and the jury discussion.
Choose a score for all seven criteria to calculate the total.
Evaluation resource: D-EMIND training pack.
Five useful lenses
Jury briefing and deliberation
Send the written briefing 5–7 days before the event. Invite jurors 30 minutes before pitches for welcome, networking and a 15-minute verbal briefing. Give each team 5 minutes to pitch and 3 minutes for questions.
- Collect every jury form and calculate average team scores separately.
- Discuss strong scores and substantial disagreements.
- Prepare one strength and one improvement suggestion for each team.
- Agree the outcome collectively; optional awards can recognise sustainability, creativity, collaboration and process documentation.
Export one sheet per team before clearing the review. Combine the jury’s scores during deliberation.
Evidence and follow-up
Track each output and record where you have saved it. Upload the files separately to the agreed project folders.
Peer review, jury feedback
and solution videos
Capture written peer review during Prototype, keep completed jury forms, and share at least the three best solution videos on the CoP within one week.
Open the Community of Practice ↗Use your project account to access the platform.
The deadlines below follow Appendix F. Confirm the upload schedule with your lead partner before the event.
File naming and shared-folder structure
Use [Country]_DCE_[Year]_[Type]_[Description], for example BE_DCE_2026_Pitch_TeamJobs.pdf. Store files in the partner folder, using the shared structure below.
- Registration & Attendance
- Challenge & Agenda
- Evaluation & Jury
- Solutions & Videos
- Certificates
- Stakeholder Feedback
- Dissemination
- Reporting & KPIs
Use the current templates in 00_Templates & Guidelines and save completed files in your partner folder.
Post-event report
Complete the six reflection questions and export your report draft. Submit the completed KPI Tracker alongside it.
Communication templates
Prepare invitations and follow-up messages using your event details. The Belgian pilot examples are available below.
Replace the bracketed details and review the draft before sending.
Visual stakeholder contact roadmap · Belgian pilot
Historical preparation calendar from the supplied handbook. Adapt dates to your own event.
Original communication examples
Examples from the Belgian pilot, May 2026. Update dates, names, links and event details before use. T24b contains a partial message.
Read the handbook
Guidance, templates and experience from the Belgian pilot.
Download a backup to keep your notes, checklists and scores. You can restore that file here on another device.