Tom Bartel's guest appearances

Tom Bartel

Digital Nomad Mastery - Travel the World

SimpleLeadership Podcast

Level-up Engineering

Email After Hours: The Podcast for Email Senders

Camille Fournier

Farhan Thawar

Katie Womersley

David Lynch

Jeff Perry

Ryan Nystrom

Joe Goldberg

Matt Martin

Claire Lew

Patrick Kua

Liam Martin

Bob Martin

Sarah Wells

Jon Thornton

James Hood

OwlTail

Episode Summary: Are you tired of fighting for attention in stuffed inboxes? Brand Indicators for Message Identification (BIMI) might be the answer. We know what marketers are thinking: Did we really need yet another email acronym? But BIMI is so much more than that. In this episode of Email After Hours, Tom Bartel, Senior Vice President of Data Services for Validity, joins hosts Guy Hanson and Danielle Gallant to explain how senders can use BIMI to win more clicks and conversions in the inbox. They’ll discuss the benefits of BIMI, how to implement it, adoption trends, and why senders will want to be early adopters of this emerging specification. (Best of all, they’ll do it in plain English!) If you enjoyed this episode then please either:Subscribe, rate, and review on Apple PodcastsFollow ‘Email After Hours’ on SpotifyEmail After Hours: The Podcast for Email Senders is handcrafted by our friends over at fame.so

Episode Summary: Are you tired of fighting for attention in stuffed inboxes? Brand Indicators for Message Identification (BIMI) might be the answer. We know what marketers are thinking: Did we really need yet another email acronym? But BIMI is so much more than that. In this episode of Email After Hours, Tom Bartel, Senior Vice President of Data Services for Validity, joins hosts Guy Hanson and Danielle Gallant to explain how senders can use BIMI to win more clicks and conversions in the inbox. They’ll discuss the benefits of BIMI, how to implement it, adoption trends, and why senders will want to be early adopters of this emerging specification. (Best of all, they’ll do it in plain English!)  If you enjoyed this episode then please either: <ul><li>Subscribe, rate, and review on <a href="https://tinyurl.com/4bvtmdfm" rel="nofollow" target="_blank">Apple Podcasts</a></li><li>Follow ‘Email After Hours’ on <a href="https://tinyurl.com/3yjfhd68" rel="nofollow" target="_blank">Spotify</a></li></ul>Email After Hours: The Podcast for Email Senders is handcrafted by our friends over at <a href="https://www.fame.so/?utm_medium=podcast&amp;utm_source=bcast&amp;utm_campaign=masters-of-community-with-david-spinks?utm_medium=podcast&amp;utm_source=bcast&amp;utm_campaign=confessions-of-a-b2b-marketer?utm_medium=podcast&amp;utm_source=bcast&amp;utm_campaign=cfo-weekly" rel="nofollow" target="_blank">fame.so</a>

BIMI, BIMI More: How to Boost Email Engagement with Tom Bartel, SVP of Data Services at Validity

Handling conflicts and giving feedback are two of the most important things a manager needs to do. It has to be a given to lead a productive developer team. So we interviewed Tom Bartel, Engineering Team Leader at trivago to share some of the tips he picked up over the years he spent as a manager.In this interview we're covering:  Common conflicts in an engineering team  How to step in and handle conficts as a manager?  Steps to prevent conflicts  Rules for giving feedback  How to give feedback to help improvement?  Common mistakes at giving feedback  Bonus advice  How to get feedback as an engineering manager?Excerpt from the interview:"At one point I had a new developer join a team of senior developers. The new guy was a junior both in skill level and age. The senior team members were used to each other and worked very well together, but the new guy didn't fit in well.It was partly the new developer’s fault. Sometimes he joked around in ways that would annoy the others, and didn't take the learning opportunities seriously enough. When his first round of feedback came, it was mostly bad. He didn't see it coming and he was devastated.I did what I talked about earlier, and got them all in the same room. We had a painful and awkward but ultimately healthy conversation. Everybody got to name what they didn't like about the situation, let it be behaviors or anything else. It resolved some misunderstandings too, because often problems are just that.I also had a one on one conversation with the new engineer. My expectations were clear: he had to stop with certain behaviors, and he had to take some things more seriously.To my surprise, he did everything I asked, and turned himself around. He applied himself, and improved the situation dramatically..."Click here to read the full interview!

Handling conflicts and giving feedback are two of the most important things a manager needs to do. It has to be a given to lead a productive developer team. So we interviewed Tom Bartel, Engineering Team Leader at trivago to share some of the tips he picked up over the years he spent as a manager.In this interview we're covering:<ul><li>  Common conflicts in an engineering team</li><li>  How to step in and handle conficts as a manager?</li><li>  Steps to prevent conflicts</li><li>  Rules for giving feedback</li><li>  How to give feedback to help improvement?</li><li>  Common mistakes at giving feedback</li><li>  Bonus advice</li><li>  How to get feedback as an engineering manager?</li></ul>Excerpt from the interview:"At one point I had a new developer join a team of senior developers. The new guy was a junior both in skill level and age. The senior team members were used to each other and worked very well together, but the new guy didn't fit in well.It was partly the new developer’s fault. Sometimes he joked around in ways that would annoy the others, and didn't take the learning opportunities seriously enough. When his first round of feedback came, it was mostly bad. He didn't see it coming and he was devastated.I did what I talked about earlier, and got them all in the same room. We had a painful and awkward but ultimately healthy conversation. Everybody got to name what they didn't like about the situation, let it be behaviors or anything else. It resolved some misunderstandings too, because often problems are just that.I also had a one on one conversation with the new engineer. My expectations were clear: he had to stop with certain behaviors, and he had to take some things more seriously.To my surprise, he did everything I asked, and turned himself around. He applied himself, and improved the situation dramatically..."<a href="https://codingsans.com/blog/handling-conflicts-giving-feedback?utm_source=Podcast&amp;utm_medium=platforms" rel="noopener noreferrer nofollow" target="_blank">Click here to read the full interview!</a>

Handling Conflicts, Giving Feedback: Tom Bartel (Engineering Manager at Trivago)

Tom Bartel of Trivago discusses moving into engineering management and creating time for writing his very informative blog on engineering management.  

Tom Bartel of Trivago discusses moving into engineering management and creating time for writing his very informative blog on engineering management.

Tom Bartel Interview