Is There "Value Stream" in the Office? —— Five Steps to Map Administrative Waste with Office VSM

1. Introduction: A Quotation Process Takes 9.5 Days, but Only 6 Hours of Actual Work

The quotation process in a certain equipment manufacturing company works like this: the sales department receives an inquiry, fills out a quotation application form, and sends it via email to the technical department for evaluation. The technical department responds after three days; the purchasing department takes two days to inquire from suppliers; the finance department takes one day to verify the price; and finally, the document is sent to the general manager's office, where it waits for two days before being signed. On average, the entire process takes 9.5 days, and the client can't wait, resulting in two orders being lost to competitors who responded faster.

The boss called the heads of all departments together to ask why the quotation process was so slow. Sales blamed the technical department for slow responses, the technical department blamed purchasing for not providing parameters, purchasing blamed finance for not completing the budget, and finance blamed the general manager for slow signing—each department felt "very busy," but no one could clearly explain where the time was being spent.

It wasn't until the quality department took the lead and drew an "Office Value Stream Map" (Office VSM) for this process that the truth came to light: out of the 9.5 days, the actual processing time totaled only 6 hours, and over 90% of the time, the document was sitting in someone's inbox or a department's to-do queue.

2. Why the Office is a "Blind Spot" for Lean Improvement

Manufacturing workshops have long used value stream mapping to identify waste, but the office is rarely "mapped." There are three main reasons for this:

First, in the workshop, physical items are in motion, and parts and work-in-progress are tangible. In the office, the flow is of documents, emails, and approval processes, which are invisible, and thus no one perceives "accumulation" as a problem. Second, in the workshop, stopwatches can measure cycle times and count work-in-progress, but the office generally lacks a measurement habit. People only track "how much was done" and not "how much was waited." Third, cross-departmental processes lack an "owner." Sales only coordinates with the technical department, the technical department only handles evaluations, and no one is responsible for the end-to-end cycle, leading to fragmented issues due to departmental silos.

The result is that in administrative processes, waiting time typically accounts for 80% to 95% of the entire cycle, with rework, duplicate data entry, and ineffective approvals being common, yet there is no map to lay out these wastes on the table.

3. Office VSM vs. Workshop VSM: Three Key Differences

The basic logic of Office VSM is the same as that of workshop VSM—trace the process, record the time, identify waste, and design a future state. However, there are three differences in the drawing method that must be noted:

First, the "product" being mapped is different. In the workshop, it is parts, while in the office, it is business objects: a quotation application, a purchase order, a customer complaint, a design change request, or a new employee onboarding procedure. When selecting objects, group them by "similar process paths" rather than by department.

Second, the symbols are different. The inventory triangle in the workshop corresponds to inboxes and to-do queues in the office; the transport arrow in the workshop corresponds to email forwarding and system document transmission; and the rework loop in the workshop corresponds to "being sent back for modification."

Third, the time composition is entirely different. In the workshop, processing time usually accounts for 30% to 50% of the cycle time; in the office, processing time often only accounts for 5% to 20%, with waiting time being the dominant factor. Therefore, when drawing an office map, waiting time must be measured and drawn separately, which is the core of the entire method.

4. Step One: Select a "Product Family," Starting with the Most Painful Process for the Customer

Don't start by mapping the entire company's processes; choose one first. The selection criteria are threefold: the process with the most customer complaints, the longest end-to-end cycle, and the highest frequency of occurrence. Meeting any one of these criteria is worth mapping.

For example, in the quotation process, the business object is the "quotation application form." Similar processes include contract evaluation, purchase orders, customer complaint handling, and drawing change requests. They follow similar paths and can be grouped into one product family. Start with the quotation process. Note a common mistake: drawing a "departmental process flowchart" is not a value stream map. A value stream map must be cross-departmental, end-to-end, starting from the customer's request and ending with the customer receiving the result.

5. Step Two: Follow a Real Document, Don't Trust the Flowchart

Many companies have beautifully drawn flowcharts on their walls, but the actual process is often completely different. Therefore, the second step must involve "following a document": select a real quotation application and follow it from start to finish, recording each step.

