These are challenging times, especially for engineering leaders. How do you “engineer” the trust in a distributed team that would occur normally in a localized workforce? Today’s guest is here to show you how. Jeremy Wight is the VP of Product and Engineering at Base. Base raised $2.6M in 2019 to build the first software platform that’s exclusively for Executive Assistants. Jeremy has been building a remote team for the past two years, and he’s collected some amazing insights about building a fully distributed engineering team. In this episode, we talk about the best-practices he’s used to keep his remote team rowing in the same direction and shipping product that matters.
Listen in to hear the full conversation.

Wes’ Takeaways:
1. High-functioning remote teams focus on moving KPIs instead of shipping features.
2. Little “p” product ownership breeds more autonomous remote workers.
3. Serendipity breeds trust, but serendipity is hard on remote teams.
4. How you win is putting the fire out in 30 seconds or less.
5. If we aren't building the right things, it doesn't matter how much we work.