3 ms·
Now that I come to think about it, I have never seen an engineering strategy document. I think one of the key principles he’s trying to say here is that having
by thenerdhead 4y ago
Now that I come to think about it, I have never seen an engineering strategy document.
I think one of the key principles he’s trying to say here is that having a bad strategy is similar to no strategy. Aligned with Rumelt’s wonderful book.
The big challenge for said good strategy is how certain decisions have been made. Most people just see a resulting backlog and ask questions accordingly. But if you knew the underlying strategy going into these backlog decisions, you’d focus more time on assessing if that strategy matches with the business and product needs.
I think many groups would benefit from hearing about their engineering strategy from their leaders. Which seems non-existent in most places.
- Spartan-S63 4y agoThis point dovetails nicely with the idea of a "Commander's Intent." In this case, a strategy document is the intent being spelled out. If it's written well, a rank-and-file engineer can read it and understand why certain allocations are made, why certain priorities are pursued, etc without having to ask too many questions or feel like a cog in a machine.