Nicolay Gerold
@nicolaygerold
@nicolaygerold
74 highlights
Here’s his 5-step process:
1/ Question every requirement
Never except that a requirement came from a department, such as from “the legal department” or “the safety department”. Requirements from smart people are dangerous because people are less likely to question them.
2/ Delete any part or process you can
You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough.
3/ Simplify and optimize
This should come AFTER step two.
4/ Accelerate cycle time
Every process can be speeded up. But only do this AFTER you have followed the first three steps.
5/ Automate
That comes last. Wait until all requirements have been questioned, parts and processes deleted, and the bugs were shaken out.
There were also additional “rules” to the Algorithm including:
1/ Camaraderie is dangerous. It makes it hard for people to challenge each other’s work.
2/ All technical managers must have hands-on experience. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword.
3/ The only rules are the ones dictated by the laws of physics. Everything else is a recommendation.
11 highlights
14 highlights
by Substack
9 highlights