A change log tells consumers what changed and when. It is one of the most revealing artifacts a provider publishes, because its cadence tells you whether the platform is alive, and its honesty tells you whether the provider respects the people depending on it. An empty change log for eighteen months says something. So does one that only ever announces additions and never mentions anything that broke.
Make it dated, specific, and complete: additions, changes, deprecations, fixes, and anything affecting behavior, limits or terms. Give it a feed so people can automate against it. Reference it from your release announcements.
The road map is the forward-looking half, and it does something more valuable than most providers realize: it lets consumers plan their own futures. That converts the relationship from uncertain dependence into something closer to partnership. You do not have to commit to dates — themes, direction, and what is explicitly not planned are enormously useful on their own.
Together they are how a provider says: here is what we did, here is where we are going, you can build on this. That is what trust is made of, and it costs a page and some discipline.
