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
If a book can be summarized, is it worth reading? An Article by Austin Kleon austinkleon.com It is my opinion that if a book’s contents can be adequately “summed up,” so that you really don’t miss anything by reading the summary, it is not actually a book worth reading. (Of course, there’s no way to tell whether a summary is adequate or not unless you have also read the book.) Also, I suspect that the harder you find it to summarize a book you have read, the more valuable it might be. On 'The Master and His Emissary' reading