问题
Why does the same outage keep recurring?
把你认为相似的卡片归为一类。分类只为方便阅读，不决定任何事。
已关闭 · 返回行动阶段
正以访客身份查看。输入用户名即可加入并参与。
先按相似性形成类别，最后再命名
标准顺序：把你认为相似的想法两两关联——关联是对称的（A~B 即 B~A；方向无关紧要），一条关联在 2 名成员做出后成立。
为什么
关联是对称的——A~B 即 B~A。类别是从成立的关联中自然形成的分组，只有已形成的类别才能被人命名。你自己的关联带有 ✕，可以撤回；你不能移除别人的。类别只用于整理墙，从不限制投票——两张提出相同主张的卡片属于澄清阶段的合并。
关联和命名只能在归类阶段进行；主持人的 ← 可以重新开启它。
未命名类别 ——如果这一类有共同主线就为它命名，否则保持未命名 (2)
Alerts fire so often that on-call mutes them
~ Customers report outa…Customers report outages before monitoring does (12)
Customers report outages before monitoring does
~ Alerts fire so often …Alerts fire so often that on-call mutes them (12)
未命名类别 ——如果这一类有共同主线就为它命名，否则保持未命名 (2)
The same three services cause most of the pages
~ The on-call rota has …The on-call rota has the same two people on it most weeks (20)
The on-call rota has the same two people on it most weeks
~ The same three servic…The same three services cause most of the pages (20)
未命名类别 ——如果这一类有共同主线就为它命名，否则保持未命名 (2)
Every team has its own logging format
~ Reliability has no bu…Reliability has no budget line of its own (15)
Reliability has no budget line of its own
~ Every team has its ow…Every team has its own logging format (15)
未命名类别 ——如果这一类有共同主线就为它命名，否则保持未命名 (2)
Runbooks are out of date within a month of being written
~ The service map in th…The service map in the wiki is two years old (16)
未命名类别 ——如果这一类有共同主线就为它命名，否则保持未命名 (2)
Post-mortem actions are written up and then never scheduled
~ Post-mortems assign a…Post-mortems assign actions to people who were not in the room (9)
~ Feature flags are nev…Feature flags are never cleaned up, so nobody knows which paths are live (14)
Feature flags are never cleaned up, so nobody knows which paths are live
~ Post-mortem actions a…Post-mortem actions are written up and then never scheduled (14)
未命名类别 ——如果这一类有共同主线就为它命名，否则保持未命名 (2)
Config lives in five places and drifts between them
~ Migrations are run by…Migrations are run by hand from a laptop (21)
Migrations are run by hand from a laptop
~ Config lives in five …Config lives in five places and drifts between them (21)
· 尚未归类 (18)
Tests that fail intermittently are retried until green
Leadership asks for a root cause within the hour, so the first plausible one wins
Success is measured in features shipped per quarter
Dependencies are upgraded only when something breaks
Deploys go out on Friday afternoons because that is when the sprint ends
Rollbacks take longer than the outage they are meant to end
Post-mortems assign actions to people who were not in the room
~ Post-mortem actions a…Post-mortem actions are written up and then never scheduled (9)
Feature work always outranks reliability work in planning
There is no time set aside after an incident, so the write-up is done at midnight
Incidents are declared late because declaring one feels like blame
Load tests were last run before the customer base doubled
One engineer knows how the payment path actually works
Error budgets exist on a slide and nowhere else
The staging environment does not resemble production
The incident channel fills with people asking for status instead of giving it
Nobody owns the shared database schema
Retries are unbounded, so a slow dependency becomes a flood
Capacity is added after the outage, never before