วีดีโอ

Really good conversation, a great reminder to validate assumptions

I mean as an engineer when i can tell that something is going on between my pms and people are putting on happy faces instead of being real, it shows and it errodes trust. It says to me, what arent they telling me? Why are these people who are busting their butts for me so worn out or so overwhelmed? Should i be worried? It sets up the environment for me to not want to put any more stress on them than they already have and to wonder if something went wrong that maybe i should be aware of. That kind of environment is nervous and makes everyone feel tentative. And for all the reasons you’ve already covered that doesn’t lend itself well to innovation and instead leads to fear based decisions and priorities.

So glad you didnt say Theresa was the thing that was wrong with that project. Lol! 😅. Also i recognize i have probably thought about you all a lot more than any of you have spent thinking of me. That was really my first greenfield project. Im lucky to have gotten to do more than one now and i have to say these sorts of experiences are memorable and unlike the usual day to day. I think they tend to stick with you just like the people do because you learn so much.

And bam. I think you guys addressed my 2 suggestions from episode 4 lol. Loving this series.

Document churn and lack of understanding over what the skip level is looking for. Ive seen some of my pms exhausted with process because of lack of clarity there. Another thing ive seen is a disconnect between the metrics being tracked and what the dev team is working on. How do you work as a team in a way that ties the work to the goals in a very visible and clear way? The last thing you want are devs eyes glazing over during your part of the weekly sync meeting or success/failure of an initiative being unclear causing mistrust that we’re even working on the right things. Id Love to hear any thoughts on that if its not already covered somewhere…. Do you have a troubleshooting episode coming up, lol like what to do when you find yourself in circumstance x y or z and how to get back to healthy as a team. What are the pitfalls to avoid in those circumstances. ❤. Also i just love hearing you guys talk again. It takes me back. 😊

So interesting to hear your thoughts on our project in retrospect. One of the things i loved about work with you all and geno were the questions you all asked and the lessons i feel we were all learning along the way. We may not have succeeded but i feel like i came away from that project understanding what business partners were supposed to be doing for a project and what a really collaborative working relationship looked like. I measure a lot of business partners against some of those experiences because they were valuable examples to me where everyone was all in and working hard to pivot and correct. Sure i wish i could point back at that as a successful effort but i feel like the working relationships towards the end of the project were well developed and I often wish i had that again.

Super stoked to watch this series! I love you two ladies!! Excited to hear your thoughts!

Adore and admire you ladies! I appreciate the intention of OKRs but writing them never feels natural and often becomes a checkbox exercise vs a practical driving force.

Loving your podcast! Commenting for the algorithm!

Thank you for this amazing podcast Leah and Marilyn! You are totally right, it's not about reading "The Book" (or books), every company is completely different and I you can't just apply what you've read to the company. it doesn't work, it doesn't fit. I also very liked the "it's not practical to be someone else", that's also a fact!