We are submitting a product enhancement request on behalf of our editorial team regarding Arc Composer's Slack workflow notifications for First Read and Second Read task creation events. This is not a bug report — the notifications are functioning as designed. However the current notification content creates a meaningful editorial workflow inefficiency that we believe could be resolved with a minor enhancement to the notification payload.
The Workflow Problem This Creates
The absence of story identification in workflow task notifications creates a repeated context-switching problem for editors throughout the working day:
Editor receives a First Read or Second Read Slack notification
Editor cannot determine from the notification whether the task is relevant to them
Editor must stop their current work, switch to Slack, open the channel, and locate the specific task
In many cases the editor discovers the task is assigned to a different editor — the interruption was unnecessary
This cycle repeats many times per day across the entire editing staff
The editorial team has noted that this cumulative context switching represents a meaningful daily productivity loss across the full editing team. The friction is entirely avoidable — the editor simply needs to know whether the task requires their attention without having to leave their current work to find out.
Why This Should Be Technically Feasible
The editorial team correctly notes that Arc already includes the story headline in publish notifications — demonstrating that Arc's notification system has access to story-level metadata at the time a notification is sent. The request is simply to apply the same story headline inclusion to the task creation notification payload that is already applied to the publish notification payload.
Guest
I cannot upvote this enough.