desk-net - editorial days - main slides - 2016-06-09

1

Twitter: #ed16 Wifi: m3connect or mercure User: editorial Password: days16

2

09:30 Welcome

09:35 Desk-Net review & preview

10:00 Content Planning Best Practices

10:45 Planning is more important than everDominic Ramel (Head of Planning @ Berner Zeitung)

11:10 Coffee break

11:25 Editorial transformation at Time Inc. UK Andrew Derrer (Senior Media Transformation Advisor @ Time Inc. UK)

11:55 Learnings from rolling out Desk-Net Robert Dönges (Managing Editor @ Südwest Presse)

12:30 How Desk-Net will support your roll-out

12:45 Lunch

3

13:45 Modular systems at Neue Zürcher Zeitung Andi Maerz (Project Lead)

14:10 Best-of-breed editing tool –LivingDocsGabriel Hase (Co-Founder)

14:30 Modular newsroom systems –how we see it

15:00 Desk-Net goes mobile

15:10 Coffee break

15:30 Desk-Net and your Content Management System

16:20 Slack, Hipchat and Desk-Net?!

16:40 Desk-Net – our roadmap for the next twelve months

17:00 End

Discussion/session for attendees from Magazinesand Departments ofCommunication

4

09:30 Welcome




11:10 Coffee break




12:45 Lunch

5

+26%

Visits (Jan – May 16 vs. Jan – May 15)

6

~ 161 000

stories entered per month(April 2016; ~ +25%)

8

Lost customersin 2015 and 2016YTD

9

More and more Desk-Net employees working for you

June 2015

Team size: 15(some part-time)

November 2015


June 2016

Team size: 22+(some part-time)

10

Custom Statuses

Cleaned up layout & entry fields

Mobile (almost done)

Performance

11

More and more Desk-Net employees working for you

June 2015


November 2015


June 2016

Team size: 22+(some part-time)

12

09:30 Welcome




11:10 Coffee break




12:45 Lunch

13

0% 20% 40% 60% 80% 100%

Planning horizons vary greatly

Top 5 newsrooms

Bottom 5 newsrooms

Stories for next 6 days

Stories planned morethan 6 days ahead

Planning horizons for newsrooms working with daily news

14

The individual authors/reporters need to enter theirown stories

_ Having someone else, e.g. a secretary enter a story createsunnecessary work and a time lag

_ Based on our interviews the dependability of users enteringtheir own stories varies significantly from customer tocustomer

_ Task for editorial top management

_ to provide understanding in the editorial department why this isimportant and

_ to enforcen this procedure(„A story that‘s not in Desk-Net won‘t get published.“)

15

There are exceptions to the rule of individual usersentering their stories

_ Stories based on appointments / press invites:

_ Typically best to have one responsible person, e.g. secretary, monitor the editorial department‘s inbox and forwardappointments to Desk-Net

_ In many cases they are making a preliminary accept/rejectdecision

_ In at least one case a secretary handled the task of accepting and assigning stories herself for routine stories

_ Stories from news feeds

_ Monitoring of the news feed at a central desk

_ Entering and assigning done by central news manager

16

What and how to enter?

_ Enter story in an understandable way

_ Third person must be able to make informed decisions

_ OK to accept a story pitch?

_ Add a video?

_ Where to publish it?

17

What and how to enter?

_ Enter story in an understandable way

_ Third person must be able to make informed decisions

_ OK to accept a story pitch?

_ Add a video?

_ Where to publish it?

_ Integrations with Content Management Systems will makeentering correct & comprehensive information even moreimportant

18

Regional publisher Mittelbayerische Zeitung defines theflow across platforms when entering a story (I)

19

Regional publisher Mittelbayerische Zeitung defines theflow across platforms when entering a story (II)

20

Determining Best Practices in editing stories is difficultas the workflows and needs strongly vary fromcustomer to customer

_ Editing of existing stories heavily depends on a customer‘sneeds, but a few aspects can be hightlighted:

_ Often heavy editing of stories, e.g.

_ assigning to other platforms

_ adding formats

_ moving publication dates

_ Editing in editorial meetings: Online, e.g. with an iPad

_ And we expect heavy usage of our upcoming mobile web app

_ Important : Think about others, think about the next day

_ One of our customers does a final review at the end of the day

21

New / Pitch Yes

No

Question

Optional

Accepted

Top Story

Mandatory

Ready for editing

Moved toCopy

In Production

Exported toCMS

Published

Proposal

Decision makingPrioritysetting

Production

Our customers‘ status levels can be structured intothree groups

22

New / Pitch Yes

No

Question

Optional

Accepted

Top Story

Mandatory

Ready for editing

Moved toCopy

In Production

Exported toCMS

Published

Proposal

Decision makingPrioritysetting

Production

23

A red icon depicts a story that won‘t be published or an event that won‘t be covered at local publisher WZO

24

How many of all published stories should be enteredinto Desk-Net?

Complex, large editorialorganisation

Small organisation

25



Focussed on story planning

Used to trackworkflow / statusses

Small organisation

26



Focussed on story planning

Used to trackworkflow / statusses

