Responsive Discovery: The underpants of a great web project
8 likes1,472 views
The document emphasizes the importance of user experience and content strategy in web design, advocating for a human-centered approach. It discusses discovery processes that focus on understanding intrinsic motivations and fostering collaboration among teams. The text also highlights the need for flexible content strategies, effective communication methods, and ongoing evaluation of projects to ensure continuous improvement and success.
![PUBLISH
FINAL
APPROVAL
REVIEW/EDIT/ARCHIVE CONTENT
[EVERY 12 MONTHS]
REVIEW ANALYTICS
[EVERY 6 MONTHS]
UNCH
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](https://image.slidesharecdn.com/responsive-discovery-confab-130604100739-phpapp02/85/Responsive-Discovery-The-underpants-of-a-great-web-project-187-320.jpg)
![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-confab-130604100739-phpapp02/85/Responsive-Discovery-The-underpants-of-a-great-web-project-188-320.jpg)
Responsive Discovery: The underpants of a great web project
- 2. We love Canada. You should too.
- 3. In Canadian airports you run into other content strategist. www.datawithasoul.com
- 4. FACT!
- 6. Find Steve on twitter @hellofisher Steve is the content nerd-herder and responsive design fanatic at The Republic of Quality. He leads the charge on the creative end of our projects, coordinating research, strategy, visual and interaction design, and content strategy. CONTACT STEVE 604-368-2151 / [email protected]
- 7. I believe that what I do saves the world (one web project at a time). The UX and Content Strategy is altruistic. We’re here to make the world a better place.
- 9. republicofquality.com The Republic of Quality is a user experience design firm. We put people first and find opportunities for organizations to innovate and grow.
- 10. I love to run
- 11. My family is great. @shannonfisher
- 12. I have a dog that looks like a deer. @slonefisher
- 13. I have an amazing daughter that is sassy and confident. I love that.
- 14. She keeps tabs on me...
- 17. yellowpencil.com Yellow Pencil has been building accessible web solutions since the Internet was just a baby. They develop and implement content first solutions for complex web projects.
- 21. Running is hard and fun!
- 22. Alaine Intro
- 23. Alaine Intro
- 24. Alaine Intro
- 25. Alaine Intro
- 26. Alaine Intro
- 27. Alaine Intro
- 50. Going to talk about the process.
- 51. Responsive design won't fix your content problem. This talk isn't about just CS, UX, or responsive design A responsive discovery is about people and what they really need. It isn’t about media queries. In fact it isn’t different from any kind of discovery...
- 52. Early on... how I have grown to see the world Discovery is where you find out what you don't know http://confabevents.com/blog/my-opinion-is-fact
- 53. Discovery is about finding the why.
- 54. Move from the inside out. Extrinsic vs intrinsic motivation. The Golden Circle - http://youtu.be/qp0HIF3SfI4
- 55. Brings me to the question of what drives us? Extrinsic vs intrinsic. Is it a motivation 2.0 or 3.0 thing? People don’t believe in what you do, they believe in why you do it. These were just some examples. What will your aha! moment be?
- 65. At RoQ we focus on a human approach.
- 67. What = undead
- 68. Why = remaining human in the face of it all. The web is about human interactions.
- 69. We focus on features and devices but that’s not right.
- 70. The web isn’t a bunch of machines. It is a bunch of humans.
- 75. We need to remember that each connection on the web is a connection with another human. We are trying to become wholehearted
- 76. We talk about process a lot, but it is just a concept. An ideal www.responsiveprocess.com
- 77. But that’s not how MS project works
- 79. The heroprocess they wanted Often we want all the super powers.
- 80. The process they needed ■ where we needed to adjust ■ page tables ■ voice and tone ■ writing guidelines ■ static design comps ■ What we did ■ governance ■ lunch and learns ■ what the web is, what it can do, how to get involved ■ Presentations ■ Four times ■ to who and what happened ■ lessons learned
- 81. surrey.ca
- 82. think about your message
- 83. Sometimes we put the right message out there the wrong way. We need to discover what to communicate, and how, but also why.
- 84. Sometimes we put the right message out there the wrong way. We need to discover what to communicate, and how, but also why.
- 85. the team
- 86. It’s a puppy! She’s cute and will love my family unconditionally!
- 87. awwww
- 88. She just wants to be with me.
- 90. business goals
- 91. What they tell you they want
- 92. What they actually want
- 93. What they end up doing...
- 94. The things they are really proud of!
- 95. How they interact with their peers
- 96. The things they love to do and how they see themselves
- 97. Those special moments where the real dog comes out
- 98. How we help them
- 99. republicofquality.com/working-together Silos are for farming, not web design What works and what doesn’t. It is about interdisciplinary teams (both vendor and client) coming together. No EGOS, no SILOS, just working together.
- 100. Alaine Intro The things we experience together
- 101. work together... weird, eh*? * Canadian content
- 102. Sitting together doesn’t always mean working together. Location is nice, but isn’t and can’t be the whole picture. Talk about remote working (client and rest of team)
- 103. When you work together you can experience things together. This also happens online and through successes
- 104. And through debates.
- 105. Location is nice, but isn’t and can’t be the whole picture. Remote working with the team can be rewarding and enlightening.
- 106. This is Steve laughing at something he knows Alaine will be horrified by.
- 107. Sure enough. Alaine = horrified. Moment shared and bonding established.
- 108. be careful to watch your back :) Also, watch your back. When teams start to bond they also start to have a little more fun. Steve = brony.
- 109. The team is everyone. Not just your company
- 110. being social is where you have more little discoveries.
- 111. Working together with the extended team. The client! The Surrey Firefighters came by to present Yellow Pencil and Steve with a frame token of their appreciation for the work we had done. Because Steve was working on-site at the City of Surrey a day a week moments like this could happen.
- 112. create an environment for unplanned moments of discovery
- 113. ux vision & design principles
- 116. This is done together, not alone in a room.
- 117. phone calls!!
- 118. Did you know this is also a PHONE!?
- 119. audit all the things!
- 125. mental models
- 126. This is where I live. Manor House
- 127. We love it there. Peaceful and close enough to everything. Describe the criteria
- 128. Started to notice things at dusk after moving in
- 129. A few more...
- 131. Umm...
- 132. seriously! These are the things you discover when you immerse yourself into the situations
- 133. http://bit.ly/11SF16J Typical card sort. People coming in. Whoever is available and interested. Out of context
- 134. You have great discoveries like...
- 135. What if we went to them?
- 140. empathy & experience mapping
- 148. Understanding the journey that people take to accomplish things is important
- 149. audience profiles
- 150. Project Analysis Surrey: had them already Drupal: opened up feedback to everyone
- 151. Personas, audience profiles Create them based on real people
- 152. be willing to adapt yourself What if an entire content strategy project had to change?
- 153. I can think of myself as superman. I know everything and can do anything.
- 154. Truth is, I’m more Clark Kent than superman. I get surprised
- 155. I make assumptions and I’m wrong a lot.
- 156. We have to be flexible and look for opportunities. Being wrong just means we’ve discovered something new we didn’t know before.
- 164. Real discovery happens between the planned activities
- 171. in-browser wireframes People don't understand spreadsheets and abstract content plans – show them the real thing
- 172. Surrey.ca Show us where the design and the content breaks. We can then iterate quickly and often. Plus, everyone could test and understand the concepts on THEIR device. So many a-ha moments.
- 173. in-browser designs
- 174. Surrey.ca We had planned for some static design elements, but found that we didn’t need them. This was due to the relationship and uniqueness of this project. Also, seeing the in-browser design comps with real content gave us even deeper insight into how the content would work.
- 178. The roadmap continues! Discoveries that couldn’t be tackled in the prior phase of the project get tackled now and in the future!
- 179. Broken out and given priorities. This is done in collaboration. Client and vendor.
- 180. lunch & learns
- 181. 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 EDITOR: 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 Seeing how the web can transform how business units work together and communicate
- 182. WALL TEAM BUSINESS UNIT KICK-OFF MEETING APPROVE CONTENT REQUIREMENTS GATHER CONTENT REQUIREMENTS CONTENT REQUEST BU MANAGER BU + WEB TEAM: Meet to discuss project requirements and timeline. BU EDITOR: Gather initial content and functional requirements. Fill out “Starting a web project” questionnaire (forthcoming) BU MANAGER
- 183. WEB TEAMALL TEAM DOCUMENT FUNCTIONAL REQUIREMENTS DOCUMENT CONTENT REQUIREMENTS KICK-OFF MEETING ary editorial content 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 rthcoming)
- 184. EDIT CONTENT DOC CONTENT APPROVAL DRAFT CONTENT BU EDITOR: BU MANAGER: Approve all editorial content 1 MONTH BEFORE LAUNCH BU EDITOR: Create all necessary editorial content 2 MONTHS BEFORE LAUNCH
- 185. CREATE FUNCTIONAL REQUIREMENTS EDIT CONTENT 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
- 186. CO SUBMIT TO WORKFLOW CONTENT ENTRY AND MIGRATION BU EDITOR: Migrate all new content into OpenText CMS 1 WEEK BEFORE LAUNCH BU EDITOR: Migrate all new content into OpenText CMS
- 187. PUBLISH FINAL APPROVAL REVIEW/EDIT/ARCHIVE CONTENT [EVERY 12 MONTHS] REVIEW ANALYTICS [EVERY 6 MONTHS] UNCH 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
- 188. 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
- 189. 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 EDITOR: 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
- 190. discovery should inspire you Nice to have