Split Personality

How to design new products in a small news organization


Emma Carew Grovum / @emmacarew

About me:

I am not actually...

A designer

A developer

An editor

A reporter


But, I've worked in all corners of the newsroom, and am now comfortable working with all of the above.

How did I become this person?

I was hired at FP to run social media and the homepage.

Then I...

  • Worked on a glitchy newsletter >> ended up overseeing all newsletters and launching a new one
  • Wanted better homepage tools >> ended up project managing the edit side of CMS rebuild

In small newsrooms, there often is not enough bandwidth to distinguish between product manager and project manager.

Now, on any given day, I am...

  • Headline writing for homepage stories
  • Choosing, recropping, swapping photos across the site
  • Troubleshooting general tech issues with reporters
  • Making quick hit graphics for stories
  • Filing bug requests with tech team
  • QAing updates from developers and sending feedback
These are 10 best practices I've learned while bouncing between tech and editorial the past year

Previously on...

Work and communicate like you've got a new team of aliens showing up to collaborate every day. Start at step 0 and assume that not everyone is up to speed at all times.

Start meeting recaps and project updates like TV shows do before new episodes, with a short "the story so far..." intro.

(especially if you are working with a new team or even just one person new to the process)

Kill scope creep early and often

Define "mission critical" and "minimally viable" upfront.

When someone says "ASAP", what does that actually mean??

How many top priority requests can exist at once?

Get organized

Like, really freaking organized.

  • Ticketing system (JIRA/Redmine. 1 task = 1 ticket)
  • Standing check-in meetings, daily email update, online chat
  • Choose a preferred screenshot and screencapture tool -- and teach people how to use it
  • Pick a non-Github place for documentation and files to live (Dropbox, Google Drive, etc) and keep it organized

YOU, call 911

One thing they teach lifeguards is to always designate a specific person to call 911 in an emergency, never saying, "someone call 911" and pointing vaguely into the crowd.

Be specific, especially in email communications. Assign tasks to people, not crowds.

Being vague wastes time

Don't waste time.

  • Don't send emails to report "the thing is broken" or that you "don't like this"
  • Be specific when you can: "this link goes to the wrong place" or "can we change the color on xyz-thing?"
  • Show don't tell: use annotated screenshots to report bugs that are hard to describe over email
  • Use screencapture gifs to show interactions that aren't working the way they should or that you expect.

Wireframes will only get you so far

If you're working with folks who aren't intimately involved with the nitty-gritty of how something is built, don't ask them to rely on sketches, mockups and wireframes only.

"Use your imagination" or "just pretend it doesn't look like this" isn't helpful for building bridges between teams.

All the "little things" add up

Tiny CSS bugs that feel like finishing touches for developers can add up quickly for the other side, making it hard to see progress.

If you can knock through a handful of small requests per week, it can buy you some goodwill on the stuff that will take much longer to solve.

Don't do things that don't work

What didn't work for us:

Unclear hierchy of stakeholders causes confusion

Revisiting decisions wastes time

Try to avoid a 23rd hour push

Hold people accountable for deliverables

Everyone can help with user testing!

If your staff can't use your website/app/product, your audience probably won't be able to use it.


But, QA-ing a project isn't something journalists do every day. Take the time to explain exactly what feedback you are looking for, and how to best report it.

Manners

It sounds dumb, but "please" and "thank you" go a long way -- especially on deadline, especially late at night, especially over email, especially you're so sick of looking at each other, your screens, and your project.

Giving your teammates the benefit of the doubt and assuming best intentions can help protect everyone's sanity.

Tips for staying sane through it all

Be realistic and manage expectations.

(to be honest, this is about 50% of the job)

Sometimes you have to be the bad cop. And it kind of sucks.

You still have to do your actual job.

Try changing venues often.

Do the things that only you can do.


Don't do the things that someone else could just as easily do.

Questions?

Thanks!

Slides are available at: http://ecarewgrovum.github.io/SNDDC-slides/#/

Downloadable PDF