Background - I'm fairly new to Product management; switched from a technical background to a product role about a year ago and currently I'm working as a Product owner for a Platform of an application which is a travel loyalty program. Question - From a Technical Product Owner point of view, up until what depth should one perform discovery and design? Sometimes I get stuck in situations where a. the problem identified seems to be very generic [lets say it was not time-permissible for me to understand the entire underlying architecture] and now engineering has to figure out the specifics and then how to solve it b. sometimes I tend to get into specifics a lot [just because I have a deeper understanding of the underlying system] leading to situations where it seems like I'm almost dictating a solution (which is actually expected from engineering). Since the role of a Technical Product Owner/Manager differs slightly wherein we need to get into the technical specifics, can you advise how much is too much and how do we strike a balance? Request - Sid, it would be great if you bring up some specific examples related to discovery and design from a Technical Product Manager point of view.

Hello, Context - I'm a Technical Product Owner (switched recently into a product role, was formerly a development lead).