Goblin Division
Technology that survives contact with reality
[ 1 / Brief ]
No plan survives first contact with the enemy
The mission still has to
[ 2 / Doctrine ]
-
2.1
Build for the mission, not the operator
The mission has requirements. The operator has preferences. When they conflict, the mission wins.
-
2.2
Build systems before features
The hard way is the fast way.
-
2.3
Bad news first
If the idea won't work, that comes up in the first meeting. Not as a foreseen surprise 6 months later.
-
2.4
Burn it down when it stops working
No elaboration necessary.
-
2.5
Small by design
No layers between the problem and the solution. Whoever designs the system builds it, deploys it, and answers for it.
[ 3 / Engagement ]
Want something that schemes and plots for you?