Product changelogs: what should users do after an update?
Explain who a product update affects, what changed and what users need to do, with clear availability and links to current instructions.
Article language: English

In this article
“We improved exports.” That sounds good until someone needs to know whether tomorrow's file will still contain the same columns. The team has closed a dozen tasks, but the customer has one task in front of them: send a report in a format their colleague can accept. They want to know whether they need to do anything.
A product changelog should explain what a released update means for its users. The version number and date help people identify the state. The entry must also explain who is affected, what actually changed and what action is needed. The team's enthusiasm alone does not establish who can use a feature.
Imagine a fictional service called Półka for preparing equipment lists. Its team has added an export with separate variant labels. The new option is available to some accounts, the previous file still works, and partners' existing templates expect the old column names. This example helps us provide useful information before someone downloads a file, rather than after an import fails.
First, show who the change affects
Separate the date an entry is published from the date a feature becomes available. You can announce today a change planned for next week, or release it in stages to different groups. A heading such as “New export available now” needs to say where and for whom. Someone without the feature should not have to start by wondering whether they are looking in the wrong place.
State the scope alongside the entry: account type, product version or another condition that actually determines access. Do not make readers identify it from an internal rollout abbreviation. If they need to check a setting or version number, show them where to find it. The product owner should confirm those conditions before publication.
Keep a Changelog proposes a chronological list of notable changes written for people and grouped by type. It also separates upcoming changes in an Unreleased section from released versions. This is a useful editorial convention to adapt to the product's audience.
Keep working names that mean nothing to customers out of the public view. “Export v2 for group B” may be clear to the technical team. For the owner of an equipment list, it is better to name the new export option and its specific availability condition. If an administrator has to enable the feature, name that role and the required action.
In company communications, we describe a similar distinction in explaining change through the audience's tasks (in Polish). A product changelog adds a lasting history of availability. Someone returning after a month should be able to tell whether an entry is still an announcement or describes a state they can use.
Explain what labels such as “beta”, “preview” and “experimental” mean for ordinary work. Is the feature available for trials? Can people rely on it in their usual workflow? What limitation remains? A label should not be decoration that weakens every sentence through fine print. If the team does not yet know how an important part behaves, the entry should say so explicitly.
GitHub's release management instructions separately describe saving a draft, publishing and marking a pre-release as not ready for production and potentially unstable. This is a distinction in one particular tool. Creating an entry alone does not prove that a change is available in the customer's environment.
Give each change its own explanation
In Półka, the heading “Export with equipment variant labels” lets readers predict the subject. The first sentence can explain that the new file adds a variant column to each item. The next can say who has access and where to select it. Details of the layout can follow.
A change card should answer four questions:
- What is different: the new file has a separate variant column, while the previous format remains an option.
- Who is affected: accounts covered by the stated rollout stage, according to the confirmed scope.
- What to do: if a separate variant column is needed, check compatibility with the recipient and select the new format; otherwise the previous one can still be used.
- Where to find details: a column description and sample file showing the approved structure.
This is a fictional card for a particular solution, not a universal template for every update. A typo fix does not need four separate paragraphs. A change that affects what people do next must retain all the information needed for a decision. Set the length according to the effect, not the number of project tasks closed.
You can attach two small examples: the previous and new files with the same fictional items. Do not also change product names and row order unless those are part of the update. Readers should see the structural difference, not solve the puzzle of two incomparable illustrations. Label each example with its format and version so a file saved later can still be identified without reopening the changelog.
Instead of a general “we improved performance”, describe the specific action and confirmed result. If the team tested preparation of one kind of list, do not extend the result to every task in the service. Without a comparable measurement, describe the behavioural change without promising a percentage improvement in speed.
A screenshot can help people find a new option, but it should show the correct state and have a caption. When the interface changes, a short text instruction explains the action without requiring the reader to make out image details. Keep the access condition next to the instruction: an image of a button does not explain why it is absent from an account outside the rollout.
For larger files, also explain what happens while users wait. If the new export starts a longer-running task, they need to know where to collect the result and whether they can leave the tab. Progress and return for a long-running task (in Polish) explores that path. The changelog states the change; the actual screen must then live up to its description.

