Zero Unnecessary Steps! Start Editing Without Requests, for Smooth Updates
The Marketing Department at DonDon Web Co.Ltd was experiencing inefficiencies in its web content update process. Previously, even when an editor identified a need for an update, they first had to register the task as a “request”. This unnecessary step led to delays and duplication of work.
To resolve this, the process owner introduced a new, streamlined workflow. Now, editors can directly initiate work without having to register a request. This change has significantly boosted operational efficiency by allowing editors to immediately begin editing.
* This process improvement story is fictional and not related to any real person or organization.
1. Issue: Editors inefficiently submit their own work requests.
DonDon Web Co.Ltd is a web development company with a team of 50. Their Marketing Department handles daily updates for web pages, ad creatives, and promotional materials.
Typically, when the Marketing Department gets a web update request, an available team member takes on the task and edits the content. After completing the work, another editor reviews it.
However, a problem arose when an editor noticed a page needed updating themselves. They still had to register the task as a request from a “requester” first. This extra step wasn’t just a burden; sometimes, another team member would pick up the same task, preventing the original editor from being able to edit the task.
2. Solution: Implement a Workflow Allowing Editors to Initiate Tasks Directly
The process owner introduced a new editing workflow to allow editors to make their own judgments and start work immediately. This revision to the traditional “request registration → editing” flow means editors can now begin editing directly, without having to go through the request registration process.
Before
View details of the workflow diagram
0. Request
The requester initiates the task and submits an editing request.
1. Edit
The editor begins the task and performs the requested edits.
2. Review
The reviewer checks the content created by the editor for any issues. If corrections are needed, they request the editor to re-edit.
1x. Re-edit
The editor performs further edits based on feedback from the reviewer.
After
View details of the workflow diagram
0. Request
The requester initiates the task and submits an editing request.
1. Edit
The editor begins the task and performs the requested edits.
1a. Edit (Self-Initiated)
The editor proactively starts the editing work.
1b. Edit (Request-Driven)
The editor performs the editing work in response to a request from a requester.
2. Review
The reviewer checks the content created by the editor for any issues. If corrections are needed, they request the editor to re-edit.
1x. Re-edit
The editor performs further edits based on feedback from the reviewer.
3. Benefits
We’ve eliminated the wasteful step of self-requesting tasks
- Eliminated the hassle of registering requests, allowing for faster operations.
- Prevents duplicate editing tasks and reduces operational waste.
- Ensures the entire process runs smoothly, preventing operational stagnation.
4. Other Business Applications
Design Revisions
Designers can start making corrections immediately, without waiting for instructions from clients or directors.
Internal Document Updates
Necessary revisions are reflected quickly, helping to keep operational manuals current.
Product Information Changes
Updates to sales pages and catalogs can be made smoothly.
Bug Fixes
You can establish a system where developers can immediately correct bugs they discover.