Skip to content
Back to Index

Sorrows / Production & marketing

Coordinating game production, assets, marketing, and community

Coordinated game production, creative assets, marketing, and community work at Sorrows, keeping artists, developers, and audience-facing teams connected around production priorities.

Nino Amor · Production & creative coordination

Sorrows
Production coordination · Explanatory artworkGame production · Assets · Marketing & community
Production coordination · Explanatory artwork. Original explanatory composition, not a customer artifact or product screenshot.

The problem

Game production connects creative, technical, and audience-facing work. The teams have different dependencies, and a delay in one area changes what the others can do next.

Project management and marketing coordination

I coordinated game production, creative assets, marketing, and community work across artists and developers. I kept schedules, dependencies, and asset handoffs connected to launch preparation and audience-facing communication.

The responsibility was cross-functional: understand what each specialty needed, make dependencies visible, and keep the next production task connected to the shared timeline.

Production and launch work on the same timeline

My remit covered game production, creative assets, development, marketing, and community work. Asset handoffs and production dependencies needed to stay connected to marketing preparation and community communication.

That coordination became part of my operating foundation: translate between specialties, make the next dependency understandable, and keep the shared priority in view.

Keep production and audience-facing work connected

The focus was on visible responsibilities and handoffs. Marketing and community work needed to follow the state of production, while the production team needed to understand upcoming communication needs.

That made timing a cross-team concern. A change in production affected what could be communicated next, so launch preparation needed to stay connected to the actual state of the work.

What I delivered

I helped the different specialties work from a shared view of production timing and launch responsibilities.

  • Production coordination: schedules, creative assets, and dependencies across artists and developers.
  • Launch preparation: connect marketing material and timing to production priorities.
  • Community communication: coordinate public-facing work and cross-team handoffs around the state of the game.

Four workstreams, one production rhythm

My coordination work sat between the people making the game and the people preparing its audience-facing materials. The next asset, development dependency, or communication task needed to stay connected to the shared production priority.

  • Game production: keep schedules, owners, and creative/technical dependencies visible.
  • Creative assets: coordinate asset work and the handoffs between contributors.
  • Marketing: connect launch preparation and materials to the state of production.
  • Community: keep audience-facing communication connected to the work in progress.

Production & creative coordination

Four workstreams, a shared production state

  1. Game production

    Schedules, owners, and technical dependencies.

  2. Creative assets

    Asset preparation and handoffs between contributors.

  3. Marketing

    Launch material and timing connected to production.

  4. Community

    Audience communication around work in progress.

Shared priority · next owner · agreed timing

A coordination map across artists, developers, and audience-facing work. It describes Nino’s production contribution without implying sole ownership of the game.

A shared rhythm across creative and technical work

Production, creative assets, marketing, and community work shared the same moving priorities. I kept the dependencies and handoffs visible so each team understood what was needed next.

What I took forward

Sorrows is part of the production and operating experience behind my current work. Coordinating technical, creative, and audience-facing teams taught me to account for the dependencies around a deliverable as well as the deliverable itself.