Borrowed with permission from Jeff Fedor, a startup veteran who writes Buzz Pressure, a bloggy blend of tech wisdom, moxy, and irreverence

. . . the VP Dev is crankier than even the crankiest of CTOs. That’s because Veeps keep it real, they shelter developers from the CTO and other C-types and in really productive cases they’re a great reality check for the CTO.

I changed the title of this article about 50 times. Some losing candidates:

• Driving your VPs crazy for fun and profit – true but fenced me in too much

• ”You got vision in my technology!”- with apologies to the good folks at Reese’s. A bit esoteric and again not enough latitude.

• “What would you say you do around here?” — with apologies to Mike Judge (please don’t sue me!). This was a tough call but I’ll learn to love again…

In both my personal and professional life I get a lot of questions around what a CTO is, exactly.

Everyone knows what a CEO does (mostly). COOs execute on vision through operations. CMOs do, ah something, yeah I’m sure they do something… with uh (capital ‘M’) Marketing. That means not the t-shirts or ball caps. [Easy Biff, I’m only joking] CFOs have it easy with the lack of ambiguity in that whole finance thing.

Sadly it isn’t so cut and dry for CTOs. Probably because we’ve been our worst enemies. We like having fingers in every pie and are slow to give up those pies. Mmmm pie.

I threw this post together to try to explain what it is CTOs do, why we do it and how you need to manage a CTO up and down. Obviously this is only my personal views from being a CTO and from commiserating and hanging out with other ones, your mileage will definitely vary.

“Typing” Your CTO

You need to know what breed of CTO you’re caring for. Each of the following has different characteristics, preferences and personality traits. Although there are other “species” out in the wild, in North American software you’ll likely have one of the following beasts:

• The Technical Founder – the person that wrote the code that got the company off the ground. Has sweated to give the alpha/beta/product life and as a result any criticisms are effectively received/interpreted as “Your baby is ugly! Now where’s your Corn Flakes so I can piss in them too!” Is never far from code.

• The Visionary – sometimes seen as the flake without any “real” deliverables. Is never far from a whiteboard. Can write code but shouldn’t.

• The Figure Head – parachuted in, probably did or was associated with something impressive in a semi-related industry. Doesn’t know most of the company but is on a first name basis with most flight crew. Is never far from PowerPoint.

All of the above are neither nocturnal nor diurnal but more typically work almost all the time. A CTO tends to segment their day into multiple sessions — this is because they’re overly concerned about “flow”. This peculiar trait is challenging for the CTO both in terms of their expectations of other’s availability and similarly their responsiveness.

Also unlike developers, CTOs are typically very social animals but their odd self-imposed schedules prevent ‘normal’ socialization outside of technical circles. Ironically this social trait does not translate to excellent management skills which most CTOs lack.

Related Species

VP Dev/R&D/Engineering – often confused with CTOs, VP Devs are a different breed entirely. You can typically distinguish a VP Dev from CTO from the CTOs ability to match markets with problems with game changing technology coupled with their capacity to speak coherently about deeply technical things at a level that business people can understand all the while retaining credibility with the technical folk in the room.

VP Devs on the other hand can be determined by their freakish level of attention to detail and love of process (again freakish). They worry, a lot, about executing on the nutty crap their CTO (particularly “The Visionary”) just cooked up and possibly presented to a large audience and you’ve got to love them for it.

As a result the VP Dev is crankier than even the crankiest of CTOs. That’s because Veeps keep it real, they shelter developers from the CTO and other C-types and in really productive cases they’re a great reality check for the CTO. Sometimes CTOs unnaturally camouflage themselves as a VP Dev until they are unconvincing in either role.

CEO – strangely the CTO and CEO are allies though cross-breeding is rare. Often they travel together on migratory patterns to key customers and events and plot “vision-y” things on cocktail napkins. This drives the organization crazy but is a really, really good thing.

Daily Habits

The Technical Founder CTO largely lives their day the same way as they did when they bootstrapped the company. Although both the coffee and the food has gotten better, the Technical Founder spends less time in code which can lead to a general crankiness. Prolonged exposure to a 3 monitor setup and some uninterrupted flow makes everything good for everyone.

The Visionary has 2-4 good whiteboard sessions per day all focussed on market dominance and shaking up the status quo. They then proceed to confuse everyone in the company with ad hoc discussion of their germinating ideas. They stare off to space during other conversations as they process even more tangential ideas. Visionaries get cranky where their days get stale or repetitive and need frequent trips to customers, standards body sessions or opportunities to speak at large venue conferences.

The Figurehead is constantly on the “circuit”. They attend 2-4 conferences and events per month. They’re excellent golfers and they spend a lot of time with customers and analysts. As a result have little time for anything else. They direct the development of ghost written whitepapers and blog postings and they appear in multiple, preferably pre-recorded webcasts. The Figurehead can get a meeting with anyone — no seriously they can. The Figurehead is happiest when left to run in the wild and then and only then will the company will reap the rewards.

CTO Language

With possibly the rare exception of the CTO Technical Founder, CTOs in general think, act and speak in the big picture. Although typically they’ve plotted things out at a fairly fine grained level, they consciously generalize details. They have to do this to serve the various audiences that CTOs interact with on a daily basis. Although it may appear that they’re glossing over details, they really aren’t they just haven’t needed or more likely had the opportunity to disaggregate at a finely grained level yet.

Still I haven’t met a CTO yet who hasn’t felt their latest brainchild wasn’t entirely possible but not without risk. You should know that CTOs do worry about risk but they also find risk thrilling and will naturally be drawn towards alpha and beta software (nightly builds preferred) like a moths to flame.

CTO Time

Because of the CTO’s “big picture” context, their notion of time isn’t the same as most of the organization that puts up with them. When a CTO says “Take a look at technology/concept X” it’s honestly not an immediate thing. Rather it is a topic they’re currently noodling and they want your thoughts on the subject and are testing the validity of the ideas.

Remain calm and know that this is why you have a VP Dev and Product Management to shield you from the tear in the CTOs time-space continuum that makes them temporally ambiguous.

Final Guidance

In summary, a CTO is the source of big picture technical and product strategy in an organization. This is often expressed during whiteboard deathmatches or through prototypes that they quietly whip up and surprise the company with. In short, they drive innovation often while frustrating the rest of the organization. CTOs are typically the external technical voice of the company and crave inspirational contact with the external world. They thrive on variety and find solace in chaos.

CTOs should not be mistaken for CIOs — a self-respecting CTO would never worry about rolling Exchange out. [Ok again, I kid.] Similarly they’re not VP Devs who actually do something tangible in an organization. Lastly CTOs are not product management though they typically do drive product strategy.