企业效能 · 创新咨询Enterprise Effectiveness · Innovation Consulting

不讲黑话,
听完就懂,
做了就变。
No jargon.
Real clarity.
Actual change.

最接地气的企业效能与创新咨询顾问。不套模板,不走流程——每一个解法,都是为你的组织量身定制的。 The most grounded enterprise effectiveness and innovation consultant. No templates, no cookie-cutter processes — every solution is built for your organization's specific reality.

"效能和创新
从来不是两件事——
它们是同一个竞争力的两面。"
"Effectiveness and innovation
are never two things —
they're two sides of the same competitive edge."

10+
年企业实战经验
Years hands-on
5+
行业覆盖
Industries served
1
亚马逊出版著作
Amazon published
100%
口碑转介绍
Referral-based
企业效能提升 · 敏捷转型落地 · 创新思维培训 · 组织管理优化 · 3S Framework · Agile Transformation · Innovation Consulting · Enterprise Effectiveness · 企业效能提升 · 敏捷转型落地 · 创新思维培训 · 组织管理优化 · 3S Framework · Agile Transformation · Innovation Consulting · Enterprise Effectiveness ·
杰哥 Roger Chung
主流机构精益敏捷认证教练Certified Lean & Agile Coach (mainstream institutions)
《To Survive in the AI Era》作者Author · To Survive in the AI Era
3S创新体系(战略·能力·冲刺)创建者Creator · 3S Framework (Strategy · Skill · Sprint)
世界500强专属顾问Exclusive Consultant to Fortune 500 Companies

关于杰哥About Roger Chung

"我不是学了敏捷去教别人的顾问。我是在真实项目里把它用出来,才开始帮别人的人。" "I didn't learn agile to teach it. I used it in real projects first — then started helping others."

从工程师到项目经理,从敏捷教练到独立顾问——我的每一步都在回答同一个问题:组织怎样才能真正动起来?

我服务过欧莱雅、宝马车联网、国家电网、拜耳等企业,涵盖科技、制造、金融、快消、汽车行业。我不讲标准流程,我善于读懂你公司的现场,用核心思维融合实际情况,给出真正能落地的解法。
From engineer to project manager, from agile coach to independent consultant — every step has been answering the same question: how do organizations actually move?

I've worked with L'Oreal, BMW Connected Vehicle, State Grid, Bayer, and more. I don't follow standard playbooks — I read your specific situation and apply core thinking to build solutions that actually land.

3S创新体系 · Roger Chung原创方法论The 3S Framework · Roger Chung's Original Methodology

大多数企业的创新失败,不是因为缺少想法,而是因为战略、能力、执行三个层面彼此脱节。3S框架提供了一套贯穿上下层级的系统性方法,让创新真正落地。 Most organizations don't fail at innovation because of a lack of ideas — they fail because Strategy, Skill, and Sprint operate in silos. The 3S Framework connects all three layers into one closed-loop system.

S1
战略 Strategy
Strategy
Where to innovate
明确创新方向与组织目标对齐。确保每一项创新投入都指向真正的竞争力提升,而不是为创新而创新。
Define where to innovate and align with organizational goals. Ensures every innovation effort builds real competitive advantage — not innovation theater.
S2
能力 Skill
Skill
How to innovate
构建团队真正能用的创新能力——思维方式、工具方法、组织文化。能力不足,战略只是PPT。
Build the actual capability to innovate — mindsets, methods, and culture. Without Skill, Strategy stays on slide decks.
S3
冲刺 Sprint
Sprint
Make it happen — fast
通过快速迭代将想法转化为真实结果。冲刺不是蛮干,是有节奏地快速验证、快速学习、快速调整。
Turn ideas into real outcomes through rapid iteration. Sprint isn't about rushing — it's about fast validation, fast learning, and fast adjustment.

3S框架已系统化整理于著作《To Survive in the AI Era: Enterprise's 3S Innovation Workbook》 The 3S Framework is fully documented in To Survive in the AI Era: Enterprise's 3S Innovation Workbook

获取书籍 ↗Get the Book ↗

服务Services

两条线,
一个目标
Two tracks,
one goal

无论你是需要系统性解决组织问题的高管,还是需要为团队定制高质量培训的HR负责人——我只做一件事:让改变真正发生。 Whether you're an executive needing systemic organizational change, or an HR leader seeking high-quality custom training — I do one thing: make change actually happen.

