traction-eos

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Entrepreneurial Operating System (EOS)

创业操作系统(EOS)

A complete system for running a business with six key components. Designed for entrepreneurial companies ($2M-$50M revenue, 10-250 employees) that want to align vision and execution.
一套包含六大核心组件的完整企业运营系统,专为营收在200万-5000万美元、员工规模10-250人的创业公司设计,帮助企业对齐愿景与执行方向。

Core Principle

核心原则

Most businesses suffer from the same core issues: people, vision, traction. EOS provides a simple, complete operating system that strengthens the Six Key Components of any organization.
The foundation: Great vision without traction is hallucination. Traction without vision is aimless. EOS connects the two through a practical, weekly operating rhythm.
大多数企业都面临着相同的核心问题:人员、愿景、执行力。 EOS提供了一套简单、完整的操作系统,能够强化任何组织的六大关键组件。
基础逻辑:缺乏执行力的愿景只是空想;没有愿景的执行力则毫无方向。EOS通过一套实用的每周运营节奏,将二者紧密关联。

Scoring

评分机制

Goal: 10/10. When evaluating or implementing business processes, rate 0-10 based on EOS component strength. A 10/10 means all six components are strong, meetings are productive, and quarterly rocks are consistently achieved; lower scores indicate gaps. Always provide current score and improvements to reach 10/10.
目标:10/10。在评估或部署业务流程时,根据EOS各组件的成熟度打0-10分。10/10意味着六大组件均表现强劲,会议富有成效,季度核心任务(Rocks)持续完成;分数越低则表明存在越多短板。需始终提供当前分数及提升至10/10的改进方案。

The Six Key Components

六大关键组件

Vision → People → Data → Issues → Process → Traction
Every business is built on these six components. EOS strengthens all six.
愿景 → 人员 → 数据 → 问题 → 流程 → 执行力
任何企业的运营都基于这六大组件,EOS能够全面强化这些组件。

1. Vision Component

1. 愿景组件

Question: Does everyone in the organization know where you're going and how you plan to get there?
Tool: Vision/Traction Organizer (V/TO)
The V/TO answers eight questions on two pages:
QuestionWhat It DefinesExample
Core Values3-7 non-negotiable beliefs"Own it", "Do the right thing", "Grow or die"
Core FocusPurpose/cause/passion + niche"Simplify small business" + "Cloud accounting"
10-Year TargetBig, hairy, audacious goal"$100M revenue" or "10,000 customers"
Marketing StrategyTarget market, 3 uniques, proven process, guaranteeWho you serve, why you're different
3-Year PictureWhat company looks like in 3 yearsRevenue, profit, headcount, key metrics
1-Year PlanRevenue, profit, measurables, goalsSpecific targets for this year
Quarterly Rocks3-7 priorities for this quarterThe most important things to accomplish in 90 days
Issues ListAll unresolved obstaclesProblems, ideas, opportunities to discuss
Process:
  1. Leadership team completes V/TO together (2-day off-site)
  2. Share with entire organization
  3. Review quarterly
  4. Update annually
Key insight: If leadership team can't agree on V/TO, you have a bigger problem. Alignment comes first.
See: references/vto.md for V/TO templates and exercises.
核心问题:组织内的所有人是否都清楚企业的前进方向及实现路径?
工具:愿景/执行力规划器(V/TO)
V/TO通过两页内容回答八大问题:
问题定义内容示例
核心价值观3-7条不可妥协的信念“主动担当”、“坚守原则”、“持续成长”
核心聚焦使命/事业热情 + 细分领域“简化小企业运营” + “云会计服务”
10年目标大胆、具有挑战性的目标“营收突破1亿美元”或“服务10000家客户”
营销策略目标市场、3项差异化优势、验证有效的流程、服务保障服务对象、差异化原因
3年蓝图3年后企业的状态营收、利润、员工规模、关键指标
1年计划营收、利润、可衡量指标、具体目标本年度的明确目标
季度核心任务(Rocks)本季度的3-7项优先级事项未来90天内必须完成的最重要事项
问题清单所有未解决的障碍待讨论的问题、想法、机会
实施流程:
  1. 领导团队共同完成V/TO(为期2天的线下会议)
  2. 向全组织公示
  3. 每季度回顾
  4. 每年更新
关键洞察:如果领导团队无法就V/TO达成共识,说明存在更严重的问题。对齐愿景是首要任务。
参考:references/vto.md 获取V/TO模板及练习指南。

