Inbound Internet Marketing Blog

SEO, Blogging, Social Media, Landing Pages, Lead Generation and Analytics

SUBSCRIBE

The HubSpot Inbound Internet Marketing blog covers all of inbound marketing - SEO, blogging, social media, lead generation, email marketing, lead nurturing & management, and analytics. Join 57,702 others and subscribe now!

Subscribe to RSS feed Add us on Facebook! Follow us on Twitter

Get Free Marketing Info!

Get the world's best marketing resources right to your inbox! Join more than 817,000 inbound marketers!

Subscribe by email

Your email:

HubSpot's Inbound Internet Marketing Blog

Current Articles | RSS Feed RSS Feed

Why IT SHOULD Be Involved in Marketing Software Decisions

 

.

This is part of 2 articles regarding the debate about the role Internet technology (IT) departments should play in making marketing software decisions.  Read part one, "Why IT Shouldn't Be Involved in Marketing Software Decisions," written by HubSpot Inbound Marketing Specialist, Matt Sullivan.

Without a doubt, IT gets frustratedI know Information Technology. Over the past 10+ years working in IT Departments, including being the head of two different professional service IT departments for 7 years, I have come to know the ins-and-outs of IT. As a result I've been able to respond to feature requests, plan out development cycles and show the value of a platform. Regardless of how I was involved with a marketing software project, there always seemed to be the same speed-bump: being brought in too late to make the project a success.

Why do you need to bring in IT?

1. Your IT team needs to plan for your project. Let's face it: any software or Web project is going to touch IT somehow.  Even something as simple as moving your website requires IT to do something.  By bringing in IT early, you can allow them to plan to dedicate some of their resources to your project.

2. IT may not want the maintenance but will be called in anyway. Matt's 7-hour car trip aside (7 hours in a car, 7 years as head of two IT departments -- same thing, right?), anyone in IT can tell you that, despite trying to get out of it, they'll have to help you out with maintenance of anything that touches computers.  Very little is as frustrating as being surprised with product questions for a product you didn't know existed.  Oh, and don't forget that the marketing department just might complain to executives that IT doesn't know what it's doing when IT can't answer that surprise question...

3. Marketing does not understand IT. If you want IT's time and attention (you know you will need it at some point during the project), try to understand their priorities.  Businesses cannot survive without their technology, so IT's primary purpose is to keep the virtual lights on.  That puts your request at the end of a very long list.  If you get IT involved in your decision-making process early on, you have a better guarantee of IT's resources when you need them.

I agree with Matt that having a full strategy in place is the key to any large Web project.  I even agree with Matt that IT should not make the final decision.  However, failing to bring IT into the process after you've narrowed down your software choices to 3-5 different products or platforms practically guarantees failure.  At the very minimum, it guarantees a lack of IT resources dedicated to you and continues to sour the already contentious IT/Marketing relationship.

At the end of the day, your IT department will appreciate you for getting them involved in the process.  If you don't, prepare to buy lots of donuts.

Join the debate!  Do you think IT teams should or shouldn't have a hand in making marketing software decisions?

Photo courtesy of Erin Vermeer

 

Free Webinar: Website Redesign for 2010

website redesign webinarLearn how to redesign your website with an internet marketing strategy in mind with Mike Volpe, HubSpot's VP of Marketing.

Download the Webinar Now and learn how to turn your website into an internet marketing machine.

Posted by Jenn Steele on Mon, Feb 22, 2010 @ 11:00 AM

COMMENTS

Great post, Jenn. My question: should IT be involved in marketing software purchasing discussions beyond commenting on the ability for IT to optimize its implementation? In other words, would it be enough for me to say, "I want to do XYZ; how effectively can you make that happen with Acme's software?" and make a decision based in part on the answer to that question? Or is wiser to purchase software based in part on IT's valuation of the software? Or both?

posted on Monday, February 22, 2010 at 11:08 AM by Matt Shaw


Excellent. When I first posted to part 1, I thought it was just anti-IT. I'm happy to see part 2 is the counterpart (pro IT). 
 
 
 
Actually, the scenario will go something like this. Marketing will probably fund the software purchase. Then IT will be involved in the installation, set-up, security, backup, etc. This is the way things should work. 
 
 
 
If marketing doesn't want to pay for it - if they want to just use the IT budget, then IT should choose the software (unless they have existing software in place). 
 
 
 
I'm a firm believer in using open source or free software, which has stood the test of time - if possible (i.e. Apache, MySQL, Perl, Drupal, Joomla, WordPress, etc.). Often you can purchase third party maintenence contracts, for a fraction of commercial software (i.e. Oracle or SQL Server). Of course, if the commercial software offers something that's unique - go that route.

