The micro/mezzo/macro of product development

When thinking about feature development, bug fixing, improvements and prioritisation, you find your brain being pulled by 3 entities of “wants”, that all interest you at a different level.

You care about the technological path you want to take. The frameworks you will use. Opening your API to other platforms. Monitoring & preventing fraud. Scaling operations. Those are the macro-interests.

You care about improving the speed of your website. Developing new features. Becoming mobile friendly. Adding personalisation in your product. Improving your Analytics implementation. Mezzo-interests.

You care about the consistency of your style guide. adding a motion effect on hover on your logo. adding gmail markup to your transactional emails. addressing users by first name, having a special background when a user has her birthday.

All 3 areas are important to create a holistic product that users love, but how should you distribute your cognitive efforts between them?

1/3 each? That sounds unbalanced, spending as much time thinking about hover effects as making your site responsive.

Is it more like 20/60/20? You should spend most of your time organizing and developing the new features and improvements that will create most of the value in the mid term, while keeping in the back of your head the strategy around the technology you are maintaining/creating, and also staying in touch with details that give an “awesome” effect to your product?