(Almost) All storiesshould bein Desk-

Net

Just the main storiesentered in Desk-NetSmall

organisation

27

09:30 Welcome




11:10 Coffee break




12:45 Lunch

28

09:30 Welcome




11:10 Coffee break




12:45 Lunch

29

09:30 Welcome




11:10 Coffee break




12:45 Lunch

30

09:30 Welcome




11:10 Coffee break




12:45 Lunch

31

11 741

monthlyactive users

(MAU)9 382

weekly activeusers

(WAU)

Our users are using Desk-Net very regularly

32

09:30 Welcome




11:10 Coffee break




12:45 Lunch

34

Same software for everyone

–hugely different ratings

35

And yes, we do listen tothose replies

–very very much actually

36

„Clarity“Ease-of-use

Speed

(Self-refreshing pages)

Top requests of our users:

37


Speed



Will be implemented in Winter 2016/2017

(it‘s not that trivial…)

38


Speed



Lots of improvements in early 2016.

Ongoing…

39


Speed



Strong request – and fuzzy request.

When we ask, we get no answers.

40

Our roadmap to address Clarity and Ease-of-Use:

_ Remove unnecessary elements (ongoing)

_ Review/streamline entry and editing processes (ongoing)

_ Refresh design (Summer/Fall 2016)

_ Drag & Drop (Summer/Fall 2016)

_ Self-refreshing pages (Winter 2016/2017)

41

We used to repeat

News > International

here.

42

We are reducing the amount of additional informationwe display in the story boxes

+2

Currently

August 2016

43







47







54

This is important!Clean design on white

background

This not so much.Clean design on white

background

55

Improvements in the My Schedule layout brought greattraffic gains compared to the overall traffic increase

80%

100%

120%

140%

160%

180%

200%

January 2015

All pages: +36%

My Schedule: +91%

May 2016

56

09:30 Welcome




11:10 Coffee break




12:45 Lunch – until 13:45 (1:45pm)

57





15:10 Coffee break




17:00 End


58





15:10 Coffee break




17:00 End


59





15:10 Coffee break




17:00 End


60





15:10 Coffee break




17:00 End


61

Eier legende Wollmilchsau

62

Editorial System

„that does everything“ Print

Digital

63

Editorial System

„that does everything“

Content Management System

for online

Archive

Digital

Print

64

Editorial System

„that does everything“


for online

Archive

Digital

Print

65

Online firstCMS the dominant system

Need for better softwareBest-of-breedsolutions

Speed, agilitySoftware-as-a-service

Cost efficiency Cloud solutions

ConnectivityREST API, potentiallywebhooks

66

Editorial System

„that used to promiseto do everything“


for online

Digital

Print

67

Editorial System



for online

Digital

Print

68






69

Source: Business Insider

70

Processes software has to cover nowadays

Software needs to cover a lot more processes thansome five, ten or twenty years ago

Processes softwarehad to coverpreviously

71

No single company can offer a

software that even remotely addresses

all software-related processes –

especially not with the necessary

quality and development speed.

72

The Washington Post‘s new „system“ is a collection oflinkek, but independently usable tools

73

The Washington Post‘s new „system“ is a collection oflinkek, but independently usable tools

74






75






76






77

And ever more software is hosted outside of thecompany‘s network

78

Native cloud solutions are taking over from on-premisesolutions

_ On-premise

Hosted and maintained on company‘s own servers

_ „Fake cloud“

Hosted by vendor, but oftensame old software

_ Cloud

Hosted at best-of-breed datacenters

_ Native cloud solutions

Features such as Desk-Net‘scross-account connectioncapability

Rented software per userdepending on other flexible criteria

REST API for connection to othersystems

79

Our API is documented at api.desk-net.com

80






81

Main integrations scenarios and directions for Desk-Net

Online Content Management Systems

Legacy Editorial Systems

Digital Asset Management Systems

Page Planning

Event Feeds

Calendar

Chat

82





Page Planning

Event Feeds

Calendar

Chat

83





Page Planning

Financial / Payment Systems

Event Feeds

Calendar

Chat

84





Page Planning

Financial / Payment Systems

Event Feeds

Calendar

Tracking tools(Chartbeat, Google

Analytics)

Chat

85

Editorial System



for online

Digital

Print

Often rather strong

workflow capabilities

Often rather weak

workflow capabilities

86

Editorial System



for online

Digital

Print

Desk-Net will improve

its workflow capabilities

87





15:10 Coffee break




17:00 End


91

Our near-term roadmap for the mobile version

Late Mayalpha release tolimited test group

• Login/logout• Story lists• My Schedule

Early/mid JulyPublic betarelease

• Login/logout• Story lists• My Schedule• Story/event

editing• Improvements

based on feedback

SeptemberEnd of beta phase

• Login/logout• Story lists• My Schedule• Story/event

entry/editing• Event lists• Absences

entry/editing

OngoingContinuousdevelopment

Decision on native apps for Android and iOS

92

https://desk-net.com/m/mobile.htm

