<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Speak Geek: Working Collaboratively with Your IT Department to Get Stuff Done</title>
	<atom:link href="http://www.bruceclay.com/blog/2008/08/how-to-speak-geek-working-collaboratively-with-your-it-department-to-get-stuff-done/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bruceclay.com/blog/2008/08/how-to-speak-geek-working-collaboratively-with-your-it-department-to-get-stuff-done/</link>
	<description>SEO and Marketing Blog</description>
	<lastBuildDate>Mon, 15 Mar 2010 19:51:58 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arthur Freydin</title>
		<link>http://www.bruceclay.com/blog/2008/08/how-to-speak-geek-working-collaboratively-with-your-it-department-to-get-stuff-done/comment-page-1/#comment-17896</link>
		<dc:creator>Arthur Freydin</dc:creator>
		<pubDate>Mon, 25 Aug 2008 13:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bruceclay.com/blog-test/2008/08/how-to-speak-geek-working-collaboratively-with-your-it-department-to-get-stuff-done/#comment-17896</guid>
		<description>&lt;p&gt;Hey Lisa,&lt;/p&gt;
&lt;p&gt;I find that the best way to get IT to take you seriously is to speak in their own language. If you come to them speaking marketing jargon and do not phrase your project in their own terms, it will be foreign to them.&lt;/p&gt;
&lt;p&gt;Also, do a bit of research &amp; provide them only the most pertinent info. For example, if you need a tracking pixel implemented, don&#039;t inundate them with why you need it implemented and what you expect to get out of it. Simply give them the code that they can copy/paste. This works especially well in smaller teams that do not need a full description of the code and justification for altering their precious code.&lt;/p&gt;
&lt;p&gt;It doesn&#039;t hurt to become an extension of the IT team either. For example, if your IT team lacks PHP knowledge and you need PHP in order to implement something you need, learn it! It&#039;s much easier for a marketing person to learn a small portion of a language that is essential to them than an IT person to learn the entire language. And you get the bonus of being indispensable as the only one in the company that knows their way around PHP!
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hey Lisa,</p>
<p>I find that the best way to get IT to take you seriously is to speak in their own language. If you come to them speaking marketing jargon and do not phrase your project in their own terms, it will be foreign to them.</p>
<p>Also, do a bit of research &#038; provide them only the most pertinent info. For example, if you need a tracking pixel implemented, don&#8217;t inundate them with why you need it implemented and what you expect to get out of it. Simply give them the code that they can copy/paste. This works especially well in smaller teams that do not need a full description of the code and justification for altering their precious code.</p>
<p>It doesn&#8217;t hurt to become an extension of the IT team either. For example, if your IT team lacks PHP knowledge and you need PHP in order to implement something you need, learn it! It&#8217;s much easier for a marketing person to learn a small portion of a language that is essential to them than an IT person to learn the entire language. And you get the bonus of being indispensable as the only one in the company that knows their way around PHP!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
