Your SlideShare is downloading. ×
Design Processes For Web Projects
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Design Processes For Web Projects

5,845
views

Published on

Presentation by Peter Boersma about Design Processes for Web Projects, given at a meeting of the Dutch front-end developers club Fronteers.nl on January 11, 2010 in Amsterdam. Deals with business, …

Presentation by Peter Boersma about Design Processes for Web Projects, given at a meeting of the Dutch front-end developers club Fronteers.nl on January 11, 2010 in Amsterdam. Deals with business, strategy, project management, research, design and evaluation aspects of web projects.

Published in: Design, Technology, Business

0 Comments
43 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,845
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
43
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Design Processes for Web Projects Peter Boersma info . nl FULL SERVICE INTERNET AGENCY Fronteers.nl, January 11, Amsterdam
  • 2. Peter Boersma (www.peterboersma.com)
    • Senior Interaction Designer for Info.nl since February 2006. Responsible for the structure and interaction design of financial websites (banks, insurance, investments ), publishers websites (Reed, Kluwer, Dutch Yellow Pages) and interactive applications (MSN’s DaVinci Code game).
    • Before that :
    • 1988-1995: Information Ergonomics, a combination of computer science and cognitive ergonomics at Twente Universiteit in The Netherlands.
    • 1995-2002: User interface designer, project manager, consultant User Understanding andconcept designer for General Design/Satama Amsterdam. Designed many interactive websites, some mobile applications, intranets, extranets, for banks (ABN AMRO), government agencies (VenW, SVB), startups (Airmiles) and older companies (Audi, VEH), partly in Finland (Nokia).
    • 2002-2005: Senior Information Architect for EzGov, a company that builds transactional online applications based on its own software platform. Many tax-related sites for the English government, plus several for the Jamaican government.
    • 2005-2006: Managing Partner and Consultant User Experience for the user experience collective User Intelligence. Projects for Delta Lloyd, Port of Rotterdam, Transavia.com, the Irish Yellow Pages and Elsevier Science.
  • 3.  
  • 4.  
  • 5.  
  • 6.  
  • 7. UCD Theory RESEARCH EVALUATE DESIGN
  • 8.  
  • 9.
    • In theory, theory and practice are the same. In practice, they are not.
    • (Albert Einstein)
  • 10. Theory =/= Practice
  • 11. Practice prototype test user research launch pitch requirements RESEARCH EVALUATE DESIGN reviews estimate position document process review optimize scope trends roadmap scenarios promote quality teams
  • 12. Practice prototype test user research launch estimate position pitch document process review requirements optimize scope trends roadmap scenarios BUSINESS MANAGE STRATEGY RESEARCH EVALUATE DESIGN promote quality teams reviews
  • 13. Practice MANAGE STRATEGY RESEARCH EVALUATE DESIGN BUSINESS
  • 14.  
  • 15. Practice pitch BUSINESS optimize
  • 16.  
  • 17.  
  • 18.  
  • 19.  
  • 20.  
  • 21.  
  • 22. Practice pitch BUSINESS optimize
  • 23.  
  • 24. Practice position trends roadmap scenarios STRATEGY
  • 25. Strategy: Trends
  • 26. Strategy: Positioning content sales community Core brand Big Competitor 2 Client 2011 Competitor Big Competitor 1 Compe-titor Comptetitor comptetitor subbrand BrandX Client
  • 27. Strategy: Scenarios A B or client.com subsite-X.client.com subsite-Y.client.com client.com
  • 28. Strategy: Roadmap
  • 29. Practice position trends roadmap scenarios STRATEGY
  • 30. Practice DESIGN RESEARCH EVALUATE
  • 31.
    • What
    • deliverable
    • is this?
  • 32.  
  • 33.
    • Persona
  • 34.  
  • 35.
    • Content Inventory
  • 36.
      • based on motivations of real people
      • with interactive modules to discover products and personalise settings
      • with background info about products and processes
      • aimed at conversion: selling relevant products in a transparent way
    Learn Play Buy Life Learn Play Buy Life
  • 37.
    • Concept Presentation
  • 38.  
  • 39.
    • Wireframe
  • 40.  
  • 41.
    • Moodboard
  • 42.  
  • 43.
    • Visual Language
  • 44.  
  • 45.
    • Usability Test Report
  • 46.  
  • 47.
    • What
    • deliverable
    • is this?
  • 48. Practice DESIGN RESEARCH EVALUATE
  • 49. Practice pitch optimize BUSINESS
  • 50. Business: Measure to Optimise Old online form - 1 step to fill out - 1 step to print - 1 thank-you page New online form - 1 step for customer Y/N - 4 steps to fill out the form - 1 step to print - 1 thank-you page 7.7% 20.3% conversion rate conversion rate
  • 51. Business: Experiment to Optimise
  • 52. Practice pitch optimize BUSINESS
  • 53. Practice estimate document process requirements scope MANAGE quality teams reviews
  • 54. Manage: Estimate
  • 55. Estimate: input/output
    • Input (when available)
    • Scope items
    • Requirements
    • Approach/process
    • Team skills
    • Experience with subject
    • Experience with client
    • Experience of client
    • Output (when possible)
    • Assumptions
    • Calculations
    • Explanations
    • Risks
  • 56. Estimate: output
    • Assuming: - we will need about 10 wireframes - (5 complex, 5 medium) - and 15 reusable components (all medium)
    • We calculate the interaction design: (5*16 + 5*12) + (15*12) = (80+60) + (180) = 320 hours
    • Note: This includes reviews and rework.
    • Risk: we don’t know who the developer is.
  • 57. Manage: Focus in Scope hard easy essential contribution Quick wins Maintenance Winners Quality improvements Pick just a few of these!
  • 58. Manage: Requirements
    • Format: <stakeholderX> wants/can <Y>
  • 59.  
  • 60. Manage: Quality Use Cases  Test Scripts  Issues  Fixes Design & Implementation
  • 61. Manage: Quality
  • 62. Manage: Quality
  • 63. Manage: Quality
  • 64. Manage: Quality
  • 65. Manage: Teams/skills
  • 66. Manage : reviews Create Deliver
  • 67. Manage : reviews Create Deliver Edit
  • 68. Manage : reviews Edit Review Deliver Create
  • 69. Manage : reviews Edit Deliver Review Prepare Review Technical Review Team Review Client Review Project Review designer designer’s senior project lead team reviewers responsible for signoff
  • 70. Manage : reviews Edit Review Deliver Create
  • 71. Manage : reviews Create Edit Project Approach Review Technical Approach Review Create Approach Review
  • 72. Manage : reviews Edit Review Deliver Create
  • 73. Manage : reviews Create Edit Project Evaluation Technical Evaluation Review Deliver
  • 74. Manage : reviews Edit Review Deliver Approach Evaluate
  • 75. Manage: Document Process
  • 76. Very basic
  • 77.  
  • 78.  
  • 79.  
  • 80.  
  • 81. somewhat complex
  • 82.  
  • 83.  
  • 84.  
  • 85. lists of deliverables
  • 86.  
  • 87.  
  • 88.  
  • 89. links between deliverables
  • 90.  
  • 91.  
  • 92.  
  • 93. beautiful diagrams
  • 94.  
  • 95.  
  • 96.  
  • 97. fully documented processes
  • 98.  
  • 99.  
  • 100.  
  • 101. Document your UCD process
    • Brainstorm to get all candidate deliverables
    • Diagram deliverables and process
    • Describe (selected) deliverables and input/outputs
    • Present process to other departments
    • Improve process
    • Create templates for deliverables
    • Write instructions around deliverables and process
    • Improve process
    • Promote your process
    • Measure working with new deliverables en proces
    • Review ad nauseam , improve continually
  • 102. Practice estimate document process requirements scope MANAGE quality teams reviews
  • 103. UCD Practice prototype test user research launch estimate position pitch document process review requirements optimize scope trends roadmap scenarios BUSINESS MANAGE STRATEGY RESEARCH EVALUATE DESIGN promote
  • 104.
    • In theory, theory and practice are the same. In practice, they are not.
    • (Albert Einstein)
  • 105.
    • In practice, practice and theory are different.
    In theory, we can change that. (Peter Boersma)
  • 106.  
  • 107. So:
  • 108.  
  • 109. make an impact on the business
  • 110. link to strategy in your design decicions
  • 111. document your work and work process
  • 112. promote the results
  • 113.  
  • 114.  
  • 115. MORE Peter Boersma
  • 116.  
  • 117. Design Processes for Web Projects Peter Boersma info . nl FULL SERVICE INTERNET AGENCY Fronteers.nl, January 11, Amsterdam

×