One of the things that sticked was he mentioned we should be inspired by movie makers when doing up front design and making decisions early in the development process.
(I blend some of my own thoughts with Pattons here, since I often use film making as a metaphor for development processes, so not all are exactly citations..)
When movie makers are looking for investors they cannot come with empty hands and say ”we will see what happens when we start making the movie” Some up front job needs to be done.
Movie makers make a lot of sketches, an early unfinished story board, outlines of the whole movie. They present the outlined story, investors make decision based on the idea presented and not the details! Investors know the finished movie will not look exactly as the outlined story board, and a lot of changes will be made during filming.
This we should learn from when making decisions on software development. We don’t need every detail when doing up front design to make good decisions. Of course, as in film production, there are always risks when investing. But specificing every detail up front does not manage risks!
How much UX design is needed up front before starting programming?
Often UX designers want to do everything up front, by old habits. And then leave it to teams to do whatever they want with it, it’s the production teams problems – I’ve unfortunately see and hear stories about this not very productive way of working. Agile teams want in stead to do very little up front and often have a hard time to know how and why integrating UX people in teams. These two communities need to find the balance, and movie making can help.
Search on ”story mapping” and you will find many inspiring ideas from movie makers on how much design needs to be done up front.
Image from Jeff Pattons presentation at Scandev: