RecruitingYB7YL

Design & Run a Coding Workshop for Teens

Design and deliver a beginner coding workshop for local teenagers.

Design & Run a Coding Workshop for TeensPhoto: Pavel Danilyuk / PexelsYouth Workshops · 1 Month
CategoryYouth Workshops
DifficultyBeginner
Time1 Month
Commitment4 hrs/week
TypeTeam
LocationOn-site · Birmingham
Team4 people
ScheduleFlexible, async-first

The Brief

What you'd be taking on

A 2-hour beginner coding workshop, designed and delivered to a group of local teens. The community centre wants to offer a tech taster session but has no one to run it. Local teens have limited access to hands-on tech learning opportunities.

The Programme

100 tasks across six phases

Every phase below carries its own tasks and the line that decides when each one is done. Nothing is left to interpretation.

Discovery

Get inside the problem before touching the work: scope, constraints, and who you're building for.

What you need coming in

  • Beginner-friendly
  • Comfortable engaging with the public
  • Willingness to commit 3–5 hours per week
Discovery tasks10
  1. 001Read the full project brief and note what the centre expects from the taster session.Done whenSummary of expectations written in your own words.
  2. 002Meet the community centre contact and confirm the workshop date, room and 2-hour slot.Done whenDate, room and time confirmed in writing.
  3. 003Ask the centre how many teens they expect and confirm the age range of the group.Done whenExpected numbers and age range recorded.
  4. 004List the equipment the centre can provide: laptops, Wi-Fi, projector and power sockets.Done whenEquipment list confirmed with the centre.
  5. 005Obtain the centre's safeguarding policy and note who the designated safeguarding lead is.Done whenPolicy copy saved and lead's name recorded.
  6. 006Clarify whether team members need DBS checks or must be supervised by centre staff.Done whenCentre's requirement confirmed in writing.
  7. 007Confirm the budget available for printing, snacks and any session materials.Done whenBudget figure confirmed in writing.
  8. 008Agree who on the team takes each role: lead, coordinator, content writer and photographer.Done whenRole assignments recorded and agreed by all four.
  9. 009Set up the shared Notion workspace and Slack channel for the project.Done whenBoth spaces created with all four members added.
  10. 010Write a one-page summary of everything learned so far and share it with the team.Done whenSummary posted and acknowledged by the team.

Research

Gather the evidence the decisions will rest on.

The objectives to work against

  1. Design a 2-hour workshop plan
  2. Prepare beginner-friendly materials
  3. Deliver the session on-site
  4. Gather participant feedback
Research tasks15
  1. 011List coding topics doable by beginners in two hours: Scratch, HTML/CSS or Python Turtle.Done whenShortlist of at least three topics written up.
  2. 012Review free beginner curricula from Code Club, Raspberry Pi Foundation and Hour of Code.Done whenNotes on three curricula saved to Notion.
  3. 013Find two or three teen coding workshops run elsewhere and note what worked for them.Done whenExamples logged with takeaways.
  4. 014Research how long teens typically stay focused and how often activities should change.Done whenRecommended activity lengths noted.
  5. 015Research icebreakers that work with teenagers who don't know each other.Done whenThree icebreaker options written up.
  6. 016Read the NSPCC guidance on running activities for under-18s and note what applies here.Done whenApplicable points listed in Notion.
  7. 017Research what a parental consent form for an under-18 workshop must include.Done whenRequired form contents listed.
  8. 018Research photography consent rules for under-18s, including how opt-outs are handled.Done whenPhoto consent requirements documented.
  9. 019Test whether each shortlisted coding tool runs in a browser without accounts or installs.Done whenTest results recorded per tool.
  10. 020Research how to support participants who have never used a computer for coding before.Done whenSupport strategies noted.
  11. 021List simple accessibility adjustments for materials, like fonts and step-by-step pacing.Done whenAdjustment checklist drafted.
  12. 022Ask the centre how they have promoted youth events before and what drew teens in.Done whenPromotion notes recorded.
  13. 023Research quick feedback methods that suit teens, such as emoji scales or exit tickets.Done whenTwo feedback formats shortlisted.
  14. 024Write a one-page research summary of topic options, safeguarding and engagement tips.Done whenSummary written and saved.
  15. 025Share the research summary with the community centre contact and note their reactions.Done whenCentre feedback logged.

Planning

Split the work, pick the tools, agree the dates.

Who does what · 4 roles

Project Lead

Coordinates the team and the community partner relationship.

Project management, communication · 4 hrs/week

Community Coordinator

Organises engagement with participants or volunteers.

Communication, organisation · 4 hrs/week

Content Writer

Documents the project for reporting and sharing.

Writing · 3 hrs/week

Photographer

Captures the project in progress for the record.

Photography · 2 hrs/week

Tools the team runs on