顾问咨询Advisory

组织效能
系统诊断与落地
Organizational
Effectiveness Advisory

适合 → CEO · CIO · CTO · PMOFor → CEO · CIO · CTO · PMO

团队很忙但产出没变好?变革方案推了几次都没落地?我不给你一套方法论,我帮你找到真正的卡点,制定能在你的组织里活起来的解法。 Teams are busy but outcomes aren't improving? Transformation initiatives keep stalling? I don't hand you a methodology — I help you find the real bottleneck and build solutions that actually work in your organization.

  • 组织效能全链路诊断Full-chain organizational effectiveness diagnosis
  • 精益 · 敏捷转型落地辅导Lean · Agile transformation coaching
  • 流程优化与执行体系重建Process optimization and execution system rebuild
  • AI时代组织能力升级Organizational capability upgrade for the AI era
预约探索通话Book a Discovery Call
定制培训Custom Training

创新与效能
定制培训课程
Custom Innovation
& Effectiveness Training

适合 → HR Director · HRBP · 培训负责人For → HR Director · HRBP · L&D Leaders

不是套路课,不是听完就忘的讲座。我根据你团队的实际情况定制内容,确保学员能把方法带回工作中真正用起来。 Not off-the-shelf courses, not forgettable lectures. I customize content to your team's reality, ensuring participants can apply the methods back at work.

  • 精益管理 · 消除浪费工作坊Lean management · Waste elimination workshop
  • 敏捷思维与实践训练营Agile mindset and practice bootcamp
  • 创新思维:斯坦福5步法 · 双钻模型Innovation thinking: Stanford 5-step · Double Diamond
  • 3S框架管理层专项培训3S Framework leadership workshop
发送培训需求Submit Training Request
To Survive in the AI Era
Enterprise's 3S Innovation Workbook
Innovation · Strategy · Execution
Roger Chung

亚马逊出版著作

Published on Amazon KDP

To Survive
in the AI Era

在AI时代,企业如何从战略到执行系统性重建竞争力?本书围绕3S框架(Strategy·Skill·Sprint)展开,专为企业决策者、高管和顾问设计,是一套可落地的闭环创新手册。评分9.5/10。 Built around the 3S Framework (Strategy · Skill · Sprint), this is more than a business book — it's a closed-loop innovation workbook designed for executives, founders and consultants. Rated 9.5/10. Covers the full business lifecycle from strategic alignment to team capability to execution.

在 Amazon 查看View on Amazon

洞察Insights

不讲黑话的
管理洞察
Management insights
without the jargon

查看全部文章View All

人效优化

Talent Effectiveness

年薪50万的高管,正在成为最贵的文员 Your ¥500K Executive Is Doing Clerk Work

某制造企业生产总监,年薪50万,72%的工作时间耗在报销核对、PPT格式调整、物料协调上。核心的产线优化、供应链降本,根本没时间做。6个月后,这个数字降到了8%——不是换了人,是换了机制……

A manufacturing plant director. ¥500K salary. 72% of working hours spent on expense reconciliation, PPT formatting, and materials coordination. Zero time for production optimization or cost reduction. Six months later, that 72% dropped to 8% — same person, different system…

低价值占比 72% → 8%Low-value work: 72% → 8% · 年节省成本 200万+Annual savings: ¥2M+ · 人效提升 32%Productivity +32%

三大根因:① 无岗位价值分级——高管承接所有层级的工作;② 无事务拦截机制——所有琐事直接对接高管;③ 无匹配的考核导向——KPI考核琐事完成率而非核心成果。

Three root causes: ① No role-value tiering — executives handle all levels of work; ② No task-filtering mechanism — all requests go directly to the executive; ③ Misaligned KPIs — measuring task completion instead of strategic outcomes.

三步解法:① 岗位价值分级(核心/重要/常规/低价值四级);② 配置商务助理推行事务拦截;③ 重设高管KPI,仅考核战略落地、业务增长、团队成长三个维度。

Three-step fix: ① Value-tier all tasks (Critical / Important / Routine / Low-value); ② Assign a business assistant with task-filtering rules; ③ Rebuild executive KPIs around strategy execution, business growth, and team development only.

企业最大的浪费,不是员工摸鱼,而是把高价值的人放在低价值的事上。

