There’s a dirty secret in the turf war between agile, lean, and waterfall: they each use the same product development process. What’s different isn’t their process, but how they apply design activities in different ways to eke out design value in different places.
So how can you alter the design process? Even better, how can you best customize the process to provide more value for the way your organization works? More importantly, how should you change the design process from sprint to sprint to get the most value out of your design activities?
How do you hack user experience?
There are five levers you can tweak to adjust how you get value out of the design process:
For each of these levers, we’ll examine how they inter-relate, how they govern the value you can get from design activities, and the issues and questions you should consider when hacking the user experience process.
This talk won’t be about nifty methods or collaboration or white boards or prototypes. When we’re done, you will leave with a toolbox for continually hacking the design process. You’ll understand why some nifty methods work for others and not for you. You’ll understand how to hack your own nifty methods that will work best for your team. And most of all, you’ll learn how to teach everyone on your team how to hack the design process.
You must be a Member to view this post and you are currently not logged in.
You can either log in below or sign up here.