82
Websites are a symptom, not the cause RENDER CONFERENCE. MARCH 2017 Sally Jenkinson @sjenkinson

Websites are a symptom, not the cause

Embed Size (px)

Citation preview

Page 1: Websites are a symptom, not the cause

Websites are a symptom, not the cause RENDER CONFERENCE. MARCH 2017 Sally Jenkinson @sjenkinson

Page 2: Websites are a symptom, not the cause

Hello!@sjenkinson

Page 3: Websites are a symptom, not the cause
Page 4: Websites are a symptom, not the cause

“HealthCare.gov, the $630 million online insurance marketplace, was a disaster after it went live…”

http://www.nytimes.com/2013/12/01/us/politics/inside-the-race-to-rescue-a-health-site-and-obama.html

New York Times

Page 5: Websites are a symptom, not the cause

“The rollout of Healthcare.gov in 2013 under former President Barack Obama, to name a related example, was a disaster.”

https://newrepublic.com/article/141203/trumpcare-already-dead

New Republic

Page 6: Websites are a symptom, not the cause

“Even Obamacare supporters had their faith shaken by Obama’s broken promises about keeping existing plans, premiums declining by $2,500, and the disastrous website roll-out.”

https://www.theatlantic.com/health/archive/2017/01/is-obamacare-just-a-branding-problem/512936/

The Atlantic

Page 7: Websites are a symptom, not the cause

“The first step is to get rid of Obamacare, which was a total disaster," Gianti said. "It was designed to fail, and taxpayers had to waste money on that failed healthcare.gov website.”

http://talkingpointsmemo.com/dc/trump-inauguration-attendees-cheer-failed-socialist-experiment

TPM

Page 8: Websites are a symptom, not the cause

When websites have problems, people remember.

Page 9: Websites are a symptom, not the cause

When your website project becomes synonymous with failure

Page 10: Websites are a symptom, not the cause
Page 11: Websites are a symptom, not the cause

“Bad impressions and bad stereotypes are quicker to form and more resistant to disconfirmation than good ones.”

Roy F. Baumeister, Ellen Bratslavsky, Catrin Finkenauer, Kathleen D. Vohs

BAD IS STRONGER THAN GOOD

Page 12: Websites are a symptom, not the cause

Turn this focus to your advantage

Page 13: Websites are a symptom, not the cause

Don’t just make websites.

Use websites to point you in the direction of everything that could be better.

Use web technologies to start thinking outside of limited approaches.

Page 14: Websites are a symptom, not the cause

Identifying issues 01

02

03

04

Why do any problems exist?

How can we apply our web thinking elsewhere?

How do we make things better?

Page 15: Websites are a symptom, not the cause

Identifying issues 1 Uncovering everything that could be better

Page 16: Websites are a symptom, not the cause
Page 17: Websites are a symptom, not the cause
Page 18: Websites are a symptom, not the cause
Page 19: Websites are a symptom, not the cause
Page 20: Websites are a symptom, not the cause

Technical discovery

Page 21: Websites are a symptom, not the cause

There are so many

factors to consider on any project

recordssoundthesame.com/wp-content/uploads/2013/04/startingpoints-FINAL.pdf

Page 22: Websites are a symptom, not the cause

Digital transformation

Page 23: Websites are a symptom, not the cause

Using a website as a lens

Page 24: Websites are a symptom, not the cause

“The system that got implemented was far too inflexible, so we’ve had to either stay be limited by it or come up with workarounds.”

Page 25: Websites are a symptom, not the cause

“We have to go back to our agency’s developers for every little change. This is expensive and takes forever.”

Page 26: Websites are a symptom, not the cause

“The site launched, but it’s incredibly slow compared to our old one and people are starting to complain.”

Page 27: Websites are a symptom, not the cause

“We’re not sure why but our analytics have shown that we’ve lost 80% of our traffic since the launch.”

Page 28: Websites are a symptom, not the cause

Extending expert reviews

Page 29: Websites are a symptom, not the cause
Page 30: Websites are a symptom, not the cause

Performance Accessibility Code review Responsive approach

Third party integrations Analytics

General attention to

detail

Extending expert reviews

Usability SEO Content

Page 31: Websites are a symptom, not the cause

Responsive approach

Page 32: Websites are a symptom, not the cause

Third party integrations

Page 33: Websites are a symptom, not the cause

General attention to detail

Page 34: Websites are a symptom, not the cause

Performance Accessibility Code review Responsive approach

Third party integrations Analytics

General attention to

detail

Extending expert reviews

