I get the sentiment, but specialization exists for a reason, and this sort of thinking could work just as well for a retail experience as it can for a software product.
I get the sentiment, but specialization exists for a reason, and this sort of thinking could work just as well for a retail experience as it can for a software product.
Some of the best ‘UX’ solutions I’ve ever heard in meetings came from the software architect, usually along the lines of “Ohhhh, THAT is what the customer is trying to do? We can repurpose the flux modules pretty easily and ship that in a week or two!”.
Without good software architects on the UX team, designers will often punt on some of their more creative ideas because they assume it won’t be possible. A great architect tends to battle boredom, so the push/pull with designers can often keep them engaged and challenged. Win-win!
this article was meant to be an introduction to show how any product, startup, or company can use User Journeys as a framework for product development (not just product design) and how if executed in a systematic way can unblock growth.