When rushing to adopt new proprietary technology in an emergency like now, be VERY cautious of future liabilities, post crisis.

The danger of treating acute pain with morphine is a long term, destructive, expensive addiction...

Many tech solutions are entirely analogous - by design. Their proprietors are delighted this crisis provides an opportunity to sneak past sensible procurement processes.

@lightweight Yes. But sometimes you *will* need to use morphine or some other proven painkiller - especially when the alternative is a crowd of people trying to "sell" you various strangely-looking ingredients and insist that you just get out of the comfort zone, overcome your laziness and roll your own painkiller just like everyone should do to ensure their independence... 😐

@z428 yup. The point is that each person has a duty to those affected by their decisions to be informed, and aware of their liabilities and other options. Most people don't bother raising the shroud of ignorance. And, remember: marketing (like a casino) never works in your best interest. See davelane.nz/marketing

@lightweight Agreed. Yet there are situations in which falling back to "household names" seems the only viable solution, and the *core* (only?) problem being that alternatives are far from being "household names" or even viable products that are available and reliable. Experiencing this with Microsoft Teams at the moment: Introduced responding to the crisis and the need to get close to 40 people to work from home all of a sudden. There were no real "easy-on" alternatives, there wasn't ...

@z428 the real problem is that this was such a shock for so many people. It's not like no one could've anticipated this sort of situation and developed a contingency. Like global heating, we all knew this would happen eventually. It just shows how useless most of our strategic planning and liability management practices are.

Follow

@lightweight I think it depends. We're actually (maybe also because of the overal level of digital / remote work in our particular domain) pretty much behind in this field of technology, so until earlier last week, remote work for the vast majority of the staff (except developers, sales and tech support) was *supposed* to be on-site, no one from the actual business team even *wanted* to work remotely for particular reasons, so planning was to consider such options merely for load-balancing ...

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!