# Separate responsibilities. One shared launch. · There are separate plans, but no shared one

All stories are fictional. They do not describe specific people, companies or projects. Any resemblance is coincidental.

Two companies prepare a joint launch. One owns the product and integration; the other handles the audience and support. Each team follows its own plan. Late in the process, materials depend on unconfirmed features and support does not know what users were promised.

## Where we could start

I would gather participants’ plans, commitments and readiness conditions. I would prepare a shared launch sequence with dependencies, owners and decisions required in advance.

## What you would have

A shared launch plan with readiness conditions and owners on both sides.

## Participants

Partner representatives, delivery leads, commercial owners and support.

## Roles and decisions

Specialists confirm their areas are ready; authorised parties approve launch.

## Factual experience, separate from the fictional story

Keiss Media: Managing digital campaigns: client requests, estimates, budgets, suppliers and delivery.
https://apiperson.com/experience/#work-keiss

Realore: International licensing and distribution of existing games, including partner work.
https://apiperson.com/career/

[There are separate plans, but no shared one](https://apiperson.com/clients/joint-launch/no-shared-plan/)

[A shared plan exists, but dependencies slip](https://apiperson.com/clients/joint-launch/dependencies/)

[Book a 30-minute call](https://calendar.app.google/4FrxQkHkAZ32PkzA9)

mailto:apiperson.com@gmail.com