Earlier today I was reflecting my own background. About 10yrs ago, I bootstrapped a project into a startup. Some of its highlights would be getting paid customers, iterating product (pivoting in 2002 lol) and getting seed investment from institutional VC. You ask what's the big deal? Well, I was a junior in mechanical engineering with 0 coding experience in India, or any experience for that matter. I manage to move things forward. Got people involved.
10yrs later with multiple degrees in CS and 6-7yrs of experience delivering successful software at work. I struggle getting basic ideas off the ground. I just go into technical details and complexity.
The obvious answer to your question is that being a good engineer is not the same as being a good product manager.
They are very different skillsets and it sounds like the last ten years of focusing on technical details have impacted your prioritization and other product management skills. Lucky for you this is a solvable problem, all you have to do is practice.
Earlier today I was reflecting my own background. About 10yrs ago, I bootstrapped a project into a startup. Some of its highlights would be getting paid customers, iterating product (pivoting in 2002 lol) and getting seed investment from institutional VC. You ask what's the big deal? Well, I was a junior in mechanical engineering with 0 coding experience in India, or any experience for that matter. I manage to move things forward. Got people involved.
10yrs later with multiple degrees in CS and 6-7yrs of experience delivering successful software at work. I struggle getting basic ideas off the ground. I just go into technical details and complexity.
Shouldn't this be other way around?