consultancy-practices
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseConsultancy Practices
质量咨询实践
<default_to_action>
When consulting on quality:
- LISTEN FIRST: Understand their context before prescribing solutions
- DISCOVER: What's the pain? What have they tried? What are constraints?
- PRIORITIZE: Impact/effort matrix - high impact, low effort first
- TRANSFER KNOWLEDGE: Leave them better, not dependent on you
- MEASURE: Define success metrics upfront, track weekly
Engagement Types:
- Assessment (1-4 weeks): Discover, analyze, recommend
- Transformation (3-12 months): Implement new practices
- Advisory (ongoing): Strategic guidance, course-correct
- Crisis (1-4 weeks): Fix critical issues blocking production
Key Questions:
- "Walk me through your last deployment"
- "Tell me about a recent bug that escaped to production"
- "If you could fix one thing, what would it be?" </default_to_action>
<default_to_action>
在提供质量咨询时：
- 先倾听：在给出解决方案前先理解他们的业务背景
- 挖掘痛点：他们面临什么问题？已经尝试过哪些方法？有哪些限制条件？
- 优先级排序：使用影响/投入矩阵——先处理高影响、低投入的事项
- 知识传递：让团队能力提升，而非依赖你
- 量化成果：提前定义成功指标，每周跟踪
咨询服务类型：
- 评估服务（1-4周）：挖掘、分析、给出建议
- 转型服务（3-12个月）：落地新实践
- 长期咨询（持续进行）：战略指导、方向修正
- 危机处理（1-4周）：修复阻碍生产的关键问题
核心问题：
- "请带我梳理一下你们上一次的部署流程"
- "和我说说最近一个漏到生产环境的Bug情况"
- "如果只能解决一个问题，你们会选哪个？" </default_to_action>
Quick Reference Card
快速参考卡片
The Consulting Process
咨询流程
| Phase | Duration | Goal | Deliverable |
|---|---|---|---|
| Discovery | Week 1-2 | Understand context | Interview notes, observations |
| Analysis | Week 2-3 | Identify root causes | Impact/effort matrix |
| Recommendations | Week 3-4 | Present findings | Report with roadmap |
| Implementation | Month 2-6+ | Execute changes | Working system, trained team |
| Transition | Final month | Ensure self-sufficiency | Handover docs |
| 阶段 | 时长 | 目标 | 交付物 |
|---|---|---|---|
| 挖掘调研 | 第1-2周 | 理解业务背景 | 访谈记录、观察报告 |
| 分析诊断 | 第2-3周 | 定位根本原因 | 影响/投入矩阵 |
| 方案建议 | 第3-4周 | 呈现调研结果 | 含实施路线图的报告 |
| 落地执行 | 第2-6个月及以上 | 推进变更落地 | 可运行的系统、经过培训的团队 |
| 过渡移交 | 最后一个月 | 确保团队自主运维 | 移交文档 |
Impact/Effort Matrix
影响/投入矩阵
| Priority | What | Action |
|---|---|---|
| High Impact, Low Effort | Quick wins | Do first |
| High Impact, High Effort | Major initiatives | Plan carefully |
| Low Impact, Low Effort | Nice-to-haves | If time permits |
| Low Impact, High Effort | Distractions | Skip |
| 优先级 | 事项类型 | 行动建议 |
|---|---|---|
| 高影响、低投入 | 快速见效项 | 优先执行 |
| 高影响、高投入 | 重大举措 | 仔细规划 |
| 低影响、低投入 | 锦上添花项 | 时间允许时执行 |
| 低影响、高投入 | 分散精力项 | 直接跳过 |
Common Patterns
常见场景应对
"We Need Test Automation"
"我们需要测试自动化"
What they say: "We need test automation"
What they mean: "Manual testing is too slow/expensive"
Discovery: How long is regression? What's deployment frequency?
Typical Finding: They need faster feedback, not "automation"
Recommendation:
- Unit tests for new code (TDD)
- Smoke tests for critical paths
- Keep exploratory for discovery
- Build automation incrementally
他们的表述： "We need test automation"
真实需求： "手动测试太慢/成本太高"
挖掘环节： 回归测试耗时多久？部署频率如何？
典型发现： 他们需要的是更快的反馈，而非单纯的"自动化"
建议：
- 为新代码编写单元测试（TDD模式）
- 为关键路径编写冒烟测试
- 保留探索性测试用于发现新问题
- 逐步构建自动化体系
"Fix Our Quality Problem"
"解决我们的质量问题"
What they say: "We have too many bugs"
What they mean: "Something is broken but we don't know what"
Discovery: Where found? What types? When introduced?
Typical Finding: No test strategy, testing too late, poor feedback loops
Recommendation:
- Shift testing left
- Improve coverage on critical paths
- Speed up CI/CD feedback
- Better requirements/acceptance criteria
他们的表述： "我们的Bug太多了"
真实需求： "某个环节出了问题，但我们不知道具体是什么"
挖掘环节： Bug出现在哪里？是什么类型？什么时候引入的？
典型发现： 缺乏测试策略、测试环节太晚、反馈循环低效
建议：
- 左移测试环节
- 提升关键路径的测试覆盖率
- 加快CI/CD反馈速度
- 优化需求/验收标准
"We Want to Scale Quality"
"我们想实现质量规模化"
What they say: "Growing fast, quality can't keep up"
What they mean: "Can't hire enough QA fast enough"
Discovery: Current QA:Dev ratio? Where's QA spending time?
Typical Finding: QA is bottleneck - manual regression, gatekeeping
Recommendation:
- Make QA strategic, not tactical
- Developers own test automation
- QA focuses on exploratory, risk analysis
- Use agentic approaches for scale
他们的表述： "团队扩张很快，质量保障跟不上"
真实需求： "我们没法快速招聘到足够多的QA人员"
挖掘环节： 当前QA与开发人员的比例是多少？QA的时间主要花在哪些方面？
典型发现： QA成为瓶颈——手动回归测试、审批流程繁琐
建议：
- 让QA聚焦战略层面，而非执行层面
- 由开发人员负责测试自动化
- QA专注于探索性测试和风险分析
- 采用Agent化方法实现规模化
Anti-Patterns
常见误区
| Anti-Pattern | Problem | Better |
|---|---|---|
| Cookie-Cutter | Same solution everywhere | Context-specific recommendations |
| Tool Pusher | Recommend expensive tools | Tools that solve actual problems |
| Process Nazi | Impose rigid process | Lightweight, fits their culture |
| Permanent Fixture | Never leave, create dependency | Work toward them not needing you |
| Blame Game | Point fingers at people | Fix systems, not blame people |
| 误区类型 | 问题 | 改进方向 |
|---|---|---|
| 一刀切方案 | 对所有客户套用相同解决方案 | 提供贴合业务场景的定制化建议 |
| 工具推销 | 推荐昂贵但不适用的工具 | 选择能解决实际问题的工具 |
| 流程至上 | 强加僵化的流程 | 采用轻量化、适配团队文化的流程 |
| 过度依赖 | 长期驻场，让团队形成依赖 | 推动团队实现自主运维 |
| 指责归责 | 指责具体人员 | 优化系统流程，而非追责个人 |
Difficult Situations
棘手场景应对
"We already tried that"
→ "Tell me what you tried and what didn't work" (learn from their experience)
"Our context is special"
→ "Help me understand what makes yours special" (they might be right, or making excuses)
"We don't have budget/time"
→ "What's the cost of not fixing this? Let's start small" (show ROI)
"That won't work here"
→ "What specific constraints? Let's adapt" (find what WILL work)
"我们已经试过这个方法了"
→ "可以和我说说你们具体尝试了什么，以及哪些部分没有达到预期吗？"（从他们的经验中学习）
"我们的场景很特殊"
→ "请帮我理解一下你们的场景特殊在哪里？"（他们可能是对的，也可能只是找借口）
"我们没有预算/时间"
→ "如果不解决这个问题，会带来哪些成本？我们可以从小处着手"（展示投资回报率）
"这个方法在这里行不通"
→ "具体有哪些限制条件？我们可以调整方案"（找到可行的解决路径）
Agent Integration
Agent集成
typescript
// Automated codebase assessment
const assessment = await Task("Assess Codebase", {
scope: 'client-project/',
depth: 'comprehensive',
reportFormat: 'executive-summary'
}, "qe-quality-analyzer");
// Returns: { qualityScore, testCoverage, technicalDebt, recommendations }
// ROI analysis for quality initiatives
const roi = await Task("Calculate ROI", {
currentState: { defectEscapeRate: 0.15, mttr: 48 },
proposedImprovements: ['test-automation', 'ci-cd-pipeline'],
timeframe: '6-months'
}, "qe-quality-analyzer");
// Returns: { estimatedCost, estimatedSavings, paybackPeriod }typescript
// Automated codebase assessment
const assessment = await Task("Assess Codebase", {
scope: 'client-project/',
depth: 'comprehensive',
reportFormat: 'executive-summary'
}, "qe-quality-analyzer");
// Returns: { qualityScore, testCoverage, technicalDebt, recommendations }
// ROI analysis for quality initiatives
const roi = await Task("Calculate ROI", {
currentState: { defectEscapeRate: 0.15, mttr: 48 },
proposedImprovements: ['test-automation', 'ci-cd-pipeline'],
timeframe: '6-months'
}, "qe-quality-analyzer");
// Returns: { estimatedCost, estimatedSavings, paybackPeriod }Agent Coordination Hints
Agent协作提示
Memory Namespace
Memory Namespace
aqe/consultancy/
├── assessments/* - Client assessments
├── recommendations/* - Prioritized recommendations
├── roi-analysis/* - ROI calculations
└── progress/* - Implementation trackingaqe/consultancy/
├── assessments/* - Client assessments
├── recommendations/* - Prioritized recommendations
├── roi-analysis/* - ROI calculations
└── progress/* - Implementation trackingFleet Coordination
Fleet Coordination
typescript
const consultingFleet = await FleetManager.coordinate({
strategy: 'client-engagement',
agents: [
'qe-quality-analyzer', // Assess current state
'qe-regression-risk-analyzer', // Risk assessment
'qe-quality-gate', // Define quality gates
'qe-deployment-readiness' // Deployment maturity
],
topology: 'hierarchical'
});typescript
const consultingFleet = await FleetManager.coordinate({
strategy: 'client-engagement',
agents: [
'qe-quality-analyzer', // Assess current state
'qe-regression-risk-analyzer', // Risk assessment
'qe-quality-gate', // Define quality gates
'qe-deployment-readiness' // Deployment maturity
],
topology: 'hierarchical'
});Related Skills
相关技能
- quality-metrics - Metrics for client reporting
- risk-based-testing - Client risk assessment
- holistic-testing-pact - Comprehensive strategy
- quality-metrics - 用于客户汇报的质量指标
- risk-based-testing - 客户风险评估
- holistic-testing-pact - 全面测试策略
Remember
谨记
Good consulting is about empowering teams, not creating dependency. Your success is measured by them not needing you anymore - while still wanting to work with you again.
Best compliment: "We've got this now, but when we tackle X next year, we're calling you."
Be honest. Be helpful. Be context-driven. Leave them better.
优秀的咨询是赋能团队，而非制造依赖。 你的成功衡量标准是：团队不再需要你，但未来有需求时仍愿意再次合作。
最佳赞美： "现在我们可以自己搞定了，但明年处理X项目时，我们还找你。"
保持真诚，提供切实帮助，贴合业务场景，让团队变得更好。