# TBM 230: From Prioritization to Accountability  ## Metadata - Author: [[John Cutler]] - Full Title: TBM 230: From Prioritization to Accountability - Category: #articles - Summary: Some quick advice to product leaders—especially leaders involved in discussions about efficiency, productivity, and ROI: If you don't provide your product's investment and governance framework, one will be provided to you. And the person providing that framework (e.g., finance, sales, or marketing) will not create a framework that is friendly to making great products. - URL: https://cutlefish.substack.com/p/tbm-230-from-prioritization-to-accountability?sd=pf&utm_source=Mind+the+Product+Newsletter&utm_campaign=ac23a53f89-prioritised-newsletter-2023-07-17&utm_medium=email&utm_term=0_babd9cfe61-ac23a53f89-110461336 ## Highlights - Most prioritization frameworks are used as "feel good" frameworks. Teams engage in a ceremonial act of performative diligence and pseudo rigor—weights, scales, and scores—to avoid the really hard conversations. ([View Highlight](https://read.readwise.io/read/01h5jhzg7ztjhhzbh7bh65bk45)) - In many companies, the funding model is: "Give us money to build the stuff you want us to build, and do the barest minimum of maintenance on the stuff you asked us to build in the past." To fulfill your end of the bargain—to be held "to account"—you deliver the stuff when you promised to. ([View Highlight](https://read.readwise.io/read/01h5jj3qm7rvn71x3mb5nmzvgf)) - Tags: [[favorite]] - the result here is a mess of poorly maintained features and products, a mountain of debt, a big team—hey, you needed all those people to build all that shiny new stuff—and a lot of people asking you about ROI, and how to keep costs down. In this model, you're playing the internal software development contractor game. ([View Highlight](https://read.readwise.io/read/01h5jj95k8j627rpcdcrg1gegn))