Record four types of information: who is processing it, how much time is spent processing, how long it waits at each stage, and how many times it is sent back for rework. Cross-verify the data sources: timestamps in the system, email send/receive records, and interviews with the parties involved. Only when all three align is the data considered valid.

Almost invariably, unexpected discoveries are made when following a document. For example, in this company: the quotation application first goes through the sales manager's approval, then to the technical department, and after the technical department's evaluation, it must be re-confirmed by the sales manager—resulting in the same document being reviewed twice by the same person. Another example is that the purchasing inquiry waits for responses from all three suppliers before starting the price verification, but the finance department can actually start the verification as soon as the first supplier responds.

6. Step Three: Calculate Two Types of Time, Turning "Waiting" into Numbers

In administrative processes, calculating two types of time reveals waste:

Processing Time (PT): the actual time spent working, such as 40 minutes for technical evaluation and 25 minutes for financial verification. Waiting Time (WT): the time spent queuing, waiting for signatures, or waiting for responses. Cycle Time (LT) = ΣPT + ΣWT.

Add three more metrics: First Pass Yield (the percentage of documents that are correct the first time and do not require rework), number of rework instances, and batch size (whether documents are processed in batches). In this company, the calculations showed that the first pass yield for quotation applications was only 62%, with an average of 0.8 rework instances per application. The technical department habitually accumulated applications for a Friday review, leading to a delay of two to three days.

Summing up these numbers, a sobering conclusion was reached: Value Ratio = Value-Added Time ÷ Total Cycle Time. The quotation process had a value ratio of only 2.6%. In other words, over 97% of the time, the customer was waiting, while the company did nothing.

7. Step Four: Draw the Current State Map, Making the Information Flow Visible

The drawing method is the same as for workshop VSM: place process boxes from top to bottom and draw a time axis at the bottom. However, the time axis should have two lines—one thin line for processing time and a thick, jagged line or queue symbol for waiting time, making it immediately clear where the time is being spent.

The map should also indicate: which department and person handles each stage, which system is used, and how frequently processing occurs. After drawing the current state map, the 9.5-day cycle was broken down into six visible waiting periods and three rework instances, and no one could say, "I don't know where the delay is" during meetings.

8. Step Five: Design the Future State, Targeting Waiting Time

The design principles for the future state are fourfold: parallelize where possible,前置 where possible, consolidate where possible, and automate where possible.

Based on these principles, the company made four improvements. First, approval grading: quotations under 50,000 yuan are signed directly by department heads without the need for hierarchical reporting, eliminating the waiting time for the general manager's approval. Second, parallelization: purchasing inquiries are changed to rolling inquiries, and financial verification is initiated in parallel with the last supplier's response. Third, eliminating duplicate approvals: the second confirmation by the sales manager is removed, and technical evaluations are co-signed. Fourth, batch elimination: technical evaluations are changed from "weekly Friday concentration" to "twice daily," replacing batch processing with single-piece flow.

After these improvements, the quotation cycle was reduced from 9.5 days to 2.1 days, and the first pass yield increased from 62% to 91%. More importantly, sales can now confidently promise delivery times to customers.

9. Implementation Tips: Four Common Pitfalls

1. Drawing a value stream map that is just a flowchart. Without time, queues, and waiting, the map loses its meaning.
2. Only drawing the current state without a future state. Without a future state map, there is no target for improvement.
3. Relying on feelings rather than actual measurements. Office processes are easily misled by "I think it's fast," so everything should be based on timestamps and document tracking records.
4. Focusing improvements only within one's own department. Cross-departmental processes must have an end-to-end responsible person, otherwise, departmental silos will absorb the improvement results.

10. One-Sentence Summary

Waste in the office is not invisible; it's just that no one has ever mapped it. Drawing an Office VSM for administrative processes turns waiting time into numbers and departmental silos into process boxes, providing a starting point for improvement—whether it's quotations, contracts, customer complaints, or changes.

In the workshop, parts flow; in the office, documents flow. Drawing a value stream map for administrative processes turns waiting from a "feeling" into a "number," providing a target for improvement.

Knowledge code: 7.1.1

Version: v20260817

Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.