Monday goal: stop using business jargon

Something to consider for the work week is to try and not use any of the phrases found in this piece. I can’t say I agree with their substitutions. Best to leave the cliches behind and strive for clear English.

Once we get rid of all the bad business cliches, we can strive to clean the world of bad office stock photos like the one above 🙂

P.S. If you don’t use those cliches, that’s great. Another thing to consider is starting a bingo card and score it every time you see or hear one of those cliches at work. Chances are you will fill your card by Friday.

One response to “Monday goal: stop using business jargon

  1. The thing with most cliches is the crowd you are working with tend to understand it. It’s like refactoring and design patterns, we don’t explain what a chain of responsibility pattern is we just expect the person to understand it or at least know where to look.

    The real skill is to translate these technology terms into things that people who are not in tech.

    Like… what is a session and what does it mean it timeouts?

    A session is like a date, you assume the session is alive if both parties are talking to each other. A session timeout is like one side stops talking for a while and the other party thinks the date is over.

    A common scenario which happens on IT land is the user does not send any data back to the server for a while which happens when he clicks submit. On the date context, this can happen when one person asks “does this dress make me look fat?” and the other person is silently thinking of how to answer that for a long time until the date gets canceled.