I recommend sharing the full document with the group, then spending time with those who have the most feedback. You often won’t get much feedback at this stage, which is fine, you are now moving into socializing the plan rather than simply crafting it.
Be aware that once you share the document with the full set of stakeholders, it will almost inevitably leak out to the wider company. Companies are design to spread context, not to conceal it, and you just can’t fight that tendency. Instead, make sure to edit out anything too sensitive to share widely, particularly changes that directly impact individuals or teams
Writing an engineering strategy.
from Irrational Exuberance
Filed under:
Same Source
- Strategy can only be employed top-down, so it’s not a question of t...
- To ensure your strategy is operating at the right altitude, ask if ...
- As an engineering executive, it’s particularly important to think a...
- **Are you confident the strategy will create leverage?** Strategies...
- **Are you willing and able to enforce the strategy?** If you think ...
- **Are you either confident in your diagnosis or do you trust the wi...
- In Staff Engineer, I argued that writing an engineering strategies ...
- View all
Related Notes
- Rigid adherence to any prioritization model, even one that’s concep...from Irrational Exuberance
- A great framework for delegating work or encouraging a team member ...from Ken Britton
- We're talking about a guy who in all seriousness has said on ma...from gist.github.com
- we are creating more data than we can manage. The primary output o...from johnnydecimal.com
- Sometimes people use "respect" to mean "treating som...from kottke.org
- I recommend that teams receiving executive feedback try to “extract...from Irrational Exuberance
- I designed the RAMBO Model as a simple framework to lead a great en...from thecodecompany.com
- These constraints create better decisions both because constraints ...from Irrational Exuberance