Syncing up on MicroSpeak

My previous post mentioned lingo, and I've come to realise more and more how much of my language (particularly in e-mails) has been influenced by the Microsoft culture. Some easy examples that I use or hear on an everyday basis now (in no particular order):

• Sync up: as in "we should sync up later when you have time"; to have a one-on-one about some specific topic.
  
• Loop in: generally used at the start of an e-mail, as in "Looping in Tom, Jerry", to introduce new recipients into an e-mail thread (oh, instead of recipients, how about "stakeholders"?).
  
• Take this offline: for when a meeting goes off-topic and everyone other than the current speakers are going to sleep, at which point a responsible moderator would say "I think that's an issue we can take offline".
  
• S+ me: lingo for "send me a meeting request", which tells the receiver of such request that I'm so busy I can't remember to meet up with you unless it's in my Outlook calendar.
  
• Low-hanging fruit: as in "I think we should aim for the low-hanging fruit in this release"; in software terms, the features that are most easily implemented, or problems that can be most easily solved; possibly the ones that give the best bang for the buck.
  
• EOD/EOW: as in "we need a dev estimate by EOD"; EOD = End Of Day, EOW = End Of Week. Closely related to COB.
• Push back: as in "I got push back on that feature", or more likely in my case "I should have pushed back more on that request"; to respond in a negative way.
  
• Drive: as in "I think Bob should drive this since he knows more about it"; to take responsibility for pushing a feature or task end-to-end, typically championing, negotiating and interfacing across different teams/disciplines. Very similar to owning something; where one also takes responsibility but on a more individual level.
  
• Visibility: as in "if we pull this off, this will be great for our visibility"; to be able to take credit for something and be noticed by higher-ups.
• Ramp up: as in "I can't give you an answer on that, I'm still ramping up right now"; preparing for work in a new area/project.
• Triage: as in "file that as a bug and we'll triage it"; to determine whether something (a bug, a feature) is worth addressing or implementing, and the urgency of same.
  

I'm sure there are other expressions that I use these days without even thinking about it, but these are definitely the ones I encounter most. Maybe it's an inadvertent tool for excluding outsiders by using our own domain-specific language, but at least we're all working off the same page.