Video summary

Kultor 7 oct Project Showcase

Main summary

Key takeaways

Educational

Main ideas / concepts / lessons

  • Purpose of “Project Showcase” (Weeks/Meetings 7 & 8) Tutors use a PPT presentation to preview what students will build in future lessons. This is designed to support:

    • Retention: keep learners from losing interest after early excitement fades.
    • Student motivation: students become excited because they can see an interesting outcome, instead of just studying abstractly.
    • Idea/imagination building: students learn what kinds of projects are possible and can later choose/develop ideas.
    • Parent awareness: parents receive a PDF/image/project plan so they understand what their child will make—improving the chance the parent will buy/continue packages.

  • Why it matters (context about package buyers)

    • Many students (especially those who buy small packages, like only 8–16 lessons) do not finish the full course.
    • For these learners, tutors need a way to convert “try it first” customers into continued customers.
    • When retention is strong, tutors may receive a bonus (roughly 10–15% mentioned in the talk).

  • Core strategy: information instead of selling

    • Tutors are not expected to do marketing/sales.
    • Instead, tutors deliver education-focused preview content: “Here’s what you’ll build later.”

Methodology / step-by-step instructions (Project Showcase implementation)

A) Timing & structure (Meetings 7 and 8)

  • Meetings 7 & 8 are where the Project Showcase happens.
  • Target delivery time is short:
    • Around ~10 minutes total per meeting (with flexibility noted up to about 15 minutes overtime max).
  • If time is insufficient:
    • Some parts of lesson 7 can be moved to homework so the main class remains on schedule.

B) What to do in Meeting 7 (Idea preview)

  1. Open with explanation
    • Explain what a project is (some children may not fully understand the concept).
  2. Display 2–3 (or more) example projects
    • Show examples that match the course topic/technology (e.g., visual programming examples).
    • Examples mentioned include:
      • A visual programming showcase
      • A ping-pong game
      • An underwater diver
      • “Freestyle” additions (encouraged) as long as they remain relevant to the material/curriculum.
  3. Engage creativity by asking students to choose
    • Ask: “What project do you want to make?”
  4. Let students know they will write/prepare their idea
    • The activity connects to next meeting (Week 8), where they will share their chosen idea.

C) What to do in Meeting 8 (Student idea submission + tutor writes)

  1. At the beginning of Week 8 / Meeting 8
    • Remind students to convey their ideas.
  2. Students present their selected idea
    • Example format in the subtitle:
      • “I want to make a space rocket…”
      • “I want to make a zoo project…”
      • “I want to make a flying dragon project…”
  3. Tutor writes the plan into the Project Showcase
    • The tutor fills in the student’s idea in the PPT-based template (described as not editable after opening a link/template).
  4. Provide the resulting showcase to parents
    • Tutor-generated content becomes a PDF/image for parents to view.
    • Parents learn what their child will build next—supporting conversion/continuation.

D) Technical/operational implementation notes (as described)

  • There is an operational structure/template:
    • A calendar indicating dates when students work, and when there is “game day,” etc. (mentioned generally).
  • The Project Showcase content is prepared through a PPT template:
    • The template includes a link/structure where editing is controlled (the speaker says it “can’t be edited” in a certain view).
  • Students are given about 1 week between Meetings 7 and 8 to think about their future project idea.

Q&A / troubleshooting guidance (common issues + what tutors should do)

1) Student project idea is too complex/difficult

  • Do not immediately reject or break the idea.
  • Strategy:
    • Encourage them to make a simple version first, then “make it cooler” later after they learn more.
    • Emphasize hope/continuation rather than stopping the idea abruptly.
  • If the idea is too far from the course scope:
    • Offer a choice from the showcased examples.
    • Develop it together by adding only what fits the curriculum.

2) Some courses may not require a “real project” submission (e.g., Scratch Junior / digital literacy / CK)

  • Even if the course doesn’t focus on student project creation in the same way:
    • The key is still to deliver project examples so students can understand what they can build later.
    • The purpose is conceptual clarity and expectation-setting, especially in early meetings.

3) Time is insufficient for the activity

  • If it can’t fit within class time:
    • Use homework for part(s) of lesson 7.
  • Overtime rule
    • Keep overtime to 10–15 minutes max (and overtime is generally not allowed).

4) Managing low-credit vs high-credit students to protect retention

  • The talk stresses different student “credit” groups:
    • Wrong handling for low-credit students can reduce retention.
    • Proper handling can keep interest high.
  • The tutor’s “goal”:
    • Keep children interested and enthusiastic so they continue (and so parents consider upgrading/continuing).
  • Bonus framing:
    • Strong retention can lead to fast tutor bonus (~10–15% mentioned).

Tips & tricks (behavioral / teaching approach)

  • Create the right “vibe/atmosphere” at the start
    • Invite students to communicate and keep engagement high early.
    • If students are sluggish, focus can fade quickly—use quick engagement checks.
  • Avoid shutting down ideas too harshly
    • Example: don’t immediately say something like “that’s impossible” (e.g., jumping from topic scope to “GTA/Roblox”).
    • Instead encourage a simpler version that can be implemented with the current tools.
  • Use “word of affirmation”
    • Praise students for courage to share ideas—even if the idea is imperfect or “strange.”
  • Show the projects clearly
    • If you don’t show the examples clearly, students become confused about what they should do.
    • This is especially important for students who struggle to imagine outcomes (digital literacy context).
  • Can add extra showcased projects
    • Yes, add more if they remain aligned with the course material.

Closing outcome / expected benefits

  • Reduce boredom in the keetu/ke-del sessions (as described).
  • Rebuild enthusiasm so that:
    • Students continue learning even after initial package credits run out.
    • Parents are more informed and more likely to continue buying.
  • Tutors improve retention metrics and can earn bonuses.

Speakers / sources featured (as named in subtitles)

  • Galang (main speaker; discusses retention, purpose, and implementation details)
  • Kevin (mentioned as the operational-side detail provider; also referenced for technical/video parts)
  • Kak Rida (asks a question; also appears in Q&A)
  • Mas Galang (same person referred to more than once; assumed to be Galang)
  • Mas Kev (mentioned in Q&A; likely Kevin)
  • Albert (referenced by name in a question during Q&A)
  • Rida / R also mentioned (appears to reference the same “Kak Rida” / a person referred to as “R”)
  • Unspecified “Operational side” team member(s)” (not individually named beyond Kevin)

Original video