True Causes
SR
← početna
7/7 · Akcije
osoba: 30 · ideja: 30
probni prolaz · ne računa se
prepreke · svako sa linkom · na javnom spisku · federacija uključena
vodi: njen voditelj (zapečaćeno)
osoba: 30 · ideja: 30 · 2 grupe
Pasoš → · Logika → · zapis
↗ podeli ovu mapu
Na drugom sajtu, kao živa mapa:
Kao slika: https://truecauses.org/d/6708d57/map.svg
Kao podaci: svi ocenjeni parovi u ovoj sobi (CSV). Svaka tvrdnja ima svoju adresu, /c/6708d57/<card>, navedenu ispod mape.
Navedite izvor kada objavljujete: Causal map: True Causes, https://truecauses.org/d/6708d57
PITANJE

Why does the same outage keep recurring?

Predložite šta da se uradi, pa procenite da li bi svaka akcija pomerila svaki koren.

Zapečaćeno pre 23 dana: ova soba više ne zna ko je sedeo u njoj; po imenu ostaje samo njen voditelj. Ono do čega je došla ostaje.
za stolom: 30 (simulirano: 29) · 3 predložene akcije za osnovne uzroke (6). Dodajte jednu, pa procenite da li svaka akcija pomera svaki uzrok.
Gledate kao gost. Unesite korisničko ime da biste se pridružili i učestvovali.
Najpre ocenite osnovne uzroke
zašto
Praksa same metode, pre nego što se predloži ijedna akcija: svaki osnovni uzrok dobija ocenu od 1 do 5 za to koliko je izvodljivo baviti se njime, koliki bi uticaj to imalo i koliko je verovatno da će se rešiti sam od sebe, bez ikakve intervencije. Prednost imaju osnovni uzroci sa velikim uticajem, visokom izvodljivošću i malom verovatnoćom da se reše sami — prioritet = uticaj + izvodljivost − verovatnoća. Ocene se uprosečuju za celu grupu i prikazuju uz broj onih koji su ocenjivali.
1 = nisko, 5 = visoko. Vaše ocene; pored njih proseci grupe.
osnovni uzrokizvodljivouticajrešava se samoprioritet
The service map in the wiki is two years old––––
One engineer knows how the payment path actually works––––
Feature flags are never cleaned up, so nobody knows which paths are live––––
The on-call rota has the same two people on it most weeks––––
Rollbacks take longer than the outage they are meant to end––––
Alerts fire so often that on-call mutes them––––
Koja akcija bi pomerila koji osnovni uzrok?
Sa strane: akcije koje su ljudi predložili. Gore: osnovni uzroci koje je mapa pronašla. Svako polje je jedno glasanje o jednom pitanju — da li bi ova akcija značajno smanjila taj uzrok? Jedna strana mora da dostigne 75% datih glasova da bi se pitanje rešilo; inače polje ostaje podeljeno. Svako polje pokazuje kako su pali glasovi — da / gore / ne — a polje je rešeno kada jedno od toga dobije tri četvrtine glasova.
zašto
Odgovor važi na 75% datih glasova, kao i svako drugo pitanje ovde. Podeljeno znači da su ljudi glasali, a nijedna strana nije dostigla taj prag — to je rezultat, a ne red čekanja, i ostaje podeljeno dok se dovoljno ljudi ne predomisli. Polje koje niko ne reši ostaje neodlučeno; nikad ne postaje „ne”. Ocenjivanje svakog para posebno sprečava da se popularnoj akciji pripiše da rešava stvari koje ne dotiče.
AKCIJAOSNOVNI UZROCI · da li ga akcija u levoj koloni umanjuje?
The service map in the wiki is two years oldOne engineer knows how the payment path actually worksFeature flags are never cleaned up, so nobody knows which paths are liveThe on-call rota has the same two people on it most weeksRollbacks take longer than the outage they are meant to endAlerts fire so often that on-call mutes them
No production deploy after 14:00 on Fridays unless the on-call engineer agrees diskutuj✗ ne, ne smanjuje
3 da / 0 gore / 26 ne
⚑ grupa se podelila
21 da / 0 gore / 8 ne
još nije odlučeno
još nije odlučeno
još nije odlučeno
još nije odlučeno
Give the shared schema one named owner and a migration tool with rollback diskutuj✗ ne, ne smanjuje
6 da / 0 gore / 23 ne
✓ da, smanjuje ovo
24 da / 0 gore / 5 ne
još nije odlučeno
još nije odlučeno
još nije odlučeno
još nije odlučeno
Reserve one engineer-week per sprint for post-mortem actions, first in the sprint, not last diskutuj✗ ne, ne smanjuje
4 da / 0 gore / 25 ne
✗ ne, ne smanjuje
3 da / 0 gore / 26 ne
još nije odlučeno
još nije odlučeno
još nije odlučeno
još nije odlučeno
Najveći učinak zasad
Give the shared schema one named owner and a migration tool with rollback smanjuje osnovne uzroke: 1 od 6
AKCIJE NA MAPI
Prikazano: sve akcije koje je soba ocenila. Direktno deluje na osnovne uzroke: 1 od 6. Bez direktne akcije: 5.
Pročitano samo iz polja koja je soba rešila u fazi Akcije. Osnovni uzrok u zelenom smanjuje bar jedna od prikazanih akcija; u sivom nijedna od njih ne deluje direktno na njega; crveni obrub znači da ga jedna od njih pogoršava.
Podelite ovaj prikaz: kao sliku · kao živu mapu za drugi sajt
The same three services cause most of the pages → The staging environment does not resemble productionFeature work always outranks reliability work in planning → Post-mortem actions are written up and then never scheduledRollbacks take longer than the outage they are meant to end → Reliability has no budget line of its ownEvery team has its own logging format → Customers report outages before monitoring doesReliability has no budget line of its own → The incident channel fills with people asking for status instead of giving itReliability has no budget line of its own → The staging environment does not resemble productionPost-mortems assign actions to people who were not in the room → Post-mortem actions are written up and then never scheduledTests that fail intermittently are retried until green → Customers report outages before monitoring doesRetries are unbounded, so a slow dependency becomes a flood → The same three services cause most of the pagesAlerts fire so often that on-call mutes them → Every team has its own logging formatThe on-call rota has the same two people on it most weeks → Post-mortem actions are written up and then never scheduledThe on-call rota has the same two people on it most weeks → Alerts fire so often that on-call mutes themFeature flags are never cleaned up, so nobody knows which paths are live → The same three services cause most of the pagesFeature flags are never cleaned up, so nobody knows which paths are live → Rollbacks take longer than the outage they are meant to endOne engineer knows how the payment path actually works → The on-call rota has the same two people on it most weeksThe service map in the wiki is two years old → Feature flags are never cleaned up, so nobody knows which paths are liveFeature work always outranks reliability work in planningFeature work alwaysoutranks reliability workin planningPost-mortems assign actions to people who were not in the roomPost-mortems assign actionsto people who were not inthe roomTests that fail intermittently are retried until greenTests that failintermittently are retrieduntil greenRetries are unbounded, so a slow dependency becomes a floodRetries are unbounded, so aslow dependency becomes afloodOne engineer knows how the payment path actually works ② Give the shared schema one named owner and a migration tool with rollbackOne engineer knows how thepayment path actually works②šta prikazane akcije čine ovom osnovnom uzroku1 AKCIJA GA SMANJUJEThe service map in the wiki is two years oldThe service map in the wikiis two years oldšta prikazane akcije čine ovom osnovnom uzrokuNIJEDNA AKCIJA NE DELUJEDIREKTNO NA NJEGAFeature flags are never cleaned up, so nobody knows which paths are liveFeature flags are nevercleaned up, so nobody knowswhich paths are livešta prikazane akcije čine ovom osnovnom uzrokuNIJEDNA AKCIJA NE DELUJEDIREKTNO NA NJEGAThe on-call rota has the same two people on it most weeksThe on-call rota has thesame two people on it mostweeksšta prikazane akcije čine ovom osnovnom uzrokuNIJEDNA AKCIJA NE DELUJEDIREKTNO NA NJEGARollbacks take longer than the outage they are meant to endRollbacks take longer thanthe outage they are meantto endšta prikazane akcije čine ovom osnovnom uzrokuNIJEDNA AKCIJA NE DELUJEDIREKTNO NA NJEGAAlerts fire so often that on-call mutes themAlerts fire so often thaton-call mutes themšta prikazane akcije čine ovom osnovnom uzrokuNIJEDNA AKCIJA NE DELUJEDIREKTNO NA NJEGAThe same three services cause most of the pagesThe same three servicescause most of the pagesPost-mortem actions are written up and then never scheduledPost-mortem actions arewritten up and then neverscheduledReliability has no budget line of its ownReliability has no budgetline of its ownEvery team has its own logging formatEvery team has its ownlogging formatThe incident channel fills with people asking for status instead of giving itThe incident channel fillswith people asking forstatus instead of giving itThe staging environment does not resemble productionThe staging environmentdoes not resembleproductionCustomers report outages before monitoring doesCustomers report outagesbefore monitoring does
Svaki broj na mapi označava osnovni uzrok koji ta akcija smanjuje.
① No production deploy after 14:00 on Fridays unless the on-call engineer agrees
② Give the shared schema one named owner and a migration tool with rollback
③ Reserve one engineer-week per sprint for post-mortem actions, first in the sprint, not last
Šta očekujemo da usledi
Predviđanja o akcijama: šta bi svaka trebalo da promeni, kako to izmeriti i kada proveriti. Tog datuma neko ko je bio u sobi upisuje pored predviđanja šta se zaista dogodilo.
zašto
Mapa kaže koje akcije pomeraju koje uzroke. Ne kaže da li ih je iko sproveo, niti da li se išta promenilo. Unos ovde je predviđanje sa datumom i nečim što se meri, napisano pošto je mapa rešena. Kada dođe taj datum, pored njega se upiše šta se zaista dogodilo, a predviđanje ostaje kakvo je bilo: pogrešno je upravo ono korisno. Niko nije glasao ni o čemu od ovoga i to ne menja ništa od onoga što je soba utvrdila.
rok: 23 Jan 2027
akcijaNo production deploy after 14:00 on Fridays unless the on-call engineer agrees
očekujemothe same cause stops coming back once fixing it is in the sprint
merilorepeat outages with the same cause, per quarter
procenesoba: 3 (medijana; procena: 15; raspon od 1 do 6)