RBT (parte II)

Parte I.
.
Nestes tempos em que andamos a preparar um caderno prático sobre o "Risk Based Thinking" (RBT) da ISO 9001:2015, dá logo para fazer paralelismos:

"Standardized processes that work are great. But if the folks at the head office get it wrong, then operations around the world can be locked into systematic dysfunction."

E:

"Call it assuming, call it blindspots, call it oversight, call it taking unknown forces for granted. Brian realized a valuable lesson from the kindergarten experience, and applied it to the Pathfinder project: inevitable, unforeseen and disruptive forces could be the ruin of the project, so there had to be a way to mitigate their potential impact.
...
Now, in space projects like the Pathfinder mission, it’s the job of someone called the fault protection engineer to look at possible failures of the spacecraft, understand how to recognize them, how the spacecraft would react, and what the consequences might be. But the focus of the job is on “what is true now,” rather than “what must be true” for things to go as planned."

1º trecho retirado de "Don’t Set Process Without Input from Frontline Workers"

2º trecho retirado de "The Gremlin Strategy, or How to Ward Off Disruption"