Press Release Results Should Be Inspected Afterwards

Yesterday Questetra Inc. published a press release. (If you're interested check it out here.)
Press releases are often communicated by the route: [releasing body – mass media – general public]. However, these days the use of a third party is often seen: [releasing body – press release agency –mass media – general public]. There may be many reasons behind this: there are more forms of media, more people in the general public read press releases, it can be used as an SEO strategy, and the media is beginning to depend on agencies.

<Tasks>
1. Register Press Release, 2. Notify Agency, 3. Check Final Release, 4. Register in Company Website

[Press Release <Measure Effect> : "1. Register Press Release" screen]

A Workflow that Automatically Posts Blogs

There are a lot of small companies that want an official blog or twitter account, with full control over the quality of the information published. We've seen a recent boost in automated systems that post prior-approved blogs/tweets. This is an operation that needs two functions: a "system that can post to a blog or twitter account by email" and a "workflow system that can send process data by email*." (Email is the key joint factor.)

* That is, a system that handles message throwing intermediate events (BPMN term), such as Questetra BPM Suite.

Reconsidering the Email Newsletter Review Process

Email newsletters are an automated process, but they do have to be written by people. And let's face it, people make mistakes. We could simply insist that writers "Just be more careful," or "Put their minds to it," etc., but let's be humane and consider the problem from a BPM point of view.

Double-checking is a very basic and useful method. But if senior employees are in charge of checking all drafts that come their way, it may be too much of a burden. This kind of system may result in a supervisor's tendency to "approve without actually reading."