Developers, you're designing experiences (and you didn't even know it)

Download Developers, you're designing experiences (and you didn't even know it)

Post on 17-Aug-2014

44.932 views

Category:

Design

2 download

Embed Size (px)

DESCRIPTION

Designers are from Venus, developers are from Mars. For far too long, the two groups have had difficulties working together. At best, it is dysfunctional, at worst, impossible. In return, we have been drowned in a sea of horrible products. Great experiences come from design and technology working together to complement each other. In this presentation, the focus in on how developers can be integrated into the design process earlier and more effectively.

TRANSCRIPT

  • DEVELOPERS, YOUREDESIGNING EXPERIENCES...AND YOU DIDNT EVEN KNOW IT.P.J. Onori@somerandomdude#youareux
  • DEVELOPERS ARE VTIALTO CREATING GREATEXPERIENCES AND SHOULDHAVE A GREATER PART INTHE DESIGN PROCESS.
  • PREFACE
  • WHAT IS USEREXPERIENCE?
  • Credit: Dan SafferMANY DIFFERENT DISCIPLINESWORKING IN UNISON
  • UX SHAPES HOW WE USE THINGS
  • THIS IS NOT AWEBSITE Credit: Chris Valleskey, http://chrisvalleskey.com
  • NEITHER IS THIS
  • THIS IS A WEBSITE
  • HOWEVER, MANY OF US WORKING ON A PRODUCTONLY VIEW IT THROUGH ONE OF THESE LENSES.
  • THE PEOPLE WHO USEYOUR PRODUCTS DO NOTSEE ANY SEPARATIONBETWEEN DESIGN ANDTECHNOLOGY.
  • BAD PRODUCTS LACK IN AT LEAST ONEOF THE AREAS
  • GREAT PRODUCTS MAKE IT ALL FITTOGETHER PERFECTLY
  • WHY ARE GREATPRODUCTS SO RARE?
  • THE DISCONNECT
  • THE ASSEMBLY LINE APPROACH ISEFFICIENT, BUT INEFFECTIVE
  • Maker Developer Designer ThinkerIT CREATES SILOS OF SPECIALISTS WITHLARGE GAPS IN EXPERTISE
  • THERES A CULTURAL RIFT BETWEENDESIGNERS AND DEVELOPERS Differences in philosophy Different types of communication Different priorities
  • MUTUAL IGNORANCE Most organizations are built around a segregated, overly structured process of creating products. The majority of people on each side have no real understanding of what the other does. A lot of people dont want to know.
  • Darcy the Danny the designer engineerEXAMPLE: DARCY AND DANNY ARETASKED TO CREATE A CAR
  • The engine noise was ruiningthe driving experience, so wedecided that the car would bepowered by a nuclear reactor.Thats cool, right?
  • The weight from the seatslowered the cars fuel efciencyby 5 percent. So we removedthem.
  • GAPS IN KNOWLEDGE CREATEGAPS IN EXPERIENCES.
  • WHY DEVELOPERSARE SO CRUCIAL FORDESIGN
  • WHEN DESIGN AND TECHNOLOGY WORKTOGETHER SEAMLESSLY, ITS MAGIC.
  • DEVELOPERS ARETHE GATEKEEPERSOF EXPERIENCE.
  • DEVELOPERS PRODUCE EXPERIENCES Developers ensure that software is snappy and stable. Developers are the rst real users of software. Developers have the opportunity to point out and/or ll in the gaps often missed in design.
  • DEVELOPERS EMPOWER ITERATION At best, we will be creating imperfect solutions to the problems we are aware of. Design has traditionally been very bad at adjusting quickly. Some of the most important design decisions happen during development and after the product launches.
  • DEVELOPERS STEER DESIGNERS AWAYFROM RATHOLES Focus and constraints are invaluable to most designers when solving problems. Good communication can save countless hours of misdirected work. Informed decisions by designers encourage well-written code.
  • DESIGNERS ARE EQUALLYIMPORTANT FOR QUALITYDEVELOPMENT.(BUT THATS A WHOLE DIFFERENT SUBJECT)
  • HOW TO MAKE THISHAPPEN
  • MAKE THE PRODUCTSEXPERIENCE EVERYONESRESPONSIBILITY.
  • SCRAP YOUR SILOS Silos isolate team members from ideas and points of view. That isolation causes one-dimensional thinking.
  • FOSTER A TEAM OFT-SHAPED PEOPLE Allows team members to make better decisions due to their broader understanding. It also lets us help other people do their jobs better.
  • EVERYONE NEEDS AFUNDAMENTALUNDERSTANDING OFDESIGN If team members touch the design in any way (implementation, testing, etc.) they need to understand the subject matter to work on it.
  • EVERYONEPROTOTYPES The type of prototyping will vary (sketches, Keynote, code-based), but working in the context of the nal product forces broader thinking. Prototyping exposes designers to the challenges of making, which creates empathy for the development process.
  • EVERYTHING PRIOR TO THE FINALPRODUCT IS A MEANS TO AN END Designs mean nothing unless they are feasible and encourage stability, performance and exibility. Elegant code is worthless unless it leads to elegant experiences. All discussions and debates are framed around the user experience rather than the specics of our role.
  • WHAT THIS AIMS TO ACHIEVE A broader view of the product by everyone on the team. Less divisions between groups with specic roles. A common language to from which to communicate. A more inclusive approach to ideation and problem solving.
  • Maker Developer Designer ThinkerLARGER SKILL OVERLAP ANDNO GAPS IN UNDERSTANDING.
  • COLLABORATION IS FUN! BUT...
  • THIS IS NOT EASY.
  • YOU DESERVE A SEAT AT THE TABLE.HOWEVER... It expects more of individuals than before. Forces people out of their comfort zones. Its no longer OK to not know. Even worse to not care.
  • YOU NEED TO KNOWHOW TO DESIGN APRODUCT ALMOST ASWELL AS YOU KNOWHOW TO BUILD ONE.
  • HOW YOU CAN GETSTARTED
  • TALK SHOP Have conversations with designers about the practice of design. Ask designers about their philosophy. During that time, share your knowledge of development with them.
  • FIND YOUR HORIZONTALSTROKE With a greater understanding of the design process, nd the subjects that interest you. Read books, subscribe to some blogs, listen to podcasts. Start guring ways to integrate that focus in your daily routine.
  • IMMERSE YOURSELF INGOOD DESIGN Look at good design in a critical manner. Try to understand the thinking behind it. Observe how it plays a role in your life (good, bad or indifferent). It should not be limited just to software.
  • BE FUSSY Pay attention to the things that bug you about products and why. When things do not meet your expectations, try to understand the reasons behind it. Care about details.
  • DESIGN EVERYTHING YOU DO Put conscious thought into everything you make. How can you improve upon them, make them better for yourself and others. Remember, design far from just aesthetics, its how people perceive, interact and use something. Constantly dwell on how to improve that which you make.
  • LASTLY, AT THE RISK OF SOUNDINGNEW-AGEY...
  • GIVE YOURSELF PERMISSION Design is learned, not innate. Practice > Talent. Expect quality work from yourself.
  • IN CONCLUSION... Always keep at the front of your mind that you are ultimately making software for another person to use. Design principles will make you a better developer.
  • THANKSP.J. Onori@somerandomdudewww.seabrightstudios.comwww.somerandomdude.com