2. People Component

2. 人员组件

Question: Do you have the right people in the right seats?
Tool: Accountability Chart
Not an org chart—an accountability chart. Defines the structure and who owns what.
Structure:
Visionary ←→ Integrator
              ├── Sales/Marketing
              ├── Operations
              └── Finance
Two key roles:
  • Visionary: Big ideas, culture, key relationships, creative problem solving
  • Integrator: Runs business day-to-day, manages team, executes vision, resolves conflicts
Rule: One person per seat. No shared accountability.
Tool: People Analyzer
Evaluate every person on two dimensions:
1. Right Person (core values fit)
Core Value+ (most of the time)+/- (sometimes)- (rarely)
Own it+
Do the right thing+/-
Grow or die+
Standard: Must be "+" on all core values. One "+/-" is a conversation. Any "-" is wrong person.
2. Right Seat (GWC)
  • Get it: Understands the role
  • Want it: Genuinely wants the role
  • Capacity: Has the mental, physical, emotional capacity
Must be "yes" on all three. If missing any one, wrong seat.
The formula: Right People + Right Seats = A-players
People decisions:
  • Right person, right seat → Keep and invest in
  • Right person, wrong seat → Move to right seat
  • Wrong person, right seat → Coaching/exit (hardest call)
  • Wrong person, wrong seat → Exit immediately
See: references/people.md for accountability chart and people analyzer templates.
核心问题:你是否将合适的人放在了合适的岗位上?
工具:责任分工图
这不是普通的组织架构图,而是明确职责归属的责任分工图,定义了组织架构及各岗位负责人。
架构:
愿景型领导者 ←→ 整合型管理者
              ├── 销售/营销
              ├── 运营
              └── 财务
两大核心角色:
  • 愿景型领导者:负责提出宏大构想、塑造企业文化、维护关键关系、创造性解决问题
  • 整合型管理者:负责日常企业运营、管理团队、执行愿景、解决冲突
规则:每个岗位只能由一人负责,不得共享职责。
工具:人员评估器
从两个维度评估每位员工:
1. 合适的人(契合核心价值观)
核心价值观+(大部分时间符合)+/-(有时符合)-(极少符合)
主动担当+
坚守原则+/-
持续成长+
标准:必须在所有核心价值观上都评“+”。出现一个“+/-”需要沟通,任何“-”都说明该员工不适合。
2. 合适的岗位(GWC原则)
  • Get it:理解岗位要求
  • Want it:真正渴望该岗位
  • Capacity:具备相应的脑力、体力、精力
必须三项全满足。若缺少任何一项,说明岗位不合适。
公式:合适的人 + 合适的岗位 = 顶尖人才
人员决策:
  • 合适的人+合适的岗位 → 留用并重点培养
  • 合适的人+不合适的岗位 → 调至合适岗位
  • 不合适的人+合适的岗位 → 辅导或辞退(最艰难的决策)
  • 不合适的人+不合适的岗位 → 立即辞退
参考:references/people.md 获取责任分工图及人员评估器模板。

3. Data Component

3. 数据组件

Question: Are you managing based on objective data, or subjective opinions?
Tool: Scorecard
A weekly report card of 5-15 numbers that tell you how the business is doing.
Scorecard rules:
  • Activity-based metrics (leading indicators), not results (lagging)
  • Weekly numbers (monthly is too slow)
  • Every number has an owner
  • Every number has a goal
  • Red/green: on track or off track
Example Scorecard:
MetricOwnerGoalW1W2W3W4
RevenueSales Lead$50K/wk
New LeadsMarketing100/wk
Demos CompletedSales20/wk
Customer NPSSupport>50
Cash BalanceFinance>$200K
Benefits:
  • Spot problems 2-4 weeks earlier
  • Reduce "gut feeling" management
  • Create accountability without micromanagement
  • Everyone knows the score
Metric selection: If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?
See: references/data.md for scorecard templates and metric selection.
核心问题:你是基于客观数据还是主观判断进行管理?
工具:业绩评分卡
这是一份包含5-15项指标的每周报告,反映企业的运营状况。
评分卡规则:
  • 采用基于行动的指标(领先指标),而非结果指标(滞后指标)
  • 每周更新数据(月度更新太慢)
  • 每项指标都有负责人
  • 每项指标都有目标值
  • 用红/绿标识:达标或未达标
