Introduction
When I started my career in 2008 as a software engineer, it didn’t take long to receive a nickname, Mr. Why. Every day, I’d get a list of requirements to implement without the faintest idea about their purpose. Trying to understand, I asked many questions but rarely got answers. When I did get something, it was pretty unconvincing. Here are some examples: “Because the business said so,” “Sales promised it to our customers,” or the classic, “My boss’s boss wants it.” Chasing unsatisfactory answers was my life, but something was about to change.
In 2012, I received the opportunity to become a product manager. Although I had no idea what it entailed, I got excited about one particular aspect: to be in a better position to obtain satisfying ...
Get Untrapping Product Teams: Simplify the Complexity of Creating Digital Products now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