The biggest waste in any organization isn't employees slacking — it's putting high-value people on low-value work.

人效优化 · 精益管理 · 制造业 / 全行业适用

Talent Effectiveness · Lean Management · Manufacturing / All Industries

流程优化

Process Design

47个审批节点,看似管控严密,实则没人负责 47 Approval Nodes. Zero Accountability.

一个需求走47个签字,少则3天多则半个月。出了问题回头追责,每个人都说"前面的人已经看过了"。层层审批不是在管控风险,是在把责任彻底稀释……

One request. 47 signatures. Three days minimum, two weeks typical. When something goes wrong, everyone says "the person before me already reviewed it." Layers of approval don't control risk — they dissolve accountability…

某财务科技公司改造成果:审批节点从47个压缩至最多21个,平均审批时长从2个月缩短至4小时,因审批不严造成的需求延期率从80%降至10%以下,审批责任明确率100%。

Results from a fintech company: Approval nodes cut from 47 to 21 max. Average approval time: 2 months → 4 hours. Requirement delay rate due to approval issues: 80% → under 10%. Accountability clarity: 100%.

三步根治:① 审批节点瘦身,最多3个节点,明确"谁申请谁负责、谁审批谁担责";② 分级授权,按金额和事项类型下放决策权;③ 审批追责制度,审批人对结果终身负责。

Three fixes: ① Slim approval nodes to 3 max, with clear ownership; ② Tiered authorization by amount and type; ③ Lifetime accountability — approvers own outcomes, not just signatures.

层层审批不是管控,是推卸责任。权责对等,才是真正的风险管控。

Layered approvals aren't control — they're distributed blame. Real risk management means matching authority with accountability.

流程优化 · 组织效能 · 互联网 / SaaS / 金融科技

Process Design · Org Effectiveness · Internet / SaaS / Fintech

组织效能

Organizational Efficiency

麦肯锡:66%的企业正在低效内耗 McKinsey: 66% of Companies Are Trapped in Inefficiency

麦肯锡调研显示,66%的高管承认自己公司效率极低。人越来越多,速度越来越慢——以前几个人一天搞定的事,现在几十个人要做一周。规模越大,效率越低,增长越慢……

McKinsey research shows 66% of executives admit their organization is highly inefficient. More people, slower results — what three people finished in a day now takes thirty people a week. The bigger you grow, the slower you move…

规模化低效的三大根源:① 流程在部门间断裂推诿,无完整价值流;② 决策权集中在上层,离业务最远的人在拍板;③ 员工不清楚自己的工作在为客户创造什么价值,无效工作大量存在。

Three root causes of scaling inefficiency: ① Processes break and stall at department boundaries; ② Decision authority sits furthest from the customer; ③ Employees don't know what value their work creates — so non-value work proliferates.

三个核心原则:① 端到端价值流打通,消除部门墙;② 最小授权单元,让听得见炮火的人做决策;③ 全员价值共识,从根源杜绝无效工作。

Three core principles: ① Build end-to-end value streams, eliminate department silos; ② Minimum authorization unit — let those closest to the customer decide; ③ Organization-wide value clarity — eliminate non-value work at the root.

没有效率的规模,越大越危险。企业的增长,靠的是效率提升,不是人员扩张。

Scale without efficiency is a liability, not an asset. Growth comes from doing more with what you have — not from hiring more people to do the same things slowly.

组织效能 · 精益 · 制造业 / 快消 / 美妆 / 汽车

Org Efficiency · Lean · Manufacturing / FMCG / Beauty / Automotive

FAQ

常见问题Common Questions

关于企业效能、敏捷转型和创新管理,这些是我被问得最多的问题。The questions I get asked most about enterprise effectiveness, agile transformation, and innovation management.

