My take on the “participant journey” discussion is that the UX perspective brings along a kind of paternalistic view of vendor/customer, manager/employee, that the LLC will determine and design the participant journey, rather than the sense that the IETF standards process defines various touchpoints and the LLC goal is to facilitate, enable, address pain points of typical user experiences.. I think you can USE the concept of “participant journey” as a good analytical method without buying into the who I think some of the wording around community and strength is fine at the core, but I’d like to see more about occasional users who have no desire for a journey, they’re just here for a limited engagement, to enable one feature or update an RFC-defined IANA value, where those users don’t need to be part of the “strong community”. You might consider calling for “using modern UX methods to help optimize the user experience” and call “analyzing and documenting (and maintaining) typical participant journeys” as a tactical choice. I think in the end the “community” we’re trying to serve are Internet users everywhere, and the strategy of the LLC should somehow reflect that. -- https://LarryMasinter.net https://going-remote.info |
