Your article really resonated with me — especially the emphasis on mapping flows and journeys to uncover opportunities and pain points.
I’m passionate about using best practices to make flow and journey maps more than just visuals — they should communicate logic, decisions, and intent.
Here’s a question I’ve been wrestling with:
👉 Do standardized best practices for documenting flows and journeys actually matter?
For example — many tools (like FigJam) follow ISO 5807 symbology, which was designed for data systems and software logic, not user experience.
By contrast, Jesse James Garrett’s Visual Vocabulary feels far better suited to the way UX teams work — especially when mapping decision trees and conditional logic.
I honestly think our design community could benefit from re-examining (and perhaps re-adopting) a shared visual language for flows and journeys — now more than ever.
What do you think? Are we overdue for some UX cartography standards?
Your article really resonated with me — especially the emphasis on mapping flows and journeys to uncover opportunities and pain points.
I’m passionate about using best practices to make flow and journey maps more than just visuals — they should communicate logic, decisions, and intent.
Here’s a question I’ve been wrestling with:
👉 Do standardized best practices for documenting flows and journeys actually matter?
For example — many tools (like FigJam) follow ISO 5807 symbology, which was designed for data systems and software logic, not user experience.
By contrast, Jesse James Garrett’s Visual Vocabulary feels far better suited to the way UX teams work — especially when mapping decision trees and conditional logic.
I honestly think our design community could benefit from re-examining (and perhaps re-adopting) a shared visual language for flows and journeys — now more than ever.
What do you think? Are we overdue for some UX cartography standards?