Neal Ford and Mark Richards present a useful way of thinking about knowledge as a technologist through the knowledge pyramid.

Mark’s pyramid illustrates how fundamentally different the role of architect compares to developer. Developers spend their whole career honing expertise, and transitioning to the architect role means a shift in that perspective, which many architects find difficult.

Here, this is applied to software architect as a role. I'd say it's also helpful for anyone in a product decision making role to consider.

The focus early on in a career is in specialization. As responsibilities expand, it becomes more important to gradually fatten the T.