Update README.md

300/600/700/README.md

@@ -7,3 +7,5 @@ This is useful but it misses a level of depth by describing a journey in a linea
 Imagine an ecommerce site that focused solely on converting the first product in a basket – thereʼd be no upsell! 
 
 Story maps can be created to show these journey loops. Arrange them by inserting **trigger** and **reference** points.
+
+Get a postit to read ʻreturn to point aʼ or ʻtrigger feedback loop Xʼ and then on another layer you can map that entire feedback loop. This increases the effectiveness of the story mapping process by being more realistic. Actions have (without being grave or drastic!) consequences and that feedback loop is something story maps should try to capture if they really want to describe the userʼs journey with the product.