Supporting Participants

How to help participants succeed during your KC7 event

The most common worry hosts have: "What if participants get stuck and ask me questions I can't answer?" Here's the secret: you're not supposed to have all the answers. KC7 teaches the cybersecurity - you're there to encourage, guide, and keep energy positive.

What Supporting Participants Actually Means

Supporting participants during a KC7 event isn't about knowing the answers or being a cybersecurity expert. It's about creating an environment where people feel safe to struggle, excited to discover, and confident enough to keep trying when things get hard.

You'll spend most of your time circulating, asking "How's it going?", celebrating small wins, and redirecting stuck participants to the resources built into the game. Think of yourself more as a coach during a game than a teacher during a lecture - you're there for encouragement and strategic guidance, not to explain every play.

The beautiful part: KC7 has built-in hints, progressive tutorials, and clear explanations built into every challenge. When someone asks "How do I filter this data?" you don't need to teach them query syntax - the game already did that. You just need to ask "Have you tried the hint button?" or "What did the earlier tutorial show you?"

You'll Be Learning Alongside Participants

Here's something that makes supporting participants easier than you might think: you'll be learning too. Throughout your event, you'll hear the same questions multiple times - "How do I search for this?" or "What does this field mean?" or "I can't find the answer to question 3."

The first time someone asks, you might fumble a bit: "Um, try clicking the hint button? Or maybe look at the tutorial again?" The third time someone asks that same question, you'll have refined your response: "Ah yes! Go back to the example in the intro section - it shows you exactly the format you need." By the fifth time, you're practically an expert on that particular sticking point.

This is actually one of the hidden benefits of hosting: you absorb the material through repetition without having to study it beforehand. By the end of your event, you'll have helped ten people understand data filtering, answered the same clarifying question about timestamps a dozen times, and developed your own explanations for concepts you'd never seen before the event started.

You're not expected to know everything at the beginning. You're learning the game alongside your participants, just a few steps ahead because you're seeing everyone's questions and watching how the game teaches each concept.