企业敏捷转型应该从哪里开始?Where should an enterprise agile transformation begin? +
敏捷转型最常见的失败是从工具开始——上了Jira,开了站会,但什么都没变。正确的起点是从最痛的一个业务问题出发:找到一个真实的交付卡点,组建一个小的跨职能团队,用敏捷方式解决它。让第一个真实的成果建立内部的信心,再逐步扩展。The most common failure in agile transformation is starting with tools — installing Jira, running standups, but changing nothing real. The right starting point is your most painful business problem: find one real delivery bottleneck, form a small cross-functional team, and solve it with agile practices. Let the first real result build internal confidence, then expand from there.
如何真正提升团队的交付效率?How do you actually improve team delivery efficiency? +
大多数效率问题不是人的问题,是流程问题。先做价值流分析,把团队所有工作环节画出来,找到等待、重复和无效环节——通常你会发现50%以上的工作不产生客户价值。把这些砍掉,效率自然提升,不需要逼员工更努力。Most efficiency problems aren't people problems — they're process problems. Start with a value stream analysis: map all your team's work steps and identify waiting, duplication, and non-value activities. You'll typically find over 50% of work doesn't create customer value. Remove those, and efficiency improves naturally — no need to push people harder.
精益和敏捷有什么区别,企业应该选哪个?What's the difference between lean and agile — which should we use? +
精益的核心是消除浪费,优化流程效率,适合有明确重复流程的场景。敏捷的核心是快速响应变化,通过短周期迭代持续交付价值,适合不确定性高的场景。成熟的组织往往把精益用于流程优化,把敏捷用于产品和项目交付,融合使用效果最好。Lean focuses on eliminating waste and optimizing process efficiency — best for repeatable processes. Agile focuses on responding to change through short-cycle iteration — best for high-uncertainty contexts. Mature organizations use lean for process optimization and agile for product and project delivery, combining both for best results.
AI时代企业需要重建哪些核心能力?What core capabilities do organizations need to rebuild for the AI era? +
AI时代对组织能力提出三个新要求:第一,快速学习和适应的能力;第二,人机协作的工作方式——让人的精力聚焦在AI无法替代的判断、创意和关系上;第三,更短的决策和交付周期。这三点恰好是精益和敏捷方法论在AI时代的新应用场景。The AI era demands three new organizational capabilities: First, rapid learning and adaptation. Second, human-AI collaboration — humans focusing energy on judgment, creativity, and relationships AI cannot replace. Third, shorter decision and delivery cycles. These three needs are precisely where lean and agile find new application in the AI era.
定制培训和标准课程有什么区别?What's the difference between custom training and standard courses? +
标准课程给的是通用方法论,听完你知道概念,但不知道怎么用在自己公司。定制培训的设计起点是你团队现在面临的真实问题:我会先了解你们的业务背景、团队痛点和学员画像,再设计案例、练习和工具,确保学员能把方法带回工作中直接用。Standard courses give you general methodologies — you leave knowing the concepts but not how to apply them. Custom training starts with your team's real problems: I first understand your business context, team pain points, and participant profiles, then design cases, exercises, and tools so participants can apply the methods immediately.

联系我Get in Touch

谈谈你的
组织问题
Let's talk about
your challenge

不需要准备完整的需求文档。简单告诉我你现在面临的问题,我们先聊15分钟,看看有没有值得深入的方向。No need for a complete brief. Just tell me what you're facing right now. Let's talk for 15 minutes and see if there's a direction worth exploring.

WeChat
WeChat QR Code
扫码添加微信
Scan to add on WeChat
杰哥 · Roger Chung

实战知识库Practice Knowledge Base

框架不是答案
用对了才是
Frameworks aren't answers.
Knowing when to adapt them is.

每一篇都来自真实项目的实战复盘——不讲教科书,只讲在客户现场真正有用的那些。 Every entry comes from real engagements — not textbooks. What actually works on the ground, and why.

Scrum · 敏捷框架Agile

当Scrum遇上"强矩阵"组织——"合规缓冲带"设计Scrum in Hierarchical Orgs — Designing a Compliance Buffer

硬套标准Scrum的结果是Sprint计划两天后因合规被推翻,迭代节奏崩溃。我们的解法不是取消Scrum,而是在框架外加了一条缓冲带……Forcing standard Scrum in compliance-heavy orgs causes Sprint plans to collapse within days. The fix isn't to abandon Scrum — it's to add a buffer layer outside the framework…

金融国企合规

阅读实战案例 →Read the case →

双钻模型 · 创新方法Double Diamond · Innovation

发散和收敛到底怎么才算做到位——快消品牌案例What Real Divergence Looks Like — A FMCG Case

大多数团队以为自己在发散,实际上是在为决策者已有的预设答案寻找论据。真正到位的发散必须同时满足两个条件……Most teams think they're diverging — they're actually finding evidence for conclusions already made. Real divergence requires two conditions simultaneously…

