Chapter #70. A User's Journey Should Have a Beginning, Middle, and End
The user's journey can be thought of in a broad or narrow way: it can be their journey through the whole product—for a dating app that could be from signing up to a first date—or it could be a fine-grained journey, for example, into a particular settings menu to change an option.
As the user goes through their "jobs to be done", they make a great many small journeys. In every case, the user should know that they have begun a journey, that that journey will end at some point, and when it has ended.
The classic anti-pattern here is users thinking, "Have I saved these settings or not?" On macOS, changing the settings and then closing the window saves the settings, while on (older) Windows applications, the user must press "save". In some more obscure systems, the user must click apply and then save.
The user is never sure whether this journey (to change a setting) has ended or not, so make it clear to them.