9 Comments
Feb 12, 2022Liked by Alexis and Adrienne

Hi! I think you may have wanted to put a different table for the second one.

Expand full comment
author

Whoops, that last table wasn't updated correctly. Thank you for pointing that out! It should be fixed now.

Expand full comment
Feb 2, 2022Liked by Alexis and Adrienne

The experience and lesson are clear and straightforward, but the API analogy is not explained or illustrated in the examples/guiding principles.

Expand full comment
author

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.

Expand full comment
Feb 3, 2022Liked by Alexis and Adrienne

Love it! Thanks.

Expand full comment
Feb 1, 2022Liked by Alexis and Adrienne

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.

Expand full comment
author

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!

Expand full comment
Feb 3, 2022Liked by Alexis and Adrienne

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."

Expand full comment
author

Thanks for your help with editing, Cale! We just updated the sentence.

Expand full comment