Brendan Kearns on creative ways of prototyping & scenario based design
Stay organized with collections
Save and categorize content based on your preferences.
Welcome to Designer Vs. Developer, a show that tries to solve the
challenges faced in the industry by opening a conversation between
the two, providing take aways, solutions to workflows, tools and
discussions on everyday struggles.
Mustafa speaks to Brendan Kearns, a Senior Interaction Designer at Google,
about creative ways to prototype and how using scenario-based design
can help you sculpt great user experiences.
In this episode:
The difference in prototyping schools of thought, showing intent vs
informing a developer.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["\u003cp\u003e"Designer Vs.Developer" is a show exploring the intersection of design and development, offering solutions and discussions on industry challenges.\u003c/p\u003e\n"],["\u003cp\u003eThis episode features Brendan Kearns, a Senior Interaction Designer at Google, discussing creative prototyping and scenario-based design for user experiences.\u003c/p\u003e\n"],["\u003cp\u003eTopics covered include prototyping approaches, redlining, and user journey mapping, with resources like AirBnB's "Painting with Code" highlighted.\u003c/p\u003e\n"],["\u003cp\u003eThe episode is available as a video recording and podcast on platforms like Spotify, Feedburner, iTunes, and Google Music.\u003c/p\u003e\n"]]],["Mustafa and Brendan Kearns, a Senior Interaction Designer at Google, discuss creative prototyping methods. They explore the differences in prototyping approaches, specifically showing intent versus informing developers. Key topics include scenario-based design, red lining, the \"throwing things over the fence\" mentality, and user journey mapping. The \"Painting with Code\" concept from AirBnB is also mentioned, offering further insight into the discussions.\n"],null,["# Brendan Kearns on creative ways of prototyping & scenario based design\n\nWelcome to Designer Vs. Developer, a show that tries to solve the\nchallenges faced in the industry by opening a conversation between\nthe two, providing take aways, solutions to workflows, tools and\ndiscussions on everyday struggles.\n\nMustafa speaks to Brendan Kearns, a Senior Interaction Designer at Google,\nabout creative ways to prototype and how using scenario-based design\ncan help you sculpt great user experiences.\n\nIn this episode:\n\n- The difference in prototyping schools of thought, showing intent vs informing a developer.\n- Red lining.\n- Throwing things over the fence.\n- [AirBnB - Painting with Code](http://bit.ly/2l0iVM5).\n- Scenario based design.\n- [User Journey Mapping](http://bit.ly/2LIamAZ).\n\nSubscribe to Designer Vs Developer Podcast via\n[Spotify](https://bit.ly/MustafaOnSpotify)\n[Feedburner](https://goo.gl/USHXv8),\n[iTunes](https://goo.gl/1E9U0G) Or\n[Google Music](https://goo.gl/qCBlST)\n\nWatch [the video recording](https://www.youtube.com/playlist?list=PLNYkxOF6rcIC60856GnLEV5GQXMxc9ByJ). \nWas this page helpful? \nYes \nWhat was the best thing about this page? \nIt helped me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had the information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had accurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was easy to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nNo \nWhat was the worst thing about this page? \nIt didn't help me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was missing information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had inaccurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was hard to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new)."]]
