Stories of Discovery: A responsive journey

Post on 11-Aug-2014

8.047 views 2 download

description

Transforming a government website with 200 content authors, tens of thousands of pages, and close to 100 different content templates into a responsive design system is tricky business. In 2013, we led a project to update and future-proof one of Canada’s fastest-growing municipalities’ main communication channel: Surrey.ca. The responsive redesign achieved unanimous support from city staff, business stakeholders, council, and the mayor. Mobile traffic has increased by 300% since launch. The improved governance and content workflow processes have facilitated new collaborations between silo’d City departments. The Surrey Web Team described this as one of the most positive changes in recent history for the City’s external and internal communication. Most importantly, it created a sense of cohesion through a wholehearted responsive design process. This project required a new approach. We needed the ability to connect deeply with everyone on our project team: client, vendor, and audience. We needed to get comfortable with imperfection, and fight through difficult moments as a team. We let go of our usual need to protect ourselves and maintain control, and worked together to solve our responsive design and adaptive content problems. Our collaborative creativity was a catalyst for changing the way the City communicates. What you’ll take away from this talk: - Understand how a responsive design process impacts team dynamics and workflow - Learn how to encourage collaboration across departments and conquer organizational silos - Hear how a responsive discovery can change a project (and why that’s okay) - Get cozy with your customers, stakeholders, and content authors – we’re all allies in the fight to make the web a better place

Transcript of Stories of Discovery: A responsive journey

RepublicOfQuality.com

vimeo.com/15266890

surrey.ca show map of lower mainland

The heroprocess they wanted

The process they needed

think about your message

the team

awwww

republicofquality.com/working-together

Silos are for farming, not web design

work together... weird, eh*?* Canadian content

be careful to watch your back :)

create an environment for unplanned moments of discovery

audit all the things!

ux vision & design principles

collaborative sketching

Call to action!

Lost call to action...

Call to action!

Call to action!

phone calls!!

mental models

http://bit.ly/11SF16J

empathy & experience mapping

mappingexperiences.com

audience profiles

Project Analysis

be willing to adapt yourself

real discovery happens between the planned activities

in-browser wireframes

http://en.wikipedia.org/wiki/Comparison_of_Android_devices

Surrey.ca

in-browser designs

Surrey.ca

celebrate successes together

don’t stop discovering

lunch & learns

WEB TEAMALL TEAM

WORKING WITH THE CITY OF SURREY WEB TEAM

BUSINESS UNIT

DOCUMENT FUNCTIONALREQUIREMENTS

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 campaignsIT should be present for applications

2 MONTHS BEFORE LAUNCH

WT SPECIALIST:Document all functional andtechnology requirements

Sign-off by BU and WTrequired

WT EDITOR:Document all content andeditorial requirements

Sign-off by BU and WTrequired

BU EDITOR:Gather initial content and functional requirements.

Fill out “Starting a web project”questionnaire (forthcoming)

BU MANAGER

CREATE FUNCTIONAL REQUIREMENTS

EDITCONTENT

PUBLISH

FINAL APPROVAL

REVIEW/EDIT/ARCHIVE CONTENT[EVERY 12 MONTHS]

REVIEW ANALYTICS[EVERY 6 MONTHS]

SUBMIT TO WORKFLOW

CONTENT ENTRYAND MIGRATION

CONTENT APPROVAL

BU EDITOR:Migrate all new contentinto OpenText CMS

1 WEEK BEFORE LAUNCH

BU EDITOR:Migrate all new contentinto 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 guideand semantic content (if neccessary)

in parallel:

WT SPECIALIST:Build all necessary functionaland technical requirements

collaboration is the key !

there is only one team

Thanks! !

republicofquality.com @hellofisher