Download as PDF, PPTX
Uploaded byDave Stadler
How to Sell Design to Developers
The document discusses the importance of effectively selling design to developers by bridging differing perspectives and promoting collaboration. It emphasizes that design goes beyond aesthetics, serving as problem-solving craftsmanship essential for creating usable applications. Key strategies include fostering team communication, conducting thorough research, and providing annotated designs to facilitate a smooth development process.
More Related Content
Similar to How to Sell Design to Developers
![PowerISO 9.2 Mac Crack + Serial Key Free Download 2026 [Latest] Software.pptx](https://cdn.slidesharecdn.com/ss_thumbnails/software-251207185653-5d5700e6-thumbnail.jpg?width=640&height=640&fit=bounds)
![Parallels Desktop v7.1.1.4366 Crack for macOS Activation Key [Latest] pptx](https://cdn.slidesharecdn.com/ss_thumbnails/softwareoverview-251207191237-21d186d4-thumbnail.jpg?width=640&height=640&fit=bounds)
![WinRAR Crack 7.13 Final Mac Keygen 2026 Download [Latest] Software.pptx](https://cdn.slidesharecdn.com/ss_thumbnails/software-251207185858-eb450678-thumbnail.jpg?width=640&height=640&fit=bounds)
![Moho Pro 14.4 Crack for MacOS Works Until 2050 [Latest] pptx](https://cdn.slidesharecdn.com/ss_thumbnails/softwareoverview-251207192639-797289c4-thumbnail.jpg?width=640&height=640&fit=bounds)
How to Sell Design to Developers
- 1. @_davestadler How to selldesign to developers. Bridging the gap between two different ways of thinking. @_davestadler
- 2.
- 3. @_davestadler Expert on pointingat things.
- 4.
- 5. @_davestadler we build web& mobile apps.
- 6.
- 7.
- 8. @_davestadler some designers just wantto create selling
- 9. @_davestadler can no longerbe silent design
- 10. @_davestadler Sales is perceivedas… ! • Necessary • Sleezy • Unfair • Unpleasant common misconceptions of sales
- 11. @_davestadler “Whether we’re employeespitching colleagues on a new idea, entrepreneurs enticing funders to invest, or parents and teachers cajoling children to study, we spend our days trying to move others. Like it or not, we’re all in sales now.” ! ~ Daniel H. Pink
- 12. @_davestadler i.e. convincing achild to brush their teeth is the root of sales… “tell me why?”
- 13.
- 14.
- 15. @_davestadler SalesValue Understanding sales isa confluence
- 16.
- 17.
- 18.
- 19.
- 20. @_davestadler what’s the goalfor devs? creating a great product!
- 21.
- 22. @_davestadler • To feelinvolved in the process • Access to Designer • Documentation ! find out what developers need
- 23. @_davestadler • Concept isthere • Functional code • Lack of empathy • Lack of polish ! development without design is bad
- 24. @_davestadler functioning Apps are notalways easy to use…
- 25. @_davestadler • Product becomesmore usable • Making more profit • Building team relationships • Educating and learning from each other benefits of buying design
- 26.
- 27. @_davestadler …but ‘making itpretty’ doesn’t make it qualitatively good.
- 28.
- 29. @_davestadler design is not justdecoration. it’s a craft.
- 30. @_davestadler “ I’ve been amazedat how often those outside the discipline of design assume that what designers do is decoration - likely because so much bad design simply is decoration. - Good design isn’t. ! - Good design is problem solving. Jeffrey Veen ”
- 31.
- 32. @_davestadler crafted apps are builtto solve problems…
- 33.
- 34. @_davestadler great user interface problemsolving + crafted apps:
- 35. @_davestadler how do weget there?
- 36. @_davestadler 1. A sayin what is being built. 2. Confidence in the design direction. 3. Annotated Design Files if developers had… they could ship great software.
- 37.
- 38.
- 39. @_davestadler teamwork makes thedream work • Avoid Waterfalls • All ideas are equal • Passing the ball • Kick-Off meetings are crucial
- 40.
- 41.
- 42. @_davestadler Team kick-off meeting •Fostering input from the team • Building a collaborative vision • Getting buy-in • Avoiding pitfalls down the road
- 43. @_davestadler early on, try toavoid saying no!
- 44. @_davestadler collaborative approach • Discoverand share with group • Speed sketching sessions for features • Divide and Conquer when appropriate • Iterate upon prototypes • Retrospective at end of sprints
- 45.
- 46. @_davestadler UX inside anAgile environment • Stagger your Sprints • Put Design one sprint ahead of development • Gives time for internal and external review, revisions, and sign-off. • Keep whole team in these early meetings • Dev feedback is necessary even before coding begins
- 47. @_davestadler Sprint 2 (Development) Product Owner Review Design Revisions1 Client Review Design Revisions 2 Sprint 3 (Design) Sprint 1 (Design) staggered sprints
- 48.
- 49.
- 50. @_davestadler designers do yourhomework • Absorb any existing research done by client • Discover personas • Interview users • Document user journeys • Track clicks • Record users’ interactions on-screen
- 51. @_davestadler ! “If I hadan hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” ~ Alfred Einstein
- 52.
- 53. @_davestadler product definition Client: BusinessGoals:Audience: Value Proposition: Assumptions: Unknowns: Research Notes: User Personas: Stakeholder: Contact Info: Timeline: Stakeholder Interview// PRODUCT DISCOVERY
- 54.
- 55.
- 56. @_davestadler user journey maps RangeofEmotions DelightedFrustratted ActionThoughts //Persona #1: Alisa “She used CIP for 2min and found a lead - Canadian company that was not on their radar - and now the technology is under evaluation” Feel Curious. Used Search to find a school/institution Using work-around because it’seasier. Used om ni-search to find school. Delighted to find the schoolIwanted. Landed on UniversityProfile page Found a tab forPatentsasexpected. Clicked ‘Patents’tab on profile page. Curiousto see whatIcan find. Searched 7 differentterm swithin school. Found whatIwaslooking for! Clicked on one patent. Dissapointed thatitem wasn’tworthwhile. Couldn’tfind anything ofinterest. Starting over,trying a new search. W entbackto search anotheruniversity, Stillsearching form ydesired content. Clicked a few patentswithin a new school. Found a profile page,thiscould be good! Clicked through to ‘Profile’ofindiviiual. Searching through a lotofpages... Continuing on,clicked through 30 pages. Tried feed tab,to see whatit’sabout. Viewed ‘Tour’ofFeed Feed looksuseful,I’lltryitout. W entto create a new feed.Confused on whatto do,leave thisfornow. Didn’tcreate theeee feed and left. Curiouswhatisfilings?Doesn’treallyhelp. Clicked the ‘Filings’tab and then left. Seen allthe parts,backto search form e. Goesbackto search. Didn’tknow aboutfilters,these can help . Usesfiltersaftertheyunderstand them . Betterresults,stilltakesawhile to filter. Clicksthrough m anypagesuntilfinding it. // JOURNEY MAP #1: Company (Buy-Side)
- 57.
- 58. @_davestadler track clicks • GoogleAnalytics • HootSuite • MailChimp • Binders full of spreadsheets
- 59. @_davestadler Usability testing • UserTesting.com •SilverbackApp.com • Screen Recordings • i.e. QuickTime • In-Person taking notes with User as they perform tasks • i.e. Goose from Top Gun
- 60.
- 61. @_davestadler …well most ofthe time
- 62. @_davestadler 3: make iteasier
- 63.
- 64. @_davestadler rapid prototypes • InVision- http://www.invisionapp.com/ - $15 to 20 a month • Balsamiq - http://balsamiq.com/ - $80 • OmniGraffle - http://www.omnigroup.com/omnigraffle/ - $200 • Axure - http://www.axure.com/ - $590 • Solidify - http://www.solidifyapp.com/ - $19 to 49 a month • Flinto - https://www.flinto.com/ - $20 a month
- 65.
- 66. @_davestadler Working side byside • Increases iterations • Feedback loop is instantaneous • Ideation can be tested quickly • Google Hangouts when remote
- 67. @_davestadler uniform direction • Usesimilar grids, patterns, elements, colors, and typography • Cat-Herd the unseen use-cases that inevitably rear their heads • Too many different paradigms can confuse users • Sometimes compromises are needed
- 68. @_davestadler clean files • Photoshop •Sketch • Illustrator • InDesign
- 69. @_davestadler photoshop ettiquette • FileOrganization • Best Practices • Naming Conventions • Layer Organization http://photoshopetiquette.com
- 70.
- 71.
- 72.
- 73.
- 74.
- 75. @_davestadler so when youget buy-in…
- 76.
- 77. @_davestadler …why are designersalways touching their faces?
- 78. @_davestadler it must be demonstrated. valueis not always apparent remember that
- 79. @_davestadler 1. Share thediscovery stage with the entire team. 2. Collect Research & Usability Data to drive problem solving 3. Create annotated documents to expedite development if designers will… they can ship great software!
- 80.
- 81.
- 82.