Back to Details

value-stream-mapping

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Value Stream Mapping

价值流映射

Create Lean value stream maps to visualize flow, identify waste, and design improvement opportunities. Based on Lean manufacturing principles adapted for knowledge work.
创建精益价值流图以可视化流程、识别浪费并设计改进机会，基于适配知识型工作的精益制造原则。

What is a Value Stream?

什么是价值流？

A value stream is the sequence of activities required to deliver value to a customer, from request to delivery. Value stream mapping (VSM) visualizes this flow to identify:
  • Value-adding activities - Steps that directly create customer value
  • Waste (Muda) - Steps that consume resources without adding value
  • Flow problems - Bottlenecks, delays, and inefficiencies
价值流是从需求提出到交付，为客户提供价值所需的一系列活动。价值流映射（VSM）将该流程可视化，以识别：
  • 增值活动 - 直接为客户创造价值的步骤
  • 浪费（Muda） - 消耗资源但不创造价值的步骤
  • 流程问题 - 瓶颈、延迟与低效

The 8 Wastes (TIMWOODS)

8种浪费（TIMWOODS）

WasteDescriptionExamples in Knowledge Work
TransportationMoving work between locationsHandoffs between teams, tool switching
InventoryUnfinished work waitingBacklog, WIP, queued requests
MotionUnnecessary movementContext switching, searching for info
WaitingIdle timeApprovals, blocked work, dependencies
OverproductionMaking more than neededUnused features, premature optimization
OverprocessingDoing more than requiredGold plating, excessive documentation
DefectsErrors requiring reworkBugs, miscommunication, rework
SkillsUnderutilized talentManual work that could be automated
浪费类型描述知识型工作中的示例
Transportation（搬运）在不同地点之间转移工作团队间的工作交接、工具切换
Inventory（库存）等待处理的未完成工作待办事项、在制品（WIP）、排队的请求
Motion（动作）不必要的动作上下文切换、搜索信息
Waiting（等待）空闲时间审批、受阻的工作、依赖项
Overproduction（过度生产）生产超出需求的产品未使用的功能、过早优化
Overprocessing（过度加工）做超出必要的工作镀金（过度优化）、冗余文档
Defects（缺陷）需要返工的错误漏洞、沟通失误、返工
Skills（技能浪费）人才未充分利用可自动化的手动工作

Workflow

工作流程

Phase 1: Define Scope

阶段1：定义范围

Step 1: Identify the Value Stream

步骤1：识别价值流

QuestionAnswer
What value are we delivering?[Customer outcome]
Who is the customer?[Internal/External customer]
Where does the stream start?[Trigger/Request]
Where does it end?[Value delivered]
问题答案
我们交付的价值是什么？[客户成果]
客户是谁？[内部/外部客户]
流程从哪里开始？[触发条件/请求]
流程到哪里结束？[价值交付完成]

Step 2: Set Boundaries

步骤2：设定边界

markdown
undefined
markdown
undefined

Value Stream Definition

Value Stream Definition

Name: Customer Order Fulfillment Trigger: Customer places order End State: Customer receives product Scope: Order entry → Shipping (excludes manufacturing) Customer: External retail customer
undefined
Name: Customer Order Fulfillment Trigger: Customer places order End State: Customer receives product Scope: Order entry → Shipping (excludes manufacturing) Customer: External retail customer
undefined

Phase 2: Current State Map

阶段2：当前状态图

Step 1: Walk the Process

步骤1：走查流程

Observe actual work (gemba walk):
  • Follow a real work item through the process
  • Document what actually happens, not what should happen
  • Note handoffs, delays, and workarounds
观察实际工作（现地行走）：
  • 跟随一个真实的工作项走完整个流程
  • 记录实际发生的情况，而非应有的情况
  • 记录工作交接、延迟和权宜之计

Step 2: Document Process Steps

步骤2：记录流程步骤

For each step, capture:
MetricDefinitionHow to Measure
Process Time (PT)Active work timeTime actually working
Lead Time (LT)Total elapsed timeClock time start to finish
Wait Time (WT)Time waitingLT - PT
% Complete & Accurate (%C&A)First-time quality% not requiring rework
针对每个步骤，记录以下信息：
指标定义测量方式
Process Time (PT)（处理时间）实际工作时间实际投入工作的时长
Lead Time (LT)（前置时间）总耗时从开始到结束的时钟时间
Wait Time (WT)（等待时间）空闲等待时间前置时间 - 处理时间
% Complete & Accurate (%C&A)（一次完成准确率）首次完成的质量无需返工的比例

