[davidgh]

One place you can start that is not so far away is making a transition from code to the product. The good news is you don’t really need anyone’s permission to do this since you are close to the product already.

A lot of developers focus on the “what” and “how” because that is the bulk of their job. Start looking at the “why”. Start asking questions when you don’t understand the “why” - being careful to present yourself as curious rather than sceptical. Try to understand the motivations behind decisions, and the trade offs that are often required.

As you become a master of the product - again not just what you’re building but why - you’ll likely find yourself with opportunities to contribute much more in the business side.