Designer vs. Developer #16: Prototyping and scenario-based design

In the latest episode of his Designer vs Developer series Mustafa Kurtuldu, Design Advocate at Google, discusses techniques on how to design user flows and not just tacking on a bit of design at the end.

Many years ago I was designing a website and was given a set of design guidelines that were quite interesting, shall we say. I think they were going for a Zen-like approach, in that it was a style without style, they used Arial everywhere and blue was their primary colour; it was painful to look at. I was tasked with designing the flow and UI. During one of the presentations, I was asked by the PM if I could “add a bit more design” to the interface. This upset me quite a bit quite a bit; it was as if design was being treated a bit like chocolate sprinkles, you add some on top. This approach to design happens when we are handed a brief and asked to create the outcome rather than look at the whole problem.

Why do I need to register?

Every month, hundreds of thousands of people visit us here on our website. The more we know about our visitors, the better and more relevant content we can provide for them. And, yes, knowing our audience better helps us find commercial partners too. We just ask you to provide a few details about yourself and what you do. Don't worry, we won't share your information with anyone, unless you give us permission to do so. In return you can:

Submit your work

Send us your latest projects, which we will review and consider to be featured on our website or in the print magazine.

Receive our newsletter

Get the latest creative insight and inspiration delivered straight to your inbox, in a newsletter curated by the CR editorial team.

Subscribe for more from CR

Subscribe to Creative Review to access all our premium online content, the digital archive which includes over 400 issues of the magazine and much more.