- celebrate when engineers identify or ask questions about gnarly use cases. PMs live in the happy path but engineers live in the corner cases. Too often I hear PMs dismissing those questions and say things like “that’s only 1% of customers so we don’t have to worry about that”
- ALWAYS loop back on the results of launches. So often engineers have no idea how their feature did and then they are asked to do more without context.
Thanks Camille and Lenny - really interesting conversation. So important to think about what happens to engineers who get missed out of the creative loop. Camille - we didn't get to "failure corner" but I was interested given your huge surface area in major financial platforms if you had one to share in the comments (probably without mentioning names).
PS: I listened to the podcast while lifting weights which when I got to the end I found out was the "right" thing to do!
These tips are good. I would add:
- celebrate when engineers identify or ask questions about gnarly use cases. PMs live in the happy path but engineers live in the corner cases. Too often I hear PMs dismissing those questions and say things like “that’s only 1% of customers so we don’t have to worry about that”
- ALWAYS loop back on the results of launches. So often engineers have no idea how their feature did and then they are asked to do more without context.
Thanks Camille and Lenny - really interesting conversation. So important to think about what happens to engineers who get missed out of the creative loop. Camille - we didn't get to "failure corner" but I was interested given your huge surface area in major financial platforms if you had one to share in the comments (probably without mentioning names).
PS: I listened to the podcast while lifting weights which when I got to the end I found out was the "right" thing to do!