Few eng orgs have clear engineering strategies, they can feel almost mythical & intimidating to write. While struggling myself, I’ve landed on a reproducible way to write useful strategies: five 5 design docs, synthesize them into 1 strategy, repeat!
lethain.com/good-engineeri…
lethain.com/good-engineeri…
The same thing works for writing genuinely useful visions as well. Write 5 strategies, extrapolate how those strategies will shape the next 2-3 years, and that’s the first draft of your vision doc.
Thanks to many folks, and @skamille and @b0rk in particular, for suggestions on the earlier version of these ideas that struggled to get them out clearly: lethain.com/engineering-st…
Also a bunch of existing articles and posts that were v helpful, starting with “Sending gifts to future-you” by @whereistanya
leaddev.com/technical-dire…
leaddev.com/technical-dire…
“A Framework for Responsible Innovation” by @CoralineAda
multithreaded.stitchfix.com/blog/2019/08/1…
multithreaded.stitchfix.com/blog/2019/08/1…
“How Big technical changes happen at slack” by @keithmadams and @johnnyrodgersis
slack.engineering/how-big-techni…
slack.engineering/how-big-techni…
Anyway, altogether, hope this helps you write your next engineering strategy and vision😀
of course, by "five 5" I meant "write 5" but it's a long tweet stream and I'm not gonna fix it 😅
• • •
Missing some Tweet in this thread? You can try to
force a refresh
