What can product managers learn from film directors?

23 Flares 23 Flares ×

blade-runner-rutger-hauer12A colleague and I were having a conversation over a pint the other day as to whether you could make the film Blade Runner using Agile processes. We concluded you could not. We thought you would need something more. You would need a vision, a way of developing that vision and a way to not lose the vision in the process.

Before UX, I worked with stage, film and TV lighting and I think the way that the vision of the film director is developed and retained in these media might aid the vision of successful products.

In film, the vision is the absolute key to success. The vision is the responsibility of the director and constrained by the budget owned by the producer. The director briefs a small number of creative and technical experts – writer, art director, lighting director – with the vision and concepts and starts a creative collaboration long before any technical details are decided.

In Blade Runner, Ridley Scott didn’t wield the camera, he didn’t write the screenplay, he didn’t act in it and he didn’t record the sound. But he made sure that the dystopian vision of 21st century LA and the ambiguity of Harrison Ford’s character’s reality engaged both our emotions and our intellects. His holistic vision made it all work together and he was responsible for it. As the big-picture vision begets the detail, a coherent creativity can flow. Rutger Hauer wrote his own final speech: “…all these moments will be lost in time, like tears in rain. Time to die”. It perfectly enhances Scott’s vision of the humanity of the replicants and is beautifully aligned.

So what can product managers learn from film directors?

Firstly, I think our traditions of inclusion, committee and flat structure work against us in our decision making. We typically allow all voices to be heard at the same decision-making level. But if we appreciate that vision is key to success, then it is better that an individual takes responsibility rather than the crowd. Film protects the vision by creating a hierarchical structure that makes it hard to lose.

Secondly, like the film director, the product manager develops the vision with three key experts – business director, experience director and technical director. This releases the experts to be creative within the constraints of the vision, but not to challenge its basic themes.

Thirdly, in film, everyone knows their roles and sticks with them, having the professionalism to not interfere in another person’s expertise. The director has plenty to do, and a belief in the capabilities of the crew to do the detail, creates the space for the director to focus on dealing with the big picture.

Finally, a camera crew would not choose shots to be filmed or not, but they would advise on cost and difficulty, so that the director could manage to budget, and they would also feedback detail ideas. The fact that Rutger Hauer wrote the most famous speech in Blade Runner is testament to that fact that film structures do not make a one-person show, but rather catalyse a creative team, one that uses all experts to their full extent.

To sum up, I find it enormously reassuring to hear that word ‘vision’ again. Like films, the success of software products comes from a vision of how a product can create a narrative, stimulate emotions to delight and excite and help us think differently about what we do.

The easiest thing to lose is the vision. It may be time to toughen up our hierarchies, seize the vision and let the experts get on with what they do best. Like Ridley Scott did with Blade Runner, and Steve Jobs did at Apple.

, , ,

  • Pingback: You Say UCD, I Say UX… | Vicky Poppins' Bag

  • Steve Dennis

    Firstly, on the whole I agree, but I’m wired to question my own assumptions, so bear with me ;)

    The only problem with this is that the *vast* majority of films that use this system (pretty much all of them) are utter crap, or don’t make their money back. Directors like Ridley Scott are rare enough as it is, and even with someone as talented as him, many of his films could also be considered pretty poor. Because of this, it doesn’t feel like this is a model we should necessarily be trying to reproduce (though aspects of it may have it’s merits).

    Having a vision isn’t enough, because it needs to also be the right vision. It would be interesting to see some discussion on how one might go about finding that person with the right vision, as that’s where a system like this will succeed or fail.

    This would be a great UXDebate topic I think :) Would love to hear both sides flesh out their arguments.

  • G

    Everything fine, except hierarchization. Product manager is not a director but an horizontal coordination role. The moment it is perceived as being hierarchically superior, it stops being product management altogether.
    There’s plenty of directors of each kind inside companies. So why do they need product managers in the first place?

  • Pingback: Fast Learning Cycles » Pitching a Vision – Loglines

23 Flares Twitter 0 Facebook 0 LinkedIn 22 Google+ 1 23 Flares ×