Really excited for this. As a tech lead on a platform engineering team without a PM, I've had to fill that role myself for a long time and honestly, I've always struggled with it. Hopefully this will make the PM hat a bit easier to wear.
Been working on a few similar things myself - in particular a personal knowledge base, but also us now having a shared knowledge base across engineering/product. The latter has been awesome, especially as our engineers and PMs have been driving it's adoption and usage as well.
I really like the idea of taking tacit knowledge and making it explicit. I've been doing it old-school with my notes for years. The idea of using the effort to build a context file as the feedback loop for clarity of thought is really powerful. Thanks for sharing that, can't wait to read the rest!
Really excited for this. As a tech lead on a platform engineering team without a PM, I've had to fill that role myself for a long time and honestly, I've always struggled with it. Hopefully this will make the PM hat a bit easier to wear.
Really great read Alex :)
Been working on a few similar things myself - in particular a personal knowledge base, but also us now having a shared knowledge base across engineering/product. The latter has been awesome, especially as our engineers and PMs have been driving it's adoption and usage as well.
Looking forward to part 2.
I really like the idea of taking tacit knowledge and making it explicit. I've been doing it old-school with my notes for years. The idea of using the effort to build a context file as the feedback loop for clarity of thought is really powerful. Thanks for sharing that, can't wait to read the rest!