示例评分卡:
指标负责人目标第1周第2周第3周第4周
营收销售主管5万美元/周
新线索营销团队100条/周
完成演示销售团队20场/周
客户NPS客服团队>50
现金余额财务团队>20万美元
优势:
  • 提前2-4周发现问题
  • 减少“凭感觉”管理
  • 无需微观管理即可建立问责制
  • 所有人都清楚企业运营状况
指标选择逻辑:如果你要休假4周,哪5-15项指标能让你了解企业的运营情况?
参考:references/data.md 获取评分卡模板及指标选择指南。

4. Issues Component

4. 问题组件

Question: Are you identifying, discussing, and solving issues quickly?
Tool: Issues Solving Track (IDS)
Identify → Discuss → Solve
Step 1: Identify
  • What's the real issue? (Not the symptom)
  • Ask "Why?" until you reach root cause
  • State the issue in one sentence
Step 2: Discuss
  • Everyone gets input (not equal time)
  • Tangents are stopped
  • Focus on the ONE issue
  • Time-boxed (usually 5-15 minutes)
Step 3: Solve
  • Decision is made
  • Action items are assigned (who + what + when)
  • Move to next issue
Three types of issues:
TypeExamplesAction
ProblemsCustomer churn, team conflict, system outageIDS → solve
IdeasNew feature, process change, market opportunityIDS → decide (yes/no/later)
ObstaclesBlocking a rock, resource constraint, dependencyIDS → remove or escalate
Issues list rules:
  • Everyone can add issues
  • Prioritize: most important first
  • Not all issues get solved every meeting
  • Unsolved issues carry forward
Common IDS mistakes:
  • Discussing symptoms, not root cause
  • Rehashing same issue every week
  • No clear action items
  • Too much discussion, not enough solving
See: references/issues.md for IDS facilitation guides.
核心问题:你是否能快速识别、讨论并解决问题?
工具:问题解决流程(IDS)
Identify(识别)→ Discuss(讨论)→ Solve(解决)
步骤1:识别
  • 问题的本质是什么?(而非表面症状)
  • 不断追问“为什么”,直至找到根本原因
  • 用一句话清晰描述问题
步骤2:讨论
  • 所有人都可发表意见(不要求时长均等)
  • 及时制止偏离主题的讨论
  • 聚焦当前单个问题
  • 设定时间限制(通常5-15分钟)
步骤3:解决
  • 做出决策
  • 分配行动任务(负责人+任务内容+截止时间)
  • 推进下一个问题
三类问题:
类型示例行动
问题客户流失、团队冲突、系统故障运用IDS流程解决
想法新功能、流程优化、市场机会运用IDS流程决策(同意/否决/延后)
障碍阻碍核心任务推进、资源限制、依赖外部支持运用IDS流程排除或升级问题
问题清单规则:
  • 所有人都可添加问题
  • 按优先级排序:最重要的问题优先处理
  • 并非所有问题都能在每次会议中解决
  • 未解决的问题自动带入下一次会议
常见IDS误区:
  • 讨论症状而非根本原因
  • 每周重复讨论同一问题
  • 未明确行动任务
  • 讨论过多,解决不足
参考:references/issues.md 获取IDS流程引导指南。

5. Process Component

5. 流程组件

Question: Have you documented and consistently followed your core processes?
Tool: Core Process Documentation
The 20/80 rule: Document 20% of your processes to get 80% consistency.
Identify core processes:
  • HR process (hiring, onboarding, reviews)
  • Sales process (lead → close)
  • Operations process (delivery, fulfillment)
  • Customer service process (support → resolution)
  • Finance process (invoicing, collections)
Documentation format:
  1. Name the process
  2. List 5-20 major steps
  3. Add just enough detail (not a 50-page manual)
  4. Make it visual where possible
Example: Sales Process "The Closer"
  1. Qualify lead (BANT: Budget, Authority, Need, Timeline)
  2. Discovery call (30 min, use question guide)
  3. Demo (customize to their pain points)
  4. Proposal (send within 24 hours)
  5. Follow up (3 touches in 7 days)
  6. Close or disqualify
Followed By All (FBA):
  • Document it
  • Train on it
  • Measure compliance
  • Update quarterly
See: references/process.md for process documentation templates.
核心问题:你是否已记录并持续遵循核心业务流程?
工具:核心流程文档
20/80法则:记录20%的流程即可获得80%的运营一致性。
核心流程包括:
  • HR流程(招聘、入职、绩效评估)
  • 销售流程(线索转化至成交)
  • 运营流程(交付、履约)
  • 客户服务流程(支持至问题解决)
  • 财务流程(开票、收款)
