A changelog does two things: it makes the work visible and it builds a rhythm of delivery. Teams that ship quietly create uncertainty because people don’t know what changed or why. Naming the thing, explaining the reason, attributing the value turns shipping into communication rather than just execution.
Done consistently, this is also the answer to Meetings are not the place to surprise people, if the work is already visible, there’s nothing new to surface in the room.