Step 3: Create Current State Map

步骤3：创建当前状态图

markdown
undefined
markdown
undefined

Current State Value Stream

Current State Value Stream

StepOwnerPTLT%C&AInventoryNotes
Order EntrySales15m2h85%50 ordersManual entry
Credit CheckFinance10m8h95%30 ordersBatch processing
Inventory AllocWarehouse5m4h90%20 ordersSystem lookup
Pick & PackWarehouse30m6h92%40 ordersManual process
ShipLogistics10m24h98%100 ordersCarrier pickup
Total Process Time: 70 minutes Total Lead Time: 44 hours Flow Efficiency: 2.7% (PT / LT)
undefined
StepOwnerPTLT%C&AInventoryNotes
Order EntrySales15m2h85%50 ordersManual entry
Credit CheckFinance10m8h95%30 ordersBatch processing
Inventory AllocWarehouse5m4h90%20 ordersSystem lookup
Pick & PackWarehouse30m6h92%40 ordersManual process
ShipLogistics10m24h98%100 ordersCarrier pickup
Total Process Time: 70 minutes Total Lead Time: 44 hours Flow Efficiency: 2.7% (PT / LT)
undefined

Phase 3: Analyze Waste

阶段3：分析浪费

Step 1: Calculate Flow Efficiency

步骤1：计算流程效率

text
Flow Efficiency = Process Time / Lead Time × 100%

Example: 70 min / 2640 min = 2.7%
Interpretation:
  • < 5%: Significant waste (typical for unoptimized processes)
  • 5-15%: Moderate efficiency
  • 15-25%: Good efficiency
  • 25%: Excellent (rare for knowledge work)
text
Flow Efficiency = Process Time / Lead Time × 100%

Example: 70 min / 2640 min = 2.7%
解读：
  • < 5%: 存在大量浪费（未优化流程的典型情况）
  • 5-15%: 中等效率
  • 15-25%: 良好效率
  • 25%: 优秀（知识型工作中较为罕见）

Step 2: Identify Waste by Type

步骤2：按类型识别浪费

markdown
undefined
markdown
undefined

Waste Analysis

浪费分析

Waiting (45% of lead time)

等待（占前置时间的45%）

  • Credit check batch processing: 8 hours → could be real-time
  • Carrier pickup schedule: 24 hours → could be on-demand
  • 信用检查批量处理：8小时 → 可改为实时处理
  • 承运人取件排期：24小时 → 可改为按需取件

Inventory (150 orders WIP)

库存（150个在制品订单）

  • Orders queue at each step
  • No pull system in place
  • 每个步骤都有排队的订单
  • 未建立拉动系统

Defects (15% rework at order entry)

缺陷（订单录入环节15%的返工率）

  • Manual data entry errors
  • Missing required fields
  • 手动录入数据错误
  • 缺少必填字段

Overprocessing

过度加工

  • Full credit check for returning customers
  • Duplicate data entry across systems
undefined
  • 为回头客执行完整信用检查
  • 跨系统重复录入数据
undefined

Step 3: Identify Bottlenecks

步骤3：识别瓶颈

The constraint (bottleneck) limits the entire system:
markdown
undefined
约束（瓶颈）会限制整个系统的效率：
markdown
undefined

Bottleneck Analysis

瓶颈分析

Primary Bottleneck: Credit Check
  • Highest queue (30 orders)
  • Batch processing creates 8-hour wait
  • Blocks downstream flow
Secondary Bottleneck: Pick & Pack
  • Manual process
  • Variable cycle time
undefined
主要瓶颈： 信用检查
  • 排队订单最多（30个）
  • 批量处理导致8小时等待
  • 阻塞下游流程
次要瓶颈： 拣货与包装
  • 手动流程
  • 周期时间不稳定
undefined

Phase 4: Future State Design

阶段4：未来状态设计

Step 1: Apply Lean Principles

步骤1：应用精益原则

PrincipleCurrent ProblemFuture State Solution
FlowBatch processingContinuous flow, single-piece
PullPush based on forecastPull based on demand
PerfectionAccept defects, fix laterBuild quality in
原则当前问题未来状态解决方案
流动批量处理连续流动、单件流
拉动基于预测推动基于需求拉动
完美接受缺陷、事后修复内置质量管控

