Lessons Log

经验日志

A lessons log entry captures significant learning from projects, incidents, or experiences in a format that's useful to future teams who weren't there. Unlike retrospectives (which focus on team improvement), lessons logs focus on organizational knowledge that transcends individual teams.patterns, anti-patterns, and hard-won wisdom.

经验日志条目以一种对未参与相关工作的未来团队有用的格式，记录从项目、事件或经历中获得的重要经验。与回顾会议（侧重于团队改进）不同，经验日志聚焦于超越单个团队的组织知识，包括模式、反模式以及来之不易的智慧。

When to Use

使用场景

After completing a significant project or initiative
Following a major incident, outage, or failure
When you realize something important that others should know
After discovering a pattern that keeps recurring
When experienced team members leave (capture their knowledge)
During post-mortems to preserve learnings

完成重大项目或举措后
发生重大事件、故障或失败后
当你意识到某些重要信息需要让其他人知晓时
发现重复出现的模式时
资深团队成员离职时（留存他们的知识）
事后复盘期间留存经验

Instructions

操作步骤

When asked to create a lessons log entry, follow these steps:

Choose a Descriptive Title Write a title that someone searching for this topic would find. Include keywords that describe the situation and the learning. Avoid generic titles like "Project X lessons."
Provide Context Explain the situation fully enough that someone who wasn't there can understand it. Include the project, timeline, team, and any relevant constraints. Future readers need this context to assess applicability.
Describe What Happened Write a factual account of what occurred. Be specific about actions taken, decisions made, and outcomes observed. Avoid blame.focus on events and systems.
Extract the Lesson Articulate what you learned clearly. The lesson should be actionable.something others can apply. Distinguish between what you observed and your interpretation of why it matters.
Formulate Recommendations Provide specific guidance for future teams facing similar situations. What should they do? What should they avoid? What questions should they ask?
Define Applicability Help readers know when this lesson applies. What situations trigger relevance? What context makes it more or less applicable?
Add Tags for Searchability Include keywords and categories that will help future searchers find this entry. Think about what someone would search for when facing a similar situation.

当需要创建经验日志条目时，请遵循以下步骤：

选择描述性标题 撰写一个便于搜索该主题的人找到的标题。包含描述场景和经验的关键词。避免使用“项目X经验”这类通用标题。
提供背景信息 充分解释场景，让未参与的人能够理解。包括项目、时间线、团队以及任何相关约束条件。未来的读者需要这些背景信息来评估经验的适用性。
描述事件经过 如实记录发生的情况。具体说明采取的行动、做出的决策以及观察到的结果。避免指责，聚焦于事件和系统本身。
提炼经验要点 清晰阐述所学到的内容。经验要点应具备可操作性，即其他人能够应用的内容。区分观察到的事实和你对其重要性的解读。
制定建议 为未来遇到类似场景的团队提供具体指导。他们应该做什么？应该避免什么？应该提出哪些问题？
明确适用范围 帮助读者了解该经验何时适用。哪些场景会触发其相关性？哪些背景因素会影响其适用性？
添加便于搜索的标签 包含有助于未来搜索者找到本条目的关键词和分类。思考人们在遇到类似场景时会搜索什么。

Output Format

输出格式

Use the template in

references/TEMPLATE.md

to structure the output.

使用

references/TEMPLATE.md

中的模板来构建输出内容。

Quality Checklist

质量检查清单

Before finalizing, verify:

Title is descriptive and searchable
Context is complete enough for someone who wasn't there
Lesson is clearly articulated and actionable
Recommendations are specific, not vague
Entry stands alone (doesn't require external context)
Tags enable future discovery

最终确定前，请验证：

标题具有描述性且便于搜索
背景信息足够完整，可供未参与的人理解
经验要点阐述清晰且具备可操作性
建议具体明确，而非模糊笼统
条目可独立存在（无需外部背景信息）
标签便于未来检索

Examples

示例

See

references/EXAMPLE.md

for a completed example.

请查看

references/EXAMPLE.md

中的完整示例。

iterate-lessons-log

Original

Translation