5 Dysfunctional IT Relationships -- and How to Fix ThemAdded 3rd Oct 2012
In large technology departments, dysfunctional relationships breed like mushrooms in a dank basement. Your dev and ops teams are no longer on speaking terms, while your junior and senior developers can't seem to agree on anything. IT and legal are constantly at each other's throats. Storage wonks are ready to declare war on the database admins, while sys admins seem to be on everyone's bad side.
Why can't they all just get along? In many cases it's the tension between conflicting demands on the same systems -- say, DBAs who complain about network performance but refuse to streamline their storage needs or business users who want to roll out new apps quickly, blissfully unaware of the effect they could have on other critical system
Fortunately there are solutions. We asked our geek relationship adviser, Crabby van Buren, to help find the common ground between these five warring factions. His advice follows.
Dysfunctional IT relationship No. 1: Storage admins vs. DBAs
Dear Crabby: Our database administrators have an insatiable appetite for storage. They never delete anything, they won't let us archive data or store it off-site, and they're constantly complaining the network is too slow. Meanwhile, the cost of storing all this data is killing our budget and making us storage engineers extremely unpopular with the CFO. What can we do?
— Underfunded & overcapacity
We feel your pain. Even today's networked and cloud storage options can't always keep up with the data explosion. But to the folks who aren't responsible for providing storage, the supply seems almost infinite.
"To solve the problem, you need to look at the groups that are producing the data," says Jim Damoulakis, CTO of Glasshouse Technologies, an IT infrastructure services provider. "DBAs are some of the biggest examples. They are extremely risk averse, tend to save everything, and want to have total control over all of it. But having to save everything forever can bring your backup systems to a screeching halt. You need to incent them to be more efficient."
In other words, once a department has to foot the bill for its insatiable storage habit, it may begin to appreciate the wisdom of efficiency. The problem is that most people hate chargebacks with a passion, says Damoulakis. The alternative is to set up a system that reports which users are consuming what resources, so when the CFO comes around to beat on the storage people for spending too much money they can say, "Talk to these guys."
Interestingly, says Damoulakis, a lot of this is already happening because of the cloud. Departments that bypass IT to order services directly from a third-party cloud vendor are finding that they're charged on a consumption basis, whether they like it or not.
"In a funny way the cloud is moving this to the forefront," he says. "It's a backdoor into a chargeback mechanism. Organizations that are adopting private clouds are also finding they can use that to make DBAs and other groups accountable for their own IT spend."
Dysfunctional IT relationship No. 2: Senior developers vs. junior developers
I'm a new software developer for a large company that desperately wants to be on the cutting edge. I'm trying to help them do that, but I keep getting stymied by the graybeards. The senior developers are always reviewing my code, and it takes forever to get approval for even a simple change. They're slowing down the company and, frankly, hurting my career. How do I tell these old dudes to back off without getting fired?
— Young & Restless
Old people -- when will they ever learn?
The first thing you need to realize is that maybe, just maybe, your more experienced developers might be right in being a little more cautious about unleashing insufficiently vetted code unto the world, says Joe Masters Emison, VP of research and development for BuildFax, which stores construction records for hundreds of millions of properties across the United States.
"Software is wonderful in that you can do amazing things with it," he says. "So a junior developer looks at Facebook and says, 'Gosh it would be easy to create X because all we'd have to do is change this one thing.' And if Facebook only served five people, that might work. But you may not understand what's required when you've got a large user base and a large body of code with a lot of people working on it."
It's the senior developer's job to contemplate all the terrible things that could happen from one tiny change, he adds. The cost of even one hour of downtime thanks to a small tweak in the code could be enormous.
For their part, senior developers must acknowledge there are scenarios where rules can be safely broken-- like editing code that's already in production -- without causing the sky to fall or the company's share price to plummet.
"There are certain situations where you want to do a live edit of a database -- say, to push out maintenance upgrades," says Emison. "Or sales might come to you and say they have a customer they need to close this quarter, but it requires certain changes to the code. When the risk of anything bad happening is low, you could be better off from a business standpoint to break the quality rules once in a while."
But if you must engage in "cowboy coding," Emison advises you follow the pink sombrero strategy laid out by Joshua Siler, a former VP with marketing firm Babcock & Jenkins who is now CTO at HiringThing, a cloud-based service that helps hiring managers post jobs online and manage applicants. Siler wrote:
Bottom line: As a junior developer, you need to learn more patience, while your bosses need to retain some flexibility. Otherwise, development turns into a fiefdom where hot new talent inevitably leaves and nothing innovative ever gets done.
Dysfunctional IT relationship No. 3: IT vs. legal
I'm an IT manager at a midsize enterprise with a lot on my plate. Yet every few days the legal department hounds me about something -- compliance, e-discovery, cloud service-level agreements, yadda yadda. It's keeping me from doing what my employer actually pays me to do. How do I get the lawyers off my back so I can get some real work done?
— Beleaguered by legal
Shakespeare may have been onto something when he wrote, "The first thing we do, let's kill all the lawyers." But without legal covering your company's back, your employer would probably be in a world of hurt -- and you'd find your job even harder to do.
A big part of the problem is that many corporate lawyers don't understand what IT does and have no idea what they're asking for, says Craig Carpenter, VP of marketing and general counsel for Recommind, a maker of e-discovery software tools. For their part, tech pros often see legal requests as a nuisance, even though one liability suit can bring the company to a screeching halt.
For example, legal might come to you and say they need all email for these 50 people from 2008 to 2012, and they need it tomorrow, says Carpenter.
"IT looks at legal and says, 'You have no idea what it's going to take to comply with that request,'" he says. "Legal looks at IT and says, 'You have no idea of the downside if we don't.'"
To bridge the gap, large enterprises need to dedicate a staffer who understands enough about both technology and legal that he or she can act as liaison between the two groups, Carpenter says.
"They don't have to experts in both fields, but they do need to understand what it means to extract metadata from both archives and live Exchange sessions," he says. "They need to know what legal really means when it says it needs to collect all emails from these 10 custodians. And they might be able to help legal understand that it's about to make life a living hell for 10 email admins and perhaps they don't really need all of the data they're asking for."
At the very least, says Carpenter, organizations should host off-sites with both teams so that they can have a regular meeting of the minds. The good news is that relations between tech and legal are improving. Surveys commissioned by Recommind indicate that two-thirds of enterprises have their legal and tech teams meet at least once every three months, and slightly more than half describe the relationship as positive.
The convergence of legal and tech is creating new job opportunities, he adds. Some day legal could end up offering you a job.
"Organizations are making roles for legal people to be part of IT or pulling people from IT into legal," he says. "But at the end of the day, most of the people who work with me have a technology background. It has created a whole new opportunity for IT professionals."
Debra Martucci, CIO and VP -IT at Synopsys and a former contractor to NASA, is upbeat about the company's investments in India.
Load balancing isn't just for websites that expect surges in traffic any more. Companies of all sizes, and in all verticals, find load balancing an effective way to address disaster recovery, scalability, failover and application virtualization needs.
As government organizations continue to deal with an increasing number of cyber threats, one thing has become clear to those who protect our digital assets: there is no silver bullet.
To give your organization the best shot at success during a disaster, you need to put a current, tested plan in the hands of all personnel responsible for carrying out any part of that plan.
Sivaram Tadepalli, CIO (Airport Sector), GMR Group recounts how he created animated stimulation on a CRT monitor many moons ago.
F5 CEO John McAdam and executive vice president of Strategic Solutions Manuel Rivelo shed light on F5 Network's new Synthesis Architecture for SDN and the companie's relationship with rivals Cisco and VMware.
Students at a U.S. military graduate school are mining social media with new methods that may change the way the armed forces collect intelligence.
The new director and CEO of CavinKare's Personal Care and Foods division, Nellaiappan Thiruambalam,wants the company to grow from Rs 1,200 crore to Rs 2,100 crore by 2015.
In a year filled with uncertainty, the CIO100 winners stood apart. Here’s a look at the difference true IT leadership can bring.
Cloud computing—in its many avatars—has helped this years CIO 100 honorees achieve remarkable business benefits. Here’s how you can too.
Can it be done better? Can we improve it further? Ask these award-winning CIOs, and the answer will always be in the affirmative.
Saving costs and driving business growth at the same time is tough. Some of this year’s CIO 100 honorees were adept at doing this.
It’s a harsh reality that threats are evolving as rapidly as technology itself. Here’s how some CIO 100 winners have responded.
This year’s CIO 100 winners have leveraged recent advancements in storage and server technologies to create datacenters of the future. Here and now.
Business intelligence has finally arrived. Here’s how five CIO 100 2013 winners have use d BI and analytics to their business’ advantage.