A roadmap explains where the product is heading and why. It should help people make trade-offs, not conceal uncertainty behind distant feature dates. Now, next and later are planning horizons: work becomes less certain as it moves further away.
An outcome states the change you want for a user or the business. A feature is one possible intervention. "Reduce time spent resolving invoice exceptions" is an outcome; "launch a new dashboard" is an output. Keep the outcome visible so evidence can change the solution.
Some dates are real commitments, such as a contractual migration deadline. Show them explicitly and explain their constraints. Do not turn every tentative idea into a promise. Dependencies, discovery results and capacity affect what can move into the next horizon.
Outcomes and constraints can coexist without invented feature dates.