Step 2: Design Improvements

步骤2：设计改进方案

markdown
undefined
markdown
undefined

Future State Design

未来状态设计

Eliminate Waiting

消除等待

  • Real-time credit API vs. batch
  • On-demand carrier pickup
  • 实时信用API替代批量处理
  • 按需承运人取件

Reduce Inventory

减少库存

  • WIP limits at each step
  • Pull signals between steps
  • 每个步骤设置在制品（WIP）上限
  • 步骤间设置拉动信号

Improve Quality

提升质量

  • Validation at order entry
  • Auto-populate from CRM
  • 订单录入环节增加校验
  • 从CRM自动填充数据

Automate Motion Waste

自动化动作浪费

  • Single system vs. multiple tools
  • API integrations
undefined
  • 单一系统替代多工具
  • API集成
undefined

Step 3: Create Future State Map

步骤3：创建未来状态图

markdown
undefined
markdown
undefined

Future State Value Stream

Future State Value Stream

StepOwnerPTLT%C&AInventoryChanges
Order EntrySales10m30m98%10 ordersValidation, auto-fill
Credit CheckSystem1m5m99%0Real-time API
Inventory AllocSystem1m5m99%0Automated
Pick & PackWarehouse25m2h96%15 ordersBetter tooling
ShipLogistics10m4h99%20 ordersOn-demand pickup
Target Process Time: 47 minutes (33% reduction) Target Lead Time: 6.7 hours (85% reduction) Target Flow Efficiency: 11.7% (4x improvement)
undefined
StepOwnerPTLT%C&AInventoryChanges
Order EntrySales10m30m98%10 ordersValidation, auto-fill
Credit CheckSystem1m5m99%0Real-time API
Inventory AllocSystem1m5m99%0Automated
Pick & PackWarehouse25m2h96%15 ordersBetter tooling
ShipLogistics10m4h99%20 ordersOn-demand pickup
Target Process Time: 47 minutes (33% reduction) Target Lead Time: 6.7 hours (85% reduction) Target Flow Efficiency: 11.7% (4x improvement)
undefined

Phase 5: Implementation Roadmap

阶段5：实施路线图

Step 1: Prioritize Improvements

步骤1：优先级排序改进措施

ImprovementImpactEffortPriority
Real-time credit APIHigh (8h → 5m)Medium1
Order entry validationMedium (15% → 2% errors)Low2
On-demand carrierHigh (24h → 4h)High3
Automated inventoryMediumMedium4
改进措施影响投入优先级
实时信用API高（8小时→5分钟）中1
订单录入校验中（错误率15%→2%）低2
按需承运人高（24小时→4小时）高3
自动化库存分配中中4

Step 2: Define Kaizen Events

步骤2：定义Kaizen改善活动

Focused improvement workshops:
markdown
undefined
聚焦式改进研讨会：
markdown
undefined

Kaizen Event: Credit Check Automation

Kaizen Event: Credit Check Automation

Scope: Eliminate credit check batch processing Target: 8 hours → 5 minutes lead time Team: Finance, IT, Process Owner Duration: 1 week intensive Deliverables:
  • API integration specification
  • Process redesign
  • Training materials
undefined
Scope: Eliminate credit check batch processing Target: 8 hours → 5 minutes lead time Team: Finance, IT, Process Owner Duration: 1 week intensive Deliverables:
  • API integration specification
  • Process redesign
  • Training materials
undefined

Output Formats

输出格式

Narrative Summary

叙述性摘要

markdown
undefined
markdown
undefined

Value Stream Analysis Summary

价值流分析摘要

Value Stream: [Name] Date: [ISO date] Analyst: value-stream-analyst
价值流： [名称] 日期： [ISO格式日期] 分析师： value-stream-analyst

Current State Metrics

当前状态指标

  • Process Time: X minutes
  • Lead Time: Y hours
  • Flow Efficiency: Z%
  • Primary Bottleneck: [Step]
  • 处理时间： X分钟
  • 前置时间： Y小时
  • 流程效率： Z%
  • 主要瓶颈： [步骤]

Top Waste Categories

主要浪费类别

  1. Waiting (X% of LT): [Description]
  2. Inventory (X orders WIP): [Description]
  3. [Other waste]: [Description]
  1. 等待（占前置时间的X%）： [描述]
  2. 库存（X个在制品订单）： [描述]
  3. [其他浪费]： [描述]

