Empathy For The Devils

Preview:

DESCRIPTION

This might be a a familiar tour through the small circles of hell we go through toward CMS readiness. Many of the gremlins and demons we encounter can be exorcized, destroyed or made our pets. Sprinkled with insights and examples, it's a manifesto on recognizing the challenges we'll face, and imagining a future we can build for a better author experience.

Citation preview

Empathy For The DevilsBETTER AUTHOR EXPERIENCES FOR CONTENT MANAGEMENT

Content is some serious wizard sh*t.

THERE ARE STILL DEVILS & DEMONS.

They’re congratulating us for our hacks.

Data

Data Access

Business Logic

Presentation

This is a publishing

problem.

They’re judging the health of a platform by

the whitepaper, not the talent pool.

SKYNET WILL NEVER HAPPEN,

BECAUSE WE HAVE I.T.

DEPARTMENTS.

Some days, just waking up is

change management.

THIS IS A

PEOPLE PROBLEM.

We will not solve it with more knobs.

The loudest one in the front-end design

process will never touch one damn knob in

the CMS.

requestor

publisher

UI

Style &Guidelines

Troubleshooting

Policies

Initial Migration

Planning

Editorial

Curation

Product

Publish

CMS

Enter & Edit Render Stage, Review & QA

Articles

Reports

Measure

Collections

Approvals

Insights

Pitch & Request

Revision

Select Template

Where’s the commitment?

requestor

publisher

UI

Style &Guidelines

Troubleshooting

Policies

Initial Migration

Planning

Editorial

Curation

Product

Publish

CMS

Enter & Edit Render Stage, Review & QA

Articles

Reports

Measure

Collections

Approvals

Insights

Pitch & Request

Revision

Select Template

Where’s the commitment?

IT'S EASIER TO DERAIL TRAINS THAN TO MAKE THEM RUN ON

TIME.

Nobody should remain abstract about "content first".

source: @karenmcgrane

Lead with the stuff any way you can.

Structured (titles, intro text, section headings)

Body content zones (numbered by the page table)

Microcopy, dynamic content & tiles

It’s up to us to break the design.

The Future

What if there was an author experience that

just dealt with the editorial intent?

What if we had inline markup, collaboration & version control for

blobs?

What if we had wireframe edit modes,

previews with context & simpler workflows for

chunks?

What if we had skilled humans to decide what

goes in a chunk & what goes in a blob?

Team Chunk

Publish

CMS

Check for Context

Stage, Review & QA

Team Blob

Measure

Editor Curates

Approvals

Insights

Pitch & Request

Fix it!

Select Template

Teams organized for content

Reports

IT’S GOING TO TAKE AN ARMY TO GET ALL OF THIS CONTENT

OUT.

CONSIDER YOURSELF

DEPUTIZED.

Thank YouQ&A

Recommended