Stories of Discovery: A responsive journey
33 likes12,161 views
The document outlines a collaborative web design process for the City of Surrey, emphasizing the importance of teamwork and adaptability throughout various stages. It includes steps for project management, content requirement gathering, and functional documentation while highlighting the need for regular reviews and analytics to improve web performance. Overall, it advocates for a cohesive approach to web design where continuous discovery and collaboration are key elements.
![CREATE FUNCTIONAL
REQUIREMENTS
EDIT
CONTENT
PUBLISH
FINAL
APPROVAL
REVIEW/EDIT/ARCHIVE CONTENT
[EVERY 12 MONTHS]
REVIEW ANALYTICS
[EVERY 6 MONTHS]
SUBMIT TO
WORKFLOW
CONTENT ENTRY
AND MIGRATION
CONTENT
APPROVAL
BU EDITOR:
Migrate all new content
into OpenText CMS
1 WEEK BEFORE LAUNCH
BU EDITOR:
Migrate all new content
into OpenText CMS
BU MANAGER:
Approve all editorial content
1 MONTH BEFORE LAUNCH
WEB TEAM:
Compile analytics data from past 6 months
BU + WEB TEAM:
Meet with BU to review and recommend next steps –
edit or archive content
WEB TEAM:
Compile analytics data from past 6 months
BU + WEB TEAM:
Meet to review and recommend changes
WT EDITOR OR WT SPECIALIST
WT EDITOR + WT SPECIALIST
WT EDITOR:
Edit editorial content for
adherance to web writing guide
and semantic content (if neccessary)
in parallel:
WT SPECIALIST:
Build all necessary functional
and technical requirements](https://image.slidesharecdn.com/responsive-discovery-ias14-140328141554-phpapp01/85/Stories-of-Discovery-A-responsive-journey-160-320.jpg)
Stories of Discovery: A responsive journey
- 39. surrey.ca show map of lower mainland
- 41. The heroprocess they wanted
- 42. The process they needed
- 43. think about your message
- 51. the team
- 53. awwww
- 65. republicofquality.com/working-together Silos are for farming, not web design
- 67. work together... weird, eh*? * Canadian content
- 71. be careful to watch your back :)
- 73. create an environment for unplanned moments of discovery
- 74. audit all the things!
- 80. ux vision & design principles
- 85. Call to action!
- 86. Lost call to action...
- 87. Call to action!
- 88. Call to action!
- 95. phone calls!!
- 97. mental models
- 116. empathy & experience mapping
- 129. audience profiles
- 130. Project Analysis
- 132. be willing to adapt yourself
- 138. real discovery happens between the planned activities
- 146. http://en.wikipedia.org/wiki/Comparison_of_Android_devices
- 148. Surrey.ca
- 149. in-browser designs
- 150. Surrey.ca
- 156. lunch & learns
- 159. WEB TEAMALL TEAM WORKING WITH THE CITY OF SURREY WEB TEAM BUSINESS UNIT DOCUMENT FUNCTIONAL REQUIREMENTS DOCUMENT CONTENT REQUIREMENTS KICK-OFF MEETING APPROVE CONTENT REQUIREMENTS GATHER CONTENT REQUIREMENTS CONTENT REQUEST BU MANAGER BU + WEB TEAM: Meet to discuss project requirements and timeline. Marketing should be present for campaigns IT should be present for applications 2 MONTHS BEFORE LAUNCH WT SPECIALIST: Document all functional and technology requirements Sign-off by BU and WT required WT EDITOR: Document all content and editorial requirements Sign-off by BU and WT required BU EDITOR: Gather initial content and functional requirements. Fill out “Starting a web project” questionnaire (forthcoming) BU MANAGER
- 160. CREATE FUNCTIONAL REQUIREMENTS EDIT CONTENT PUBLISH FINAL APPROVAL REVIEW/EDIT/ARCHIVE CONTENT [EVERY 12 MONTHS] REVIEW ANALYTICS [EVERY 6 MONTHS] SUBMIT TO WORKFLOW CONTENT ENTRY AND MIGRATION CONTENT APPROVAL BU EDITOR: Migrate all new content into OpenText CMS 1 WEEK BEFORE LAUNCH BU EDITOR: Migrate all new content into OpenText CMS BU MANAGER: Approve all editorial content 1 MONTH BEFORE LAUNCH WEB TEAM: Compile analytics data from past 6 months BU + WEB TEAM: Meet with BU to review and recommend next steps – edit or archive content WEB TEAM: Compile analytics data from past 6 months BU + WEB TEAM: Meet to review and recommend changes WT EDITOR OR WT SPECIALIST WT EDITOR + WT SPECIALIST WT EDITOR: Edit editorial content for adherance to web writing guide and semantic content (if neccessary) in parallel: WT SPECIALIST: Build all necessary functional and technical requirements
- 161. collaboration is the key ! there is only one team