Chase the Data, Not the IT

Information Technology-'IT'-is luxurious. Every CEO, CFO, COO-truely every manager at every stage of every organization in existence knows that irrefutable truth. It's generally a prime line item in each organization finances. For the IT department, handling the employer technical capability approach first locating a product that meets some thing want the employer has come up with (and every now and then the odd whim of a unmarried supervisor), then the acquisition, set up, schooling, and maintenance of the hardware, software, networks, and databases that go along with the device. Then you get to fear approximately interfaces between the gear, reviews, protection (each internal and external), and the terrific, irrepressible, eccentric, and in many instances destruction habits of the give up users even after you've provided complete end-to-quit schooling on the new product. Then a person adjustments their mind and you get to do all of it over again. I personally agree with every metropolitan place have to have a non-public asylum for IT managers. This facility should come whole with regions for the temporarily insane to conduct non-public and violent destruction of laptop hardware, provide them a setup of punching luggage made to appear to be ignorant (not stupid, just unrealistic) corporation officials, and a further stomping floor complete of dummies made to resemble a diffusion of knuckle-headed quit users. And a unique location of hell for hackers... Such a facility could be stuffed to capability at all times. The madness would not forestall with the IT branch. For other agency managers, IT modifications means hours or days of education, downtime and loss of productivity that comes with IT problems, disasters, or system upgrades. For income group of workers, an IT glitch can suggest misplaced opportunity, lack of revenue, and a much less than stellar image of the agency that may stay in a client's thoughts for years. Salesmen may additionally by no means triumph over a terrible patron revel in generated by way of failed IT. The word "the laptop is your pal" is not widely spoken among income human beings. But IT is a vital evil, isn't always it? What organization may want to characteristic without it? Well, it is essential. Even an enterprising younger individual entering the workforce for the first time mowing yards wishes a way for clients to reach him/her, a way to manipulate a time table, perhaps even a way to music who has paid their invoice. But does IT must be evil? What if the evil-ness comes due to the fact we are trying to solve the incorrect problem with the IT? We're seeking to pressure a round peg into a rectangular hole, imagining IT can remedy our trouble with out definitely identifying what the hassle is? We purchase computers, networks, communications, and all varieties of things to do one element-capture and manipulate records. A easy reality that we inherently all know but gloss over-it isn't always the IT that's important, it's what's traversing that IT. It's approximately the records. Those little bits and bytes that make up characters that make up records elements that coalesce into information that offers us expertise that in addition transforms into intelligence that may be used and acted upon.

It's about the facts. Yet we chase the equipment riding the facts. But wait (you are saying)! We have our databases. That's part of the IT. That's where our information is saved. We need the IT to get to our facts. It's OUR statistics. Well, sure... Form of. But not simply. Your corporation does shop records into the databases associated with your business enterprise, generally interior a proprietary database that is a component and parcel to the software program you have bought. Most-or as a minimum a excellent deal-of that statistics is duplicated in different structures, some internal to your organization, however most surely in some different outside system. And putting in place a database is tough paintings, what with getting items diagnosed, parsed, moved into the right fields, validated, and such. It takes time and manpower which translates into dollars spent. And how clean is it to get it lower back out of that database as soon as you've got decided to transport directly to the next cool IT product? How many IT managers work an go out approach on the equal time they may be growing their acquisition approach? If you buy a proprietary product, do what facts rights you have and the way you may get out of that product while the time comes? Because it will. (By the way, the solution is normally 'no'-it's tough enough to get the product up and running while telling your dealer and employer leadership which you're already planning (and spending price range on) its loss of life.) OK, so who has the facts (wherein is your database honestly located and who manages it? Who has get entry to? Who owns it (do not make an assumption right here))? How will it be brought again so you can move it to a competitor's platform? Do you need to buy a proprietary (which means, luxurious) device to extract the statistics? Who handles issues? Who continues the documentation over the years so you truly recognize what that database looks like and precisely what each element approach (because that changes too)? This borders on the geeky but X won't continually and all the time imply X, or maybe now its X+2. Maybe X is now alpha-numeric while it started out out as numeric most effective. This records is clearly important-what modified and while? Without that documentation, you have no way of understanding if your information is complete, if its simply accurate or if its been corrupted.