Hi there! Micro interactions are not supposed to be in high level journeys, it's important to stick to zoom levels. I'm sending you here some articles to dive into the topic: - www.smaply.com/blog/customer-journey-management - www.smaply.com/blog/reasons-journey-map-repository I hope this helps! :)
@@smaply all the insight is really appreciated! Micro journeys aren’t a good example. Let me put it this way: In a bank, making a payment is a customer journey that will occur in multiple higher level journeys. It’s hard to position it in a single hierarchy. What about transversal journeys?
Hi @@ktoure! I understand what you mean. Your payment process will occur in multiple journeys and is not going to change, no matter in which context it is. Here, a network visualization will help you, as this step needs to be linked to all journeys. This will be solved in Smaply 3.0, where the first version will be released soon. :)
What would you like to ask Marc Stickdorn? Leave us a comment, we're striving to provide you with new webinar sessions on your favorite topics!
Hi Marc! The proposition is to have a hierarchy with n levels. What happens when a micro journeys is used by more than one higher level journey?
Hi there! Micro interactions are not supposed to be in high level journeys, it's important to stick to zoom levels. I'm sending you here some articles to dive into the topic:
- www.smaply.com/blog/customer-journey-management
- www.smaply.com/blog/reasons-journey-map-repository
I hope this helps! :)
@@smaply all the insight is really appreciated! Micro journeys aren’t a good example.
Let me put it this way: In a bank, making a payment is a customer journey that will occur in multiple higher level journeys. It’s hard to position it in a single hierarchy. What about transversal journeys?
Hi @@ktoure! I understand what you mean. Your payment process will occur in multiple journeys and is not going to change, no matter in which context it is. Here, a network visualization will help you, as this step needs to be linked to all journeys. This will be solved in Smaply 3.0, where the first version will be released soon. :)