<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Scott Burkett&#039;s Pothole on the Infobahn &#187; manager</title>
	<atom:link href="http://www.scottburkett.com/tag/manager/feed" rel="self" type="application/rss+xml" />
	<link>http://www.scottburkett.com</link>
	<description>Blogging, opining, ruminating, and pontificating on entrepreneurship, venture capital, process improvement, technology, online communities, business networking, IT Management, online social networking, and other things that melt in the warm Atlanta sun.</description>
	<lastBuildDate>Wed, 02 May 2012 00:23:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<copyright>2006-2007 </copyright>
	<managingEditor>scott@incursio.com (Scott Burkett&#039;s Pothole on the Infobahn)</managingEditor>
	<webMaster>scott@incursio.com (Scott Burkett&#039;s Pothole on the Infobahn)</webMaster>
	<ttl>1440</ttl>
	<image>
		<url>http://www.scottburkett.com/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
		<title>Scott Burkett&#039;s Pothole on the Infobahn</title>
		<link>http://www.scottburkett.com</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>Blogging, opining, ruminating, and pontificating on entrepreneurship, venture capital, technology, online communities, business networking, IT Management, online social networking, and other things that melt in the warm Atlanta sun.</itunes:summary>
	<itunes:keywords></itunes:keywords>
	<itunes:category text="Society &#38; Culture" />
	<itunes:author>Scott Burkett&#039;s Pothole on the Infobahn</itunes:author>
	<itunes:owner>
		<itunes:name>Scott Burkett&#039;s Pothole on the Infobahn</itunes:name>
		<itunes:email>scott@incursio.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://www.scottburkett.com/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<item>
		<title>How Not to Hire a CIO</title>
		<link>http://www.scottburkett.com/technology-leadership/how-not-to-hire-a-cio-230.html</link>
		<comments>http://www.scottburkett.com/technology-leadership/how-not-to-hire-a-cio-230.html#comments</comments>
		<pubDate>Mon, 17 Apr 2006 11:00:12 +0000</pubDate>
		<dc:creator>Scott Burkett</dc:creator>
				<category><![CDATA[IT Management]]></category>
		<category><![CDATA[CIO]]></category>
		<category><![CDATA[CTO]]></category>
		<category><![CDATA[executive]]></category>
		<category><![CDATA[hands-on]]></category>
		<category><![CDATA[hiring]]></category>
		<category><![CDATA[manager]]></category>

		<guid isPermaLink="false">http://www.scottburkett.com/index.php/archives/230</guid>
		<description><![CDATA[Sadly, today&#8217;s post is going to be comprised of &#8220;YARS&#8221;, or Yet Another Recruiting Story. The one really good thing about being &#8220;in transition&#8221;, is that I am never at a loss for recruiting stories! Today we are going to explore how NOT to go about hiring a CIO, CTO, or other types of technology &#8230;<p class="read-more"><a href="http://www.scottburkett.com/technology-leadership/how-not-to-hire-a-cio-230.html">Continue reading <span class="meta-nav">&#8594;</span></a></p>]]></description>
			<content:encoded><![CDATA[<p><img style="margin-left:10px" align="right" id="image266" alt="hiring.png" src="http://www.scottburkett.com/wp-content/uploads/2006/04/hiring.png" />Sadly, today&#8217;s post is going to be comprised of &#8220;YARS&#8221;, or Yet Another Recruiting Story. The one really good thing about being &#8220;in transition&#8221;, is that I am never at a loss for recruiting stories! Today we are going to explore how NOT to go about hiring a CIO, CTO, or other types of technology executives.</p>
<p><span id="more-230"></span></p>
<p>The other day, a colleague of mine forwarded a rather interesting Atlanta-based CIO opportunity. This particular opportunity was for a $20-25M logistics company focusing on the railroad industry. One of the key requirements was some experience working within either the logistics, railroad, or supply chain industries. Since I have some supply chain experience in my background, I thought I would toss my name into the proverbial hat and learn a bit more about what they were doing.</p>
<p>Now I should point out that from what the job description stated, this firm needs some serious help.  They&#8217;ve gone from $6M to $25M in 4 years, and as a result of that rapid growth, their technology systems are, well, quite &#8220;varied.&#8221;  They have 5 different platforms, and my guess is, its all held together with bubble gum and bailing wire.  Hence, their need for someone to come in and straighten out the mess, and position them for growth by consolidation and migration.</p>
<p>I sent the recruiter a nice but succinct introductory email, along with my resume. She replied to me several days later with a rather interesting email. In this email, she pasted a lengthy questionnaire, along with some instructions.</p>
<p>I took a quick look at the first few questions, and they seemed routine enough, so I thought I would take some time to compose a nice response. Given that recruiters can quickly become overwhelmed with candidates (and also having personally hired hundreds of candidates over the years), I completely understand the various screening techniques that they use.<br />
<blockquote><p>NOTE: Be sure to ANSWER all the questions below, as well as:</p>
<p>*where you LIVE NOW&#8230;local Atlanta candidates will be given FIRST consideration!!</p>
<p>*when you are available to interview,</p>
<p>*when you are available to start and</p>
<p>Your MINIMUM annual salary requirements.</p></blockquote><br />
Now the questions above seemed pretty innocuous. These are all standard fare when it comes to any job interview.<br />
<blockquote><p>NOTE:<br />
** Experience in transportation, logistics, rail, distribution or supply-chain industries is absolutely required for this position.If interested, write back with the number of years of experience and a brief explanation of that specific experience in each of the following:</p>
<p># Years in logistics software (name of software)<br />
# Years in supply chain software (name of software)<br />
# Years in railroad<br />
# Do you consider yourself an expert in Microsoft Project, Excel, Access, Word, PowerPoint?<br />
# EDUCATION: from where? in what?</p></blockquote><br />
Text<br />
<blockquote><p>Please go through this technology&#8230;and let me know how much experience you have in each:<br />
# .Net<br />
# ADO<br />
# ADO.Net<br />
# ASP<br />
# ASP.Net<br />
# BCP<br />
# BEAM Resources<br />
# C#<br />
# COM<br />
# Crystal Reports<br />
# DTS<br />
# HTML<br />
# IIS<br />
# JavaScript<br />
# MDX<br />
# Oracle Database<br />
# PowerBuilder PFC<br />
# SQL OLAP<br />
# SQL Server database<br />
# VBScript<br />
# Visual Basic<br />
# XML<br />
# XSL</p>
<p>**NOTE: Also be SURE that if you have a particular experience from the above listing..that you have reflected that technology under the specific job(s) where you used it on you resume&#8230;not just in your technical skills section!</p></blockquote><br />
However, as I progressed further into the list of questions, it became readily apparent to me that the person sourcing this role (or at least the person who put together these questions) had little understanding of the way that executives are hired. Curious, I did a little more research on the company that the recruiter works for, and the haze quickly vanished as I realized that she worked for a body shop (staff augmentation firm). Now it made perfectly good sense. She simply didn&#8217;t know any better. Sending out these questionnaires is how she routinely hires IT staffers for her clients. Nothing wrong with it &#8211; it makes perfectly good sense in that arena. However, it doesn&#8217;t translate well into the executive space.</p>
<p>Trust me when I say that you don&#8217;t need to know how many &#8220;years of experience&#8221; a CIO has with HTML, or whether or not they have direct experience in two dozen other technologies (which is what this questionnaire asked). Technology executives need to understand 3 things about a given technology: what it <em>does</em>, what it <em>costs</em>, how it <em>integrates</em>. They don&#8217;t need to have memorized all of the attributes of HTML table tags or CSS options.</p>
<p>In order to make this post a bit more fun, I sent this job description to a retained executive recruiter who is an associate of mine, and asked him to rewrite the job description.  This is what he sent back:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><em>Scott, this one is bad. Real bad. Very unprofessional.</em></p>
<p><em>First, we push our clients to write the job description. That way we can validate what they asked for. However, probably half we have to write for them.</em></p>
<p><em>Couple of things to look for at first and avoid &#8230;</em></p>
<ol>
<li><em>Any job opportunity with out a compensation range is a red flag</em></li>
<li><em>Any job opportunity which point out negative aspects of the job &#8211; &#8220;Downtown&#8221; , &#8220;fallen by the wayside&#8221;</em></li>
<li><em>Any C-level opportunity that talks about parking dollars or riding Marta hints that it is very small</em></li>
<li><em>Any C-level opportunity that list detailed low level requirements that our required</em></li>
</ol>
<p><em>The following is a big sign that this is being handled by a non-executive recruiter:</em><br />
<blockquote><p><em>Also provide me with your availability to interview, when you would be available to start and your minimum salary requirement. When you are available to interview, when you  are available to start and Your MINIMUM annual salary requirements.</em></p></blockquote><br />
<em>&#8230; all that before they have even spoken with you!</em></p>
<p><em>OK here goes the rewrite. This is difficult because I don&#8217;t know what the client is really looking for &#8230;</em></p>
<p><em>Position: CIO<br />
Location: Atlanta, GA<br />
Compensation:  $150k-$200k<br />
Summary:</em></p>
<p><em>A world-class provider of Logistics and Supply Chain software products is looking to fill a CIO position. This client provides Logistics Management and integrated Supply Chain tracking systems to customers on five continents. The client has been in an accelerated growth mode and is looking for a leader who can set strategy and bring structure to an organization which has grown very rapidly. The CIO will be responsible for an organization that manages a variety of technologies such as … Visual Basic, Crystal Reports, .Net, Oracle, IIS and ASP, PowerBuilder/PFC, XML, XSL, JavaScript, VBScript, HTML, and DHTML.</em></p>
<p><em>Requirements:</em></p>
<ul>
<li><em>Experience in transportation, logistics, rail, distribution or supply-chain industries is needed</em></li>
<li><em>Experience setting IT Strategy</em></li>
<li><em>Experience consolidating multiple IT platforms and architectures</em></li>
<li><em>Experience reorganizing and motivating IT organizations</em></li>
</ul>
<p><em>If you are interested or know someone who might be, please call us at …</em><br />
&#8212;&#8212;&#8212;&#8212;-</p>
<p>What a difference!</p>
<p>At any rate, this is what can happen when you let a body shop staff your CIO role. If you are in the market for a CIO, CTO, or some other technology executive, you owe it to yourself to partner with a recruiter or firm that specializes in handling executive-level hires. Retained firms are the best, but more expensive. Many contingency-based firms can also handle your requests with skill and care. If you insist on going with a body shop to find your CIO/CTO/Tech VP, take some time to review their process &#8211; make sure that they are looking for the right things &#8211; the things that will matter to you in the end.</p>
<p>By not doing so, you run the risk of running off decent candidates, and fostering the perception that your firm isn&#8217;t serious about its executive-level technology hires.</p>
<p>Cheers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.scottburkett.com/technology-leadership/how-not-to-hire-a-cio-230.html/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Mornin&#8217; Cup: Hands-on, Hands-off</title>
		<link>http://www.scottburkett.com/technology-leadership/mornin-cup-hands-on-hands-off-73.html</link>
		<comments>http://www.scottburkett.com/technology-leadership/mornin-cup-hands-on-hands-off-73.html#comments</comments>
		<pubDate>Wed, 01 Feb 2006 13:19:36 +0000</pubDate>
		<dc:creator>Scott Burkett</dc:creator>
				<category><![CDATA[IT Management]]></category>
		<category><![CDATA[CIO]]></category>
		<category><![CDATA[CTO]]></category>
		<category><![CDATA[executive]]></category>
		<category><![CDATA[hands-on]]></category>
		<category><![CDATA[hiring]]></category>
		<category><![CDATA[manager]]></category>
		<category><![CDATA[technology_management]]></category>

		<guid isPermaLink="false">http://www.scottburkett.com/index.php/archives/73</guid>
		<description><![CDATA[I had a rather interesting discussion this week with the chief executive of a small, but growing tech firm here in Atlanta. He informed me that he was looking to hire a &#8220;hands-on&#8221; CIO. Intrigued, I dug in a little more. He had originally called me to gauge my interest as a potential candidate for &#8230;<p class="read-more"><a href="http://www.scottburkett.com/technology-leadership/mornin-cup-hands-on-hands-off-73.html">Continue reading <span class="meta-nav">&#8594;</span></a></p>]]></description>
			<content:encoded><![CDATA[<p><img hspace="10" align="right" alt="karatekid.jpg" id="image172" title="karatekid.jpg" src="http://www.scottburkett.com/wp-content/uploads/2006/01/karatekid.jpg" />I had a rather interesting discussion this week with the chief executive of a small, but growing tech firm here in Atlanta. He informed me that he was looking to hire a &#8220;hands-on&#8221; CIO. Intrigued, I dug in a little more.</p>
<p><span id="more-73"></span></p>
<p>He had originally called me to gauge my interest as a potential candidate for this role. As it turned out, I was not a good fit for the position, as the industry involved was not something I had direct experience in.  I did, however, offer to learn more about the position, in hopes of turning him on to someone who would be a better fit.</p>
<p>When I asked him to describe the responsibilities he envisioned for this person, he initially told me that the CIO would need to really be able to jump into the fire and help the development team with the day-to-day development effort. I told him that it sounded to me like he needed to hire a &#8220;software development manager&#8221;, not a CIO.  Hiring a good development manager would provide more focus on his software engineering efforts. Additionally, it would be more <em>cost effective</em> than hiring a CIO, and the <em>savings </em>could then be put back into the budget for other things.</p>
<p>He pondered this for a moment, and proceeded to inform me that this person would <em>also </em>need to be responsible for keeping the network and data center up and running.  This would involve network availability monitoring, and management of all of the routers, switches, servers and other big glowy boxy-looking thingamajigs in the data center. I told him that it sounded to me like he needed to hire a &#8220;network operations manager&#8221; to work <em>in conjunction with</em> his software development manager.</p>
<p>He muffled a small sigh, and replied that he was also looking for this person to manage the strategic alignment with their technology partners, and provide architectural oversight for the company&#8217;s core software product line.  I told him that it sounded to me like he needed a &#8220;chief technology officer&#8221;, or CTO, to work in <em>side-by-side</em> with the network ops manager and the development manager.</p>
<p>I thought about his burgeoning list of needs for a moment, and realized that his expectations were a <em>wee bit</em> out of skew.  I posed the questions &#8220;what are the priorities here?  Which tasks are more important than others?&#8221;  He replied that they were all equally important, and that he was hoping to find them all in the same person, as he only had room in the budget for a single hire. Suffice it to say, I don&#8217;t think he liked my advice.</p>
<p>I realize that smaller firms need employees that are able to wear many hats, but in this day and age they can&#8217;t conceivably wear them all at once. I suppose that it is <em>possible </em>to find someone capable of doing all of the things he wants, it just isn&#8217;t very <em>probable</em>. 10 or 15 years ago, it wasn&#8217;t only probable, it was easy.  That is simply no longer the case.</p>
<p>Back then, you could wear all of those hats with very little effort, as the technical environments we worked within back then were not as sophisticated and as complex as what we have today. Technology folks back then, even at the executive or managerial levels, were not required to become intimate with the business drivers &#8211; no longer the case.   In addition, the standards against which we had to adhere were sparse or nonexistant (for example, HIPAA &#038; Sarbanes Oxley).</p>
<p>In situations like this, it is probably more advantageous to prioritize your needs by aligning them with your overall business strategy, and hire accordingly. At some point, it may make sense to bring on a CIO-level hire, however a tighter focus on <em>operational-level</em> hires is probably going to have a better ROI in the short-term. In addition, you avoid the risk of putting someone too junior in a role that will eventually require someone more senior (as your business scales).</p>
<p>Cheers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.scottburkett.com/technology-leadership/mornin-cup-hands-on-hands-off-73.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

