Blog

It's Never a Good Time To...

7/16/07

We thought we had it bad before computers. Companies thought they were choking on paper.

Way too much paper for everything we did. Forms in triplicate. Quadruplicate. And photocopiers – they added to the tidal wave of paper.

Then computers came along. “Aha,” we said, “the advent of a paperless workplace!” Bits and bytes will replace all this paper. And our lives will be easier. Simpler. Better!

Whooops. Those bits and bytes not only exploded the amount of paperwork, but now business faced another problem: the data avalanche.

Now we are swamped with paper.

And overwhelmed with data. Data, data, everywhere. Data required by law. Data required by policy. Data driven by new products. Data for new ERP systems. Data for sales. Data for marketing. Data for finance. Data for HR.

Will it ever end?

Nope. Someday we may wake up and everything we do grinds to a halt, choked on data.

The point is, there is never a good time to develop better ways to deal with data. Not tomorrow. Not next week. Or next month. Or next year.

It will only get worse. There is never a good time to get ahead of the data avalanche.

Except for today. The only “best time” there is. Take a look around. Take some time to think. Even if you have to lock yourself in your office. Or run away to the wilderness.

But look at your data for what it is. The avalanche that will never end. And find ways to deal with it. Quickly. Efficiently. And automatically.

Today. Because there never is a good time to…

Leave a comment


Name
Email
URL

	Download a FREE full-function 30-day eval copy of Foxtrot!
	Receive the FREE eval on a CD (second day delivery).
	Receive a FREE 45-minute “Proof of Concept”. We will automate a task on your system, using your data, with Foxtrot installed on your system, all executed using Webex.

First Name

Last Name

Company

Position

Address

City

State

Country

Phone

All fields required.

Based on your assistance, I was able to successfully write a script that automatically logs a message when an error occurs without having to stop and restart the script manually for each record. Last week, this would have 'liberated' me from having to do so 104 times while the script was trying to run to completion. We will now be even more efficient with this process, plus I can incorporate my newfound knowledge to other scripts which may have similar scenarios in other areas of our bank. Thanks for setting aside some of your valuable time to follow up with my support question.

Ken Scharnagl, AVP Research, Testing, Implementation