You periodically need to revisit your diagnosis to make sure it still fits, still works for you, plays to your strengths as a team/business.
It doesn't need to be fancy, or a one liner. But as you know quite well, there is no such thing as "best way" in software, only "right way, for now" ☺️
It doesn't need to be fancy, or a one liner. But as you know quite well, there is no such thing as "best way" in software, only "right way, for now" ☺️
Comments
Thanks, that’s interesting food for thought.
When you say “who are you competing against” are you expecting engineering strategy to _explicitly_ derive from a broader company strategy?
It simplifies the complex world, gives structure to the policy/actions, and defines the domain where actions will be taken.
"We have engineering challenges" might be a (rough) diagnosis for a company strategy.
So I'd say "are you expecting engineering strategy to _explicitly_ derive from a broader company strategy?" isn't quite the right question.
But I'd be really cautious about an engineering strategy that's decoupled from company strategy.
Yeah, there's eng stuff that won't be in the corp-level strategy. But it should all fit under guiding policy.