76
Platform Content

Platform ≠ Content

Embed Size (px)

DESCRIPTION

Slides from my talk about the difference between content and platform design and why it is essential to understand the difference. It explains why designers are uniquely qualified to solve some of the toughest problems facing newsrooms today. This talk explores how platform design is the new battleground for audience retention and how designers play a crucial role in building successful digital products.

Citation preview

Page 1: Platform ≠ Content

PlatformContent

Page 2: Platform ≠ Content

Thank you to my smart friends: Callie NeylanJeremy PennycookPaulo LopezMax PfennighausPatrick CooperBenjamin DauerWes LindamoodJosh HatchJoel SuchermanKinsey WilsonMiranda MulliganMichael Yoch

Ian AdelmanTyson EvansBill CouchMatt MansfieldJustin FerrellBryan HaggertyMatt ThompsonRon CoddingtonMichael ManessLaura RamosIrakli NadareishviliMarc Lavallee

Page 3: Platform ≠ Content

Louisville Slugger

Page 4: Platform ≠ Content

About me

•Newseum

•Knight-Ridder/Tribune

•SmartBrief

•USA TODAY

•NPR

•Twitter

Rockwell

Page 5: Platform ≠ Content
Page 6: Platform ≠ Content
Page 7: Platform ≠ Content
Page 8: Platform ≠ Content
Page 9: Platform ≠ Content
Page 10: Platform ≠ Content
Page 11: Platform ≠ Content
Page 12: Platform ≠ Content
Page 13: Platform ≠ Content
Page 14: Platform ≠ Content
Page 15: Platform ≠ Content
Page 16: Platform ≠ Content
Page 17: Platform ≠ Content
Page 18: Platform ≠ Content
Page 19: Platform ≠ Content

CONTENT

Newseum

KRT

USA TODAY

NPR

Twitter

PLATFORM

Page 20: Platform ≠ Content

Understanding the differences between the platforms is essential to creating good work.

Content design and platform design are different beasts.

Page 21: Platform ≠ Content

ContentExploratory

Specific

Custom

Storytelling

Pacing

PlatformRigid

General

Template-driven

Distribution

Wayfinding

The perfect page The perfect system

Page 22: Platform ≠ Content

What is the best way to tell this story?

What problem am I helping this reader solve?

Page 23: Platform ≠ Content

reporting the story

bandwidth

readabilitypacing

illustration

graphics

metrics

wayfinding

CMS

scale

sharing

CONTENT

PLATFORM

Page 24: Platform ≠ Content

“...like trying to make one pair of shoes fit everybody’s feet.”Jony IveFastCoDesign.com

Page 34: Platform ≠ Content
Page 36: Platform ≠ Content
Page 37: Platform ≠ Content

Digital news design is still broken.

•Many story pages still feel the same.

•Pages are filled with unnecessary junk.

•Things don’t work on mobile.

Page 38: Platform ≠ Content

Samey

Page 39: Platform ≠ Content

152 choices in the top nav.

Page 40: Platform ≠ Content
Page 41: Platform ≠ Content
Page 42: Platform ≠ Content

Unsolicited NYTimes redesign by Andy Rutledge

Page 43: Platform ≠ Content

Your competitive set?

Page 46: Platform ≠ Content
Page 48: Platform ≠ Content

Gmail = ubiquitous

Page 49: Platform ≠ Content

News / Information Consumption

News Orgs → ← Tech Orgs

Page 50: Platform ≠ Content

Jim Roberts Is Mashable’s Exective Editor and Chief Content OfficerMashable October 30, 2013

Page 51: Platform ≠ Content

Source: wikipedia

Jeff Bezos Says Washington Post Could Take a Page From AmazonABC NewsSeptember 25, 2013

Page 52: Platform ≠ Content

The battle for audience retention will be fought on the platform.

Design plays a crucial role in helping news organizations make digital products.

Page 53: Platform ≠ Content

How might design help create better experiences?

We must create beautiful spaces in which our audiences want to spend time.

Lots of time.

Page 56: Platform ≠ Content

Design thinking can help

•Context

•Research

•Empathy (user-centered)

•Synthesis → Insights

Page 57: Platform ≠ Content

Why?

•Answer the right questions

•Better answers, faster

•Proactive, not reactive

Page 58: Platform ≠ Content

Building great products can’t happen in dysfunction.

Our organizational structures are kryptonite to innovation.

Page 59: Platform ≠ Content

The baggage:

Paid to manage risk.

Distribution Content

Paid to tell stories.

vs.

Page 60: Platform ≠ Content

TechnologistsBetter!

ProductShepherds

User Experience

Page 61: Platform ≠ Content

Good experiences thrive in organizations where design is respected.

Page 62: Platform ≠ Content

Visual journalists are ready-made problem solvers.

•Ask questions

•Observation helps challenge status-quo

•Readers are fickle

Page 65: Platform ≠ Content

If you’re not agile, you’re doing it wrong.

•Small

•Multidisciplinary

•Empowered

•Accountable

Page 66: Platform ≠ Content

Fertilizer for Agile

•Clear strategic direction

•Co-location

•Mutual understanding

Page 67: Platform ≠ Content
Page 68: Platform ≠ Content

Evaluate and iterate

Page 69: Platform ≠ Content

Tappable prototype

Page 70: Platform ≠ Content

Understand how things work.

We say “build” for a reason.

Page 71: Platform ≠ Content
Page 72: Platform ≠ Content
Page 73: Platform ≠ Content

Handing a PSD to a developer does not make you a platform designer.

Knowledge of how things work is critical to making informed design decisions.

Page 74: Platform ≠ Content

Start small:

•Little experiments

•Skunk works can be cheap

•Google is free

•Show, don’t tell

•SHIP IT.

Page 75: Platform ≠ Content

Understanding the differences between the platforms is essential to creating good work.

Experience is everywhere.

Page 76: Platform ≠ Content

Thanks!

@dwjr