Creating a feedback loop for customer input sounds important, but I think that might be something we do after establishing the journey. I’m a bit confused about the order.
I’m leaning towards identifying potential risks first. It makes sense to know what could go wrong before diving into the design, but I’m not completely confident.
I remember practicing a question where we had to prioritize steps in customer journey design. I feel like mapping technical requirements might come later, but I could be wrong.
I think the first step should be defining the desired outcome and value proposition. It seems like a logical starting point, but I'm not entirely sure.
Hmm, I'm not sure about this one. Mapping the technical requirements could be important too, to make sure the journey is actually feasible. I'll have to think this through.
Lilli
4 months agoVicente
4 months agoDorthy
4 months agoLai
4 months agoLucina
5 months agoKent
5 months agoPaola
5 months agoSamira
5 months agoShalon
6 months agoRikki
6 months agoRutha
6 months agoJamal
6 months agoFranklyn
6 months agoSanda
7 months agoAnnabelle
7 months agoJohana
8 months agoBrynn
8 months ago