Future State Targets

未来状态目标

  • Lead Time Reduction: X%
  • Flow Efficiency Target: Y%
  • Quality Target: Z% first-time right
  • 前置时间减少： X%
  • 流程效率目标： Y%
  • 质量目标： Z%一次做对

Recommended Actions

建议行动

  1. [High priority improvement]
  2. [Medium priority improvement]
  3. [Lower priority improvement]
undefined
  1. [高优先级改进措施]
  2. [中优先级改进措施]
  3. [低优先级改进措施]
undefined

Structured Data (YAML)

结构化数据（YAML）

yaml
value_stream:
  name: "Customer Order Fulfillment"
  version: "1.0"
  date: "{ISO-8601-date}"
  analyst: "value-stream-analyst"

  boundaries:
    trigger: "Customer places order"
    end_state: "Customer receives product"
    customer: "External retail customer"

  current_state:
    total_process_time_minutes: 70
    total_lead_time_hours: 44
    flow_efficiency_percent: 2.7
    wip_total: 240

    steps:
      - name: "Order Entry"
        owner: "Sales"
        process_time_minutes: 15
        lead_time_hours: 2
        complete_accurate_percent: 85
        inventory: 50
        waste_types:
          - type: defects
            description: "Manual entry errors"
          - type: motion
            description: "Multiple system entry"

      - name: "Credit Check"
        owner: "Finance"
        process_time_minutes: 10
        lead_time_hours: 8
        complete_accurate_percent: 95
        inventory: 30
        is_bottleneck: true
        waste_types:
          - type: waiting
            description: "Batch processing"

  waste_analysis:
    - type: waiting
      percent_of_lead_time: 45
      root_causes:
        - "Batch processing"
        - "Scheduled pickups"

    - type: inventory
      total_wip: 240
      root_causes:
        - "No WIP limits"
        - "Push system"

  future_state:
    target_process_time_minutes: 47
    target_lead_time_hours: 6.7
    target_flow_efficiency_percent: 11.7

    improvements:
      - name: "Real-time credit API"
        waste_eliminated: waiting
        impact: high
        effort: medium
        lead_time_reduction_hours: 7.9

  roadmap:
    - phase: 1
      improvements: ["Real-time credit API", "Order validation"]
      duration_weeks: 4

    - phase: 2
      improvements: ["On-demand carrier", "Inventory automation"]
      duration_weeks: 8
yaml
value_stream:
  name: "Customer Order Fulfillment"
  version: "1.0"
  date: "{ISO-8601-date}"
  analyst: "value-stream-analyst"

  boundaries:
    trigger: "Customer places order"
    end_state: "Customer receives product"
    customer: "External retail customer"

  current_state:
    total_process_time_minutes: 70
    total_lead_time_hours: 44
    flow_efficiency_percent: 2.7
    wip_total: 240

    steps:
      - name: "Order Entry"
        owner: "Sales"
        process_time_minutes: 15
        lead_time_hours: 2
        complete_accurate_percent: 85
        inventory: 50
        waste_types:
          - type: defects
            description: "Manual entry errors"
          - type: motion
            description: "Multiple system entry"

      - name: "Credit Check"
        owner: "Finance"
        process_time_minutes: 10
        lead_time_hours: 8
        complete_accurate_percent: 95
        inventory: 30
        is_bottleneck: true
        waste_types:
          - type: waiting
            description: "Batch processing"

  waste_analysis:
    - type: waiting
      percent_of_lead_time: 45
      root_causes:
        - "Batch processing"
        - "Scheduled pickups"

    - type: inventory
      total_wip: 240
      root_causes:
        - "No WIP limits"
        - "Push system"

  future_state:
    target_process_time_minutes: 47
    target_lead_time_hours: 6.7
    target_flow_efficiency_percent: 11.7

    improvements:
      - name: "Real-time credit API"
        waste_eliminated: waiting
        impact: high
        effort: medium
        lead_time_reduction_hours: 7.9

  roadmap:
    - phase: 1
      improvements: ["Real-time credit API", "Order validation"]
      duration_weeks: 4

    - phase: 2
      improvements: ["On-demand carrier", "Inventory automation"]
      duration_weeks: 8

Mermaid Diagrams

Mermaid 流程图

