Decide what not to say in a launch

A launch draft often becomes a storage place for everything the organisation has wanted to say. The new offer, company history, future roadmap and founder's philosophy arrive in the same opening. Readers may understand that something important is happening without understanding what is available now.

Protect the announcement

Write a sentence stating what is new, who it concerns and when it is available. Use that sentence to judge the rest of the draft. Material that explains the offer or changes the reader's decision belongs nearby. Material that merely demonstrates how much work went into the launch may belong elsewhere.

In a hypothetical course launch, the essential information could be the subject, intended learner, delivery format and enrolment date. A long history of the organisation's teaching philosophy may be interesting, but it should not delay the answer to whether the course fits the reader's needs.

Remove premature promises

Future ideas can make a launch sound larger while creating expectations the business is not ready to meet. Separate available features from plans, and consider whether the plans need to be public at all. If a roadmap item has no confirmed scope or timing, do not write about it as though it is part of the current offer.

Also remove unsupported market claims added for excitement. ‘The first’, ‘the only’ and ‘a revolution’ change the burden of evidence without necessarily helping a buyer. A precise explanation of the new service is usually more useful than an expansive claim about its place in history.

Cut detail, not necessary conditions

Conciseness does not justify hiding restrictions, important costs or eligibility requirements. These details can materially affect a decision and need a clear place. The editing task is to reduce competing stories, not to make the offer look simpler by withholding its boundaries.

Move supporting material to appropriate destinations. Technical details can live on the product page, the origin story on an About page and a longer explanation in a separate article. Link only where the destination helps the reader continue the task. A launch does not need to become a directory of everything on the website.

Read the shortened version without the headline. Can someone still identify the new thing and the next step? Then read only the headline and first paragraph. Do they promise the same thing as the detailed page? The launch is ready when those layers agree, not when every internal stakeholder has obtained a sentence in the opening.