Votelantern

New feature announcement: one message, three places

A feature nobody hears about might as well not have shipped. The people who would use it are busy, and they won't go looking. A good announcement meets them where they already are, says which problem is now solved, and shows them where to click.

Below are three places to announce a new feature, a written-out example for each (all for made-up products), and a template to fill in.

The three parts of every announcement

Whatever the place, an announcement needs the same three parts, in this order.

  1. The problem, in the reader's words. Start with the annoyance people had, not with the feature's name. Readers decide in one line whether this is about them.
  2. What changed. One or two plain sentences. Name the new thing and what it now lets people do.
  3. How to use it. Where to find it and the first step, so a reader can try it in a minute.

Two optional extras help. Thank the people who asked for it, and say honestly what isn't included yet, so nobody finds the gap the hard way.

Place 1: the changelog entry

The changelog is the record. It is where support staff link to, where customers search later, and where every other announcement can point. It can carry the most detail.

Example: Ferncount, a fictional expense app for small charities

Split one expense across several funds

Treasurers told us that when a purchase was paid partly from one grant and partly from another, they had to enter the same receipt twice and fix the totals by hand.

You can now split a single expense across as many funds as you need. Each part keeps its own amount and fund code, and reports show each fund's share.

How to use it: open an expense, choose Split, pick the funds and type each amount. Ferncount warns you if the parts don't add up to the total.

Not yet: splitting by a fixed share is planned, but for now each part takes an amount.

Thanks to everyone who voted for this on our feedback board.

Why it works: the first paragraph is the problem, the second is the change, the third is where to click, and the limit is stated up front.

Place 2: the in-app "what's new" note

People already inside your product are the likeliest to use the feature today. A small "what's new" panel reaches them without an email. Space is tight and attention is short, so keep it to a title and two sentences, with a link to the full entry.

Example: Roomtally, a fictional meeting-room booking tool

Book a weekly meeting once

No more booking the Monday team room every single week. On the booking form, choose Repeat and pick weekly or monthly. [Read more]

Why it works: the title says what you can now do, the first sentence names the chore that went away, and the second is the one instruction a reader needs.

In Votelantern, the widget's "what's new" panel shows your latest changelog entries inside your app, so the entry and the note come from the same place. Write the entry's title and first line so they can stand on their own.

Place 3: the email to the people who asked

An email is the most personal of the three, so it goes only to people who opted in to hear about that request. In Votelantern, they are the voters who left "Email me updates" checked. You don't send it by hand: publishing a changelog entry linked to the request moves the request to Shipped and emails those voters, each email with an unsubscribe link. Nobody else gets it.

Here is what a good one says.

Example: Glazebook, a fictional class-booking app for pottery studios

Subject: The gift vouchers you asked for are here

Hi Dana,

You voted for "Sell gift vouchers for classes" and asked to hear when it changed. It shipped today.

Until now, studios had to sell vouchers on paper and type the codes in by hand at the door. Now you can sell a voucher from your booking page, and the buyer gets a code they can spend on any class.

To turn it on, go to Settings, then Vouchers, and set the amounts you want to sell.

See the full changelog entry: [link]

You're getting this because you chose "Email me updates" on this request. [Unsubscribe]

Why it works: the opening line reminds the reader why they are getting the email, which is what makes it welcome rather than noise. Then the same three parts follow.

A fill-in template

Copy this and fill in the brackets. Use the full version for the changelog, the first two lines for the in-app note, and the opening line plus the full version for the email.

Title: [what people can now do, in their words]

The problem: [one sentence on the annoyance this removes]

What changed: [one or two sentences naming the new thing]

How to use it: [where to find it, and the first step]

Not yet (optional): [what isn't included, and whether it's planned]

Thanks (optional): [who asked; link to the request]

Email opening (email only): You voted for "[request title]" and asked to hear when it changed. It shipped today.

Mistakes to avoid

Doing this in Votelantern

In Votelantern, changelog entries are written in markdown and link to the requests they ship, so the record, the in-app note and the voter email all start from one entry.

Two templates give you a starting layout. The release-notes template groups changes as New, Improved and Fixed for customers; it is previewed, with three releases for a made-up dance-studio app, on the release notes template page.

Open this in Votelantern

The Keep a Changelog-style template adds version numbers and fixed headings for readers who want the full history; see it on the changelog template page.

Open this in Votelantern

For what changelog tools include plan by plan, see changelog software.

Prices here are drafts and could change before launch. The changelog, the widget and voter emails are on the Free plan at $0, with a "Powered by Votelantern" badge. Team (price not set yet) puts the changelog on your own domain and lets you remove the badge. Business is the plan above it (price not set yet).

FAQ

How long should a feature announcement be? As long as the three parts need and no longer. For the in-app note that is two sentences; a changelog entry can run to a few short paragraphs.

Should every small improvement get its own announcement? Not its own email or note. Group small changes into one changelog entry, and save the in-app note for something people will use this week.

What subject line works for a feature email? One that names the request in the reader's words, such as "The gift vouchers you asked for are here". Avoid "Big news" and other lines that could be about anything.

Can I announce a feature that's only on some plans? Yes, but say which plans in the first line, so readers on other plans don't go looking for it.

All templates and guides