[_djo_]

Triage isn't a word that came out of tech, though. It's a term from the medical field, specifically for trauma care, and effectively means prioritisation under pressure.

A product manager really should know and understand this, because it's not like it's impenetrable tech jargon. They should also be the ones making those prioritisation calls, albeit with a solid understanding of the real trade offs.

In a situation like this there can be multiple reasons for the mismatch, none of which have anything to do with needing a language translator. For instance, is the product manager trying to force through that feature without moving out the team's other work to match? If so, then they will obviously get the 'triage' demand and be forced to make a priority call.

I've seen that too often in my career, where from the PM/PO side a feature or improvement is 'obvious' but because they won't take on the political battle of moving out a team's other feature work that's less valuable they either force the team to work beyond their capacity or, if they have more backbone, to refuse outright.

Or is the team intransigent and inflexible, and trying to protect low value but more technically interesting work? Then that, too, is a problem and needs to be solved through incentive changes and other measures, because it's just as unhealthy.

[juve1996]

> A product manager really should know and understand this, because it's not like it's impenetrable tech jargon.

It's not tech jargon but it's a medical term, that has to do with people possibly dying or wounded soldiers that can't be handled, and now we're using it in tech? Ignoring the ridiculous overexaggerating that is, this is exactly the kind of jargon that techies will get mad at managers for using.

Just say what you want. "We have other priorities, how does this fit with those, and what item will have lower priority now?"

[_djo_]

Except that the semantic shift of triage to also meaning any under pressure prioritisation of too-scarce resources, including in a project sense, is decades-old and predates its usage in tech. This is a case of tech adopting business jargon, not the other way around.

Even if the product manager wasn't familiar with the term itself, they'd surely be familiar with the idea of prioritising incoming tasks by importance and value and moving out work with lower scores. A simple question should've allowed them to link the word and the concept in their heads. This is unlike true tech jargon, where both the word itself and the underlying concept might be completely unfamiliar to anyone outside of tech and difficult to understand.

You shouldn't have to explain prioritisation to a product manager.