Excellent collection of laws/wisdom. Several of these are my experience with large software implementation projects

A few other things that I found:

1. If you find the bugs/issues sooner in the implementation, the cost of remediation is low and it exponentially increases the later you find the big/issues.

2. No project meets the cost, timeline and business objectives set at the beginning of the project.

3.starting with the minimal viable product and then learning from the implementation of it and enchancing it is the best way to implement a successful large project.

and all the above wonderfully add to the below book:


Expand full comment

Fantastic collection of wisdom.

37. (Henshaw's Law) One key to success in a mission is establishing clear lines of blame.

-very hard to do, but giving people "ownership" over particular aspects has been really helpful in my businesses

33. (Patton's Law of Program Planning) A good plan violently executed now is better than a perfect plan next week.

-sometimes. The real trick is knowing when this is true, and when it's not. You'll be wrong about this a lot of the time.

20. A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately.

-I wish I had known this 20 years ago!

Expand full comment

37 reminds me of Apple’s Directly Responsible Person (DRI) model. Maybe a good topic for tomorrows post

Expand full comment

Do it! I love the quick definitional stuff.

Maybe you can write up something like that one day and I can expand on it for a piece. I'd be down- I like to speculate about things, and you're great at being concise.

Expand full comment

Your comment on #33 = a salutary shout-out to #21 😉

Expand full comment

46. If the choice is 2 or 13, pick 2.

Expand full comment

Lovely post. I’m in for more!

Expand full comment