Designer, implementor, user, writer A Fragment by Donald Knuth dl.acm.org Thus, I came to the conclusion that the designer of a new system must not only be the implementor and the first large-scale user; the designer should also write the first user manual. The separation of any of these four components would have hurt TeX significantly. If I had not participated fully in all these activities, literally hundreds of improvements would never have been made, because I would never have thought of them or perceived why they were important. Eating your own dog food making
The management strategy that saved Apollo 11 An Article by Matthew Ström matthewstrom.com In 1969, the people in charge of Apollo 11 trusted a 23-year-old engineer in a back room of mission control to make one of the most consequential decisions of this decade-defining mission. And they did so in seconds, without deliberating or debating. Next time you’re faced with a decision, ask yourself: how can this decision be made on the lowest level? Have you given your team the authority to decide? If you haven’t, why not? If they’re not able to make good decisions, you’ve missed an opportunity to be a leader. Empower, enable, and entrust them. Take it from NASA: the ability to delegate quickly and decisively was the key to landing men on the moon. Central planning gives poor resultsBeware SAFe, an Unholy Incarnation of Darkness managementdecisionstrust