How to Announce a New Feature (Without Boring Anyone)
Nobody cares that you shipped a feature. They care that a job they do is now easier. The announcement is about the job.
Read articleTopic
Nobody cares that you shipped a feature. They care that a job they do is now easier. The announcement is about the job.
Read articleA product update is a digest of changes grouped by what they do for the user, not a list of commits the engineering team shipped.
Read articleA device frame makes a screenshot read as a product in a feed. Sometimes it adds nothing, and sometimes it's the whole image.
Read articleAn annotated screenshot is the closest thing to showing the product in person. It has to be accurate, because the arrows point at real UI.
Read articleThe demo video is not a feature tour. It's the customer doing the job, with the product as the answer.
Read articleA marketing screenshot is not a capture of the screen. It's a capture of the product doing the job, with the customer's data in it.
Read articleThe launch video is the product doing the job. The talking about the product is the part people skip.
Read articleThe store shows the first few lines, and the rest hides behind the "more" link. The opening is the only paragraph everyone reads.
Read articleThe pricing page answers the objections. The hidden pricing page is the one that makes the prospects leave.
Read articleThe user opens the release note for one reason: what changed and what it means for me. The internal ticket language is not the answer.
Read articleA demo is proof on a timeline.
Read articleFor a visual product, the screenshot is the proof.
Read article