Your point on involving developers early on is spot on. If product requirement documents or other types of analysis are done in silos of PM/UX and engineers are only involved at the end of the process, it leads to knowledge disconnect and potentially incorrect architecture decisions from the start.
Samuel, I really enjoyed this article.
System thinking for me means involving developers very early in the product development process and keeping them in the loop.
Only if you understand your domain and the product’s users well you can think holistically on the impact of your work on their experience.
Nice one 👌🏼
Thank you, Peppe! I'm glad you liked it.
Your point on involving developers early on is spot on. If product requirement documents or other types of analysis are done in silos of PM/UX and engineers are only involved at the end of the process, it leads to knowledge disconnect and potentially incorrect architecture decisions from the start.