I’m always thinking about how to be a better partner to my tech lead (TL) and how to distill my learning into a repeatable formula I can adapt to any situation. I remember once kicking off a meeting for a PRD I had just written with a new tech lead. My goal was to finish the meeting with a timeline and milestones. While we accomplished those things by the end of the meeting, I had a sinking feeling that the meeting didn’t go well, but I couldn’t pinpoint the reason.
Hi Xi, Thanks for sharing your feedback! We agree, the title is not clear, so we've updated the title to better reflect the principles in the post. Thanks for your help in making our posts more straightforward for other readers.
Don't mean to be rude, but I think this post could use some further editing. There are a number of inconsistencies (e.g. using tech lead, engineer, and EM interchangeably, fast iterations equal success in both frameworks?) that make it a bit hard to follow.
Hi Cale, Thanks for sharing your thoughts. The inconsistent vocabulary does make it a little hard to follow. We've just updated the post. Thanks for your support in making our posts more accessible to other readers!
Appreciate that - it is definitely much clearer now.
Some further editing is still required though. For example, the last sentence of the article: "By calibrating answers from the TL with the context you’ve gathered about their capabilities and PRD, so that you can ensure the success of your product launch."
Hi! I think you may have wanted to put a different table for the second one.
Whoops, that last table wasn't updated correctly. Thank you for pointing that out! It should be fixed now.
The experience and lesson are clear and straightforward, but the API analogy is not explained or illustrated in the examples/guiding principles.
Hi Xi, Thanks for sharing your feedback! We agree, the title is not clear, so we've updated the title to better reflect the principles in the post. Thanks for your help in making our posts more straightforward for other readers.
Love it! Thanks.
Don't mean to be rude, but I think this post could use some further editing. There are a number of inconsistencies (e.g. using tech lead, engineer, and EM interchangeably, fast iterations equal success in both frameworks?) that make it a bit hard to follow.
Hi Cale, Thanks for sharing your thoughts. The inconsistent vocabulary does make it a little hard to follow. We've just updated the post. Thanks for your support in making our posts more accessible to other readers!
Appreciate that - it is definitely much clearer now.
Some further editing is still required though. For example, the last sentence of the article: "By calibrating answers from the TL with the context you’ve gathered about their capabilities and PRD, so that you can ensure the success of your product launch."
Thanks for your help with editing, Cale! We just updated the sentence.