Lesson Goal

In Lesson 6 you connected your monetization system to long-term KPIs like retention and payer behavior.

In this lesson you will:

• Turn those KPIs into a small live ops roadmap.
• Define event types and cadence that match your capacity.
• Build a three‑month content calendar you can realistically maintain.

You are not trying to copy a giant F2P publisher. You are designing sustainable live ops for a tiny team.

Step 1 – Clarify Your Live Ops North Star

Before you add events, decide what success looks like.

Write down in one or two sentences:

• Your primary KPI for live ops (for example: D7/D30 retention, payer conversion, or average revenue per paying user).
• One player‑first goal (for example: “players feel there is always something interesting to come back for, without pressure or FOMO spam”).

Keep this short. You will use it to evaluate every event idea in this lesson.

Mini‑task:
Open a doc called live-ops-north-star for your project and paste these two sentences at the top.

Step 2 – Choose a Live Ops Cadence You Can Actually Deliver

The fastest way to kill live ops is to promise a weekly event when you only have time for a monthly one.

Look at your real constraints:

• How many developer hours per week can you truly spend on events and offers?
• How much art/content can you create or reuse without crunch?
• How often can you push builds or server‑side configs safely?

Based on this, pick a starting cadence such as:

• Lightweight: 1 small event per month + 1 minor offer refresh.
• Moderate: 1 small event every two weeks + 1 featured offer rotation.
• Ambitious (only if you have help): 1 small event per week + rotating offers and bundles.

Mini‑task:
Commit to one starting cadence in your doc. Write why it fits your team today, not your fantasy team later.

Step 3 – Define Simple, Repeatable Event Types

You do not need ten kinds of events. You need two or three repeatable patterns that fit your game.

Brainstorm event types in three buckets:

1. Engagement Events (no spend required)
   • Example: double XP weekend, bonus crafting resources, bonus cosmetics from normal play.
   • Goal: increase sessions and playtime without forcing purchases.
2. Value‑Add Monetization Events
   • Example: starter bundle refresh, ethical limited‑time bundles, cosmetics themed around a mini‑event.
   • Goal: give good deals to players who already want to spend, without punishing non‑spenders.
3. Progression or Challenge Events
   • Example: community challenge bar, personal milestone quests, leaderboard events (only if your game supports them).
   • Goal: give players short‑term goals that fit your core loop.

Circle or highlight:

• 2 event types you can implement using existing systems (quests, multipliers, bundles, etc.).
• 1 more event type you might add later once the basics are stable.

Mini‑task:
For each chosen event type, write:

• A one‑sentence player pitch (why it is fun).
• A one‑sentence business pitch (how it supports your KPIs without being predatory).

Step 4 – Build a Three‑Month Live Ops Calendar

Now you will map your cadence and event types into a concrete calendar.

Create a simple table or spreadsheet with columns like:

• Week/Date Range
• Event Name
• Event Type (engagement, value‑add, challenge)
• Key KPI Focus (retention, payer conversion, ARPPU, etc.)
• Required Assets/Changes

Fill the next 12 weeks with:

• Your chosen cadence (for example: one event every two weeks).
• At least one low‑pressure engagement event per month.
• No more than one monetization‑heavy event per month to start.

Make sure every event:

• Reuses as many existing assets and systems as possible.
• Has a clear exit condition (when it ends and what happens to rewards/offers).

Mini‑task:
Mark 2–3 weeks as “no major event” buffer weeks. These protect you from burnout and give space for bugfixing and experimentation.

Step 5 – Wire Live Ops into Your Analytics Plan

Your events only matter if you can see what they did.

For each planned event, add a tiny analytics section:

• Event ID or name you will log.
• Start and end timestamps.
• Key metrics to compare before, during, and after the event (for example: sessions per DAU, D1/D7 for new installs during the event, conversion on specific offers).

If you are using engine or third‑party analytics:

• List the events and properties you need to add (for example: event_type, event_name, offer_id).
• Note which dashboards or charts you will use to review results.

Mini‑task:
Pick one existing dashboard (or spreadsheet) and sketch a simple “Event Review” view that shows:

• The event window on a timeline.
• Retention and revenue metrics during that window.

You will refine this in later lessons; for now, you only need a place to look.

Step 6 – Sanity‑Check for Player Trust and Team Health

Before you ship any event calendar, run two quick reviews:

1. Player Trust Check
   • Would a reasonable player feel tricked, trapped, or pressured by your calendar?
   • Are there “must pay or miss out forever” designs that you can soften or replace with earnable paths?
2. Team Health Check
   • Does your calendar assume more art, code, or QA than you have?
   • Do events overlap with holidays, launches, or life events that will stretch the team?

If either check fails, scale back:

• Reduce event frequency.
• Replace complex event types with simpler engagement boosts.
• Move experiments to safer windows.

Your Checklist Before Moving On

Before you continue to the next lesson, make sure you have:

• A short live ops north star that ties to one or two key KPIs.
• A realistic cadence you and your team can support.
• 2–3 repeatable event types that fit your game and values.
• A three‑month calendar sketched out with events, KPIs, and buffers.
• A basic plan to track and review the impact of each event.

You now have a live ops roadmap that supports your KPIs and respects your players and your team. In later lessons you will plug this roadmap into concrete pricing tests, A/B experiments, and platform constraints.