We work with plenty of journalists who use primary source material alongside their assignments. Now they can store theses files with their work directly in Camayak, so their colleagues can access them, too. Simply use the media tab and upload the file of your choice to store along with everything else you need to share.
It all started with a community college in Torrance, California.
“Oh, so you’re not a CMS?” Kate McLaughlin – the adviser to the student media department at El Camino College asked. “I think I get what you’re saying. You’re just workflow, right? That could actually be really helpful”.
Soon after El Camino College became our first beta tester in 2011, Steve Wolgast, who had recently joined Kansas State University’s CollegianMedia Group from the New York Times, decided we were worth taking seriously and invited us to pitch for helping the ‘Collegian organize itself more efficiently and publish approved stories directly to its new WordPress site.
Over a year earlier, our initial plan for building Camayak had emerged out of a sense that we could contribute to a healthier ecosystem of CMS designed specifically for news production. Around the same time, other companies like Burt Herman’s Storify were looking to give journalists better tools for composing their articles, while outsourcing services like Contently were also starting to make workflow a key part of their appeal to clients that were hiring writers through the same interface. For everyone in the news production business, speeding up collaboration was becoming more important for shrinking editorial teams to get the most out of their staff budgets.
Today, we’re still working towards our goals of offering better archiving and multi-platform publishing to publishers, regardless of which CMS or social platforms they’re using. Over the last three years, we’ve grown our customer base by eliminating bottlenecks in the processes of pitching, assigning, editing and approving editorial work. People using Camayak have published over 7 million words between them, enjoyed integrations with major media companies like Getty Images and even built their own connections to other services like Slack.
Encouragingly, we’ve seen increases in productivity in almost every single newsroom we’ve worked with for at least twelve months. We’ve also connected customers to help one another with advice and, particularly with student newsrooms, have enjoyed compiling data representations to point out quirky trends that their staff have helped to generate.
Photo credit: Roman Heindorff
Earlier this year we even made “Journalism-Driven Data” – a musical rendition of some newsroom activity numbers:
Helping newsrooms become more active is a big part of our pitch, so we’re happy to see rising engagement as newsrooms also use Camayak to increase the size of their contributor roster. Here’s the trend of how frequently Camayak users were pitching new ideas, during our first two years as a live product:
And a similar surging trend for how often Camayak users were commenting on their newsroom activity each month:
At the moment we have a diverse range of clients, from high schools to PR firms and college media to non-profit news organizations. Because we’ve charged for our service since day one, our reception among newsrooms has focused on our cost-to-benefit ratio. For up to thousands of dollars a year, is Camayak worth its expense? When a CMS and server costs are inescapably necessary for delivering content to its audience (although Facebook and other platforms might challenge this), how does a pre-publishing tool that only the newsroom interacts with stack-up as a budget priority? For most teams that are used to using their free generic tools, plugins and overtime (particularly in the form of student labor), the answer is: not at all.
Since Camayak isn’t itself a revenue generating tool, we’ve always known that our ability to demonstrate our value would need to be user-centric and not cost-based. Quickly delivering value to the people that are actually using Camayak is, for example, much more rewarding than speculating to a senior editor that their existing workflow processes might be undermining their ability to save time and even grow their operation. With that in mind we aim to satisfy three types of user so that they each insist on retaining Camayak once they’ve tried it:
Reporter. First and foremost, logging into your newsroom as a reporter and contributing to its flow of content needs to be seamless and engaging, irrespective of whether you’re a veteran or newbie. Our second goal is to convert the collaboration data we track into meaningful statistics that offer a broader and deeper insight into a reporter’s performance in their newsroom. We do this by offering them a free portfolio of their work and, increasingly, helpful data on their productivity and style. As it stands, few – if any – services can offer insights like Camayak can into a reporter’s actual newsroom performance.
Editor. Our objective with editors is to noticeably reduce the amount of confusion and admin tasks that surround the process of tracking editorial progress, week-in, week-out. This equates to a real saving in the amount of time it takes to produce the same amount of work as before Camayak was introduced to the newsroom. Since all assignments and pitches are tracked through Camayak, editors need a birds-eye view of their editorial calendar, which we have the information to build for them. Editors should find themselves with less micro-managing to do and more opportunity to determine strategy.
Administrator. We want to give the people paying the bills the best insights they can get on how their staff are performing. They, like editors, should also be able to piggyback off of their newsroom’s momentum to offer best practice advice where it’s needed most and commend excellent work more easiy.
Before any of these people log into a trial Camayak account, we usually answer some questions around objections that senior newsroom staff have on their minds. Such concerns include:
“This is going to cost us money we don’t have”. Two or three years agoI read a report claiming that newsrooms were not unlike a typical Fortune 500 company, in that on average they would devote between 2-4% of their operating budget to IT services that improved their business. To be as competitive as possible, we’re committed to putting downward pressure on our pricing as our client base grows, particularly at the student/education level.
“This is just going to be another login for our staff to remember”. When you’re dealing with a high turnover of staff and/or folks that aren’t technically advanced, the fewer interfaces they can be trained on, the better. Camayak replaces Google Drive, Dropbox, server access and even your CMS to offer content producers a single login to all their newsroom collaboration.
“We already have a CMS that handles our workflow”. Once you’ve chosen a CMS you can expect to keep investing in the platform to make it move with your changing requirements in the future. Sometimes this investment is so intimidating that it can, often in conjunction with a dissatisfaction towards the platform itself, push you towards wanting to move to a different CMS entirely. Outsourcing workflow to a purpose-built layer like Camayak limits a newsroom’s dependence on their CMS and fundamentally de-couples content production from where it eventually is displayed. As audience engagement platforms proliferate, designing a single CMS with both production and rendering requirements puts priorities at risk.
“Everybody has to use it in order for it to work” (aka “can’t some of us use one tool and the rest of us use another?”). One of the main reasons we hear of people choosing to track their editorial workflow with tools like Camayak is to ensure they generate clean audit trails of what they’ve done. By addressing three different sets of user needs (see above) we work to make sure that the main stakeholders in a newsroom can each improve their workflows by using Camayak. While there may be a learning curve that comes with new tool, homogenizing the format of a team’s input reduces the number of repetitive tasks between applications and significantly in the long term allows us to provide consistent performance measuring to editors and administrators.
We’re working to build a better product that learns from the lessons we’ve taken from working with so many awesome newsrooms already. If you’re looking for advice on how to manage your editorial calendar, streamline your editorial workflow or scale up your content production, you can find us at email@example.com.
We’ve been working on a feature to help newsrooms figure out how to evaluate and pay their staff more efficiently, week-in, week-out. Here’s why.
Every fortnight, writers at the Kansas State Collegian fill out their pay sheets so they can show their editors what they worked on. On average, let’s say it takes just 2 minutes for each writer to fill one of these pay sheets out. Each desk editor then checks their writers’ sheets to make sure they’re accurate. On average, this takes each desk editor 10 minutes to do. The person who’s responsible for collecting all these pay sheets then needs to enter each person’s details into a spreadsheet, so it can go into the billing system. This takes them about an hour each fortnight.
Here’s what that means.
30 writers write articles over a two-week period, so 30 people spend 2 minutes each writing their pay sheet (60 minutes in total). Four desk editors take 10 minutes each to check these writer sheets (40 minutes in total). Then an editor needs to summarize the pay sheets so they can be added to the billing system (60 minutes in total).
Total time spent every two weeks = 2 hours, 40 minutes
Total time spent every 10 week semester = 13 hours, 20 minutes
In this case, our goal is to save the newsroom over twelve hours a semester in tracking whom they should pay and how much. In comparison, a newsroom like The Daily Wildcat at the University of Arizona has seven desk editors that spend about 30 minutes each counting their writers’ bylines. That’s a total of over four hours of time that Camayak could save them, every fortnight.
At Georgia Southern’s Student Media department, the students are paid through a bi-weekly stipend. Even though they spend less time tracking how many assignments each writer has worked on each week, they can sometimes lose track of a writer falling short of their weekly commitment.
A writer stops writing regularly and therefore no longer qualifies for she fortnightly stipend. Since the writer hasn’t officially informed their editors that they’re quitting, payroll doesn’t know that they shouldn’t be paid this week.
In this case, Camayak can now save the newsroom from over-paying its contributors, to ensure that it never spends more money than it has to.
Analyzing staff performance with visualizations
We exported payroll data for a couple of newsrooms that use Camayak and using the RAW visualization tool, turned their statistics into pretty pictures.
The size of the circles refers to how many assignments each staff member completed and/or uploaded files to, between July 2014 and February 2015. The larger the circle, the more assignments they worked on. The colors of the circles reference how many files each staff member uploaded to those assignments. The closer to orange, the fewer files they uploaded. The closer to blue, the more they did.
Kansas State Collegian
113 staff wrote and/or uploaded files to approved assignments from July 2014 to February 2015.
Largest circle: 236 assignments
Darkest blue: 221 file uploads
Darkest orange: 0 files uploaded
113 staff wrote and/or uploaded files to approved assignments from July 2014 to February 2015.
After we launched our daily email roundup, editors asked us to include a reminder to their writers if they had upcoming deadlines. From today, we’ll let your writers know if they have a deadline within the next 24 hours. We’ll even nag them if they miss it.
We’ve also changed the way your calendar looks in Camayak so you can see who’s assigned to each item that appears. As well as viewing assignments for a specific desk or publishing destination, you can now also choose to see all your contributors’ first submission deadlines alongside your publishing schedule.
This is a plot about four newsrooms using the Camayak platform. We plot various indicators of staff behavior over time.
The time dimension is represented in the music as time. The music is composed of verses, each verse corresponding to a season. Each season is broken into four equal parts (approximately 23 days each), and each verse is correspondingly broken into four “phrases”.
We distinguish between the summer season and all other seasons in these ways.
* Chord progression (i v i III versus I V vi IV)
* Presence of drums (off during the summer)
The commenting on assignments and pitches in newsrooms and assignment of tasks to writers affects the main rhythms and the use of drums.
The rhythm for the melody is based on averaged data across all the newsrooms and dates for the particular season. There are two underlying tracks, and the data affect how fast the rhythm; one of them gets faster when more comments are made in the newsrooms, and the other gets faster when more assignments are created. Similarly, the bass drum turns on when there are lots of comments, and the hi-hat turns on when there are lots of assignments.
The rhythm is also based on the number of pitches submitted; measures get more notes added at the end of the measure when more pitches are submitted. (If a lot of pitches are submitted, notes eventually get added to the beginning of each measure too.)
Pitches of all notes are based on the data for the particular newsroom during the particular 23-day section of the particular season; pitches are higher when more assignments were created.
The time dimension also is represented in the video, as the x-axis. The season’s name is shown in text, and the background color changes to grey in the Summer.
The y-axis in the video is the activity generated per day. Activity per day is plotted incrementally—in 23-day sections and one organization at a time. The name of the present organization is written towards the bottom-left of the screen, and the curve for that organization is shown in front of all of the other curves.
At the right end of the curves are plotted an alternating circle and triangle. Their size is proportional to the number of pitches submitted (circle) and users registered (triangle) for the particular date.
Activity is low during the summers and very low at the beginning and ends of the song. Low activity during the summers occurs because three of the newsrooms are student newsrooms, which have much less activity when school is out. Low activity at the beginning occurs because the newsrooms had not yet begun using Camayak, and low activity occurs at the end because we are using data that were exported a couple months ago.
There is a weekly trend of high activity on weekdays and low activity during the week.
We’re offering every student newsroom we work with the chance to earn $300 by shooting and editing a 60-second video to explain how your staff use Camayak.
Any newsroom that meets the criteria for what we’re looking for will receive a $50 check right away*. Then, if we select your video to use as part of our marketing and training campaigns, we’ll send you another check for $250. Easy, eh?
*In order to qualify for your $50 and $250 reimbursements, your video must…
– be no shorter than 50 or longer than 65 seconds – include footage (or animation) of your campus, newsroom and students – show at least three people’s POV on how they find Camayak useful
You may only submit one video on behalf of your newsroom, so be sure to discuss this with your colleagues. When you’re ready, you can use a large file transfer service like WeTransfer’s free version to send us your work, by addressing it to firstname.lastname@example.org.
We’ll be accepting video submissions until March 15th at Midnight, Eastern Time and will be awarding an extra prize to the most creative video we end up using.
We’ve all been there. You’re waiting for your editor to send your work back to you so you can make some changes. You’re expecting an email to let you know you can start working on it. The email never arrives.
The next morning, you find out that your editor sent you your assignment, but you weren’t logged into Camayak (and either didn’t have desktop notifications activated, or were away from your computer) and so you missed it.
From today, anyone who’s been assigned to a step in your assignment’s workflow will receive an email 15 seconds after the assignment is sent to them (unless you choose to send it to someone else in that time), letting them know that it’s ready for them to work on. By picking someone for an empty step, you’ll make sure they get that email, too.
For those of you using comments to tag people with emails that prompt them to log in, you can still do so if you’re a writer trying to notify an editor at an empty step. As an editor, you’re able to assign another editor to that empty step to ensure they receive the automatic notification.
Today we’re announcing a new partnershipwith Getty Images, the world’s leader in visual communications, which gives Camayak users direct access to over50 million images for non-commercial use in any of their assignments.
Using the embed tool, anyone working on an assignment in Camayak can now draw on Getty Images’ latest news, sports, celebrity, music and fashion coverage; immense digital photo archive; and rich conceptual images to illustrate their assignments.
Whether you’re covering a news event or looking for creative images to illustrate the gist of a story, inserting high quality media into your editorial workflow has never been easier.
In a bid to support young journalists and their college media programs, The Austin Chronicle is partnering with Camayak to offer its professional-grade tools to local students for free. Camayak, which is also used by journalism schools at TCU, SMU and UT El Paso among others in Texas, will be offered free of charge to any state school media organization in Austin, courtesy of The Chronicle. The partnership, which The Chronicle hopes will help its editors identify promising young writers and photographers, is designed to help student media weather budget threats and grow its influence in the city.
For more information or to claim your free Camayak license, please email email@example.com.
Camayak customers experienced three service outages though the evening hours of February 3rd (US Time Zones)/Early Morning February 4th UTC.
The outages spanned the following times:
Outage 1 (34 minutes):
– UTC From 02/04/2015 03:39 to 02/04/2015 04:13
– CST From 02/03/2015 21:39 to 02/03/2015 22:13
Outage 2 (12 minutes):
– UTC From 02/04/2015 04:37 to 02/04/2015 04:49
– CST From 02/03/2015 22:37 to 02/03/2015 22:49
Outage 3 (40 minutes):
– UTC From 02/04/2015 04:54 to 02/04/2015 05:34
– CST From 02/03/2015 22:54 to 02/03/2015 23:34
In the times between the outages, service may have been slow as customers tried to reconnect.
Part 1: The service outage
We have determined that the service outages were caused by the following circumstances:
1) A customer inadvertently created a large number of publishing destinations pointing to non-existent or misconfigured WordPress instances.
2) When the customer went to the manage publishing destinations page, Camayak attempted to validate the publishing destinations. Due to the specific circumstances of those WordPress instances, the validation code ended up waiting a long time for validation before timing out.
3) The validation attempts tied up application server threads, preventing them from being used to service other customer’s requests
4) Our load balancer, seeing that the applications servers were not responding to the validation requests in a timely fashion re-attempted those requests to other application servers, causing application server threads on those servers to be tied up waiting for validation.
5) This process continued until all application server threads were tied up waiting for validation.
6) Eventually, the validation requests timed out fully, and the application server threads were available to process other requests.
Steps 2-6 of this process happened three times, causing the three outages.
1) We have, as of February 4th 16:45 UTC (10:45 CST) released a fix to our application server software to ensure that reasonable timeouts on the validation attempts. The validation timeout is well below the load balancer timeout, to ensure the cascade effect in (4) does not happen.
2) We have, as an additional measure, increased our application server capacity.
Part 2: The support outage
The Camayak support team was unable to respond to support queries from customers, which began at UTC 04:01, until UTC 07:29. The reasons for this are detailed here.
We have, as of February 4th 14:45 UTC (08:45 CST) set up a notifications system with extra features to alert and inform off duty support personnel of service outages. This is an addition to our existing notifications framework for other critical and non-critical alerts.