流程映射指南：流程图、BPMN、泳道图与价值流图详解

Process Mapping by danhvb/my-ba-skills

GitHub

安装命令

npx skills add https://github.com/danhvb/my-ba-skills --skill 'Process Mapping'

方法论数据可视化数据分析

🇨🇳中文介绍

流程映射技能

目的

创建清晰、专业的业务流程图表，以可视化工作流程、识别低效环节，并向利益相关者和开发团队传达流程。

使用时机

记录当前状态（现状）流程
设计未来状态（未来）流程
识别流程差距和低效环节
向利益相关者传达工作流程
系统设计和集成规划

流程映射类型

1. 流程图

最适合：简单、线性的流程符号：

⬭ 椭圆形：开始/结束
▭ 矩形：流程/活动
◇ 菱形：决策
▱ 平行四边形：输入/输出
→ 箭头：流向

示例 - 订单处理：

Start → Receive Order → Validate Order → [Valid?]
                                           ├── Yes → Process Payment → [Paid?]
                                           │                            ├── Yes → Ship Order → End
                                           │                            └── No → Notify Customer → End
                                           └── No → Reject Order → End

2. BPMN 2.0（业务流程模型与标注）

最适合：涉及多个参与者的复杂流程 关键元素：

事件：开始（○）、中间（◎）、结束（◉）
活动：任务（▭）、子流程（▭+）
网关：排他（◇×）、并行（◇+）、包容（◇○）
泳道：用于不同参与者的池和道

示例 - 发票审批 BPMN：

Pool: Invoice Approval Process
├── Lane: Requester
│   ├── Start Event
│   ├── Task: Submit Invoice
│   └── Task: Revise Invoice (if rejected)
├── Lane: Manager
│   ├── Task: Review Invoice
│   └── Gateway: Approve? (Yes/No)
├── Lane: Finance
│   ├── Task: Process Payment
│   └── End Event: Invoice Paid

3. 泳道图

最适合：展示职责的跨职能流程结构：为每个角色/部门设置水平或垂直泳道

示例 - 客户支持：

| Customer        | Support Agent    | Technical Team   | Manager         |
|-----------------|------------------|------------------|-----------------|
| Submit Ticket   |                  |                  |                 |
|       ↓         |                  |                  |                 |
|                 | Receive & Triage |                  |                 |
|                 |       ↓          |                  |                 |
|                 | [Can Resolve?]   |                  |                 |
|                 | Yes: Resolve     |                  |                 |
|                 | No: ────────────→| Investigate      |                 |
|                 |                  |       ↓          |                 |
|                 |                  | [Need Escalation?]               |
|                 |                  | No: Fix & Return |                 |
|                 |                  | Yes: ───────────→| Approve Fix    |
|                 | Update Customer  |←─────────────────|                 |
| Receive Update  |←─────────────────|                  |                 |

4. 价值流图

最适合：精益流程改进，识别浪费元素：流程步骤、等待时间、增值与非增值活动

流程层级

L0：上下文图

整个系统的高层视图
显示外部实体和交互
一页纸，执行摘要级别

L1：流程区域视图

主要的流程区域/模块
显示区域之间的关键输入/输出
5-10 个主要流程

L2：详细流程流

流程内的逐步活动
包含决策和分支
显示负责角色

L3：程序步骤

详细的程序/工作指导
逐屏指导
用于培训/标准操作程序

Mermaid 图表（基于代码）

流程图示例

flowchart TD
    A[Start: Customer Order] --> B{Inventory Available?}
    B -->|Yes| C[Reserve Inventory]
    B -->|No| D[Backorder]
    C --> E[Process Payment]
    E --> F{Payment Successful?}
    F -->|Yes| G[Create Shipment]
    F -->|No| H[Notify Customer]
    G --> I[Ship Order]
    I --> J[End: Order Delivered]
    D --> K[Notify Customer of Delay]
    H --> L[End: Order Cancelled]

序列图示例

sequenceDiagram
    participant Customer
    participant WebApp
    participant PaymentAPI
    participant OrderService
    
    Customer->>WebApp: Submit Order
    WebApp->>OrderService: Create Order
    OrderService-->>WebApp: Order ID
    WebApp->>PaymentAPI: Process Payment
    PaymentAPI-->>WebApp: Payment Confirmed
    WebApp->>OrderService: Confirm Order
    OrderService-->>WebApp: Order Confirmed
    WebApp-->>Customer: Order Confirmation

状态图示例（订单状态）

stateDiagram-v2
    [*] --> Pending: Order Created
    Pending --> Processing: Payment Confirmed
    Pending --> Cancelled: Payment Failed
    Processing --> Shipped: Shipment Created
    Processing --> Cancelled: Customer Request
    Shipped --> Delivered: Delivery Confirmed
    Delivered --> Returned: Return Requested
    Returned --> Refunded: Refund Processed
    Delivered --> [*]
    Refunded --> [*]
    Cancelled --> [*]

特定领域流程示例

电子商务：结账流程

Start → View Cart → Enter Shipping → Select Shipping Method → 
Enter Payment → Review Order → Place Order → 
[Payment OK?] → Yes: Confirmation → End
              → No: Payment Error → Retry/Cancel

