Identifying & clearing bottlenecks

Modified on Tue, 22 Nov 2022 at 03:29 PM

The Command Center provides dashboard-style analytics for your publication(s) to help you uncover inefficiencies and bottlenecks, manage your team’s workload, and easily communicate with contributors via intuitive call-to-actions.

Get an at-a-glance view of everyone's workload, and easily redistribute tasks for overloaded users. Stop triaging dozens or more stories to uncover whether some of them have missing assignments or if your assignees have failed to accept a task.

In short, the Command Center will help your publications become more efficient, ensure timely content production, and help you meet your marketing goals.


How to navigate to the Command Center

Click on the drop down in the top right corner and select the Command center

Below is a short description of the command center widgets.

Average Completion Time:

This widget is the overarching theme of the entire dashboard. The average completion time is the time it takes from story creation to the expected publish date on a piece of content.

The large number provides the average time time to completion over the past 30 days, whereas the trend chart below provides the completion time over the past 6 months.

Hover over the chart to see the time to completion times as well as number of stories that were completed during the given month.

 User Workload:

This widget gives a snapshot of what everyone on your team is working on.

Page through five users at a time to view the stories each team member is “Working On" or has on their “Upcoming" agenda. Toggle between “Next Week" to view data for the upcoming week and “All

Time" to view upcoming projects for the foreseeable future. You can also click on the expansion triangle in front of the user to see how many stories he or she is working on across publications. By clicking on the number listed for the stories each contributor is “Working On" or “Upcoming," you will be taken to a filtered Stories Library.

User Delays:

The User Delay widget allows you to see the percentage of workflow steps that were completed late by each contributor.

Click the blue arrow next to each contributor to see the number of steps they've worked on in the last 90 days and their average delay time. The user “Contently Network" is an average of delays from all of your network contributors.

With the click of a button, content managers can swiftly message contributors with delays via a templated or custom message.

Below the contributor list is a historical trend chart, which shows the percentage of late stories by month.


 Unassigned Steps:

This widgets informs you which in-progress stories are missing assignments. The call-to-action button allows you to jump into the workflow of the story and quickly assign a user.

The historical trend graph shows a month-to-month breakdown of the number of stories that were published with an unassigned step.

Late Stories: 

The Late Stories widget identifies the percentage of late stories in the last 30 days. In addition, you’ll be able to see a list of late stories, as well the number of days they are past their expected publish date. Click on the button next to a late story to send a templated or customized message to the assigned user.

The historical trend chart shows the number of late stories published per month.

Pressing Stories:

The Pressing Stories widget contains stories that currently have a late workflow step, as well as stories that have been left idle in-between workflows steps for a significant amount of time. These

data points are key indicators that the final publish deadline might be missed.

This widget will also provide a call-to-action button that allows you to easily message the current assignee.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article