NotionSlackGoogle WorkspaceCanva
Planning tasks15
  1. 026Choose the coding topic and tool based on the research and the centre's feedback.Done whenTopic and tool decision recorded with reasons.
  2. 027Define what each participant will have built by the end of the two hours.Done whenEnd-of-session outcome written in one sentence.
  3. 028Break the two hours into a minute-by-minute outline with regular activity switches.Done whenTimed outline drafted in Notion.
  4. 029Pick the icebreaker and plan how the room will be arranged for it.Done whenIcebreaker and room layout chosen.
  5. 030Assign on-the-day duties: who teaches, who floats to help, who greets, who photographs.Done whenDuty list agreed by all four members.
  6. 031Outline the parental consent form, including emergency contact and a photo opt-out.Done whenForm contents outlined.
  7. 032Write a risk assessment for the session and share it with the centre.Done whenRisk assessment approved by the centre.
  8. 033Agree how teens will sign up and how many places to cap the session at.Done whenSign-up route and cap agreed with the centre.
  9. 034Plan the promotion push: poster locations, the centre's channels and timing.Done whenPromotion plan written with dates.
  10. 035List every material to produce: slides, handouts, starter files, forms and signage.Done whenMaterials checklist created.
  11. 036Plan a backup version of the coding activity that works without Wi-Fi.Done whenBackup activity outlined.
  12. 037Choose the feedback method and fix when in the session it happens.Done whenFeedback method and timing added to the outline.
  13. 038Plan how the materials will be packaged so the centre can rerun the session without you.Done whenHandover pack structure agreed.
  14. 039Book a full team rehearsal date ahead of the workshop day.Done whenRehearsal date in everyone's calendar.
  15. 040Walk the centre contact through the full plan and log any changes they request.Done whenPlan sign-off recorded.

Execution

The build. Most of the hours on this project live here.

Skills you'll practise here

CommunicationCommunity EngagementEvent PlanningEmpathyOrganisationTeamwork
Execution tasks40
  1. 041Write the full workshop lesson plan from the timed outline, with a goal for each section.Done whenLesson plan document completed.
  2. 042Build the example project yourself end-to-end in the chosen tool.Done whenWorking example project saved.
  3. 043Break the example project into small numbered steps a total beginner can follow.Done whenStep list drafted.
  4. 044Design the session slides in Canva following the numbered step list.Done whenSlide deck drafted.
  5. 045Write the step-by-step participant handout matching the slides.Done whenHandout drafted.
  6. 046Prepare starter files so participants skip blank-screen setup and start building fast.Done whenStarter files created and tested.
  7. 047Write the parental consent form, including the photography opt-out tick box.Done whenConsent form drafted.
  8. 048Send the consent form to the centre for safeguarding approval.Done whenCentre approval received in writing.
  9. 049Design the promotional poster in Canva with date, time, age range and sign-up details.Done whenPoster designed.
  10. 050Get the centre's approval on the poster before anything is printed.Done whenPoster approved.
  11. 051Print the posters and put them up at the agreed locations.Done whenPosters displayed.
  12. 052Write short promo text for the centre's social channels and newsletter.Done whenPromo text sent to the centre.
  13. 053Open sign-ups and set up a tracker of names against the agreed cap.Done whenSign-up tracker live.
  14. 054Distribute consent forms to parents of signed-up teens via the centre.Done whenForms distributed via the centre.
  15. 055Chase outstanding consent forms and log returns against the sign-up list.Done whenTracker shows form status for every participant.
  16. 056Write a helper crib sheet covering common errors in the activity and their fixes.Done whenCrib sheet completed.
  17. 057Prepare an extension task for teens who finish the main build early.Done whenExtension task added to the materials.
  18. 058Produce the materials for the no-Wi-Fi backup activity.Done whenBackup materials ready to use.
  19. 059Test the full coding activity on one of the centre's actual laptops.Done whenActivity confirmed working on centre hardware.
  20. 060Fix any issues found in the laptop test and run the activity again.Done whenRetest passed.
  21. 061Create the feedback forms in the chosen format, ready for the end of the session.Done whenFeedback forms finalised.
  22. 062Run the full rehearsal with the team, teaching the session in real time.Done whenRehearsal completed and timed.
  23. 063Log every timing overrun and confusing step spotted during the rehearsal.Done whenRehearsal notes recorded.
  24. 064Revise the slides, handout and lesson plan based on the rehearsal notes.Done whenRevised versions saved.
  25. 065Print the handouts, sign-in sheet, feedback forms and spare consent forms.Done whenAll printed materials ready.
  26. 066Confirm final participant numbers with the centre and send a reminder to attendees.Done whenFinal headcount confirmed and reminder sent.
  27. 067Pack the workshop kit: prints, name stickers, pens, spare forms and the crib sheets.Done whenKit packed against the materials checklist.
  28. 068Confirm day-of logistics: room access time and which centre staff will be present.Done whenAccess time and staffing confirmed in writing.
  29. 069Arrive early on the day and set up tables, chairs, projector and signage.Done whenRoom set up before doors open.
  30. 070Switch on every laptop and load the starter files before participants arrive.Done whenEvery seat has a working, loaded laptop.
  31. 071Greet and sign in each participant, checking a completed consent form for every teen.Done whenSign-in sheet complete with consent verified for all.
  32. 072Run the icebreaker and introduce the team and the plan for the two hours.Done whenIcebreaker delivered to the whole group.
  33. 073Teach the guided build, following the lesson plan while helpers float between tables.Done whenGuided build section delivered.
  34. 074Run the mid-session break with snacks and reset the group for the second half.Done whenBreak held roughly on schedule.
  35. 075Support the free-build section, handing the extension task to anyone who finishes early.Done whenEvery participant working on their own build.
  36. 076Photograph the session, keeping opted-out participants out of every shot.Done whenPhotos taken with opt-out list respected.
  37. 077Hand out the feedback forms in the final minutes and collect every response.Done whenCompleted forms collected from participants.
  38. 078Close the session with a show-and-tell and share free ways for teens to keep coding.Done whenTake-home next-steps shared with the group.
  39. 079Pack down the room and return the centre's equipment as agreed.Done whenRoom returned to its original state.
  40. 080Hold a same-day team debrief and write down what went well and what didn't.Done whenDebrief notes saved while fresh.

