# Product launch

*Invented process document. Nothing here is real.*

Notes from the launch retro, put together after the Assess launch. Half of this is what we did and
half is what we said we would do next time.

## Roughly how it goes

Product tells us a thing is coming. Usually about six weeks out, sometimes less. We get whatever
documentation exists, which varies a lot.

Product marketing works out the positioning and writes the messaging. Then the content team write
the assets off the back of that. Assets are normally the website page, a launch email, some social
posts, and an internal deck so the sales team know what to say.

Somewhere in there we need to check the claims with product, because on the Assess launch we said
something the product did not do and it had to be pulled after it had gone out. So check with
product if you are unsure about a capability.

Then it goes live on the launch date.

## Things we said we would fix

- Start earlier. Six weeks is not enough if product documentation is thin.
- Get the claims checked properly rather than at the end.
- Stop rewriting the internal deck from scratch every time.
- Keep the assets somewhere findable. At the moment the latest version of anything is whichever
  file in the shared drive has the most recent date on it, which has caused problems.

## Who does what

Product marketing owns messaging. Content owns the assets. Design does the visuals when they have
capacity. Sign off by the relevant people before it goes out.