Why Your Workflow Feels Like a Slow Kung Pao Chicken Order—and How to Fix It

The article uses a humorous restaurant analogy to illustrate typical pitfalls in workflow design and management, especially in IT operations.

1. Focus on Function, Not Process

Just like a chef who keeps adjusting the dish based on late requests, a workflow should implement the required functionality rather than a rigid, unchangeable process. Requirements often change during development, making a static workflow ineffective.

Therefore, workflow management systems need flexibility, offering modular components that users can assemble themselves, instead of hard‑coding every step.

2. No "Lock" Means Trouble

When a case is assigned to multiple users without a locking mechanism, duplicate operations can occur. If the operation is idempotent, it may be harmless, but non‑idempotent actions can cause serious issues.

Developers must consider concurrency impacts and implement a lock, such as a claim‑based approach where only the claimant can see and act on the task. A case should never be managed by multiple people simultaneously without proper control.

3. Simplicity Over Complexity

Over‑complicating a workflow leads to inefficiency. A simple, clear process is preferable; “less is more.”

For example, in a hardware repair scenario, allowing every user to submit repair requests creates unnecessary confirmation steps, whereas restricting the request to a qualified SE streamlines the process.

4. Clear Role Separation

When a repair case involves multiple devices, bundling them into a single case can cause logical problems if some devices are repaired while others remain pending. Each device should be treated as an individual task within a case, with clear ownership and closure procedures.

5. Allow Graceful Exit

A workflow must permit participants to reject or abort actions when they cannot be performed, enabling the business state to revert or terminate gracefully. Approval steps often lack a reject option, forcing users to proceed even when inappropriate.

6. Use Precise Terminology

Domain‑specific terms should be used accurately to avoid confusion. For instance, in DNS configuration, the concept of a "View" must be called "View" and not renamed arbitrarily, as misnaming can lead to operational errors.