posted on Monday, February 22, 2010 at 11:48 AM by Randy Kemp


Of course IT has to be involved with Marketing's Software Decisions. Marketing may know what the software needs to accomplish but only IT subject matter experts can understand how different software choices will affect ongoing operational expenses and therefore long-term ROI - not to mention security and performance concerns. The days of either department being able to deal with each other in isolation are behind us. Here's a blog post I wrote in regards to Inertia in IT but it could just as easily apply to Marketing.  
 
http://www.thommitchell.com/2009/11/16/inertia-in-it-changing-hearts-and-minds/ 
 
 
 
Thanks for starting a good discussion on such an important topic. 
 
 
 
Thanks,  
 
Thom Mitchell 
 
http://www.thommitchell.com

posted on Monday, February 22, 2010 at 1:17 PM by Thom Mitchell


@Matt,  
 
I think the answer to your question is "a little bit of both". So much of it depends on historic relationship of IT & marketing, how IT's systems are implemented, which department has bandwidth, etc.  
 
I personally ALWAYS want marketing to make the final decision and involve IT only as much as necessary in order to make an optimal decision. But it's still nice to have a conversation to see if/how systems integrate/etc.

posted on Monday, February 22, 2010 at 1:50 PM by Jenn Steele


Thom is on the money. Particularly at larger organizations, the role of IT is not just to set up and maintain hardware/software systems. It is to make the organization run efficiently through those systems. Marketing will be the subject matter expert when it comes to functionality, and IT should be the subject matter when it comes to scalability, maintenance, interoperability, etc. 
 
That said, I've experienced the bottleneck of IT before. But when all is working correctly, they should be involved in the process.

posted on Monday, February 22, 2010 at 4:35 PM by Tracey


As several commentators have said, it's a balance. I agreee with Randy Kemp's assessment of the respective roles of IT and Marketing; essentially, each group contributing according their specific skills and experience. THere's no question that IT should be involved in IT decisions and should be involved in at least first-line ongoing support, but specialist consultants and vendors should be allowed to getting on with doing what they do every day. I wrote about this recently myself and hopefully struck this balance! 
 
What IT needs to do for Marketing

posted on Wednesday, February 24, 2010 at 3:01 AM by Simon Daniels


As several commentators have said, it's a balance. I agreee with Randy Kemp's assessment of the respective roles of IT and Marketing; essentially, each group contributing according their specific skills and experience. THere's no question that IT should be involved in IT decisions and should be involved in at least first-line ongoing support, but specialist consultants and vendors should be allowed to getting on with doing what they do every day. I wrote about this recently myself and hopefully struck this balance! 
 
What IT needs to do for Marketing

posted on Wednesday, February 24, 2010 at 3:01 AM by Simon Daniels


As several commentators have said, it's a balance. I agreee with Randy Kemp's assessment of the respective roles of IT and Marketing; essentially, each group contributing according their specific skills and experience. THere's no question that IT should be involved in IT decisions and should be involved in at least first-line ongoing support, but specialist consultants and vendors should be allowed to getting on with doing what they do every day. I wrote about this recently myself and hopefully struck this balance! 
 
What IT needs to do for Marketing

posted on Wednesday, February 24, 2010 at 3:02 AM by Simon Daniels


It's interesting seeing a paired set of articles like this explore two sides of a common situation. This isn't just an IT and Marketing story, but also and IT and Sales, IT and Finance, IT and Operations... 
 
In a nutshell, IT is responsible for providing tools to allow data input and collection, data storage, and data retrieval and reporting. There are many IT departments that choose the passive role of computer repair or simply don't want the responsibility. Funding a department that is shirking it's responsibilities seems like a poor decision to me. Maybe it's a communications issue, a strategic prioritization issue, a lack of resources, or simply someone that is holding down a role they don't understand. Find the root cause and fix the problem. The job of IT in a business is to fulfill that responsibility, bypassing them in the hopes to get something done more quickly is only going to make the problem worse. 
 
Something interesting I noticed in the marketing perspective was the comment about level of experience and knowledge. This is something we all need to work on. Expertise in one area does not make you an expert at all. Being an expert at CMS's doesn't help you determine the impact on the network equipment, server licensing, existing budget negotiations, disaster recovery plans, local regulatory acts, and any of a dozen other topics. Having a subject matter expert in-house will lighten the load a little on IT, whose training and budgetary costs obviously weren't taken into account as part of the implementation planning, but it does not replace this responsibility.

posted on Sunday, February 28, 2010 at 2:17 PM by Eli Weinstock-Herman


Comments have been closed for this article.