At Signavio, we ‘eat our own dog food’ when it comes to our software products. This article describes why and how we use Signavio Workflow to streamline our publishing workflow for blog posts, such as the one you are reading now.
Context for Signavio’s publishing workflow
The Signavio blog is a team effort that includes members of the marketing team, designers, and technical writers who work on the product development teams. The marketing team is based at Signavio’s head office in Berlin, while two of the technical writers work remotely from other countries. This distributed team relies on online collaboration tools for collaborative writing, which don’t have any task management support.
Signavio’s blog is more formal than a personal blog written and published by a single person. Our process requires approving proposed topics, reviewing content to improve quality, and specialist tasks such as selecting suitable photos.
We publish blog posts on a variety of topics, on a regular schedule of approximately one blog post per week, in each of two blogs. Keeping to this schedule without wasting time writing articles that won’t be published anytime soon, while always having the next post ready in time requires careful planning and close collaboration.
Benefits of workflow automation
By using workflow automation to streamline our blog publishing workflow, Signavio’s marketing department has generated a number of benefits.
- Better visibility of the blog post publication pipeline.
- Less time wasted on requesting, writing, and consuming status updates.
- Reduced cycle time, as a result of fewer and shorter delays for task handovers between people working on a blog post.
- Further reduced cycle time, by identifying tasks that the team can complete in parallel.
- Automatic notifications that make sure everyone in the company knows about new blog posts.
- User-friendly process modelling, which allows the Content Manager to incrementally update the process model to improve the automation without depending on process analysts or IT support.
The rest of this article documents how we implemented our blog post publication process in Signavio Workflow, to achieve these benefits.
Process description - how to automate your publishing workflow
Publish a blog post on the company website.
Form - a proposal for a new blog post that describes who will write it and what it will be about.
The process consists of two phases of approval and content creation tasks, followed by a result notification.
The process starts with a Management Approval, followed by a Rejection Notification if the proposal is rejected. Note that the Approve content approval is simplified to a single task, and doesn’t use an explicit decision and loop back to the Write article task. Instead, corrections at this stage are handled informally, via comments on the case view.
Note that Select stock photo is a sub-process, rather than a single task. This allows the design team to design and manage their own process for selecting photos and other illustrations for blog posts. This sub-process proceeds in parallel while the author writes the article, based on information in the article proposal.
The process ends with a Result Notification that sends the published article’s title and URL to the whole company.
Each blog post involves four different people, in different roles, from the larger team.
- Author - Triggers the process by submitting an article proposal, writes the article content, and publishes the article using the blog’s content management system (CMS). For some blog posts the author is a technical writer from one of the product teams.
- Content Manager - Performs the two approvals - the initial article proposal and the finished article content.
- Copy Editor - A member of the marketing team, who is a native English speaker, who reviews and corrects the draft article.
- Designer - A member of the marketing website design team, who selects stock photography or other illustrations for the article.
The process defines a number of variables, which capture the data for each case (each blog post). All but one of the fields first appear on the trigger form, and make up the blog post proposal.
Author. The role described above, selected here manually because it is a Required Role Assignment and might not be the same person as whoever submits the proposal and starts the case.
Title. The article title, which identifies the case in Signavio Workflow’s Cases overview.
Category. Indicates whether the blog post is intended for the Corporate Blog or the Applied BPM & DMN blog.
Description. Describes the article’s topic, so the design team can select a suitable photo without having to wait for the final article text.
Planned publication date. Allows the Content Manager to position the blog post in the publication schedule.
Draft blog post. The URL of the draft article in the online collaboration platform. The author may already set this on the trigger form, at the proposal stage, if there is already an article outline.
Published URL. The URL of the published article on the Signavio website, used to share the published article. This is the only field that is not present on the trigger form, as it is only set at the end of the process in the publication task, and used in the final notification.
The process model shown above is a simplification of the complete process. For example, the model does not include the social media marketing tasks that the Social Media Manager performs.
There is currently no integration between the workflow and the two external systems: the online collaboration tool used for writing draft articles, and the CMS where they are published. In principle, it would be possible to automatically generate an empty draft article in the first system when the process starts, and automatically push the draft article to the CMS when it is complete. For now, at least, these tasks are not frequent or time-consuming enough to make this worthwhile.
A content publication process, such as our blog post publication process, is the perfect example of a business process that benefits from workflow automation for a number of reasons.
- Each case involves a number of people, who don’t sit in the same room.
- Each case requires management approval.
- The Content Manager needs an overview of open cases.
- Each case has required information and required steps.
- The exact process model is too company-specific for a generic task management system or CMS workflow to be suitable.
- The Content Manager needs to be able to regularly implement process improvements, without depending on external help.
To try Signavio Workflow for your own blog post publishing workflow, sign up for a free 30-day trial.