PLAYER DRIVENACADEMY
← All packs·CP-002·L01·18 MIN

Community Presence Beats Community Theater

Learn how consistent, human community presence creates trust and moves feedback into the work.

CommunityLive OpsTrust & Safety
── THREE LESSONS
~5 MIN EACH
  1. 01
    LESSON 1·CP-002-L1·5 MIN

    Be Present Where the Community Lives

    By the end of this lesson, you will be able to identify the real places where your players gather.

    EXAMPLE · InnoGames multilingual community operations; Discord; Reddit; Steam forums; In-game spaces

    Duration: about 5 minutes Primary pillar: Community Secondary pillars: Live Ops Learner promise: By the end of this lesson, you will be able to identify the real places where your players gather.

    ### Opening Hook

    A community does not live where the brand wishes it lived. It lives where players already ask questions, share wins, complain, trade knowledge, and build identity.

    ### Core Idea

    Community presence starts with location. If the team is only active on the channels it owns, it may miss the places where player trust is actually forming.

    The source moment for this lesson is: Fiene Ziegler: community management should be everywhere the community is.

    ### Game Or Real-World Example

    Examples to use: InnoGames multilingual community operations; Discord; Reddit; Steam forums; In-game spaces.

    Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

    ### Practical Model

    Ask these questions:

    1. Where do players ask for help?

    1. Where do players celebrate or show off?
    2. Where do players complain before they churn?

    ### Mini Action

    List the top three places your players actually gather.

    ### Transition

    Once you know where the community lives, the next question is how you show up there. That brings us to human tone.

    ### On-Screen Notes

    - Find the real gathering places.

    • Owned channels are only part of the map.
    • Community presence follows player behavior.
    ↳ Your action

    List the top three places your players actually gather.

  2. 02
    LESSON 2·CP-002-L2·5 MIN

    Talk Like a Human

    By the end of this lesson, you will be able to rewrite a stiff announcement in a more human voice.

    EXAMPLE · Discord announcement; Steam update post; Reddit reply; In-game notice

    Duration: about 5 minutes Primary pillar: Community Secondary pillars: Trust & Safety Learner promise: By the end of this lesson, you will be able to rewrite a stiff announcement in a more human voice.

    ### Opening Hook

    Players can tell when a message sounds like a wall. They can also tell when a real person is paying attention.

    ### Core Idea

    Human tone does not mean being casual about serious issues. It means being clear, consistent, and present enough that players know someone is actually listening.

    The source moment for this lesson is: GDC Community Clubhouse panel: consistency and human tone matter.

    ### Game Or Real-World Example

    Examples to use: Discord announcement; Steam update post; Reddit reply; In-game notice.

    Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

    ### Practical Model

    Ask these questions:

    1. Say what happened without hiding behind vague language.

    1. Say what the team is doing next.
    2. Say how players can help or what they can expect.

    ### Mini Action

    Rewrite a robotic announcement in a human voice.

    ### Transition

    Human tone builds trust, but community work also has to move information. That is where feedback loops come in.

    ### On-Screen Notes

    - Tone is operational, not cosmetic.

    • Clarity builds trust.
    • Consistency matters more than perfect wording.
    ↳ Your action

    Rewrite a robotic announcement in a human voice.

  3. 03
    LESSON 3·CP-002-L3·5 MIN

    Close the Feedback Loop

    By the end of this lesson, you will be able to describe how one player concern reaches the product team.

    EXAMPLE · Beta programs; Hero launch feedback; Patch sentiment reports

    Duration: about 5 minutes Primary pillar: Community Secondary pillars: Live Ops Learner promise: By the end of this lesson, you will be able to describe how one player concern reaches the product team.

    ### Opening Hook

    A community team that only collects feedback becomes a suggestion box. A community team that routes feedback becomes part of the operating system.

    ### Core Idea

    Closing the loop means players can see that feedback was heard, understood, and either acted on or explained. It also means internal teams know what the community is actually experiencing.

    The source moment for this lesson is: GDC Community Clubhouse panel: feedback should get back into the development cycle.

    ### Game Or Real-World Example

    Examples to use: Beta programs; Hero launch feedback; Patch sentiment reports.

    Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

    ### Practical Model

    Ask these questions:

    1. Capture the signal.

    1. Translate it into a useful product question.
    2. Report back with what changed, what did not, and why.

    ### Mini Action

    Define how one player concern reaches the product team.

    ### Transition

    Now we can turn these lessons into a weekly operating habit: the Presence Cadence.

    ### On-Screen Notes

    - Feedback needs a route.

    • Players need a response rhythm.
    • Community is part of live operations.
    ↳ Your action

    Define how one player concern reaches the product team.

