The document discusses best practices for redesigning a website, including when to redesign, identifying key team members, developing a strategy document, creating blueprints, the design and development process, testing, and maintenance. It recommends establishing clear goals and stakeholder sign-off before beginning, using tools like Skype and Basecamp for communication, and providing training and documentation for handoff and maintenance.

1. Redesign:
Avoiding the Pitfalls
Chad Williams
chadw@5Qcommunications.com

4. How Often?

6. Refresh vs. Redesign

8. Why Redesign?

13. 150,000
112,500
75,000
37,500
0
2005 2006 2007 2008

15. Why Redesign?
• Confusing Navigation
• New Audience
• New Logo/Branding

16. When NOT to
redesign?

17. When NOT to redesign
• Jones syndrome
• Bleeding edge
• If it works, don’t scrap it, tweak it
• Your boss wants it

18. Before you
Begin

19. Identify Team

20. Identify Team
Strategist

21. Identify Team
Strategist
Project
Manager

22. Identify Team
Strategist
Project
Designer
Manager

23. Identify Team
Strategist
Project
Designer Developer
Manager

24. Identify Team
Strategist
Project Content
Designer Developer
Manager Writer

25. Should You Outsource?
• Talent
• Time
• Resources

26. Outsourcing Tips
• Get References
• Single Point of Contact
• Single Firm
• Clear Expectations
• Don’t Micro-Manage

27. Communication Tools
www.skype.com
Basecamp
www.basecamphq.com
www.getharvest.com

28. Workflow
Cycle

30. Strategy:
Doing the right thing
Tactics:
Doing it the right way

31. Who?

32. Who?
Strategist

34. Ask Right Questions

35. Tools

36. In Person Meeting

38. In Person Meeting

40. In Person Meeting

44. Strategy Document
• High Level Goals and Benchmarks
• Audience Profile/Personnas
• Feature List
• Estimated Costs
• Estimated Timelines
• Sign-off by stake holders

46. Strategy Document
• High Level Goals and Benchmarks
• Audience Profile/Personnas
• Feature List
• Estimated Costs
• Estimated Timelines
• Sign-off by stake holders

48. Who?

49. Who?
Strategist
Project Content
Designer Developer
Manager Writer

50. Blue Prints
• Creative Brief
• Site Map
• Wireframes
• Technical Specifications (opt)
• Content Delivery Plan
• SEO Keyword Research and Recos (opt)
• Re-estimate of the Project

51. Creative Brief
• Project Summary
• Target Audience
• Primary Goals
• Perception/Tone/Feel

54. Technical Specifications
• Hosting Environment
• Programming Languages
• Architecture / Tools
• Specifications for New Features

55. Content Delivery Plan

56. Re-estimate
• Budget
• Schedule

58. Who?

59. Who?
Designer

62. Who?
Project Content
Designer Developer
Manager Writer

63. Process
• Review Blue Prints and Schedule
• Set File Structure
• Slicing and Optimizing Images
• Creating HTML Templates and Pages
• Integrate Backend development
• 301 Redirects

64. Testing
• Design Check
• HTML Check
• Functionality Check
• Content Check
• Stakeholder Approval

65. Handoff
• Production Style Guide
• Training

67. Maintenance Schedule

70. Workflow
Cycle

71. Resources/Credits
• 5Q Team & Clients
• Gospelcom Conferences
• iStock Photo • Web Redesign 2.0:
Workflow that Works
www.istockphoto.com
by Kelly Goto and
Emily Cotler

72. Chad Williams
chadw@5Qcommunications.com
www.5Qcommunications.com