4 Comments
Apr 28Liked by Basma Taha, Fran Soto

Thanks for the mention Fran, loved this collaborative post! 🔥

Expand full comment
author

Thank you, Alex!

Expand full comment

#1 and #5 are the most crucial imo.

Regarding demos - sometimes, there is no formal procedure for those, and you can create one! A couple of years ago one of our engineers started Coding & Chill sessions - 30-45 minutes every 2 weeks, where engineers could talk about cool technical things, both work related and not.

When you initiate such recurring meetings, and orchestrate it - you get bonus points in addition to your presentation :)

And #5 is very under utilized! When we release something, I try as much as I can to let the engineers write the release message to the team (and not the PM/me). This helps them get visibility, and also get closer to other departments.

Expand full comment
author

I totally agree, Anton.

If there's no mechanism, create one. We are engineers, we create things :)

Many people will see these as distractions from their work. But there's a lot of benefit on becoming well connected with people outside your team and increasing your visibility

Expand full comment