Whatever you call your job in UX-User Experience Designer/Researcher/Architect/Visionary, you are trying to understand and focus in on one main opportunity. Or, as is more common, the SERIES of opportunities that will lead you into a successful Experience for whomever is using your system.
Mostly, this gets applied in the area of software. And frankly, depending on the style of software development-it breaks. Take Agile, for example. No longer are you looking to make the experience about your user-you make it about breaking up the research you can do into manageable chunks for the Development Team. Your focus is no longer on the person who will be using the end-product, but rather the person on the team who will feel as if the process is getting enough of the proper inputs.
It's a way to make the process of software development seem scale-able, and so now you can apply Design Thinking into the sprint and everyone is happy.
You can't do big picture stuff 2 weeks at a time, and Design Thinking is not about insights that can be cleverly packaged.
Sometimes you will uncover insights that will break the larger product. And because the rest of the team is already following the train tracks laid out for the project-the train has left the station-heading to a place where it will run out of track. Sometimes pivoting is required, based on UX work.
Good luck with bringing back that kind of news to your team. Not only do we have to pivot on the product, but we also need to change our way of working. Even if it is just a matter of a week to have sessions about re-envisioning the product-the mechanics are already greased to follow the old process. It's possible. But just be aware of how much harder it will be.
Mostly, this gets applied in the area of software. And frankly, depending on the style of software development-it breaks. Take Agile, for example. No longer are you looking to make the experience about your user-you make it about breaking up the research you can do into manageable chunks for the Development Team. Your focus is no longer on the person who will be using the end-product, but rather the person on the team who will feel as if the process is getting enough of the proper inputs.
It's a way to make the process of software development seem scale-able, and so now you can apply Design Thinking into the sprint and everyone is happy.
You can't do big picture stuff 2 weeks at a time, and Design Thinking is not about insights that can be cleverly packaged.
Sometimes you will uncover insights that will break the larger product. And because the rest of the team is already following the train tracks laid out for the project-the train has left the station-heading to a place where it will run out of track. Sometimes pivoting is required, based on UX work.
Good luck with bringing back that kind of news to your team. Not only do we have to pivot on the product, but we also need to change our way of working. Even if it is just a matter of a week to have sessions about re-envisioning the product-the mechanics are already greased to follow the old process. It's possible. But just be aware of how much harder it will be.
No comments:
Post a Comment