Current State Flow:
mermaid
flowchart LR
    subgraph Current State
        A[Order Entry<br/>PT: 15m | LT: 2h<br/>WIP: 50] --> B[Credit Check<br/>PT: 10m | LT: 8h<br/>WIP: 30]
        B --> C[Inventory<br/>PT: 5m | LT: 4h<br/>WIP: 20]
        C --> D[Pick & Pack<br/>PT: 30m | LT: 6h<br/>WIP: 40]
        D --> E[Ship<br/>PT: 10m | LT: 24h<br/>WIP: 100]
    end

    style B fill:#ff9999
Future State Flow:
mermaid
flowchart LR
    subgraph Future State
        A[Order Entry<br/>PT: 10m | LT: 30m<br/>WIP: 10] --> B[Credit<br/>API: 1m<br/>WIP: 0]
        B --> C[Inventory<br/>Auto: 1m<br/>WIP: 0]
        C --> D[Pick & Pack<br/>PT: 25m | LT: 2h<br/>WIP: 15]
        D --> E[Ship<br/>PT: 10m | LT: 4h<br/>WIP: 20]
    end

    style B fill:#99ff99
    style C fill:#99ff99
当前状态流程：
mermaid
flowchart LR
    subgraph Current State
        A[Order Entry<br/>PT: 15m | LT: 2h<br/>WIP: 50] --> B[Credit Check<br/>PT: 10m | LT: 8h<br/>WIP: 30]
        B --> C[Inventory<br/>PT: 5m | LT: 4h<br/>WIP: 20]
        C --> D[Pick & Pack<br/>PT: 30m | LT: 6h<br/>WIP: 40]
        D --> E[Ship<br/>PT: 10m | LT: 24h<br/>WIP: 100]
    end

    style B fill:#ff9999
未来状态流程：
mermaid
flowchart LR
    subgraph Future State
        A[Order Entry<br/>PT: 10m | LT: 30m<br/>WIP: 10] --> B[Credit<br/>API: 1m<br/>WIP: 0]
        B --> C[Inventory<br/>Auto: 1m<br/>WIP: 0]
        C --> D[Pick & Pack<br/>PT: 25m | LT: 2h<br/>WIP: 15]
        D --> E[Ship<br/>PT: 10m | LT: 4h<br/>WIP: 20]
    end

    style B fill:#99ff99

When to Use

适用场景

ScenarioUse Value Stream Mapping?
Process improvementYes - identify waste
New system designYes - design for flow
Cost reductionYes - find inefficiencies
Lead time complaintsYes - find bottlenecks
Quality problemsPartial - with root cause analysis
Greenfield projectMaybe - limited current state
场景是否适合使用价值流映射？
流程改进是 - 识别浪费
新系统设计是 - 设计流畅流程
成本降低是 - 发现低效环节
前置时间投诉是 - 找到瓶颈
质量问题部分适用 - 需结合根本原因分析
全新项目可能适用 - 当前状态数据有限

Integration

集成

Upstream (Discovery)

上游（发现阶段）

  • process-modeling - Understand current process
  • capability-mapping - Link to business capabilities
  • stakeholder-analysis - Identify process owners
  • process-modeling - 理解当前流程
  • capability-mapping - 关联业务能力
  • stakeholder-analysis - 识别流程负责人

Downstream

下游

  • Requirements - Improvement requirements
  • Systems design - Automation opportunities
  • Project planning - Kaizen event planning
  • 需求管理 - 改进需求定义
  • 系统设计 - 识别自动化机会
  • 项目规划 - Kaizen活动规划

Related Skills

相关技能

  • journey-mapping
    - Customer experience perspective
  • capability-mapping
    - Capability view of value delivery
  • root-cause-analysis
    - Investigate bottleneck causes
  • prioritization
    - Prioritize improvement initiatives
  • process-modeling
    - Detailed BPMN process diagrams
  • estimation
    - Estimate improvement effort
  • benchmarking
    - Current vs target comparison
  • journey-mapping
    - 客户体验视角
  • capability-mapping
    - 价值交付的能力视图
  • root-cause-analysis
    - 调查瓶颈原因
  • prioritization
    - 优先级排序改进举措
  • process-modeling
    - 详细BPMN流程图表
  • estimation
    - 估算改进投入
  • benchmarking
    - 当前与目标状态对比

Version History

版本历史

  • v1.0.0 (2025-12-26): Initial release
  • v1.0.0 (2025-12-26): 初始版本