Break the muscle-memory loop
When an action moves, customers often look where it used to be. Put a quiet pointer on the new home and link to the explanation.
Small New, Moved, and Updated signposts sit on the relevant part of your product and take customers straight to the changelog detail.
Use up to three signposts per changelog entry. Set a page match and expiry date for each one.
Changelogs work best when the right customer sees the right context at the moment it matters. Signposts make that connection without interrupting their work.
When an action moves, customers often look where it used to be. Put a quiet pointer on the new home and link to the explanation.
Show the change before someone tries an old workflow and gets an unexpected result. The detail is one click away.
A feature cannot help customers who never find it. Highlight the control they need, exactly where they already work.
These static product examples show the label, the interface element it belongs to, and the context customers receive.
A familiar control has moved from the header into the side navigation. The faded old location and highlighted new home make the value of the signpost immediately clear.
An export now requires approval. The signpost appears directly on the control, while the linked changelog context explains the new condition before the customer acts.
A useful new action sits alongside the customer’s existing workflow. The New label gives it enough prominence to be discovered without interrupting the page.
There is no extra campaign to build. Add the signpost while publishing the changelog entry that contains the answer.
Publish the customer-facing explanation in ChangeCrab as usual.
Use your browser’s Inspect menu to copy the element, then optionally match a URL and choose an expiry date.
The label appears at the control’s corner or beside it. Clicking it opens that changelog entry.
Use contextual signposts to help customers discover what is new, find what moved, and understand what changed.
Create your free changelog