business-analyst

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Business Analyst

业务分析师

Overview

概述

Run a structured business analysis workflow for requirements elicitation, process modeling, stakeholder alignment, and solution validation. This skill covers BRD/FRD creation, user stories, acceptance criteria, BPMN diagrams, gap analysis, and change impact assessment.

运行结构化业务分析工作流，涵盖需求获取、流程建模、利益相关者对齐及解决方案验证。该技能包含BRD/FRD文档创建、用户故事撰写、验收标准制定、BPMN流程图绘制、差距分析及变更影响评估。

Features

功能特性

Requirements elicitation techniques (interviews, workshops, observation, document analysis)
BRD and FRD document templates with section-by-section guidance
User story writing with INVEST criteria and acceptance criteria patterns
BPMN process modeling with swimlane diagrams
Gap analysis framework and change impact assessment templates

需求获取技术（访谈、研讨会、观察、文档分析）
带分节指导的BRD和FRD文档模板
符合INVEST标准的用户故事撰写及验收标准模板
带泳道图的BPMN流程建模
差距分析框架及变更影响评估模板

Usage

使用方法

Identify the user's BA need (requirements, process modeling, user stories, or solution validation)
Follow the corresponding workflow below
Produce structured outputs: BRD/FRD documents, user stories, BPMN diagrams, or gap analysis reports

识别用户的业务分析需求（需求类、流程建模类、用户故事类或解决方案验证类）
遵循下方对应的工作流
生成结构化输出：BRD/FRD文档、用户故事、BPMN流程图或差距分析报告

Examples

示例

User: "Gather requirements for a new feature" Agent: Runs Requirements Elicitation workflow, conducts stakeholder interviews, produces BRD with functional and non-functional requirements
User: "Map our order fulfillment process" Agent: Runs Process Modeling workflow, creates BPMN diagram with swimlanes, identifies bottlenecks and handoff points
User: "Write user stories for login" Agent: Runs User Story Writing workflow, produces stories with INVEST criteria and Given/When/Then acceptance criteria

用户：“为新功能收集需求” Agent：启动需求获取工作流，开展利益相关者访谈，生成包含功能与非功能需求的BRD
用户：“绘制我们的订单履行流程” Agent：启动流程建模工作流，创建带泳道的BPMN图，识别瓶颈与交接节点
用户：“为登录功能撰写用户故事” Agent：启动用户故事撰写工作流，生成符合INVEST标准并带有Given/When/Then验收标准的故事

When to Use

适用场景

Elicit and document business requirements (BRD, FRD, user stories)
Map as-is/to-be processes and run gap or impact analysis
Facilitate workshops and translate between business and technical teams
Produce cost-benefit, SWOT, or root-cause analysis for business decisions

获取并记录业务需求（BRD、FRD、用户故事）
绘制现状/目标流程并开展差距或影响分析
主持研讨会，搭建业务与技术团队间的沟通桥梁
为业务决策生成成本效益分析、SWOT分析或根本原因分析报告

Workflow Selection

工作流选择

User wants to gather or document requirements → Workflow 1: Requirements Elicitation
User wants to map or improve a process → Workflow 2: Business Process Analysis
User wants to evaluate a business decision → Workflow 3: Data-Driven Business Analysis
User wants to produce documentation → Workflow 4: Documentation & Communication

用户需收集或记录需求 → 工作流1：需求获取
用户需绘制或优化流程 → 工作流2：业务流程分析
用户需评估业务决策 → 工作流3：数据驱动型业务分析
用户需生成文档 → 工作流4：文档编制与沟通

When NOT to Use

不适用场景

Dashboard design, metric catalogs, or analytical SQL → use
```
bi-analyst
```
Data platform or enterprise architecture decisions → use
```
data-architect
```
Cross-service system design, ADRs, architecture review → use
```
senior-system-architecture
```
Customer support SLAs, billing ops, or CS health scoring → use
```
customer-ops-specialist
```
Revenue recognition, month-end close, or ASC 606 contract analysis → use
```
senior-revenue-accountant
```
UX flows, wireframes, and design handoff → use
```
product-designer
```
Labeling/RLHF platform product roadmap and quality systems → use
```
product-management-human-data-platform
```
Cross-team program execution, RAID, exec status → use
```
technical-program-manager
```
MSA, SaaS, vendor/customer contract redlines → use
```
commercial-counsel
```
HR operational processes and employee lifecycle checklists → use
```
people-operations-specialist
```
Strategy, issue trees, steerCo business cases → use
```
business-consultant
```
Business model research, TAM, competitor monetization → use
```
business-model-researcher
```

