When Customer Journeys Don’t Work: Arcs, Loops, & Terrain An Article by Stephen P. Anderson stephenanderson.medium.com Thinking [in terms of loops and arcs] allows us to let go of a specific journey or sequence, and imagine dozens of scenarios and possible sequences in which these skills can be learned. This doesn’t mean there aren’t more fundamental skills that other skills build upon, but we can let go the tyranny of how, precisely, a person will move through a system. We’re free to zoom in and obsess on these loops, which does two things for us: Approach the design of a system as the design of these as small but significant moments of learning. Consider the many ways these loops might be sequenced, with the exact order being less important. uxsystemsfeedbackgames
Designing Synced Blocks An Article by Ryo Lu www.notion.so Theodor H. Nelson, “As We Will Think." Proceedings of Online 72 Conference, Bruanel University, Uxbridge, England, 1972 What if the exact same information could live and breathe in multiple places? For example, if your company’s process for requesting time off changes, you’d probably have to find all the pages that mention the policy and manually update each of them. Synced Blocks changes that. Instead of going through and updating the process to request time off in every page it’s referenced, turning it into a Synced Block allows you to update it once and have those changes reflected everywhere. Even though it’s a simple idea, it opens up many possibilities for how information can be structured and shared. TransclusionOpen Transclude for Networked WritingProject XanaduThe brilliance of notion hypermedia