Why Product Request SLAs Fail
Source: https://www.mironov.com/slas/ ↗
Mironov has been writing the most consistently useful voice on the daily operational reality of product management for two decades.
This piece is a short argument against a specific anti-pattern: internal stakeholders pushing product teams to commit to service-level agreements on request turnaround, as if product were a ticketing desk.
Mironov's response is surgical — SLAs work when the work is commodified and predictable, both of which are definitionally untrue of product work.
For product direction the piece is useful vocabulary for a conversation many PMs have regularly and badly.
Pair it with Mironov's broader blog — there is no better operational complement to the strategic literature.
Central argument
Mironov argues that applying SLAs to product requests is a category error: SLAs are a tool for commodified, repeatable work where volume and effort are predictable, and product work is neither. When stakeholders push for turnaround commitments on feature requests or roadmap items, they are implicitly treating product management as a service desk — a framing that corrupts prioritisation by rewarding request velocity over strategic value. The piece insists that committing to SLAs forces product teams to optimise for responsiveness rather than outcomes, undermining the core function of product judgment.
Critique
Mironov's argument is persuasive on its own terms but largely assumes a product team operating with meaningful strategic autonomy and executive cover — conditions that do not exist in many organisations. In contexts where product has historically failed to deliver predictability, stakeholder pressure for SLAs is often a rational response to opacity and broken trust, not simply a misunderstanding of product work. The piece diagnoses the symptom well but sidesteps the harder question of what commitments product teams should make to rebuild that trust without surrendering to the ticketing-desk model.
Why it matters for product
For a CPO, the SLA anti-pattern is most dangerous not at the individual PM level but in how it shapes organisational design — specifically when business units are given formal channels to submit requests with implied turnaround expectations, which quietly reorients the product function toward internal client services. This piece provides precise language to intervene in that structural drift before it calcifies into process, particularly when resisting pressure from sales, operations, or regional leads who have real leverage and are used to getting it.