davetwichell

I've been in marketing for a while and my technical chops extend to being able to "run the demo" and even that gave me opportunities that others didn't.

One of the most valuable people on my marketing team when I was at a large company was our "Tech marketing" person. Someone who could build the demos and POCs and answer technical questions from customers and prospects. Maybe something like this or a "Solutions Engineer" could be a good fit

"A software development team is less like a sales team and more like a band." There's an Oasis joke to be made here, I just can't put my finger on it

"This type of always-on mentality is something that many companies are learning to combat because it is unhealthy and a leading indicator of bigger issues down the road."

This is something I've struggled with on and off during my career. I like my work and want to help things move along where I can, but being always-on impacts on my family life long-term.

Willing to share your story on video? We'll include it in an upcoming article (and enter you in a drawing for $100) https://vocalvideo.com/c/linearb-2

Love the "secrets" Nadav shared with Dan: The #1 characteristic of a great team: They make other teams around them better.

“Engineering and product teams need shared metrics and OKRs to stay aligned and encourage the teamwork you’re looking for.”

“Never use velocity to measure performance and never share velocity outside of individual teams.” I wonder how many teams stick to this

Worth checking out if only for the Zoom video background

But release are less frequent and larger. Sounds risky

Focusing on the wrong metrics can ruin a dev team's culture

Love the coffee talk zoom meeting

Agree that process is more important output, as long as the output is there . . .

Is everyone else seeing the same impact on cycle time?