Quality Assurance

Check the work against the standard before the client ever sees it.

How the founder judges done

  • Workshop delivered as planned
  • Positive participant feedback
  • Materials reusable for future sessions
QA tasks10
  1. 081Type up every feedback response into a single tally in Notion.Done whenAll responses transcribed.
  2. 082Write the feedback summary: ratings, standout quotes and what to change next time.Done whenFeedback summary drafted.
  3. 083Check every photo against the opt-out list and delete any that breach consent.Done whenPhoto set complies with consent records.
  4. 084Update the lesson plan to reflect what actually happened on the day, timings included.Done whenLesson plan updated to the as-run version.
  5. 085Proofread the handout and slides and fix every error spotted during the session.Done whenCorrected final versions saved.
  6. 086Verify the starter files and example project open correctly from a fresh download.Done whenFresh-download test passed.
  7. 087Assemble the reusable pack: plan, slides, handout, starter files, crib sheet, forms.Done whenPack folder complete and labelled.
  8. 088Ask a teammate to set the pack up from its instructions alone, with fresh eyes.Done whenPeer review completed with notes.
  9. 089Fix every issue raised in the peer review of the pack.Done whenAll review notes resolved.
  10. 090Check the finished work against the brief: session delivered, feedback in, pack reusable.Done whenChecklist confirms every objective met.

Delivery & Reflection

Hand it over properly, then write down what the team learned.

What the client walks away with

A delivered workshop with materials the centre can reuse for future sessions.

Handed over

  • Workshop lesson plan
  • Session materials
  • Feedback summary
Delivery tasks10
  1. 091Share the feedback summary with the community centre contact.Done whenSummary sent and acknowledged.
  2. 092Deliver the consent-cleared photo set to the centre for their records and promotion.Done whenPhotos handed over.
  3. 093Hand over the reusable session pack and walk the centre through running it themselves.Done whenWalkthrough completed.
  4. 094Agree with the centre where the pack will live and who keeps it up to date.Done whenStorage location and owner confirmed.
  5. 095Write the project story for the record, using the debrief notes and photos.Done whenWrite-up completed.
  6. 096Send a thank-you note to participants and parents via the centre, with next-step links.Done whenThank-you note sent via the centre.
  7. 097Ask the centre whether they want a repeat session and log their answer.Done whenCentre response logged.
  8. 098Return or securely dispose of the consent forms in line with the centre's data policy.Done whenForms handled per policy and confirmed.
  9. 099Hold the final team retrospective and record lessons for the next community project.Done whenRetro notes saved.
  10. 100Submit the completed project for credential review and close it out.Done whenProject marked complete.

FAQs

Common questions

Is this project paid?

No — RogueBoard projects are unpaid. What you earn is real experience, portfolio evidence, and a verified reference.

Can beginners join?

Depends on the role — check the Difficulty rating and each role's required skills above. Several roles on this project are beginner-friendly.

What if I miss a meeting?

Let your Project Lead know in advance where possible. One missed check-in won't remove you from the team, but consistent attendance is expected.

Can I leave early?

You can step back from a project, but try to hand off your work cleanly so the team and the credential process aren't disrupted.

Will I receive a reference?

Yes — completing your role to the agreed standard earns a verified RogueBoard credential and a reference you can point employers or clients to.

YB7YLDesign & Run a Coding Workshop for Teens
Apply to Join →