I have had a weeknotes practice for a few years, starting in my upward 1:1 doc, and more recently expanding to public slack posts. It is always worth the time for my own reflection, for future reference, and for radiating intent.

seen from United Kingdom

seen from United States
seen from Brazil
seen from China
seen from United States

seen from United States
seen from France
seen from United States
seen from United States
seen from United States
seen from China
seen from United States

seen from Brazil
seen from India

seen from United States
seen from United States
seen from United States
seen from United States
seen from United States

seen from United States
I have had a weeknotes practice for a few years, starting in my upward 1:1 doc, and more recently expanding to public slack posts. It is always worth the time for my own reflection, for future reference, and for radiating intent.
I've read a good book about technical leadership and seniority in engineering recently - "Staff Engineer" by Will Larson. I've already reviewed it here (feel free to check it), so today I'd like to focus solely on one of the concepts covered in the book: so-called "Glue Work" (GW). It's
Always, always radiate intent - “IMHO the issue usually occurs when the person doing [glue work] doesn't "sell" it well enough (to both: the manager and the whole team) - e.g., by proactively (beforehand) raising its need & importance.”
As simple encouragement to act, “ask forgiveness, not permission” is fair enough. But here are 4 reasons to signal your intentions:
I'm a big fan of David Marquet's "Turn The Ship Around"