To put it simply, an engineering strategy is a document that defines:
- The what and the why of Engineering’s resource allocation against its priorities
- The fundamental rules that Engineering’s teams must abide by
- How decisions are made within Engineering
strategyが分からないまま5年位経った。
The reason most written strategies don’t apply is because they’re actually visions of how things could ideally work, rather than accurate descriptions of how things work today. This means they don’t help you plot a course through today’s challenges to the desired state.
The reason they often aren’t written down, is that strategy is no more, or less, than how the organization tackles its problems, which executives often don’t think is valuable to write down. That’s not to say that these undocumented strategies are consistently good strategies, (they often aren’t), but if you’ve ever been upset that your company doesn’t have an engineering strategy, then I assure you that you do! Your engineering strategy is how you approach your current challenges.
戦略とはQCCでいうAction Reportのことなのだな。
The good news is that these strategies do exist, even if they aren’t written down or are visions pretending to be strategies. The bad news is that this means you’ll have to do some work of your own to make sure you understand these other strategies before you start writing engineering’s.
どこでも空気を読まないといけないのは変わらない。
