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

Efficient Workflow for Design and Development Projects

Ken Woodworth
October 26, 2011

Efficient Workflow for Design and Development Projects

We'll take a look at how our web design and development company moves Drupal projects from concept, to design, to production, using Drupal as the technical backbone for much of the process. We'll discuss how we communicate with clients and manage expectations. We'll also touch on lessons learned and things we do differently after 12 years of doing business.

Ken Woodworth

October 26, 2011

More Decks by Ken Woodworth

Other Decks in Design


  1. Justin Toupin CEO & Creative Director, Aten Design Group Twitter:

    @justin2pin Drupal: justin2pin Blog: atendesigngroup.com/blog/author/justin
  2. Why Process Matters • Consistent results require an effective, repeatable

    process. • Process helps manage expectations. • Process creates efficiency
  3. “ When we understand that slide, we'll have won the

    war ” - US General Stanley McChrystal
  4. Defining The Process • Iterative • Collaborative • Three Distinct

    Phases • Discovery • Design • Implementation
  5. “ A complex system that works is invariably found to

    have evolved from a simple system that worked. … A complex system designed from scratch never works and cannot be made to work. You have to start over, beginning with a working simple system.” -John Gall (Gall's Law)
  6. Discovery Objectives • Establish Goals • Define Audience • Assess

    Content • Create Structure • Plan for Implementation
  7. Discovery Objectives & Deliverables • Establish Goals • Define Audience

    • Assess Content • Create Structure • Plan for Implementation • Creative Brief • Audience Statement • Content List • Sitemap • Requirements Documents
  8. Simple Deliverables are Good • Focus on Content, not Format

    • Provide Flexibility • Encourage Change
  9. Our Design Approach • Design for goals and users •

    Present a single design concept, get feedback, and iterate. • Design enough to establish art direction.
  10. User-Focused Design • Design first, worry later • Design for

    real users • Test with real users • Usability workshops • Software Solutions • Feedback Forms
  11. Why one design? • Creating multiple designs is almost always

    wasted effort. • Multiple options can lead to creating a Frankenstein. • A single design concept establishes appropriate focus.
  12. Design Kick-Off Meeting • Gather branding materials and style guides.

    • Follow up any of the feedback from the client surveys. • Get a feel for the desired style.
  13. Mood Boards • Based on branding materials, client surveys &

    client conversations. • Used to explore possible typography, UI patterns, and general design styles. • Prevent heading in the wrong direction.
  14. The Design Concept • Present one or two pages, often

    one • Content and Structure have been established • Design direction has been explored
  15. Iterate • Rarely will you nail a design the first

    time. • Discovery continues throughout the design process. • Expect Changes.
  16. After the Design Phase • We aren't trying to design

    everything. • Establish art direction that can be applied. • Move on to working with actual content.