"Planning is doing" may be the most under appreciated point.
I'm privy to a group involved with a US semiconductor initiative working on the order of $B. My current takeaway from the initiative is that they're trying to build the framework to build the thing before building the thing once - a common failure mode.
So they aren't planning by doing, they're planning by planning. Building one thing first before scaling it up would be a huge de-risk, but it probably doesn't seem like enough work to justify the $.
In software, planning by doing might also be similar to the concept of "tracer bullets" mentioned in The Pragmatic Programmer book.
This was fantastic, and very timely for me, thank you!
Thanks! Very glad it was useful.
"Planning is doing" may be the most under appreciated point.
I'm privy to a group involved with a US semiconductor initiative working on the order of $B. My current takeaway from the initiative is that they're trying to build the framework to build the thing before building the thing once - a common failure mode.
So they aren't planning by doing, they're planning by planning. Building one thing first before scaling it up would be a huge de-risk, but it probably doesn't seem like enough work to justify the $.
In software, planning by doing might also be similar to the concept of "tracer bullets" mentioned in The Pragmatic Programmer book.