Good CTO, Bad CTO

Good CTO: Understands that developers are on the critical path: nothing "is" until someone writes some code.
Bad CTO: Thinks that developers are no different than business analysts, admins, or envelope stuffers, and treats them that way.

Good CTO:  Understands that formal process, while invaluable, is not infallible and must be augmented by the performance of excellent people.
Bad CTO: Forces creativity and determination to take a back seat to process.

Good CTO: Wants people to be "intrapreneurs", to feel as if they're running their own little "business within a business".
Bad CTO: Thinks that being "part of the team" is more important that getting work done, no matter what it takes.

Good CTO1: Listens.
Bad CTO: Talks.

Good CTO: Strives to understand customer issues deeply as a basis for all technology decisions.
Bad CTO: Forces customers to fit into his vision of technology.

Good CTO: Prototypes and iterates in order to learn "what".
Bad CTO: The specs are the Bible, at least until Version 2.0.

Good CTO: Ready, Aim, Fire. Or when super speed is needed: Ready, Fire, Aim.
Bad CTO: Fire. Fix. Fire. Fix. Fire. Fix.

Good CTO: Prioritizes "why"; facilities "what"; accepts "how".
Bad CTO: Dictates "how". Blames when "what" doesn't match "why".

Good CTO: Daily interaction.
Bad CTO: He works here?

Good CTO: Leader.
Bad CTO: Politician.

Good CTO: Encourages customers to provide input and feedback.
Bad CTO: Depends upon training and documentation when customers don't "get it".

Good CTO: Encourages developers to identify their needs and is eager to satisfy them.
Bad CTO: Blames developers for missing deadlines when they lack the resources they need.

Good CTO: Offices or war rooms.
Bad CTO: Cubicles.

Good CTO: Intense interaction as needed.
Bad CTO: Meetings.

Good CTO: Has finger on the pulse of the organization.
Bad CTO: Needs town hall meetings and web conferences.

Good CTO: To foster moral, always strives to do the right thing.
Bad CTO: To foster moral, cheerleading and gimmicks.

Good CTO: Developers love coming to work.
Bad CTO: Developers love their work in spite of their company.

Good CTO: Googles you.
Bad CTO: Wants you go Google him.

Good CTO: Watches the project plans and schedules.
Bad CTO: Watches the clock.

Good CTO: Stays for years until our baby grows up.
Bad CTO: Moves on just before the smoke and mirrors clear up.

Good CTO: Worries about 2 things: Getting our work done and keeping our people.
Bad CTO: Worries about 2 things: How he looks and how he feels.

Follow me: http://twitter.com/#!/edw519

Permalink

| Leave a comment  »