Check the route from the feature back to its explanation too. A short link beside the new export option can explain the difference before someone chooses a format. If it leads to a general page with dozens of entries, the user must search again. Link to the specific update and preserve a way back to the list they are preparing.
A notice that a feature is ending needs a date and a way forward
Announcing that a format will be withdrawn is not the same as removing it. Users need to know what works now, how long they can use it and what they need to prepare. If the date depends on a group or contract, state the relevant scope. Do not make people infer it from one general heading.
In our example the previous export remains available. The entry should therefore not sound as though all templates must be migrated immediately. If the team later decides to turn off the old format, it will need a separate notice explaining the consequences and available help. The earlier announcement can be linked to the current state while retaining its date.
An archive alone is not enough as the only route for an important warning. If a template must be prepared before the format is turned off, agree with the product owner where users will learn about it during ordinary work. It might be a notice at export with a link to details. The changelog remains a lasting explanation, but people should not discover the date only after their usual task stops working.
Show what happens to files already prepared and tasks already started. Changing the default format for new exports does not necessarily mean rebuilding previously saved material. Readers need that distinction. Without it, they may unnecessarily repeat work or send a partner a different file from the one they intended.
If an update is rolled back, the changelog should reflect the current state. Do not leave “available to everyone” in place when the feature has temporarily disappeared. Explain the scope, the available way to complete the task and where to obtain further information. Simply deleting the previous entry removes context for people who have already read it.
Aeneia Design We can design a changelog that connects version and availability with a specific user action. We will organise the update card and its links to instructions and the place where the task is performed. Show users what an update means
The archive should answer old questions too
Keep entry URLs recognisable and preserve access to a specific version. A support team may send a link in a conversation, and a user may return to it later. Changing the list layout should not break that reference. When moving content, preserve a route to the right information.
Show recent entries so people can recognise the subject and date without opening every card. In a larger archive, useful criteria reflect what people actually seek: product area, type of change or version. An “improvements” filter helps little if the company uses it for everything from a new field to an entirely different workflow.
Separate the changelog from current instructions. An entry explains what changed at a particular time; instructions describe how to work now. Do not force a new user to read two years of updates to learn how to prepare an export today. Connect the two materials in the right place and make their purposes clear.
A download centre (in Polish) should identify the correct sample version and its use. If an entry describes new columns but the linked file still shows the old layout, the information becomes contradictory. Before publication, check the file contents, not merely the address.
Across languages, keep the status, date and instructions consistent. Versioning a multilingual offer (in Polish) illustrates how decisions can diverge in parallel content. In a digital product, similarly check whether an entry in one language still describes a future announcement while another declares the feature available.
A broader external announcement can link to a press centre with facts and materials (in Polish). A media announcement and a user changelog serve different audiences, but must agree on what has been launched. A description of company success should not get ahead of the product's confirmed state.
Make one person responsible for keeping it current
Before publication, the product owner confirms behaviour and availability, while the editor checks clarity. The workflow can be connected to a CMS content publication process (in Polish). Approving the entry does not replace confirmation that the described option actually works for the stated group.
Before publication, compare the short description with the full entry. The list might say “Export for everyone”, while the expanded text correctly specifies a limited stage. Both are part of the same message. Also check any message or banner leading to the update: it should retain the main condition rather than promise a broader scope for a stronger headline.
Give the draft to someone who knows the product but did not work on the update. Ask whether the change already applies to them, whether action is required and where to take it. Do not ask only whether they like the tone. If the answer requires an explanation from the author, put the missing information in the entry itself.
Then check the information from the perspective of an account that has not received the feature. Can that person still recognise their situation? Do they know the old export remains available? This is a proposed acceptance exercise. Keep the result for an account with the new feature separate from the result for one without it, so both scopes can be reconstructed without guesswork.
In the Aeneia Design offer, a changelog like this is part of designing communication and the service experience. In Półka, a good entry will let someone prepare the right file without guessing whether “improved” also means “compatible with my template”. An update can delight the team. It should also make the recipient's next step easier.