文档格式:
  1. 命名流程
  2. 列出5-20个主要步骤
  3. 内容简洁(无需写成50页的手册)
  4. 尽可能可视化
示例:销售流程“成交闭环”
  1. 线索筛选(BANT原则:预算、决策权、需求、时间节点)
  2. 需求调研(30分钟,使用问题指南)
  3. 产品演示(针对客户痛点定制)
  4. 提交方案(24小时内发送)
  5. 跟进(7天内3次触达)
  6. 成交或淘汰线索
全员遵循(FBA):
  • 文档记录
  • 培训落地
  • 衡量合规性
  • 每季度更新
参考:references/process.md 获取核心流程文档模板。

6. Traction Component

6. 执行力组件

Question: Are you executing on your vision every day?
Two tools: Rocks and Level 10 Meetings
核心问题:你是否每天都在推进愿景的落地?
两大工具:季度核心任务(Rocks)和Level 10会议

Rocks (Quarterly Priorities)

季度核心任务(Rocks)

Definition: The 3-7 most important things to accomplish in the next 90 days.
Why 90 days?
  • Long enough to accomplish something meaningful
  • Short enough to maintain urgency
  • Natural human rhythm for focus
Rock-setting process:
  1. Review V/TO (vision, 3-year, 1-year)
  2. Brainstorm: "What must get done this quarter to stay on track?"
  3. Narrow to 3-7 company rocks
  4. Assign each rock to one owner
  5. Each leadership member also has 3-7 individual rocks
  6. Share with entire organization
  7. Track weekly
SMART rocks:
  • Specific: "Launch new pricing page" not "improve pricing"
  • Measurable: Clear completion criteria
  • Achievable: Can be done in 90 days
  • Realistic: Given current resources
  • Time-bound: Due end of quarter
Rock scoring:
  • Done = checked off (no partial credit)
  • Not done = carried forward or dropped
  • Goal: 80%+ completion rate
Anti-patterns:
  • Too many rocks (>7) → Focus is diluted
  • Rocks too vague → Can't tell if done
  • No owner → Nobody accountable
  • All rocks are "business as usual" → Not moving the needle
See: references/rocks.md for rock-setting exercises.
定义:未来90天内必须完成的3-7项最重要事项。
为什么是90天?
  • 足够长以完成有意义的事项
  • 足够短以保持紧迫感
  • 符合人类的自然专注周期
设定流程:
  1. 回顾V/TO(愿景、3年蓝图、1年计划)
  2. 头脑风暴:“本季度必须完成哪些事项才能保持正轨?”
  3. 筛选出3-7项企业级核心任务
  4. 为每项任务分配负责人
  5. 每位领导成员也需设定3-7项个人核心任务
  6. 向全组织公示
  7. 每周跟踪进度
SMART核心任务:
  • Specific(具体):“上线新定价页面”而非“优化定价”
  • Measurable(可衡量):明确完成标准
  • Achievable(可实现):90天内可完成
  • Realistic(现实):结合现有资源
  • Time-bound(有时限):季度末截止
核心任务评分:
  • 完成:打勾(不接受部分完成)
  • 未完成:带入下一季度或取消
  • 目标:完成率达到80%以上
反模式:
  • 核心任务过多(>7项)→ 分散注意力
  • 核心任务模糊 → 无法判断是否完成
  • 未分配负责人 → 无人问责
  • 所有核心任务都是“日常工作”→ 无法推动企业发展
参考:references/rocks.md 获取核心任务设定练习指南。

Level 10 Meeting (Weekly Leadership Meeting)

Level 10会议(每周领导会议)

The most important meeting in EOS. Runs every week, same day, same time, same agenda.
Duration: 90 minutes, never longer.
Agenda:
TimeSectionPurpose
5 minSegueGood news (personal and professional)
5 minScorecardReview weekly numbers
5 minRock ReviewOn track / Off track for each rock
5 minCustomer/Employee HeadlinesQuick updates
5 minTo-Do ListReview last week's to-dos (done or not done)
60 minIDSIdentify, Discuss, Solve issues
5 minConcludeRecap to-dos, rate meeting 1-10
Level 10 meeting rules:
  • Starts on time, ends on time (non-negotiable)
  • Same day, same time every week
  • No phones/laptops (except for agenda)
  • IDS gets 60 of 90 minutes (most important part)
  • Rate meeting 1-10 at end (target: 8+)
  • If below 8, discuss what to improve
