Thread by @lissijean

Great question! I worked with a #remote team as a PM and our team is all very remote these days - Spain, Kansas, Amsterdam, NYC, Croatia. Here’s my tips for #prodmgmt /1

Establish times you will be online, especially if there are different timezones. Make sure everyone knows how to reach you and when you will be available. /2

Set checkins once a day if you’re not used to working remote to make sure you can align. As you get better at aligning remotely, you can move this down to a quick slack message. /3

Jump on Zoom or video messaging to hash things out. You don’t need to set a specific time - if you’re working through something on chat and it’s easier to do it face to face, get used to jumping on a call. This usually resolves things 10x faster. /4

Document, document, document. If you haven’t been doing this before it’s time to start. I’m not talking crazy long specs, but your team needs to know where to go find answers if they can’t reach you. It’s very different than walking over to a desk to ask questions. /5

Retro every week on the remote parts - how is it going? What can we improve? /6

Keep an open line of communication with your stakeholders. They may not be as comfortable working remotely as your dev team. Set up more frequent check ins with them. Use documentation to communicate more effectively. Send updates in emailed. /7

Besides this general advise, I can say my team and I worked really really well remotely. We were constantly chatting online, jumped on video when needed, and generally talked the same amount remotely as we would have in the office. /8

We also made sure our team knew when we were going heads down or needed to step away. There was no guessing if we were coming back that day or how long we’d be gone for. /9

Over communicating was key for us at the beginning. As we learned our flows, we decreased set meetings for adhoc ones. We chatted more online.

You’ll find your groove. Seeing what works and refining it every week will help you move along. /10