How do you balance "must do" work (compliance, maintenance, etc.) with objective/goal oriented work?

3 answers

All related (11)

Director of Product Management at Splunk • January 10

Before jumping into the "must do" work, it's best to understand the reason for doing the work. Sometimes the "must do" work is warranted. For example, compliance could have high customer impact whic

2 Saves

Saloni Patil

Director of Product at MikMak | Formerly Discover, IRI • September 30

The balance/percentage should be agreed upon by the EM and the PM and shared with the broader org for visibility. For example, in a team of 5 engineers, one engineer's time could be set aside for 'mus

9 Saves

Didier Varlot

Product Manager at | Formerly ClickUp • December 15

The main risk is constantly deprioritizing the Compliance and maintenance work and building a tech debt at such a level that it will take forever to pay it back. There are two kinds of situations: 1-

2 Saves

What framework should I use to prioritize either dedicating engineering resources to build out product functionality or just using a 3rd party service?

How do you get autonomy for prioritizing your roadmap when your sales process is very sales heavy, and sales leadership wants to dictate priorities?

What framework should I use to prioritize either dedicating engineering resources to build out product functionality or just using a 3rd party service?

How do you determine how much of your roadmap should be focused on existing customers vs prospects?

Which stakeholders have input into your roadmap, and how to balance giving them influence vs control?