仪表板设计、指标目录或分析型SQL → 使用
```
bi-analyst
```
数据平台或企业架构决策 → 使用
```
data-architect
```
跨服务系统设计、ADR、架构评审 → 使用
```
senior-system-architecture
```
客户支持SLA、账单运营或客户成功健康评分 → 使用
```
customer-ops-specialist
```
收入确认、月末结账或ASC 606合同分析 → 使用
```
senior-revenue-accountant
```
UX流程、线框图及设计交接 → 使用
```
product-designer
```
标注/RLHF平台产品路线图与质量体系 → 使用
```
product-management-human-data-platform
```
跨团队项目执行、RAID、高管状态汇报 → 使用
```
technical-program-manager
```
MSA、SaaS、供应商/客户合同修订 → 使用
```
commercial-counsel
```
HR运营流程与员工生命周期检查清单 → 使用
```
people-operations-specialist
```
战略规划、议题树、SteerCo业务案例 → 使用
```
business-consultant
```
商业模式研究、TAM、竞品变现分析 → 使用
```
business-model-researcher
```

Core Workflows

核心工作流

1. Requirements Elicitation

1. 需求获取

Step-by-step process:

Prepare
- Review existing documentation, systems, and pain points
- Identify stakeholders (sponsors, users, implementers)
- Define scope boundaries (in-scope, out-of-scope)
Elicit
- Interview key stakeholders using open-ended questions
- Observe users in their current workflow (shadowing)
- Review existing reports, data, and system outputs
- Run workshops for complex or cross-functional needs
Analyze & consolidate
- Group requirements by theme (functional, non-functional, technical)
- Resolve conflicts between stakeholders
- Prioritize using MoSCoW or weighted scoring
Validate
- Walk through requirements with stakeholders
- Confirm understanding with prototypes or examples
- Get formal sign-off before proceeding

分步流程：

准备阶段
- 审阅现有文档、系统及痛点
- 识别利益相关者（发起人、用户、实施人员）
- 定义范围边界（范围内、范围外）
获取阶段
- 使用开放式问题访谈关键利益相关者
- 观察用户当前工作流（影子跟随法）
- 审阅现有报告、数据及系统输出
- 针对复杂或跨职能需求开展研讨会
分析与整合阶段
- 按主题分组需求（功能型、非功能型、技术型）
- 解决利益相关者间的冲突
- 使用MoSCoW或加权评分法进行优先级排序
验证阶段
- 与利益相关者共同审阅需求
- 通过原型或示例确认理解一致性
- 推进前获取正式签字确认

2. Business Process Analysis

2. 业务流程分析

Analysis workflow:

Map the current state (as-is)
- Identify actors, steps, decisions, and handoffs
- Note time spent, pain points, and error rates
- Document data inputs and outputs at each step
Identify gaps and inefficiencies
- Redundancies, manual workarounds, bottlenecks
- Missing integrations, duplicate data entry
- Compliance risks or audit gaps
Design the future state (to-be)
- Streamline or automate steps
- Eliminate non-value-add activities
- Define new roles, systems, and data flows
Plan the transition
- Phased rollout vs big-bang
- Change impact assessment
- Training and communication plan

分析工作流：

绘制当前状态（现状）
- 识别参与者、步骤、决策点及交接环节
- 记录耗时、痛点及错误率
- 记录各步骤的数据输入与输出
识别差距与低效点
- 冗余环节、手动变通方案、瓶颈
- 缺失的集成、重复数据录入
- 合规风险或审计缺口
设计未来状态（目标）
- 简化或自动化步骤
- 消除非增值活动
- 定义新角色、系统及数据流
规划过渡方案
- 分阶段上线 vs 一次性切换
- 变更影响评估
- 培训与沟通计划

3. Data-Driven Business Analysis

3. 数据驱动型业务分析

Analytical techniques:

Technique	When to Use	Output
Cost-benefit analysis	Evaluate initiatives	ROI, payback period, NPV
SWOT analysis	Strategic planning	Strengths, weaknesses, opportunities, threats
Root cause analysis	Problem diagnosis	5 Whys, fishbone diagram
Process mining	Understand actual vs documented process	Bottleneck map, variant analysis
Benchmarking	Compare performance	Gap vs industry leaders

分析技术：

技术	适用场景	输出
成本效益分析	评估举措	ROI、投资回收期、净现值
SWOT分析	战略规划	优势、劣势、机会、威胁
根本原因分析	问题诊断	5Why分析法、鱼骨图
流程挖掘	对比实际流程与文档流程	瓶颈地图、变体分析
基准测试	绩效对比	与行业领导者的差距

4. Documentation & Communication

4. 文档编制与沟通

Key documents:

Document	Purpose	Audience
Business Requirements Document (BRD)	What the business needs and why	Business stakeholders, project sponsor
Functional Requirements Document (FRD)	How the system should behave	Developers, QA, solution architects
User Stories	Feature from user perspective	Agile team, product owner
Process Flow	Visual step-by-step workflow	All stakeholders
Data Dictionary	Definitions of fields and terms	Technical team, data consumers

核心文档：

文档	用途	受众
Business Requirements Document (BRD)	明确业务需求及原因	业务利益相关者、项目发起人
Functional Requirements Document (FRD)	定义系统应具备的行为	开发人员、QA、解决方案架构师
用户故事	从用户视角描述功能	敏捷团队、产品负责人
流程流程图	可视化分步工作流	所有利益相关者
数据字典	定义字段与术语	技术团队、数据使用者