Why "Level 10"?
  • Every meeting is rated 1-10 by participants
  • Goal is to consistently achieve 10/10
To-Do rules:
  • 7-day action items only
  • Each has owner and due date
  • Done = 100% complete
  • 90%+ completion rate is target
See: references/level-10.md for meeting facilitation guides.
EOS中最重要的会议。每周固定时间、固定时长、固定议程。
时长:90分钟,绝不超时。
议程:
时间环节目的
5分钟开场暖场分享个人及工作中的好消息
5分钟业绩评分卡回顾查看每周指标数据
5分钟核心任务进度回顾每项核心任务的达标/未达标情况
5分钟客户/员工动态快速更新重要信息
5分钟待办事项回顾查看上周待办事项的完成情况
60分钟IDS流程识别、讨论、解决问题
5分钟会议总结回顾待办事项,为会议打1-10分
Level 10会议规则:
  • 准时开始、准时结束(不可妥协)
  • 每周固定时间、固定日期
  • 禁止使用手机/笔记本电脑(仅可查看议程)
  • IDS环节占90分钟中的60分钟(最重要部分)
  • 会议结束时打分1-10分(目标:8分以上)
  • 若低于8分,讨论改进方向
为什么叫“Level 10”?
  • 每位参会者为会议打1-10分
  • 目标是持续达到10/10的满分
待办事项规则:
  • 仅记录7天内的行动任务
  • 每项任务都有负责人和截止时间
  • 完成=100%完成
  • 目标完成率90%以上
参考:references/level-10.md 获取会议引导指南。

EOS Implementation Timeline

EOS实施时间表

Typical rollout: 2 years to full implementation
PhaseTimelineFocus
Focus DayDay 1 (8 hours)Accountability chart, rocks, scorecard, Level 10
Vision Building Day 1Month 1V/TO: core values, core focus, 10-year target
Vision Building Day 2Month 2V/TO: marketing strategy, 3-year, 1-year, rocks
Quarterly SessionsEvery 90 daysReview rocks, set new rocks, IDS major issues
Annual PlanningYearlyFull V/TO review, set 1-year plan, Q1 rocks
Self-implementation vs. EOS Implementer:
  • Self: Read the book, follow the tools (free, slower)
  • EOS Implementer: Certified facilitator guides the process (faster, expensive)
典型落地周期:2年完成全面实施
阶段时间聚焦内容
聚焦日第1天(8小时)责任分工图、核心任务、业绩评分卡、Level 10会议
愿景构建第1天第1个月V/TO:核心价值观、核心聚焦、10年目标
愿景构建第2天第2个月V/TO:营销策略、3年蓝图、1年计划、核心任务
季度会议每90天回顾核心任务、设定新核心任务、运用IDS解决重大问题
年度规划每年全面回顾V/TO、设定1年计划、第一季度核心任务
自行实施 vs EOS认证顾问:
  • 自行实施:阅读书籍,按照工具操作(免费,进度较慢)
  • EOS认证顾问:由认证引导师指导实施(进度快,付费)

Organizational Checkup

组织健康检查

Rate your company 1-5 on each statement:
ComponentStatementScore (1-5)
VisionLeadership team is on the same page with where we're going and how to get there
PeopleWe have the right people in the right seats
DataWe manage from a weekly scorecard of 5-15 numbers
IssuesWe solve issues quickly and permanently
ProcessCore processes are documented and followed by all
TractionWe set and achieve 90-day priorities (rocks)
Scoring:
  • 25-30: Strong (maintain and fine-tune)
  • 20-24: Good (close gaps)
  • 15-19: Average (significant work needed)
  • Below 15: Weak (consider EOS implementer)
针对以下陈述为企业打1-5分:
组件陈述评分(1-5)
愿景领导团队对企业的前进方向及实现路径达成共识
人员我们将合适的人放在了合适的岗位上
数据我们基于包含5-15项指标的每周评分卡进行管理
问题我们能够快速、永久地解决问题
流程核心流程已形成文档并全员遵循
执行力我们设定并完成了90天核心任务
评分解读:
  • 25-30分:优秀(保持并优化)
  • 20-24分:良好(弥补短板)
  • 15-19分:一般(需要大量改进)
  • 低于15分:薄弱(建议聘请EOS认证顾问)

Common Mistakes

常见误区