ERP：采购到付款（P2P）

Requisition → Approval Workflow → Purchase Order → 
Goods Receipt → Invoice Receipt → 3-Way Match → 
[Match OK?] → Yes: Payment → End
           → No: Exception Handling

CRM：线索到成交

Lead Capture → Lead Scoring → [Qualified?] → 
Yes: Create Opportunity → Discovery → Proposal → 
Negotiation → [Won?] → Yes: Close → Account Created
                     → No: Lost Analysis

CDP：数据激活流程

Data Collection → Identity Resolution → Profile Unification → 
Segmentation → Audience Building → Channel Activation → 
Campaign Execution → Response Tracking → Analytics

最佳实践

设计原则

✅ 应做：

保持简单和可读性
始终使用一致的标注
包含清晰的起点和终点
清晰地显示决策点
记录异常和错误路径
对多角色流程使用泳道
为复杂步骤添加注释
对图表进行版本控制

❌ 不应做：

用过多细节使图表过于复杂
混合使用标注风格
忘记异常/错误流程
跳过与利益相关者的验证
在不了解流程的情况下创建图表

验证

与流程负责人一起走查
与实际用户核实
用真实场景测试
记录假设
获得利益相关者签署同意

工具

Figma

设计自定义流程图表
使用 BPMN 符号的组件库
共享以进行协作

Mermaid（基于代码）

嵌入 Markdown 文档
友好的版本控制
在 Lark/Notion 中快速创建图表

Lucidchart/Miro

专业的 BPMN 图表
实时协作
模板库

流程分析技巧

识别瓶颈：哪里速度变慢？
发现冗余：哪些是重复的？
发现交接问题：哪里会出现遗漏？
质疑价值：这个步骤是否增加价值？
考虑自动化：哪些可以自动化？

后续步骤

流程映射之后：

差距分析（参见 gap-analysis 技能）
流程优化建议
系统变更需求
基于流程流的用户验收测试场景

参考资料

BPMN 2.0 规范（OMG）
价值流图（精益）
业务流程映射最佳实践

每周安装数

代码仓库

danhvb/my-ba-skills

首次出现

1970年1月1日

安全审计

Gen Agent Trust HubPass SocketPass SnykPass

🇺🇸English

Process Mapping Skill

Purpose

Create clear, professional business process diagrams that visualize workflows, identify inefficiencies, and communicate processes to stakeholders and development teams.

When to Use

Documenting current state (As-Is) processes
Designing future state (To-Be) processes
Identifying process gaps and inefficiencies
Communicating workflows to stakeholders
System design and integration planning

Process Mapping Types

1. Flowcharts

Best for : Simple, linear processes Symbols :

⬭ Oval: Start/End
▭ Rectangle: Process/Activity
◇ Diamond: Decision
▱ Parallelogram: Input/Output
→ Arrow: Flow direction

Example - Order Processing :

Start → Receive Order → Validate Order → [Valid?]
                                           ├── Yes → Process Payment → [Paid?]
                                           │                            ├── Yes → Ship Order → End
                                           │                            └── No → Notify Customer → End
                                           └── No → Reject Order → End

2. BPMN 2.0 (Business Process Model and Notation)

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

3. Swimlane Diagrams

Best for : Cross-functional processes showing responsibilities Structure : Horizontal or vertical lanes for each role/department

Example - Customer Support :

| Customer        | Support Agent    | Technical Team   | Manager         |
|-----------------|------------------|------------------|-----------------|
| Submit Ticket   |                  |                  |                 |
|       ↓         |                  |                  |                 |
|                 | Receive & Triage |                  |                 |
|                 |       ↓          |                  |                 |
|                 | [Can Resolve?]   |                  |                 |
|                 | Yes: Resolve     |                  |                 |
|                 | No: ────────────→| Investigate      |                 |
|                 |                  |       ↓          |                 |
|                 |                  | [Need Escalation?]               |
|                 |                  | No: Fix & Return |                 |
|                 |                  | Yes: ───────────→| Approve Fix    |
|                 | Update Customer  |←─────────────────|                 |
| Receive Update  |←─────────────────|                  |                 |

4. Value Stream Mapping

Best for : Lean process improvement, identifying waste Elements : Process steps, wait times, value-add vs. non-value-add

High-level view of the entire system
Shows external entities and interactions
One page, executive summary level

L1: Process Area View

Major process areas/modules
Shows key inputs/outputs between areas
5-10 major processes

L2: Detailed Process Flow

Step-by-step activities within a process
Includes decisions and branches
Shows roles responsible

L3: Procedural Steps

Detailed procedures/work instructions
Screen-by-screen guidance
Used for training/SOPs

Mermaid Diagrams (Code-based)

flowchart TD
    A[Start: Customer Order] --> B{Inventory Available?}
    B -->|Yes| C[Reserve Inventory]
    B -->|No| D[Backorder]
    C --> E[Process Payment]
    E --> F{Payment Successful?}
    F -->|Yes| G[Create Shipment]
    F -->|No| H[Notify Customer]
    G --> I[Ship Order]
    I --> J[End: Order Delivered]
    D --> K[Notify Customer of Delay]
    H --> L[End: Order Cancelled]