Why This Role Matters (Even Though You're Not Teaching)

Your presence and energy transform what could be a frustrating solo experience into an engaging, supportive learning event. When someone gets stuck for 10 minutes and starts feeling discouraged, you're the person who says "Getting stuck is part of being a security analyst - you're building real skills right now." That encouragement matters more than technical expertise.

You're also reading the room, managing energy levels, and ensuring everyone feels included regardless of their speed or skill level. You'll notice when someone needs a confidence boost, when the whole room needs a break, and when to celebrate discoveries to build momentum. These facilitation skills matter more than cybersecurity knowledge.

The Emotional Journey You'll Support

Participants typically experience a rollercoaster during KC7 events, and understanding this helps you know when to intervene:

Early excitement (first 15 minutes): "This looks cool!" They're engaged, curious, and optimistic. Your job: channel that energy, set positive expectations, and get everyone successfully started.

First frustration (20-30 minutes in): "Wait, this is actually hard." They hit their first genuinely challenging question. Your job: normalize the struggle, remind them hints exist, and celebrate the fact that they're learning.

Flow state (30-60 minutes): Many participants hit a groove where they're absorbed in investigation. Your job: don't interrupt unnecessarily, just circulate quietly and be available.

Second wind or fatigue (60+ minutes): Energy either surges as they make breakthroughs or sags from mental effort. Your job: read which is happening and either celebrate momentum or provide encouragement.

Understanding this arc helps you anticipate needs and intervene at the right moments.

---

Your role as a KC7 host is to create a positive, encouraging environment where participants feel comfortable learning and exploring. You don't need to be a cybersecurity expert - KC7 handles all the technical instruction. Your job is to facilitate, encourage, and guide.

Your Role as Host

What You ARE Responsible For

• Creating a positive learning environment where participants feel safe to make mistakes

• Offering encouragement when someone gets stuck or frustrated

• Monitoring energy levels and overall group engagement

• Pointing participants to built-in resources like hints and challenge descriptions

• Celebrating discoveries and breakthrough moments

• Managing time and keeping the event flowing smoothly

What You're NOT Responsible For

• Teaching cybersecurity concepts - the game does this automatically

• Solving challenges for participants - learning happens through discovery

• Being an expert - you're a facilitator, not an instructor

• Ensuring everyone finishes - the journey is more valuable than completion

• Answering every technical question - it's okay to say "let's see what the game teaches us"

Remember: KC7 is designed to be self-guided. The game provides all the instruction needed. Your encouragement and positive energy are what make the experience memorable!

During the Investigation

Circulating and Checking In

For in-person events:

• Walk around the room every 10-15 minutes

• Watch for body language signals (frustration, excitement, confusion)

• Ask open questions: "How's it going?" or "What are you discovering?"

• Don't hover - give participants space to think

For virtual events:

• Monitor chat for questions or frustration

• Watch for participants who haven't spoken or asked questions

• Use breakout rooms for small group check-ins if needed

• Send periodic encouragement in chat

Energy Check-Ins

30-45 minutes in:

"How's everyone doing? I'm seeing great progress on the scoreboard! Remember, there are built-in hints if you get stuck, and you're welcome to discuss approaches with each other."

60 minutes in:

"We're about halfway through! If you're feeling stuck, that's completely normal - these challenges are designed to make you think. Use those hint buttons and don't hesitate to ask questions."

Final 30 minutes:

"We have about 30 minutes left. If you haven't finished, that's completely normal! Focus on the challenges you find most interesting rather than trying to complete everything."

Energy Tip: If you notice the whole room getting quiet or tense, it might be time for a quick group encouragement break or reminder about collaboration.

Handling Common Situations

"I'm completely stuck!"

Good responses:

• "Have you tried clicking the hint button for this challenge?"

• "What approach have you tried so far?"

• "Sometimes taking a fresh look at the evidence helps - what story do you think the data is telling?"

• "Would it help to talk through what you've discovered so far?"

Avoid:

• Giving the answer directly

• Taking over their keyboard/screen

• Making them feel inadequate: "This one's easy!"

"Is this answer right?"

Good responses:

• "What makes you think that's the answer?"

• "Does that fit with what you've discovered so far?"

• "Try submitting it and see what happens - that's how we learn!"

• "Walk me through your reasoning"

Avoid:

• Looking at their screen and confirming/denying

• Saying "I don't know" without redirecting them

• Checking your own solution guide

"I don't understand what this means..."

Good responses:

• "The game will explain new concepts as you encounter them"

• "Try reading through the challenge description again - what's it asking you to find?"

• "What do you think might be happening in this scenario?"

• "Have you seen similar patterns in earlier challenges?"

Avoid:

• Launching into a technical explanation

• Assuming they need to understand everything immediately

• Dismissing their confusion

"This is too hard!"

Good responses:

• "These challenges are meant to be challenging! Getting stuck is part of learning."

• "What would you need to know to solve this? Sometimes breaking it down helps."

• "Try using a hint - they're designed to help without spoiling the answer"

• "Would talking through it with a neighbor help?"

Avoid:

• Agreeing that it's too hard

• Lowering expectations: "Don't worry about finishing"

• Comparing them to others who are ahead

"I'm finished! What now?"

Good responses:

• "Awesome work! Did you explore all the bonus challenges?"

• "Would you be willing to help others who are stuck without giving away answers?"

• "Check out the analytics on your dashboard - what patterns do you notice?"

• "Try approaching a challenge you solved in a different way"

Avoid:

• Letting them distract others who are still working

• Making other participants feel slow

• Leaving them with nothing to do

Giving Hints Without Spoilers

The Three-Level Hint System

Level 1 - Redirect to resources: "Have you tried the hint button? It'll point you in the right direction."

Level 2 - Ask guiding questions: "What columns of data do you have available? What's the question asking you to find?"

Level 3 - Provide strategic direction: "This challenge is about looking for patterns in the timestamps. Focus on when things happened."

Never provide exact answers or syntax. If someone is really stuck, guide them to use the built-in hint system or encourage collaboration with peers.

The Socratic Method

Instead of answering directly, ask questions:

Participant: "How do I filter this data?" You: "What are you trying to find? What would filtering help you discover?"

Participant: "Should I use this field or that field?" You: "What does each field represent? Which one answers the question you're trying to solve?"

This helps them develop problem-solving skills rather than just getting answers.

Managing Diverse Skill Levels

For Beginners or Struggling Participants

• Normalize the struggle: "These are designed to be challenging - you're doing great!"

• Celebrate small wins: "You just learned how to filter data! That's a real skill!"

• Reduce scope: "Focus on questions 1-5 first, then come back to the others"

• Encourage collaboration: "Find someone to work with - two heads are better than one!"

For Advanced Participants

• Deepen thinking: "You got the answer quickly - can you explain why that works?"

• Extend challenges: "Try solving it a different way" or "What else could you discover from this data?"

• Peer teaching: "Could you help explain your approach to someone who's stuck?"

• Speed isn't everything: "The scoreboard shows who's fastest, but understanding why is most valuable"

In-Person Events

Managing Mixed Skill Levels In-Person

Seating strategy:

• Mix skill levels at tables to encourage peer learning

• Don't group all beginners together

Group dynamics:

• Encourage natural collaboration at tables

• Watch for dominant personalities taking over

• Ensure quieter participants get attention too

Physical movement:

• Spend proportionally more time with struggling participants

• Don't camp out at the advanced table

• Create a rotation pattern so everyone gets face time

Virtual Events

Encouraging Stuck Participants

Signs Someone Needs Encouragement

• Not typing or clicking for several minutes

• Asking the same question multiple times

• Visible frustration - sighing, head in hands

• Disengagement - checking phone, browsing other sites

• Comparison anxiety - constantly checking scoreboard

Effective Encouragement Techniques

Normalize the experience: "You know what? This question stumps almost everyone at first. You're in good company!"

Shift focus from completion to learning: "You've already learned how to analyze network logs - that's huge! The next challenge will build on that."

Provide perspective: "Professional cybersecurity analysts get stuck on problems all the time. Learning to work through it is the skill you're building."

Celebrate progress: "You're asking really good questions. That critical thinking is exactly what investigators need."

Offer a fresh start: "Sometimes stepping away for a minute helps. Grab some water and come back with fresh eyes."

The Power of a Growth Mindset: Phrase feedback as "you haven't figured it out YET" rather than "this is hard for you." The word "yet" implies progress is possible!

Creating a Positive Learning Environment

Setting the Right Tone

From the very beginning, establish that:

• Struggle is expected and valuable

• Collaboration is encouraged - this isn't a test of individual knowledge

• Questions are welcomed - there are no "dumb questions"

• Different approaches are valid - there's often more than one way to solve challenges

• Learning matters more than winning - the scoreboard is for fun, not judgment

Handling Negative Dynamics

If someone is being dismissive or showing off: Redirect privately: "I love your enthusiasm! Could you channel that into helping others without giving away answers?"

If competition becomes toxic: Address the group: "Remember, we're all learning together. The scoreboard is for fun - the real win is understanding these concepts."

If someone is giving away answers: Intervene quickly: "Thanks for wanting to help! Instead of sharing the answer, try asking them questions that guide their thinking."

Celebrating Diverse Achievements

Don't just celebrate the top scorers. Recognize:

• Best questions asked

• Most improved during the session

• Great collaboration

• Creative problem-solving approaches

• Persistence through challenges

• Helping others learn

When to Intervene vs. Let Them Struggle

Let Them Struggle When:

• They're actively working and thinking

• They haven't used available resources (hints, challenge descriptions)

• The struggle is 5-10 minutes, not hours

• They're showing engagement, not frustration

• They're collaborating with peers to solve it

Intervene When:

• Frustration is turning into disengagement

• They've been stuck for 15+ minutes without progress

• They're not aware of available resources

• Technical issues are blocking them (see Troubleshooting)

• They're comparing themselves negatively to others

• They're about to give up entirely

The Sweet Spot: Research shows learning happens in the "zone of proximal development" - challenges that are difficult but achievable with guidance. Your job is to keep participants in that zone.

Using Your Host Tools to Support Participants

Live Scoreboard

What it tells you:

• Overall group progress and engagement

• Who might be racing ahead (could help others)

• Who might be stuck (could use encouragement)

How to use it:

• Check every 15-20 minutes, not constantly

• Use it to gauge when to give time warnings

• Don't call out individual positions publicly unless celebrating

Analytics Dashboard

What it tells you:

• Which challenges are most difficult for your group

• Overall success rates on each question

• Time spent on different sections

How to use it:

• Identify common sticking points for general guidance

• Understand which concepts to potentially discuss afterward

• Don't use it to single out individual participants

Support Strategy by Event Format

In-Person Events

In-Person Support Strategies

Advantages:

• Can read body language and energy

• Easy to give quick encouragement while circulating

• Natural peer collaboration at tables

• Can see technical issues immediately

Best practices:

• Circulate constantly - don't stay in one spot

• Crouch to eye level when helping individuals

• Use group announcements for common issues

• Bring energy through your physical presence

• Position yourself visibly so participants can flag you down

Common challenges:

• Hard to help multiple people simultaneously

• Can accidentally show answer on someone's screen

• Noise levels may make quiet participants hard to hear

Virtual Events

Handling Technical Issues During Events

For participant-facing technical issues, see the Troubleshooting Guide for common problems and solutions.

Your response framework:

1. Stay calm - your energy sets the tone

2. Acknowledge the issue - validate their frustration

3. Try quick fixes - refresh, different browser, clear cache

4. Escalate if needed - contact KC7 support

5. Keep others engaged - don't let one issue derail the event

Technical Issues vs. Challenge Difficulty: Make sure participants aren't confusing "this challenge is hard" with "something is broken." If KC7 is loading and accepting answers, it's working - the difficulty is intentional!

Supporting Different Learning Styles

Visual Learners

• Encourage use of the scoreboard and visual data representations

• Suggest they sketch out data relationships

• Point to charts and graphs in the game interface

Verbal Learners

• Encourage talking through problems with neighbors

• Ask them to explain their reasoning out loud

• Facilitate discussion of approaches

Kinesthetic Learners

• Encourage trying different approaches and experimenting

• Normalize trial and error

• Suggest taking notes or writing out patterns

Reading/Writing Learners

• Point them to written challenge descriptions

• Encourage note-taking about discoveries

• Suggest they write out their reasoning

Post-Investigation Support

After the Investigation Period

Some participants will finish early, others won't complete all challenges. Your support continues:

For those who finished:

• Celebrate their achievement

• Encourage them to help others without spoiling answers

• Suggest exploring challenges more deeply

• Engage them in discussing what they learned

For those still working:

• Reassure them that not finishing is normal

• Remind them they can continue later

• Focus on what they HAVE accomplished

• Ensure they don't feel rushed or inadequate

Setting Up Success for Continued Learning

"Remember, you can keep accessing this game anytime. Many people find it helpful to continue the investigation at their own pace, try challenges again, or explore different approaches. Your account saves all your progress!"

---

Quick Reference: Support Strategies

Situation	Response Strategy
Completely stuck	Direct to hints → Ask what they've tried → Guide with questions
Asking if answer is right	Reflect question back → Ask for reasoning → Encourage submission
Doesn't understand concept	Point to game explanations → Ask guiding questions → Encourage exploration
Too hard/frustrated	Normalize struggle → Celebrate progress → Suggest collaboration
Finished early	Celebrate → Suggest peer teaching → Deepen understanding
Technical issue	Stay calm → Try quick fix → Escalate to support if needed

Additional Resources

• Troubleshooting Guide - Common technical issues and solutions

• Event FAQs - Frequently asked questions about running events

• Technical Requirements - Platform requirements and setup

• Discord Community - Connect with other hosts for support

---

Remember: Your most important job is creating an environment where participants feel excited to learn, safe to struggle, and celebrated for trying. KC7 provides the cybersecurity education - you provide the encouragement and positive energy that makes it memorable!