I work in digital service design. We have a vocabulary that is meaningful to us.
We work in lean multi-disciplinary teams under an agile framework to develop user-centred services, with a rapid reiteration process to deliver a minimum viable product early and release value.
All these phrases caught on as buzzwords for people that have no understanding of what they mean (just that they were very good in improving the way many things were done). So agile became lurch from crisis to crisis. Lean became fire as many people as possible and cut wages. MVP became any old cobbled together in a rush.
Quick crib sheet:
User-centred design - you know nothing, so stop building things then testing them on an unsuspecting world (who are probably unimpressed with your efforts). Instead, use qualified researchers to uncover what people are trying to achieve, then start building things that service this need.
Agile / Re-iteration / MVP - Start with the biggest need first. Keep close contact with the ultimate users of your thing to ensure it works and is easy to use (people don't use things the way you think they will). Be prepared to frequently rethink. Get your service out there helping people ASAP and add additional needs in due course.
Lean / multi-disciplinary team - create a team of people who have a specific skill to lend, avoid unnecessary layers of management (self-organising is best) and governance (need less of this if truly user-centred).
My choice for hated term (other than socialising documents, though my better half hates the phrase 'capture' as in capture learning) is one that occurs frequently in blogs about agile projects: it's an oddly self-deprecating phrase, but lots of industry leaders say they have 'recently been thinking about (x)' - what they are referring to is months of investigation into (x), not just sitting at the desk for 5 mins.