May 29, 2014
‘Prototyping for Business Outcomes’ Recap from ModevUX
Last week, Erik Isaksen and I had the opportunity to present a workshop at ModevUX on “Prototyping for Business Outcomes.” ModevUX is an international mobile and user experience conference that Pete Erickson and his Modev team put on once a year. We had the good fortune of being among presenters from companies like Microsoft, Capital One, eBay, Google, Microsoft, IBM, and many others.
In our presentation, Erik and I discussed some of the merits of implementing a “prototype first” business model before committing to a full-scale product development effort. Among the greatest benefits of prototyping is the ability to break out of the cycle of the typical 6 phases of a software development project. We were fortunate to have a room full of highly engaged UX professionals who came with a number of great questions throughout the presentation.
Some of the key takeaways from the presentation were:
- Defining some of the typical business outcomes a company would look for in building new product
- Our definition of what a prototype is and is not, from a fidelity, functionality, and content perspective
- The importance of setting expectations on reusability and fidelity
- Why you should engage with clients early and often in the prototyping process
You can view the complete presentation on “Prototyping for Business Outcomes” via the Slideshare embed below.
You can also view the presentation in its entirety via the YouTube embed below.