Usability SEO Content

Page 35: Websites are a symptom, not the cause

gist.github.com/greywillfade/20f48ba67d799784040e

Page 36: Websites are a symptom, not the cause
Page 37: Websites are a symptom, not the cause
Page 38: Websites are a symptom, not the cause

Everyone is different

Page 39: Websites are a symptom, not the cause
Page 40: Websites are a symptom, not the cause
Page 41: Websites are a symptom, not the cause

Why do any problems exist? 2 Understanding root causes

Page 42: Websites are a symptom, not the cause

Root cause analysis

Page 43: Websites are a symptom, not the cause

Sakichi Toyoda and The 5 Whys

Page 44: Websites are a symptom, not the cause
Page 45: Websites are a symptom, not the cause

Fishbone/ Ishikawa diagramVisualise cause and effect

Page 46: Websites are a symptom, not the cause

People, processes, technology, & strategy

Page 47: Websites are a symptom, not the cause

People

Page 48: Websites are a symptom, not the cause

Technology

Page 49: Websites are a symptom, not the cause

Strategy

Page 50: Websites are a symptom, not the cause
Page 51: Websites are a symptom, not the cause

Process

Page 52: Websites are a symptom, not the cause
Page 53: Websites are a symptom, not the cause
Page 54: Websites are a symptom, not the cause

3 How can we apply our web thinking elsewhere? Using digital to transform more widely

Page 55: Websites are a symptom, not the cause

Root causes to make sites better

Web thinking to make other things better

Page 56: Websites are a symptom, not the cause

Web thinking to make other things better

Root causes to make sites better

Page 57: Websites are a symptom, not the cause

Being more proactive

Page 58: Websites are a symptom, not the cause
Page 59: Websites are a symptom, not the cause

“The sooner we can order parts, the sooner they come in, the sooner we’ll see a performance increase”

Page 60: Websites are a symptom, not the cause

1. Help the team to have a faster car, through more efficient processes.

2. Save time and money.

3. Provide staff with better tools and processes, removing frustrations (and helping them to get home on time!)

4. Be more sustainable into the future.

5. Better use technology to gain advantages on other teams.

Page 61: Websites are a symptom, not the cause

1. Help the team to have a faster website, through more efficient processes.

2. Save time and money.

3. Provide staff with better tools and processes, removing frustrations (and helping them to get home on time!)

4. Be more sustainable into the future.

5. Better use technology to gain advantages on competitors.

Page 62: Websites are a symptom, not the cause
Page 63: Websites are a symptom, not the cause
Page 64: Websites are a symptom, not the cause
Page 65: Websites are a symptom, not the cause

Use the web and digital principles to bring benefits to the wider business.

Page 66: Websites are a symptom, not the cause

Building for the future 🚀

Page 67: Websites are a symptom, not the cause
Page 68: Websites are a symptom, not the cause

Making change happen4 How do we make things better?

Page 69: Websites are a symptom, not the cause

Communicate improvements

Standards and principles

Teach, don’t just do

Get the right team

Stay open

Page 70: Websites are a symptom, not the cause
Page 71: Websites are a symptom, not the cause
Page 72: Websites are a symptom, not the cause

Give people an easy way to understand why something matters.

Page 73: Websites are a symptom, not the cause

Communicate improvements

Standards and principles

Teach, don’t just do

Get the right team

Stay open

Page 74: Websites are a symptom, not the cause
Page 75: Websites are a symptom, not the cause
Page 76: Websites are a symptom, not the cause
Page 77: Websites are a symptom, not the cause

Communicate improvements

Standards and principles

Teach, don’t just do

Get the right team

Stay open

Page 78: Websites are a symptom, not the cause

Communicate improvements

Standards and principles

Teach, don’t just do

Get the right team

Stay open

Page 79: Websites are a symptom, not the cause

Communicate improvements

Standards and principles

Teach, don’t just do

Get the right team

Stay open

Page 80: Websites are a symptom, not the cause

ethanmarcotte.com/wrote/free-faster

Page 81: Websites are a symptom, not the cause

Identifying issues

Why do any problems exist?

How can we apply our web thinking elsewhere?

How do we make things better?

Page 82: Websites are a symptom, not the cause

Credits: flickr.com/photos/ideonexus/3776943478 commons.wikimedia.org/wiki/File:Lenteconv_3.svg Kepler 16-b courtesy NASA/JPL-Caltech

Sally Jenkinson

@sjenkinson [email protected] recordssoundthesame.com sallyjenkinson.co.uk

Thank you!