team-live-ops

Live-ops planning can be coordinated through a structured pipeline that aligns cross-disciplinary teams across scoping, economy design, and narrative phases. You provide a season or event description to initiate the workflow and approve proposals at each decision gate.

Season planning is best structured using a phase-driven pipeline that covers scoping, theme, economy, analytics, content writing, and communications. This ensures game-design, systems-design, production, and narrative roles remain aligned before progressing through user-approved decision gates.

Yes, this live-ops workflow applies to both seasonal events and one-off live content launches. It guides scoping, narrative framing, economy design, and communications planning for any post-launch content update requiring multi-role team coordination.

Decision gates are managed using labeled proposals that require explicit user approval before advancing to the next phase. This governance ensures consensus across game-design, systems-design, production, and narrative teams at each stage of the live-ops pipeline.

The live-ops planning pipeline generates integrated outputs including design documents, analytics plans, and communications calendars. These deliverables are produced through subagent delegation across the scoping, theme, economy, and content writing phases.

No prior event design experience is required to run the season planning workflow. You simply provide a season name or event description to begin, and the pipeline handles cross-disciplinary delegation, narrative framing, and economy design through structured phases.