From inboxing to thought showers: how business bullshit took over

Re:From inboxing to thought showers: how business bullshit t... by hliyan on Wednesday December 27, 2017 @11:06PM (#16020240)

Having moved from engineering to management, I can attest that at least some of these terms have specific meanings where I work, except when they're abused. It's just that they used to sound like nonsense when I weren't faced with management responsibilities.

KT - the expectation is that the recipient should be able to perform the conductor's responsibilities after the knowledge transfer.

Stakeholder - there is a very specific group of people (mostly VP and above) that fall into this category. They need to be "kept in the loop" (another bullshit word, I suppose) when major changes to features, resources or business strategy are made.

ROI - for us, this boils down to a number, either in dollars or an expected change in a KPI (another bullshit term?)

On the same page - when a meeting/mail thread is started with this intent, the idea is that multiple teams with different/conflicting priorities need to agree on something so that they won't later claim "why weren't we told about this?"

Going forward - it's better than saying "from now on", which feels like a finger-wag to me

Synergy - yup, it's mostly bullshit

[ Parent | on HN ]

Re:From inboxing to thought showers: how business bullshit t... by closeparen on Thursday December 28, 2017 @03:27AM (#16020975)

Huh. For us, cross functional means very specifically that backend, mobile, and frontend engineers are on the same team (previously there was a backend team, a frontend team, and a mobile team, and getting a major feature done required coordinating all three).

[ Parent | on HN ]