focus-timeboxing-8020

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Focus, Timeboxing, and 80/20

Purpose

目的

Focus, Timeboxing, and 80/20 provides structured techniques for managing attention, prioritizing high-impact work, and using time constraints to overcome procrastination and context-switching. This skill guides you through identifying your vital few tasks (80/20), designing focus blocks, timeboxing work, and managing energy to maximize deep work output.

Focus, Timeboxing, and 80/20 提供了一套结构化技巧，用于管理注意力、优先处理高影响力工作，并通过时间限制来克服拖延和工作场景切换问题。该方法会引导你识别关键的少数任务（80/20原则）、设计专注时段、进行Timeboxing工作管理以及优化精力分配，从而最大化深度工作的产出。

When to Use

适用场景

Use this skill when:

Overwhelmed by tasks: Too many things competing for attention, unsure where to focus
Procrastination: Important work gets delayed, easier tasks feel more urgent
Context-switching: Constantly interrupted, can't get into flow state
Productivity planning: Designing daily/weekly schedules, allocating time to priorities
Deep work needed: Complex thinking, writing, coding, design requiring sustained focus
Energy management: Feeling burned out, working long hours with low output
80/20 analysis: Identifying which 20% of efforts drive 80% of results
Meeting overload: Calendar packed, no time for focused work
Task batching: Grouping similar tasks (emails, calls, admin) for efficiency
Deadline pressure: Using time constraints productively (Parkinson's Law)

Trigger phrases: "timeboxing", "Pomodoro", "deep work", "80/20 rule", "Pareto principle", "focus blocks", "task batching", "energy management", "time management", "procrastination", "productivity system"

在以下场景中使用该方法：

任务过载：过多事务分散注意力，不确定该聚焦何处
拖延问题：重要工作不断推迟，简单任务反而显得更紧急
频繁切换场景：持续被打断，无法进入心流状态
效率规划：设计每日/每周日程，为优先级任务分配时间
需要深度工作：复杂思考、写作、编码、设计等需要持续专注的工作
精力管理：感到 burnout，长时间工作但产出低下
80/20分析：识别能驱动80%成果的20%核心工作
会议过载：日程被会议占满，没有专注工作的时间
任务批量处理：将同类任务（邮件、电话、行政事务）分组以提升效率
截止日期压力：利用时间限制提升效率（帕金森定律）

触发关键词："timeboxing"、"Pomodoro"、"deep work"、"80/20 rule"、"Pareto principle"、"focus blocks"、"task batching"、"energy management"、"time management"、"procrastination"、"productivity system"

What Is It?

是什么？

Focus, Timeboxing, and 80/20 combines three complementary techniques for managing attention and priorities:

Core components:

80/20 Principle (Pareto): 20% of inputs drive 80% of outputs. Identify vital few tasks with disproportionate impact.
Timeboxing: Allocate fixed time periods to tasks. Work expands to fill time (Parkinson's Law), so constrain it.
Deep Work: Sustained, distraction-free focus on cognitively demanding tasks (Cal Newport). Produces high-value output.
Energy Management: Match task intensity to energy levels. Protect peak hours for most important work.
Batching: Group similar low-focus tasks (email, admin, calls) to minimize context-switching.

Quick example:

Scenario: Software engineer overwhelmed with tickets, meetings, code reviews, and a complex feature to build.

80/20 Analysis:

20% (High Impact): Ship new payment feature (biggest customer request, revenue impact)
80% (Lower Impact): Bug fixes, refactoring, minor tickets, meetings

Timeboxed Weekly Plan:

Mon-Wed mornings (9-12am): Deep work on payment feature (3hr blocks, no meetings, Slack off)
Mon-Wed afternoons (2-4pm): Code reviews, standups, pair programming
Thu-Fri: Batch meetings, planning, admin, lower-priority tickets

Daily Timeboxing (Monday):

9:00-10:30am: Payment feature - API design (90 min deep work)
10:30-10:45am: Break, walk outside
10:45-12:15pm: Payment feature - Implementation (90 min deep work)
12:15-1:00pm: Lunch
2:00-3:00pm: Batch code reviews (5 PRs, 12 min each)
3:00-3:30pm: Standup + team sync
3:30-4:00pm: Emails, Slack, admin
4:00pm: Hard stop, no evening work

Outcome: Payment feature shipped in 3 days (18 hours deep work) vs. estimated 2+ weeks with constant interruptions. 80/20 focus + timeboxing unlocked 4× productivity.

Core benefits:

Parkinson's Law harnessed: Time constraints force decisions, prevent perfectionism
Context-switching eliminated: Batching and focus blocks preserve flow state
Guilt-free focus: Pre-allocated time for deep work and admin reduces anxiety
Energy optimization: High-impact work during peak hours, admin during low energy
Measurable progress: Timeboxes create accountability and completion satisfaction

Focus, Timeboxing, and 80/20 结合了三种互补的技巧，用于管理注意力和工作优先级：

核心组件：

80/20原则（帕累托法则）：20%的投入驱动80%的产出。识别具有 disproportionate 影响力的关键少数任务。
Timeboxing：为任务分配固定时长。工作会自动填满可用时间（帕金森定律），因此需要人为限制时长。
Deep Work：持续、无干扰地专注于高认知需求的任务（出自Cal Newport）。能产出高价值成果。
精力管理：根据精力水平匹配任务强度。将巅峰时段留给最重要的工作。
批量处理：将同类低专注需求的任务（邮件、行政、电话）分组，以减少工作场景切换。

快速示例：

场景：软件工程师被工单、会议、代码评审和复杂功能开发压得喘不过气。

80/20分析：

20%（高影响力）：交付新支付功能（最大客户需求，影响营收）
80%（低影响力）：Bug修复、代码重构、小型工单、会议

每周Timeboxing规划：

周一至周三上午（9-12点）：深度开发支付功能（3小时专注时段，无会议，关闭Slack）
周一至周三下午（2-4点）：代码评审、站会、结对编程
周四至周五：批量处理会议、规划、行政事务、低优先级工单

每日Timeboxing安排（周一）：

9:00-10:30：支付功能 - API设计（90分钟深度工作）
10:30-10:45：休息，外出散步
10:45-12:15：支付功能 - 功能实现（90分钟深度工作）
12:15-1:00：午餐
2:00-3:00：批量处理代码评审（5个PR，每个12分钟）
3:00-3:30：站会 + 团队同步
3:30-4:00：邮件、Slack、行政事务
4:00：强制结束工作，不加班

结果：支付功能在3天内交付（18小时深度工作），而原本在频繁干扰下预计需要2周以上时间。80/20聚焦 + Timeboxing 使效率提升了4倍。

核心优势：

利用帕金森定律：时间限制迫使决策，避免完美主义
消除场景切换：批量处理和专注时段保留心流状态
无负罪感专注：预先分配深度工作和行政事务时间，减少焦虑
优化精力分配：巅峰时段处理高影响力工作，低谷时段处理行政事务
可衡量的进度：Timeboxing 建立责任感和完成任务的满足感

Workflow

工作流程

Copy this checklist and track your progress:

Focus & Timeboxing Progress:
- [ ] Step 1: Identify your 80/20
- [ ] Step 2: Design focus blocks
- [ ] Step 3: Timebox your week
- [ ] Step 4: Timebox your day
- [ ] Step 5: Execute with discipline
- [ ] Step 6: Review and adjust

Step 1: Identify your 80/20

What 20% of tasks drive 80% of your results? Separate vital few from trivial many. See resources/template.md.

Step 2: Design focus blocks

Block time for deep work on high-impact tasks. Match duration to task type (Pomodoro 25min, Deep Work 90-120min). See resources/template.md and resources/methodology.md.

Step 3: Timebox your week

Allocate weekly calendar: deep work blocks, meeting blocks, batched admin, buffer time. See resources/template.md and resources/methodology.md.

Step 4: Timebox your day

Break day into time-constrained blocks with start/end times. Schedule breaks. Plan evening hard stop. See resources/template.md.

Step 5: Execute with discipline

Honor timeboxes. Use timers. Eliminate distractions (Slack off, phone away, close tabs). Take breaks. See resources/methodology.md.

Step 6: Review and adjust

Weekly review: Did you protect deep work? What interrupted focus? Adjust schedule. See resources/template.md and resources/methodology.md.

Validate using resources/evaluators/rubric_focus_timeboxing_8020.json. Minimum standard: Average score ≥ 3.5.

复制以下清单并跟踪进度：

专注与Timeboxing进度跟踪：
- [ ] 步骤1：识别你的80/20核心任务
- [ ] 步骤2：设计专注时段
- [ ] 步骤3：规划每周Timeboxing
- [ ] 步骤4：规划每日Timeboxing
- [ ] 步骤5：严格执行
- [ ] 步骤6：复盘与调整

步骤1：识别你的80/20核心任务

哪些20%的任务能驱动80%的成果？区分关键少数与琐碎多数。参考 resources/template.md。

步骤2：设计专注时段

为高影响力任务的深度工作预留时间。根据任务类型匹配时长（Pomodoro 25分钟、Deep Work 90-120分钟）。参考 resources/template.md 和 resources/methodology.md。

步骤3：规划每周Timeboxing

分配每周日程：深度工作时段、会议时段、批量行政事务时间、缓冲时间。参考 resources/template.md 和 resources/methodology.md。

步骤4：规划每日Timeboxing

将一天划分为带起止时间的限时区块，安排休息时间，设定每日强制结束时间。参考 resources/template.md。

步骤5：严格执行

遵守Timeboxing安排。使用计时器。消除干扰（关闭Slack、远离手机、关闭无关标签页）。按时休息。参考 resources/methodology.md。

步骤6：复盘与调整

每周复盘：是否保护了深度工作时间？哪些因素打断了专注？调整日程。参考 resources/template.md 和 resources/methodology.md。

使用 resources/evaluators/rubric_focus_timeboxing_8020.json 进行验证。最低标准：平均得分 ≥ 3.5。

Common Patterns

常见模式

Pattern 1: Pomodoro Technique (25 min focus)

Format: 25 min focused work + 5 min break, repeat 4×, then 15-30 min break
Best for: Tasks with high resistance (procrastination), need for frequent breaks, building focus habit
Tools: Timer, task list, distraction blockers
When: Short tasks, starting new habits, high-distraction environments
Guardrails: Don't interrupt Pomodoro mid-session, actually take breaks (don't skip)

Pattern 2: Deep Work Blocks (90-120 min)

Format: 90-120 min uninterrupted focus on single cognitively demanding task
Best for: Complex thinking (writing, coding, design, strategy), high-value creative work
Preparation: Clear goal for session, all resources ready, distractions eliminated
When: Peak energy hours (usually morning), maximum 2-3 blocks per day
Guardrails: No meetings during deep work, Slack/email off, phone in another room

Pattern 3: Weekly 80/20 Planning

Format: Sunday/Monday - identify top 3 high-impact goals for week, schedule deep work blocks
Best for: Strategic prioritization, ensuring vital few get attention
Output: 3-5 focus blocks (90-120 min each) on calendar for week's top priorities
When: Start of week, quarterly planning, project kickoffs
Guardrails: Protect these blocks ruthlessly, treat like unmovable meetings

Pattern 4: Task Batching (30-60 min blocks)

Format: Group similar low-cognitive-load tasks (emails, calls, admin) into single session
Best for: Reducing context-switching, clearing small tasks efficiently
Examples: Email batches (11am, 4pm), meeting blocks (Tue/Thu afternoons), admin Fridays
When: Low-energy periods, after deep work, end of day
Guardrails: Set timer, don't let batches expand, resist checking email outside batches

Pattern 5: Maker's Schedule (Half-day or Full-day blocks)

Format: Uninterrupted half-days (4+ hours) or full days for creative/technical work
Best for: Large projects (research paper, product launch, complex feature), flow-state work
Preparation: Clear all meetings for that period, OOO on Slack, backup plan if interrupted
When: Critical deadlines, breakthrough work needed, once/week minimum for makers
Guardrails: Communicate boundaries, delegate urgent issues, plan breaks within block

Pattern 6: Energy-Based Scheduling

Format: Match task type to energy level (peak → deep work, trough → admin, recovery → meetings)
Best for: Maximizing output while preventing burnout
Typical cycle: Peak (9am-12pm) → Trough (2-3pm) → Recovery (4-5pm)
When: Designing weekly/daily schedules, recovering from overwork
Guardrails: Track your actual energy patterns (not generic), honor low-energy periods with rest

模式1：Pomodoro Technique（25分钟专注）

格式：25分钟专注工作 + 5分钟休息，重复4轮后，休息15-30分钟
最佳适用：具有高抗拒性的任务（拖延）、需要频繁休息的场景、培养专注习惯
工具：计时器、任务清单、干扰拦截工具
适用时机：短任务、培养新习惯、高干扰环境
注意准则：不要在Pomodoro中途打断，真正休息（不要跳过）

模式2：深度工作时段（90-120分钟）

格式：90-120分钟不间断专注于单一高认知需求任务
最佳适用：复杂思考（写作、编码、设计、战略）、高价值创意工作
准备工作：明确会话目标、准备好所有资源、消除干扰
适用时机：精力巅峰时段（通常是上午），每天最多2-3个时段
注意准则：深度工作时段无会议，关闭Slack/邮件，手机放在另一个房间

模式3：每周80/20规划

格式：周日/周一 - 确定本周3个高影响力目标，安排深度工作时段
最佳适用：战略优先级排序，确保关键少数任务得到关注
产出：在日历上为本周最高优先级任务安排3-5个90-120分钟的专注时段
适用时机：周初、季度规划、项目启动
注意准则：坚决保护这些时段，视为不可移动的会议

模式4：任务批量处理（30-60分钟时段）

格式：将同类低认知负荷任务（邮件、电话、行政事务）分组为单个会话
最佳适用：减少场景切换，高效处理小型任务
示例：邮件批量处理（11点、16点）、会议批量安排（周二/周四下午）、行政事务批量处理（周五）
适用时机：精力低谷时段、深度工作之后、一天结束时
注意准则：设置计时器，不要让批量处理时间膨胀，避免在批量时段外查看邮件

模式5：创造者日程（半天或全天时段）

格式：不间断的半天（4小时以上）或全天用于创意/技术工作
最佳适用：大型项目（研究论文、产品发布、复杂功能开发）、心流状态工作
准备工作：清除该时段的所有会议，Slack设置为OOO（外出），准备中断后的备用方案
适用时机：关键截止日期、需要突破性工作时，创造者每周至少安排一次
注意准则：明确沟通边界，委托紧急事务，在时段内规划休息

模式6：基于精力的日程安排

格式：根据精力水平匹配任务类型（巅峰→深度工作，低谷→行政事务，恢复→会议）
最佳适用：最大化产出同时防止 burnout
典型周期：巅峰（9am-12pm）→ 低谷（2-3pm）→ 恢复（4-5pm）
适用时机：设计每周/每日日程、从过度工作中恢复
注意准则：跟踪自己实际的精力模式（而非通用模式），尊重低精力时段并休息

Guardrails

注意准则

Critical requirements:

Protect deep work time: No meetings, no Slack, no email during focus blocks. Treat as sacred. One interruption destroys 20+ min of flow. Schedule deep work during peak energy (usually mornings).
Respect Parkinson's Law: Work expands to fill available time. Shorter timeboxes force prioritization and prevent perfectionism. Better: 90 min timebox with clear outcome than open-ended "work on this."
Actually identify 80/20: Most people work on 80% (low-impact). Force rank tasks by impact. Top 20% should get 80% of your focus time. Cut, delegate, or batch the rest.
Energy > Time: 8 hours tired < 4 hours energized. Don't schedule deep work during low-energy troughs. Match intensity to energy. Trough = admin/meetings, not complex thinking.
Build in buffer: Don't timebox every minute. 20% unscheduled time for unexpected issues, overflow, breaks. Over-scheduled = fragile. One delay cascades.
Hard stops prevent burnout: Define end-of-day (e.g., 5pm hard stop). No evening work unless true emergency. Constrained time forces prioritization, endless time enables procrastination.
Breaks are non-negotiable: 90 min deep work → 10-15 min break. Walk, stretch, look outside. Don't skip breaks to "power through." Focus degrades exponentially after 90-120 min.
Measure focus quality, not hours: 3 hours deep work > 8 hours distracted. Track how many focus blocks completed per week, not total hours. Quality over quantity.

Common pitfalls:

❌ No real deep work blocks: Calendar full of meetings, "focus time" constantly interrupted. Protect minimum 2-3× 90-min blocks per week.
❌ Ignoring 80/20: Everything feels important. Force rank. If you can't identify top 20%, ask: "If I could only work 10 hours this week, what would I do?"
❌ Timeboxing trivia: Scheduling every email, every Slack message. Batch low-value tasks, don't timebox them individually.
❌ Skipping breaks: "I'll break after I finish this." Then work 4 hours straight, output quality tanks. Use timer, force breaks.
❌ Peak hours on admin: Checking email at 9am (peak energy). Save admin for afternoon trough. Peak hours = deep work only.
❌ Overcommitting: Timeboxing 10 hours of work into 8-hour day. Be realistic. Under-schedule, over-deliver.

核心要求：

保护深度工作时间：专注时段内无会议、无Slack、无邮件。将其视为神圣不可侵犯的时间。一次中断会破坏20分钟以上的心流。在精力巅峰（通常是上午）安排深度工作。
尊重帕金森定律：工作会自动填满可用时间。更短的Timeboxing 迫使优先级排序，避免完美主义。更好的选择是：90分钟带明确成果的Timeboxing，而非开放式的“处理这项工作”。
真正识别80/20核心任务：大多数人在处理80%的低影响力任务。强制排序任务优先级。前20%的任务应获得80%的专注时间。削减、委托或批量处理其余任务。
精力 > 时间：8小时疲惫工作 < 4小时高效工作。不要在低精力低谷时段安排深度工作。根据精力匹配任务强度。低谷时段 = 行政事务/会议，而非复杂思考。
预留缓冲时间：不要把每分钟都排满。预留20%的非计划时间用于意外问题、溢出工作和休息。过度安排的日程很脆弱，一次延迟会引发连锁反应。
强制结束工作防止 burnout：定义每日结束时间（例如17点强制结束）。除非真正紧急情况，否则不加班。有限的时间迫使优先级排序，无尽的时间会导致拖延。
休息是必须的：90分钟深度工作 → 10-15分钟休息。散步、拉伸、看向窗外。不要为了“硬扛”而跳过休息。90-120分钟后专注力会呈指数级下降。
衡量专注质量而非时长：3小时深度工作 > 8小时分心工作。跟踪每周完成的专注时段数量，而非总时长。质量优先于数量。

常见误区：

❌ 无真正的深度工作时段：日程被会议填满，“专注时间”不断被打断。每周至少保护2-3个90分钟的专注时段。
❌ 忽略80/20原则：所有事情都显得重要。强制排序。如果无法识别前20%的任务，问自己：“如果本周只能工作10小时，我会做什么？”
❌ 为琐碎任务做Timeboxing：为每封邮件、每条Slack消息安排时间。批量处理低价值任务，不要单独为其做Timeboxing。
❌ 跳过休息：“完成这个再休息。”然后连续工作4小时，产出质量暴跌。使用计时器，强制休息。
❌ 巅峰时段处理行政事务：9点查看邮件（精力巅峰）。把行政事务留到下午低谷时段。巅峰时段仅用于深度工作。
❌ 过度承诺：把10小时的工作塞进8小时的日程。要现实。少安排，多交付。

Quick Reference

快速参考

Timeboxing durations:

Duration	Best For	Rest After
25 min	Pomodoro, high-resistance tasks, building habit	5 min
50 min	Focused work, moderate complexity	10 min
90 min	Deep work, complex thinking, creative tasks	15 min
120 min	Maximum deep work (rare, high expertise)	20-30 min
Half-day (4h)	Maker's schedule, breakthroughs, flow state	Lunch + afternoon off

Energy-based scheduling:

Time	Energy Level	Task Type	Examples
6-9am	Peak (early risers)	Deep work	Writing, coding, strategy
9am-12pm	Peak (most people)	Deep work	Complex problems, creative work
12-2pm	Lunch dip	Meetings, social	Standups, 1:1s, collaboration
2-3pm	Trough	Admin, batching	Email, Slack, expense reports
3-5pm	Recovery	Moderate work	Code reviews, planning, lighter tasks
Evening	Low	Rest or routine	Reading, exercise, NOT deep work

80/20 identification:

Ask these questions:

"If I could only work 10 hours this week, what would I do?"
"Which tasks, if done well, make everything else easier or unnecessary?"
"What creates 10× value vs. 1× value?"
"What will matter in 6 months? What won't?"

Focus blockers (eliminate during deep work):

Slack/Teams (quit app or set DND)
Email (close tab/app)
Phone (different room, airplane mode)
Browser tabs (close all except work-related)
Open floor plans (noise-canceling headphones, office door)
Notifications (disable all)
Meetings (schedule-free mornings)

Batching categories:

Email batches: 11am, 4pm (2× per day max)
Meeting blocks: Tue/Thu afternoons
Admin batch: Friday afternoons (expense reports, timesheets, planning)
Code review batch: After lunch (30-60 min)
Quick calls batch: 30-min slots back-to-back

Weekly planning template (simplified):

Monday-Wednesday mornings: Deep work on Priority 1 (3× 90-min blocks)
Monday-Wednesday afternoons: Meetings, collaboration, moderate work
Thursday: Deep work on Priority 2 (morning), meetings (afternoon)
Friday: Batched admin, planning next week, code reviews

Inputs required:

Current commitments: Meetings, recurring tasks, deadlines
Energy patterns: When are you most/least energized? (track for 1 week)
Top priorities: What are your 3-5 most important outcomes this week/month?
Task list: Everything competing for attention (to identify 80/20)

Outputs produced:

```
weekly-timeboxed-schedule.md
```
: Calendar with focus blocks, meeting blocks, batch times
```
daily-plan.md
```
: Time-blocked day with start/end times, breaks scheduled
```
8020-analysis.md
```
: Prioritized task list with vital few identified
```
focus-time-tracker.csv
```
: Log of focus blocks completed, quality, interruptions

Timeboxing时长建议：

时长	最佳适用	休息时长
25分钟	Pomodoro、高抗拒性任务、培养习惯	5分钟
50分钟	专注工作、中等复杂度任务	10分钟
90分钟	深度工作、复杂思考、创意任务	15分钟
120分钟	最长深度工作（罕见，需高熟练度）	20-30分钟
半天（4小时）	创造者日程、突破性工作、心流状态	午餐 + 下午休息

基于精力的日程安排：

时间	精力水平	任务类型	示例
6-9点	巅峰（早起人群）	深度工作	写作、编码、战略
9点-12点	巅峰（大多数人）	深度工作	复杂问题、创意工作
12-14点	午餐低谷	会议、社交	站会、一对一沟通、协作
14-15点	低谷	行政事务、批量处理	邮件、Slack、费用报销
15-17点	恢复	中等难度工作	代码评审、规划、轻量任务
晚上	低	休息或常规事务	阅读、锻炼，不要做深度工作

80/20核心任务识别：

问自己这些问题：

“如果本周只能工作10小时，我会做什么？”
“哪些任务如果做好了，会让其他事情变得更容易或不必要？”
“哪些任务能创造10倍价值 vs 1倍价值？”
“哪些事情在6个月后仍重要？哪些不重要？”

专注干扰项（深度工作时需消除）：

Slack/Teams（退出应用或设置DND）
邮件（关闭标签页/应用）
手机（放在另一个房间，开启飞行模式）
浏览器标签页（关闭所有非工作相关标签）
开放式办公区（降噪耳机、关闭办公室门）
通知（禁用所有）
会议（安排无会议的上午）

批量处理分类：

邮件批量处理：11点、16点（每天最多2次）
会议批量安排：周二/周四下午
行政事务批量处理：周五下午（费用报销、工时表、规划）
代码评审批量处理：午餐后（30-60分钟）
快速电话批量处理：30分钟连续时段

简化版每周规划模板：

周一至周三上午：深度处理优先级1任务（3个90分钟时段）
周一至周三下午：会议、协作、中等难度工作
周四：上午深度处理优先级2任务，下午会议
周五：批量处理行政事务、规划下周工作、代码评审

所需输入：

当前承诺：会议、重复任务、截止日期
精力模式：你何时精力最充沛/最低落？（跟踪1周）
最高优先级：本周/本月3-5个最重要的成果
任务清单：所有需要关注的事务（用于识别80/20核心任务）

产出内容：

```
weekly-timeboxed-schedule.md
```
：包含专注时段、会议时段、批量处理时间的日程表
```
daily-plan.md
```
：带起止时间、休息安排的每日时间区块计划
```
8020-analysis.md
```
：已排序的任务清单，标注关键少数任务
```
focus-time-tracker.csv
```
：已完成的专注时段记录、专注质量、干扰项

focus-timeboxing-8020

Original

Translation

Focus, Timeboxing, and 80/20

Focus, Timeboxing, and 80/20

Table of Contents

目录

Purpose

目的

When to Use

适用场景

What Is It?

是什么？

Workflow

工作流程

Common Patterns

常见模式

Guardrails

注意准则

Quick Reference

快速参考