快消美妆产品创新

阅读实战案例 →Read the case →

八大浪费 · 精益管理8 Wastes · Lean

我在服务现场发现的"第九种浪费"——决策浪费The 9th Waste I Found on the Ground — Decision Waste

传统八大浪费聚焦执行层,但有一种更致命更隐蔽的浪费——不决策、假装决策、翻盘式决策。它放大其他所有浪费……The classic 8 wastes focus on execution. But there's a more lethal, invisible one — non-decisions, fake decisions, and reversed decisions. It amplifies all others…

零售数字化决策机制

阅读实战案例 →Read the case →

Kanban · 敏捷框架Agile

看板不只是一块板——在非研发团队引入流动思维的三个适配动作Kanban Beyond the Board — 3 Adaptations for Non-Dev Teams

看板落地失败的常见原因不是板子画得不对,而是只搬来了可视化的表象,没引入限制在制品和管理流动的内核……Most Kanban failures aren't about drawing the board wrong. They import the visual without the core: WIP limits and flow management…

市场团队非研发流动管理

阅读实战案例 →Read the case →

SAFe · 规模化敏捷Scaled Agile

SAFe不是重型Scrum——PI Planning在制造企业的改造版本SAFe Isn't Heavy Scrum — How We Rebuilt PI Planning for Manufacturing

PI Planning的核心价值不在于两天的时间盒,而在于跨团队依赖关系被显性化、被面对面协商这个过程。我们把它压缩成了一天……PI Planning's value isn't the two-day timebox — it's making cross-team dependencies visible and negotiated face-to-face. We compressed it to one day…

制造业汽车多团队

阅读实战案例 →Read the case →

LeSS vs SoS · 规模化敏捷Scaled Agile

多团队Scrum时,我什么时候选LeSS,什么时候选SoSWhen to Choose LeSS vs SoS — My Decision Framework

选框架的核心变量不是团队数量,而是产品边界和团队耦合度。选错框架的代价是直接而隐蔽的……The real decision variable isn't team count — it's product boundary and coupling degree. Choosing wrong has direct and hidden costs…

SaaS研发团队规模化

阅读实战案例 →Read the case →

精益管理 · 服务型团队Lean · Service Teams

精益不是零库存——对服务型团队做精益改造,我先改的是"完工定义"Lean Isn't Zero Inventory — The First Thing I Fix Is the Definition of Done

服务型团队的库存是看不见的:未回复的邮件、待审的方案、进行中的需求讨论。它们不占物理空间,却占用了最稀缺的资源——注意力……Service team inventory is invisible: unread emails, pending proposals, open requirement discussions. No physical space — but consuming the scarcest resource: attention…

科技企业解决方案团队知识工作

阅读实战案例 →Read the case →

斯坦福五步法 · 创新方法Design Thinking · Innovation

在B2B企业里,"共情"这一步需要重新设计In B2B, the Empathy Step Needs to Be Redesigned

B2B场景中"用户"和"客户"往往不是同一个人。硬套标准共情做法,要么拿不到真实信息,要么拿到的是被精心挑选的客套话……In B2B, "user" and "customer" are rarely the same person. Standard empathy methods either fail to get real information or return carefully curated pleasantries…

B2B SaaS供应链产品设计

阅读实战案例 →Read the case →

Google HEART · 用户体验UX Measurement

HEART模型的本土化改造——没有大规模数据时如何做体验度量Localizing HEART — UX Measurement Without Big Data

HEART在B2B产品和企业内部系统中面临同一挑战:没有大规模数据。但这不意味着用不了,而是需要"小样本替代"策略……HEART faces the same challenge in B2B and internal systems: no large-scale data. But that doesn't mean it's unusable — it means small-sample substitution…

HR系统企业内部产品体验度量

阅读实战案例 →Read the case →

用户体验设计 · 服务设计UX Design · Service Design

体验地图不是画画而已——如何把它变成跨部门对齐工具Experience Maps Aren't Art Projects — Using Them as Alignment Tools

一张体验地图贴到墙上时,各部门的第一反应是沉默。地图清楚显示,客户为了完成一件事被迫在五个部门间辗转……When an experience map goes on the wall, departments go silent. The map shows clearly: the customer crosses five departments just to complete one thing…

保险理赔跨部门协作

阅读实战案例 →Read the case →