Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Designing For Development - 2015

Designing For Development - 2015

The old “waterfall” model of design, development, and client partnerships, where projects are expected to be handed off from one entity to the next, often falls short among changing scopes, project discovery processes, and evolving requirements. We will discuss the added value that up-front communication and agile collaboration methods bring to a web-based project to save time, money, and headaches. For project managers, contractors, agencies, and anyone else who has to manage or work with multiple team members on a web project

Michelle Schulp Hunt

September 26, 2015
Tweet

More Decks by Michelle Schulp Hunt

Other Decks in Design

Transcript

  1. @marktimemedia HI, I’M MICHELLE @marktimemedia i do a lot of

    work with developers&teams Can’t we all just get along?
  2. @marktimemedia CSS STYLE GUIDE Colors Headings Text Lists Fonts Links

    Buttons Forms Icons Tooltips Navigation Asides POSSIBLE  REUSABLE  ELEMENTS:  
  3. @marktimemedia PROVIDING DESIGN FEEDBACK The Old Way: Looking at literal

    mockups Evaluating layout, design, and content all at once as pages The New Way: Start with evaluating look and feel Evaluating design as a series of increasingly specific systems/rules
  4. @marktimemedia PROVIDING DESIGN FEEDBACK Think about Design Systems, not specific

    pages Evaluate clarity and communication Remember it’s for your audience, not for you Be specific! Ask questions! Good designers can always answer “why?”
  5. @marktimemedia PROVIDING DEVELOPMENT FEEDBACK Focus on “how it works.” Evaluate

    cross-platform usability and consistency of experience rather than pixel perfection Explain what you expect to happen in addition to what is actually happening Be specific! Ask questions! Good developers can always answer “why?”