↳
CONCLUSION · ARTIFACT TASK · 3 MIN

Presence Cadence

By the end of this conclusion, you will be able to draft a weekly rhythm for listening, responding, escalating, and reporting back.

Duration: about 3 minutes Primary pillar: Community Secondary pillars: Live Ops, Trust & Safety Learner promise: By the end of this conclusion, you will be able to draft a weekly rhythm for listening, responding, escalating, and reporting back.

### Opening Hook

Presence is not just being online. It is a rhythm players can feel.

### Core Idea

A Presence Cadence turns community work into a repeatable habit: where you listen, when you respond, what you escalate, and how you report back.

The source moment for this lesson is: Pull-quote candidate: talk to them like a human being.

### Game Or Real-World Example

Examples to use: Any active community channel.

Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

### Practical Model

Ask these questions:

1. Channel

  1. Listening rhythm
  2. Response rhythm
  3. Escalation path
  4. Report-back moment

### Mini Action

Draft a weekly presence rhythm: listen, respond, escalate, report back.

### Transition

This pack can lead into the Community Operator cohort, where the cadence becomes a real operating practice.

### On-Screen Notes

- Presence is a rhythm.

  • Human tone plus feedback routing creates trust.
  • The artifact is a weekly cadence.

Duration: 2 to 3 minutes Primary pillar: Community Completion artifact: Presence Cadence

### Speaker Script

Let us put the pack together.

The three lessons are meant to move from idea to action. You looked at the core principle, grounded it in examples, and now you will turn it into a small artifact.

Complete the Presence Cadence using these fields:

1. Community channel

  1. Player behavior seen there
  2. Listening rhythm
  3. Response rhythm
  4. Escalation path
  5. Report-back moment

This artifact should be specific enough that another person could understand the situation and respond with a useful suggestion.

If you want to go deeper, this pack leads into the upcoming Community Operator cohort.

## Facilitator Notes

Keep the lesson practical. Use the source moments as sparks, not as long readings. The learner should leave with a concrete artifact, not just a summary of a transcript.

Suggested discussion prompt:

What is one part of this lesson you could apply to a game, community, or product decision this week?

## Source Moments To Verify Before Publishing

- D:\Player Driven\transcripts\Fiene Ziegler - InnoGames-transcript.txt:539

  • D:\Player Driven\transcripts\GDC 23 - panel_1_-_community_clubhouse_transcript.txt:274
  • D:\Player Driven\transcripts\GDC 23 - panel_1_-_community_clubhouse_transcript.txt:226
↳ Your artifact

Draft a weekly presence rhythm: listen, respond, escalate, report back.

› Open artifact template

Presence Cadence

Pack: CP-002, Community Presence Beats Community Theater Completion artifact for: Community

## Instructions

Choose one community channel for a real or imagined game. Build a Presence Cadence that explains where you listen, how often you respond, what you escalate, and how you report back to players.

Suggested examples:

- Discord launch channel

  • Steam discussion board
  • Subreddit
  • In-game guild chat
  • Support ticket pattern
  • Creator community

## Your Artifact

### Community channel

Response:

Player behavior seen there

Response:

Listening rhythm

Response:

Response rhythm

Response:

Escalation path

Response:

Report-back moment

Response:

## Example

Community channel: Discord bug-report channel

Player behavior seen there: Players repeat the same confusion after each patch.

Listening rhythm: Review daily after major updates and twice weekly otherwise.

Response rhythm: Acknowledge recurring issues within 24 hours when possible.

Escalation path: Send repeated issues to production and support leads with examples.

Report-back moment: Post a weekly what we heard note with what changed and what is still under review.

## Submission Guidance

Minimum length: 120 words.

The entry should be specific enough that a real team could understand the situation and consider the proposed improvement.

── CHECK YOUR UNDERSTANDING

Take the Community Presence Beats Community Theater quiz.

8 short questions + 1 written artifact. Passing earns 25 credits toward your Player Driven profile.

JOIN ACADEMY → TAKE THE QUIZ
↳ Coming next: Cohort: Community Operator (240 min) — Practice presence, rituals, feedback loops, reporting, and team health across a guided cohort.