Sequence Diagram Example

sequenceDiagram
    participant Customer
    participant WebApp
    participant PaymentAPI
    participant OrderService
    
    Customer->>WebApp: Submit Order
    WebApp->>OrderService: Create Order
    OrderService-->>WebApp: Order ID
    WebApp->>PaymentAPI: Process Payment
    PaymentAPI-->>WebApp: Payment Confirmed
    WebApp->>OrderService: Confirm Order
    OrderService-->>WebApp: Order Confirmed
    WebApp-->>Customer: Order Confirmation

State Diagram Example (Order Status)

stateDiagram-v2
    [*] --> Pending: Order Created
    Pending --> Processing: Payment Confirmed
    Pending --> Cancelled: Payment Failed
    Processing --> Shipped: Shipment Created
    Processing --> Cancelled: Customer Request
    Shipped --> Delivered: Delivery Confirmed
    Delivered --> Returned: Return Requested
    Returned --> Refunded: Refund Processed
    Delivered --> [*]
    Refunded --> [*]
    Cancelled --> [*]

Domain-Specific Process Examples

E-commerce: Checkout Flow

Start → View Cart → Enter Shipping → Select Shipping Method → 
Enter Payment → Review Order → Place Order → 
[Payment OK?] → Yes: Confirmation → End
              → No: Payment Error → Retry/Cancel

ERP: Purchase-to-Pay (P2P)

Requisition → Approval Workflow → Purchase Order → 
Goods Receipt → Invoice Receipt → 3-Way Match → 
[Match OK?] → Yes: Payment → End
           → No: Exception Handling

Lead Capture → Lead Scoring → [Qualified?] → 
Yes: Create Opportunity → Discovery → Proposal → 
Negotiation → [Won?] → Yes: Close → Account Created
                     → No: Lost Analysis

CDP: Data Activation Flow

Data Collection → Identity Resolution → Profile Unification → 
Segmentation → Audience Building → Channel Activation → 
Campaign Execution → Response Tracking → Analytics

Keep it simple and readable
Use consistent notation throughout
Include clear start and end points
Show decision points clearly
Document exceptions and error paths
Use swimlanes for multi-role processes
Add annotations for complex steps
Version control diagrams

Overcomplicate with too many details
Mix notation styles
Forget exception/error flows
Skip validation with stakeholders
Create without understanding the process first

Walk through with process owners
Verify with actual users
Test with real scenarios
Document assumptions
Get stakeholder sign-off

Design custom process diagrams
Use component libraries for BPMN symbols
Share for collaboration

Mermaid (Code-based)

Embed in markdown documentation
Version control friendly
Quick diagrams in Lark/Notion

Professional BPMN diagrams
Real-time collaboration
Template libraries

Process Analysis Tips

Identify bottlenecks : Where do things slow down?
Find redundancies : What's duplicated?
Spot handoff issues : Where do things fall between cracks?
Question value : Does this step add value?
Consider automation : What can be automated?

After process mapping:

Gap analysis (see gap-analysis skill)
Process optimization recommendations
Requirements for system changes
UAT scenarios based on process flows

BPMN 2.0 Specification (OMG)
Value Stream Mapping (Lean)
Business Process Mapping best practices

Excel财务建模规范与xlsx文件处理指南：专业格式、零错误公式与数据分析

42,000 周安装

流程映射指南：流程图、BPMN、泳道图与价值流图详解

🇨🇳中文介绍

流程映射技能

目的

使用时机

流程映射类型

1. 流程图

2. BPMN 2.0（业务流程模型与标注）

3. 泳道图

4. 价值流图

流程层级

L0：上下文图

L1：流程区域视图

L2：详细流程流

L3：程序步骤

Mermaid 图表（基于代码）

流程图示例

序列图示例

状态图示例（订单状态）

特定领域流程示例

电子商务：结账流程

ERP：采购到付款（P2P）

CRM：线索到成交

CDP：数据激活流程

最佳实践

设计原则

验证

工具

Figma

Mermaid（基于代码）

Lucidchart/Miro

流程分析技巧

后续步骤

参考资料

🇺🇸English

Process Mapping Skill

Purpose

When to Use

Process Mapping Types

1. Flowcharts

2. BPMN 2.0 (Business Process Model and Notation)

相关 Skills

3. Swimlane Diagrams

4. Value Stream Mapping

Process Levels

L0: Context Diagram

L1: Process Area View

L2: Detailed Process Flow

L3: Procedural Steps

Mermaid Diagrams (Code-based)

Flowchart Example

Sequence Diagram Example

State Diagram Example (Order Status)

Domain-Specific Process Examples

E-commerce: Checkout Flow

ERP: Purchase-to-Pay (P2P)

CRM: Lead-to-Close

CDP: Data Activation Flow

Best Practices

Design Principles

Validation

Tools

Figma

Mermaid (Code-based)

Lucidchart/Miro

Process Analysis Tips

Next Steps

References

最新 Skills