Careers In Web Design


Published on

Presentation for graphic design students showing various creative careers in the web business. This acts as an intro for them to explore career choices in designing for the web. Presentation given at Suffolk university on Sept 25, 2009

Published in: Design, Business, Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Careers In Web Design

  1. Careers in Web Design<br />Working in the Web 2.0<br />Sept 2009<br />Adrian Mendoza<br />UX principal<br />Mendoza Design & Marlin Mobile<br />
  2. Your Sister<br />(Tools)<br />Facebook<br />Iweb<br />Wordpress<br />Your Grand-father<br />Who is a web designer?<br />Blogs<br />Your Cat<br />Myspace<br />Twitter<br />Dreamweaver<br />Expression<br />Your<br />Friends<br />To many choices, not enough design!<br />
  3. What is design?<br /><ul><li>A unique solution
  4. A new perspective on an old problem
  5. A view based on history and context
  6. A cooperative process
  7. An understanding of color and shape
  8. A political or sociological point of view</li></ul>Why should web design be any different?<br />
  9. The Design Process<br />Concept<br />Schematic Design<br />Final Design<br />Prototype<br />Build<br />(Iterative Process)<br />As with traditional graphic, interior, industrial design, etc, <br />The same design process applies to web design. <br />
  10. Careers are connected to the process<br />Concept<br />Schematic Design<br />Final Design<br />Prototype<br />Build<br />Usability<br />Art Director<br />Prototyper<br />QA<br />UI Designer<br />Developer<br />Information Architect<br />Interactive Designer<br />Analyst<br />Copywriter<br />UX Lead<br />
  11. Concept<br />Requirements are gathered for the client; Non functional, Market, functional, and specification data is put together to begin to understand what will be built.<br />UX Lead<br />Using focus groups, testing sessions, and market data they learn about an existing product and report on what is broken, missing, or potential enhancements by interviewing users (customers).<br />Usability<br />Acting as an moderator between the client, creative, and usability; they manage these relationships, while beginning to propose the user experience of the product/site. Sometimes UX leads are Information architects<br />Information Architect<br />Focusing on business and functional requirements; they speak with the customer to create documentation to record functionality and market data. They will also begin to create deadlines and schedules for the project.<br />Using information from the analyst and the usability team; they create users personas to document current and potential users. User personas help create a series of archetypes of customers/users.<br />Analyst<br />
  12. Schematic Design<br />Wireframes and sitemaps are put together to begin to rough out the pages ad user experience of the new site. This work will directly influence the design.<br />UX Lead<br />Using the clients existing brand guidelines, they begin to document the look and feel of the brand and of any current job to establish these guidelines for the client<br />Art Director<br />Taking the user personas and usability information they work with defining an overall vision of what the users experience for the customer will be. They work with the client in proposing the key interactions of the project.<br />Information Architect<br />Working with wireframes and sitemaps, they translate the user personas into visual functional representations of the project. The focus is to show functionality, sizes, shapes and placement of key components of the project.<br />Working with the client, they begin to catalogue all of the content that the project needs. If content, copy, and images are missing they will create, edit, and propose these elements.<br />Copywriter<br />
  13. Final Design<br />User Interfaces are created that best represent the information design and the branding. Common pages are designed to best show the different design variations in pages.<br />UX Lead<br />Now focusing on using the brand guidelines to create a consist vision, they start guiding the design to retain as many unique design elements that best represent the information design and the branding.<br />Art Director<br />Working with the creative team, their goal is to maintain the user experience of the information design. They focus on balancing the design vision with the business requirements of the client.<br />Interactive Designer<br />Working with the art director, they work on designing a user interface that best balances the brand and information design. They take into account color, accessibility, fonts, content and the creative direction of the site.<br />Working with the UI designer, they focus on designing any interactive frameworks, UI elements and moving components of the site. They might work in flash, flex, or silver light to design these interactive pieces.<br />UI Designer<br />
  14. Prototype<br />A semi-functional version is created to best represent the designs into a working user experience. Prototypes can be quick click-through to show pages or a fancy flash interactive experience that shows interaction and animation.<br />Reviewing the prototype and design, they begin to establish the bases technologies that will be used to create the project. They might work on the data structure or other infrastructure pieces.<br />Developer<br />UX Lead<br />At this stage they are working with the team to translate the design into a working prototype. Their role in this key stage is to make sure the user experience is clearly articulated and that all key UX paths are shown.<br />Taking the design, they will begin to create a semi-functional working version of the project. The intent is to show the user experience to client and to the development team. Prototypes can be made in flash, html, or even in images.<br />Prototyper<br />
  15. Build<br />The Final Design and the Prototype are now used to create the actual working version of the project. This might range from complex backend systems to the building the visual design into static, dynamic, or interactive pages.<br />Now ready to start building, the developers will begin to implement the technology and templates needed to create the project. They will build the front end (what the users sees) and the back end (the technology that runs the site).<br />Developer<br />Working with the development team, they test and check the for bugs before it gets released. This may take a week or up to months. They will use the users personas document from the IA to simulate the user paths.<br />QA<br />
  16. PDAs<br />Mobile<br />Small Devices<br />So What <br />Can I Do?<br />Websites<br />Games<br />TV<br />Video<br />Desktop Apps<br />Multimedia <br />Kiosks<br />So many careers, and so much design!<br />(And the design process is part of all of them!)<br />
  17. Who is Adrian?<br />Adrian&apos;s career is highlighted by over 10 years of design and user experience in the handheld, pharmaceutical, financial, and educational sectors. His first studio, Synthesis3, worked with several Palm OS software companies in creating their brand for both a web and retail presence. In the financial and education sector, customers included Sovereign Bank, Houghton Mifflin, MIT and Harvard. Adrian has consulted in UX and Information Architect lead roles for Fidelity&apos;s E-business design group, Thomson Financial, and T.Rowe Price. Adrian earned his Bachelors from the University of Southern California and his Masters from the Harvard Graduate School of Design.<br />Currently he is the UX principal at Mendoza Design a Brookline MA based UX consultancy; and the mobile UX principal at Marlin Mobile a user experience, optimization, and performance company. Additionally he is senior lecturer at the School of Art and Design at Suffolk university in Boston, MA.<br />Questions? Contact<br /><br /><br />Follow Adrian on Twitter @marlinUX<br />Or read his mobile UX blog at<br />