Dan wrote:

The bottom line is, as I alluded to in an earlier post, is that
nothing at that level gets done around here without a project, a committee,
a cost/benefit analysis, and testing up the wazoo. It'd be a minimum of two
months before anything like this could be enacted.

Dan:

I see some great responses already, so I have nothing useful to add for that.

But something about that paragraph seems backwards to me. (Your other comments seem to kind of support my view.)

That is, your organization allows mass changes by non-tech people ("too much to expect the non-techie group responsible") to important documents (spreadsheets or whatever) that act as some kind of encapsulated 'routing tables', and expects them to be done in a few days, essentially with no significant errors.

Yet, the trained techs can't implement techniques that should make it mostly transparent to users without jumping through more hoops than trained animals at a 3-ring circus.

Things that make you go "Hmmmm...".

Ain't business fun?

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.