Structure · Why does the same outage keep recurring?

THE QUESTION

Why does the same outage keep recurring?

Does one significantly influence the other? Three quarters of the votes cast decide.

Viewing as guest. Enter a handle to join and take part.

Questions are shared out between groups, so you get the ones your group was given — not all 180.

why

Nobody could answer several hundred pairs. Each pair goes to one group; a pair that splits is then referred to other groups, so it can appear in your list later even though it started elsewhere. The settled count includes every group's work, which is why it climbs faster than your own list shrinks.

176 / 180 settled 0 for you to answer

Last tally: 176 decided · 1 escalated to cross-group panels · 0 contested · 3 below quorum — panels need at least max(2, 75% of panel) votes cast; your smallest panel has 15 members.

Completed phase — the record of pairs and votes stands above.Check the logic ↗

Reliability has no budget line of its own	→	Feature flags are never cleaned up, so nobody knows which paths are live	open	discuss
The same three services cause most of the pages	→	…	open	discuss
The incident channel fills with people asking for status instead of giving it	→	The service map in the wiki is two years old	open	discuss
The staging environment does not resemble production	→	Rollbacks take longer than the outage they are meant to end	open escalated	discuss
Tests that fail intermittently are retried until green	→	Customers report outages before monitoring does	✓ yes	discuss
Alerts fire so often that on-call mutes them	→	Customers report outages before monitoring does	✓ yes	discuss
Alerts fire so often that on-call mutes them	→	Every team has its own logging format	✓ yes	discuss
Every team has its own logging format	→	Customers report outages before monitoring does	✓ yes	discuss
The on-call rota has the same two people on it most weeks	→	Alerts fire so often that on-call mutes them	✓ yes	discuss
Feature work always outranks reliability work in planning	→	Post-mortem actions are written up and then never scheduled	✓ yes	discuss
One engineer knows how the payment path actually works	→	The on-call rota has the same two people on it most weeks	✓ yes	discuss
The on-call rota has the same two people on it most weeks	→	Post-mortem actions are written up and then never scheduled	✓ yes	discuss
Post-mortems assign actions to people who were not in the room	→	Post-mortem actions are written up and then never scheduled	✓ yes	discuss
The service map in the wiki is two years old	→	The staging environment does not resemble production	✓ yes	discuss
Rollbacks take longer than the outage they are meant to end	→	Reliability has no budget line of its own	✓ yes	discuss
Reliability has no budget line of its own	→	The staging environment does not resemble production	✓ yes	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	The same three services cause most of the pages	✓ yes	discuss
Reliability has no budget line of its own	→	The incident channel fills with people asking for status instead of giving it	✓ yes	discuss
The same three services cause most of the pages	→	The staging environment does not resemble production	✓ yes	discuss
The service map in the wiki is two years old	→	Feature flags are never cleaned up, so nobody knows which paths are live	✓ yes	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	Rollbacks take longer than the outage they are meant to end	✓ yes	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	The same three services cause most of the pages	✓ yes	discuss
The on-call rota has the same two people on it most weeks	→	Customers report outages before monitoring does	✓ inferred	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	The staging environment does not resemble production	✓ inferred	discuss
Post-mortem actions are written up and then never scheduled	→	Every team has its own logging format	✗ no	discuss
Every team has its own logging format	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Feature work always outranks reliability work in planning	→	Customers report outages before monitoring does	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Tests that fail intermittently are retried until green	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	One engineer knows how the payment path actually works	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Customers report outages before monitoring does	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Customers report outages before monitoring does	✗ no	discuss
Customers report outages before monitoring does	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Feature work always outranks reliability work in planning	→	Tests that fail intermittently are retried until green	✗ no	discuss
Tests that fail intermittently are retried until green	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
Feature work always outranks reliability work in planning	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Tests that fail intermittently are retried until green	→	Every team has its own logging format	✗ no	discuss
The on-call rota has the same two people on it most weeks	→	Tests that fail intermittently are retried until green	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	Every team has its own logging format	✗ no	discuss
Feature work always outranks reliability work in planning	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Tests that fail intermittently are retried until green	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Alerts fire so often that on-call mutes them	→	One engineer knows how the payment path actually works	✗ no	discuss
Customers report outages before monitoring does	→	One engineer knows how the payment path actually works	✗ no	discuss
Alerts fire so often that on-call mutes them	→	Post-mortem actions are written up and then never scheduled	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
One engineer knows how the payment path actually works	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Customers report outages before monitoring does	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
Feature work always outranks reliability work in planning	→	Every team has its own logging format	✗ no	discuss
Customers report outages before monitoring does	→	Post-mortem actions are written up and then never scheduled	✗ no	discuss
Customers report outages before monitoring does	→	Every team has its own logging format	✗ no	discuss
Customers report outages before monitoring does	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	One engineer knows how the payment path actually works	✗ no	discuss
Customers report outages before monitoring does	→	Tests that fail intermittently are retried until green	✗ no	discuss
Every team has its own logging format	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
Every team has its own logging format	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Every team has its own logging format	→	Post-mortem actions are written up and then never scheduled	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	Tests that fail intermittently are retried until green	✗ no	discuss
The on-call rota has the same two people on it most weeks	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Alerts fire so often that on-call mutes them	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
One engineer knows how the payment path actually works	→	Tests that fail intermittently are retried until green	✗ no	discuss
Tests that fail intermittently are retried until green	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Feature work always outranks reliability work in planning	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Customers report outages before monitoring does	→	Feature work always outranks reliability work in planning	✗ no	discuss
One engineer knows how the payment path actually works	→	Customers report outages before monitoring does	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	Customers report outages before monitoring does	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Feature work always outranks reliability work in planning	✗ no	discuss
Alerts fire so often that on-call mutes them	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
One engineer knows how the payment path actually works	→	Post-mortem actions are written up and then never scheduled	✗ no	discuss
The on-call rota has the same two people on it most weeks	→	One engineer knows how the payment path actually works	✗ no	discuss
Tests that fail intermittently are retried until green	→	One engineer knows how the payment path actually works	✗ no	discuss
The on-call rota has the same two people on it most weeks	→	Every team has its own logging format	✗ no	discuss
Alerts fire so often that on-call mutes them	→	Tests that fail intermittently are retried until green	✗ no	discuss
Every team has its own logging format	→	One engineer knows how the payment path actually works	✗ no	discuss
The on-call rota has the same two people on it most weeks	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	Tests that fail intermittently are retried until green	✗ no	discuss
Every team has its own logging format	→	Alerts fire so often that on-call mutes them	✗ no	discuss
The on-call rota has the same two people on it most weeks	→	Feature work always outranks reliability work in planning	✗ no	discuss
Tests that fail intermittently are retried until green	→	Feature work always outranks reliability work in planning	✗ no	discuss
Tests that fail intermittently are retried until green	→	Post-mortem actions are written up and then never scheduled	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Alerts fire so often that on-call mutes them	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Post-mortem actions are written up and then never scheduled	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	Feature work always outranks reliability work in planning	✗ no	discuss
One engineer knows how the payment path actually works	→	Feature work always outranks reliability work in planning	✗ no	discuss
Error budgets exist on a slide and nowhere else	→	Every team has its own logging format	✗ no	discuss
Tests that fail intermittently are retried until green	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	Customers report outages before monitoring does	✗ no	discuss
Every team has its own logging format	→	Tests that fail intermittently are retried until green	✗ no	discuss
One engineer knows how the payment path actually works	→	Post-mortems assign actions to people who were not in the room	✗ no	discuss
Feature work always outranks reliability work in planning	→	One engineer knows how the payment path actually works	✗ no	discuss
Every team has its own logging format	→	Feature work always outranks reliability work in planning	✗ no	discuss
One engineer knows how the payment path actually works	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Alerts fire so often that on-call mutes them	→	Error budgets exist on a slide and nowhere else	✗ no	discuss
Post-mortems assign actions to people who were not in the room	→	One engineer knows how the payment path actually works	✗ no	discuss
Alerts fire so often that on-call mutes them	→	Feature work always outranks reliability work in planning	✗ no	discuss
One engineer knows how the payment path actually works	→	Every team has its own logging format	✗ no	discuss
Feature work always outranks reliability work in planning	→	The on-call rota has the same two people on it most weeks	✗ no	discuss
Post-mortem actions are written up and then never scheduled	→	Feature work always outranks reliability work in planning	✗ no	discuss
The same three services cause most of the pages	→	The service map in the wiki is two years old	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	The same three services cause most of the pages	✗ no	discuss
Config lives in five places and drifts between them	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
…	→	The staging environment does not resemble production	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	Config lives in five places and drifts between them	✗ no	discuss
Reliability has no budget line of its own	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
The same three services cause most of the pages	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
The service map in the wiki is two years old	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
Config lives in five places and drifts between them	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	The service map in the wiki is two years old	✗ no	discuss
…	→	Reliability has no budget line of its own	✗ no	discuss
The service map in the wiki is two years old	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	Reliability has no budget line of its own	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	…	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	Reliability has no budget line of its own	✗ no	discuss
Config lives in five places and drifts between them	→	The staging environment does not resemble production	✗ no	discuss
…	→	Config lives in five places and drifts between them	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	…	✗ no	discuss
Reliability has no budget line of its own	→	Config lives in five places and drifts between them	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
The same three services cause most of the pages	→	Reliability has no budget line of its own	✗ no	discuss
…	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	The service map in the wiki is two years old	✗ no	discuss
Config lives in five places and drifts between them	→	Reliability has no budget line of its own	✗ no	discuss
The staging environment does not resemble production	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	Config lives in five places and drifts between them	✗ no	discuss
The service map in the wiki is two years old	→	Reliability has no budget line of its own	✗ no	discuss
The service map in the wiki is two years old	→	Config lives in five places and drifts between them	✗ no	discuss
The staging environment does not resemble production	→	Config lives in five places and drifts between them	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	The service map in the wiki is two years old	✗ no	discuss
The staging environment does not resemble production	→	The service map in the wiki is two years old	✗ no	discuss
The staging environment does not resemble production	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
…	→	The same three services cause most of the pages	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
…	→	The service map in the wiki is two years old	✗ no	discuss
Config lives in five places and drifts between them	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
The staging environment does not resemble production	→	…	✗ no	discuss
Reliability has no budget line of its own	→	…	✗ no	discuss
The same three services cause most of the pages	→	Config lives in five places and drifts between them	✗ no	discuss
…	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	The staging environment does not resemble production	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
Config lives in five places and drifts between them	→	…	✗ no	discuss
The staging environment does not resemble production	→	The same three services cause most of the pages	✗ no	discuss
Reliability has no budget line of its own	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
Config lives in five places and drifts between them	→	The same three services cause most of the pages	✗ no	discuss
The staging environment does not resemble production	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	The staging environment does not resemble production	✗ no	discuss
…	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
Config lives in five places and drifts between them	→	The service map in the wiki is two years old	✗ no	discuss
The same three services cause most of the pages	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	Config lives in five places and drifts between them	✗ no	discuss
Reliability has no budget line of its own	→	The service map in the wiki is two years old	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	…	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	Config lives in five places and drifts between them	✗ no	discuss
Config lives in five places and drifts between them	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
Feature flags are never cleaned up, so nobody knows which paths are live	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
The service map in the wiki is two years old	→	…	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	The same three services cause most of the pages	✗ no	discuss
Rollbacks take longer than the outage they are meant to end	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
Reliability has no budget line of its own	→	The same three services cause most of the pages	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
The same three services cause most of the pages	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ no	discuss
The service map in the wiki is two years old	→	The incident channel fills with people asking for status instead of giving it	✗ no	discuss
The service map in the wiki is two years old	→	The same three services cause most of the pages	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	…	✗ no	discuss
The staging environment does not resemble production	→	Reliability has no budget line of its own	✗ no	discuss
The incident channel fills with people asking for status instead of giving it	→	The staging environment does not resemble production	✗ no	discuss
The same three services cause most of the pages	→	Rollbacks take longer than the outage they are meant to end	✗ no	discuss
…	→	Retries are unbounded, so a slow dependency becomes a flood	✗ no	discuss
Retries are unbounded, so a slow dependency becomes a flood	→	Reliability has no budget line of its own	✗ no	discuss