MistakeWhy It FailsFix
Skipping Level 10sLose weekly rhythm, issues pile upProtect meeting, never cancel
Too many rocksNo focus, nothing gets doneMax 7 company rocks, 3-7 per person
Vague rocksCan't tell if doneWrite SMART rocks with clear criteria
No scorecardManaging by gut, surprisesChoose 5-15 weekly numbers
Wrong people keptDrags entire team downUse People Analyzer, make tough calls
V/TO not sharedTeam doesn't know the visionShare with entire company
误区失败原因解决方案
跳过Level 10会议失去每周运营节奏,问题堆积保护会议时间,绝不取消
核心任务过多分散注意力,一事无成企业级核心任务最多7项,每人3-7项
核心任务模糊无法判断是否完成制定符合SMART原则的核心任务
未使用业绩评分卡凭感觉管理,意外频发选择5-15项每周指标
留用不合适的人员拖垮整个团队运用人员评估器,做出艰难决策
未公示V/TO团队不了解愿景向全公司公示V/TO

Quick Diagnostic

快速诊断

Audit any business:
QuestionIf NoAction
Does leadership agree on vision?MisalignmentComplete V/TO together
Right people in right seats?Performance issuesPeople Analyzer on all seats
Managing from data weekly?Reactive managementBuild weekly scorecard
Issues solved permanently?Same problems repeatImplement IDS in Level 10s
Core processes documented?InconsistencyDocument top 5 processes
90-day priorities set and tracked?No tractionSet quarterly rocks
对任何企业进行审计:
问题如果答案为“否”行动
领导团队是否对愿景达成共识?愿景不一致共同完成V/TO
是否将合适的人放在了合适的岗位上?绩效问题对所有岗位运用人员评估器
是否基于每周数据进行管理?被动管理构建每周业绩评分卡
是否能永久解决问题?问题重复出现在Level 10会议中运用IDS流程
核心流程是否已形成文档?运营不一致记录前5项核心流程
是否设定并跟踪90天核心任务?缺乏执行力设定季度核心任务

Reference Files

参考文件

  • vto.md: Vision/Traction Organizer templates, eight questions
  • people.md: Accountability chart, People Analyzer, GWC
  • data.md: Scorecard templates, metric selection
  • issues.md: IDS process, facilitation, issue types
  • process.md: Core process documentation templates
  • rocks.md: Rock-setting exercises, SMART rocks
  • level-10.md: Meeting agenda, facilitation, rating
  • implementation.md: EOS rollout timeline, self-implementation guide
  • case-studies.md: Companies that implemented EOS successfully
  • vto.md: 愿景/执行力规划器模板、八大问题
  • people.md: 责任分工图、人员评估器、GWC原则
  • data.md: 业绩评分卡模板、指标选择指南
  • issues.md: IDS流程、引导方法、问题类型
  • process.md: 核心流程文档模板
  • rocks.md: 核心任务设定练习、SMART核心任务
  • level-10.md: 会议议程、引导方法、评分机制
  • implementation.md: EOS落地时间表、自行实施指南
  • case-studies.md: 成功实施EOS的企业案例

Further Reading

延伸阅读

This skill is based on the Entrepreneurial Operating System developed by Gino Wickman. For the complete system:
本技能基于Gino Wickman开发的创业操作系统(EOS)。如需了解完整系统,请参考:
  • 《Traction: Get a Grip on Your Business》(《掌控你的企业》)作者:Gino Wickman
  • 《Get a Grip》(《企业掌控力》)作者:Gino Wickman & Mike Paton(以商业寓言形式讲解EOS)
  • 《Rocket Fuel》(《火箭动力》)作者:Gino Wickman & Mark C. Winters(愿景型领导者+整合型管理者的协作关系)

About the Author

关于作者

Gino Wickman is the creator of EOS (Entrepreneurial Operating System) and founder of EOS Worldwide, a community of certified EOS Implementers who help companies implement the system. Wickman has worked with thousands of entrepreneurial leadership teams and has helped them get real traction. Traction has sold over 2 million copies and EOS is used by over 250,000 companies worldwide. His work focuses on the practical tools needed to run an entrepreneurial company.
Gino Wickman是创业操作系统(EOS)的创始人,也是EOS Worldwide的创立者,该组织拥有一批认证EOS顾问,帮助企业部署EOS系统。Wickman已与数千个创业公司领导团队合作,帮助他们实现真正的执行力。《Traction》销量已超过200万册,全球有超过25万家企业在使用EOS。他的研究聚焦于创业公司运营所需的实用工具。