« Mo Cheeks and a fundamental question of leadership | Main | metacool Thought of the Day »


best design-blog post I've read in over a year. Thank You!

This is absolutely right! Lately I read a story where sombody stated: I do not follow a process, I'm in a cloud of activities...

Managers should trust people over processes, and create some space for creativity and failure. That was one of the reasons to start my blog: www.r2xp.wordpress.com


I couldn't agree more with you Diego. Prototyping is a mix of art and science. If you are dealing with services and experiences, I'd argue it is more art than science, and as such, it can get a bit messy and fuzzy.

I've been a Service Design consultant for 9 years now, and I still find it quite challenging to get clients to adopt this ‘prototyping mindset’.

Funny enough, from a clients’ point of view, the idea of prototyping as a process can be quite paradoxical: on one hand it’s about reducing risks, on the other, however, it can make them feel that the process is quite risky – as it’s not often linear and structured.

My take is that it requires a lot of expectation management and reassuring – which sometimes mean that we need to demonstrate we are using a structured process (as you argued in your post), but in the background you are playing with all these ideas. It’s like the duck swimming idea: calm on the surface, [organised] chaos beneath…

Erick Mohr

I disagree and I will tell you why. I've been trying to visualize a process similar to a cooking recipe for a long time, no success so far. But that doesn't mean it cannot be done. And while I agree that there are many different activities and they are not always linear and certainly not always applied in the same order, there might be 'multiple' cooking recipes that describe the whole.

For example, a redesign of an existing app calls for different set of methods as a proposal or a project with clearly defined requirements. In yet another case the exact same pre-conditions might have you attack the beast very differently based on team structure & capabilities, budget, goals, economy, etc.

In summary, there are plenty of ways of doing it and to experts it becomes a furball. To non-experts it becomes non-understandable - and that's why we try to generalize and explain in simple words.

Cheers, Mike

Prototyping is a process that needs a safe space, a tolerance zone for intuition, experience and room for controlled failures.

The comments to this entry are closed.