We are sending this URL to you as we speak – no need to type it in yourselfThis is just the second version of our alpha version – very limited in scope (no editing, no menus)Do not share with (many) colleaguesPlease do provide feedback to [email protected]

93

https://desk-net.com/m/mobile.htm

We are sending this URL to you as we speak – no need to type it in yourselfThis is just the second version of our alpha version – very limited in scope (no editing, no menus)Do not share with (many) colleaguesPlease do provide feedback to [email protected]

• We are sending this URL to you as we speak – no need to

type it in yourself.

• This is just the second version of our alpha version – very

limited in scope (no editing, no menus).

• Do not share with (many) colleagues, yet.

• Please do provide feedback to [email protected]

94





15:10 Coffee break




17:00 End


95





15:10 Coffee break




17:00 End


96

Multiple integration projects are currently going on

In partnership with vendorsand integrators:

_ LivingDocs_ scheduled for integration

_ Woodwing Content Station_ close to roll-out; integrator A&F

_ Woodwing Elvis_ Live (ftp export)

_ EidosMedia_ project at Tamedia ongoing

_ Infomaker - Writer_ concept phase ongoing

_ Vjoon‘s K4_ early talks with integrators

_ Other Scandinavian CMS provider

_ early talks

_ We are working on ourown integrations:

_ WordPress plugin_ development ongoing

_ Drupal_ after release of WordPress

plugin

_ Potentially Joomla and others after that

97

_ In development

_ Release schedule for late Q3

_ Two-way integration

_ Desk-Net � WordPress

_ WordPress � Desk-Net

_ Blueprint for the Drupalintegration

98

Users plan and manage their stories in Desk-Net

99

Tom Peters

Once a story is in a specific status we hand over data toWordPress where it appears in the story list.

100

This is a story with a text assignment for Tom Peters. And it is scheduled for publication in the website's News section on Monday, March 7th, 3:00pm (15:00).View in Desk-Net

The article can then be created and edited in the CMS –but a lot of data is pre-entered.

101


The article can then be created and edited in the CMS –but a lot of data is pre-entered.

102


The story is published either at the pre-defined time orat any other time.

103

Once the story has been published the CMS informsDesk-Net about the updates made to the story.

104

_ Ongoing project at Tamedia ofSwitzerland

_ Interest signalled by other majorEidosMedia customers

_ Initially a one-way integration

_ Desk-Net � EidosMedia Méthode

105

Mapping between DeskNet & Méthode – Méthode Topic

106

Mapping between DeskNet & Méthode – DeskNet Story

107

_ Integrator A&F (Switzerland) has built a connector for Content Station

_ Works, will be refined in thenext few weeks

_ Roll-out currently and in thenext few months at

_ Somedia and

_ Migros Medien

_ Connector available to otherWoodwing customers as well

_ Integration with Elvis hasbeen implemented at/for Time Inc

108





15:10 Coffee break




17:00 End


109

Grafik: Slack Screenshot

Source: pmorch on GitHub

110

Grafik: Rise of Slack

The rise of Slacksince early 2014

Source: mukeshbalani.com

112

ManagementContent Production & Publishing

Chat

Phone

Email

Talk

113

Personal notification scenario: New assignment

114

Personal notification scenario: New assignment with actions

115

Sharing scenario: Share a story to discuss it

116

General notification scenario I: New stories

117

General notification scenario II: Published stories

118

Interaction scenario: Create a story straight from Slack

119

Our initial priorities for connecting with chat tools:

1. Start a discussion about a story from Desk-Net in the chat tool

2. Receive personal notifications

Will make notificationsettings more granular firstly in order to avoidspam – relevant for emailsas well

3. Non-personal notifications

_ We will focus first on Slack, then on Hipchat and potentially others

_ Reason:

_ More users on Slack

_ (Seemingly) Easierintegration with Slack thanwith Hipchat

120


Chat

Phone

Email

Talk

121


Chat

Phone

Email

Talk

Comments-

in Desk-Net or outside?

122





15:10 Coffee break




17:00 End


123

Our High-Level Roadmap for the next twelve months

Q3/16 Q4/16 Q1/17 Q2/17

Mobile

Availability

Auto-RefreshEase-of-use

Tasks/Workflow

Notifications/Chat integration

Security / Performance / CMS Integrations

Beta Release

124


Q3/16 Q4/16 Q1/17 Q2/17

Mobile

Availability



Tasks/Workflow

Main improvements:

• Easier entry and editing

• Shifts in bars with drag & drop

• Improved availability overviews:

• Daily / multi-day view

• Annual view

• Display of availability at user

selection

• 2017:

• Capacity calculation

• Data export

125


Q3/16 Q4/16 Q1/17 Q2/17

Mobile

Availability



Tasks/Workflow

Main improvements:

• Mark tasks as done

• Improved task lists

• Alerts

126


Q3/16 Q4/16 Q1/17 Q2/17

Mobile

Availability



Tasks/Workflow

Main improvements:

• More granular notification

settings

• Slack integration, potentially

others

• Non-personal notifications

128

GoodbyeAuf Wiedersehen

VaarwelNäkemiin

Kwaheri

Hejdå