Home > Software Engineering > 2013 New Year Resolutions for all CTOs

2013 New Year Resolutions for all CTOs

The most successful CTOs are managing champions of a process developing and executing technology strategy which helps deliver measurable and sustainable business results.

That’s the common wisdom.   I believe that exceptional CTOs are exceptional because they take this common wisdom even further:

“… deliver measurable business results which create a sustainable competitive advantage”.

It’s very comforting to see your closest competitor in the rear view mirror.  Yet the journey to this point in a company evolution is extremely difficult.

It does not have to be difficult.   The three elements of success – people, process, and technology – have not changed.  Exceptional CTOs know this very well.

My selected New Year resolutions for all CTOs in 2013 …


– Bring the question of strategic alignment into every conversation, even if someone else is responsible for executing other elements of company’s strategic and operating plan.   Does Sales organization have capacity to begin training well in advance of the launch date of a new, more complex solution offering?  Who is responsible for enabling Sales organization?  Is the Customer Support organization ready to accept the first call from a customer using the new major release?  Is the root cause decomposition process working?   Will it lead to a discovery of defect?  Or – a recognition that training was inadequate?

– You may build the best product.  But someone else may need your help to educate the Sales team.  Do not be afraid to bring it up and get on the road to educate the Sales team or even engage customers in the early stages of the sales process.


– Great teams are built and nurtured, not created.   Hire people who can demonstrate they subscribe to the mission and can work with others.  Great talent working alone does not contribute to the larger goal.   Get to know every engineer and treat each individual like they are the most important person.

– Tell your team on January 2 that you in fact work for them (instead of everyone working for you).  Your job is to establish clear objectives, enable everyone, remove barriers, and get out of the way.  This is the “right side up” organization – and it works.

– Great teams are quickly minimized by marginal managers.   Find a suitable opportunity for  them outside of your company.  Never transfer problems.   Do not be afraid of managing directly while finding a replacement.  Ask the most senior members of the team to participate in the interview process.

– Dedicate at least 50% of your time coaching the team.   Find a way to change the course of a meeting where the majority is trying to convince the minority why something may be impossible.   What if the minority is right?  What if something impossible is actually possible?   How do we – as a team – shift the dialog and determine one or more alternatives?

– Remind yourself every morning that listening is more important than talking

– Remind your team members that complex problems often require a collection of techniques in order to create a sustainable solution.  Excessive reliance on one process or technique often leads to failure

– If your team fails, immediately accept the failure for the team.  Then find the answer together


– Automate everything

– Bring focus on quality as early as possible in the design cycle.  If the functionality depends on correct database state after a series of updates, did anyone consider how to create an automated testing harness to generate several database states in order to test this functionality in the future?

– Over invest in the build / release engineering infrastructure

– Over emphasize defensive programming

– Over emphasize self educational error management, logging, and reporting approach;  ensure this is reflected in every engineering estimate

– Build and foster a culture where the value of finding and addressing the root cause is more important than who caused the problem

– Institute few metrics which are truly meaningful and highlight the performance of your organization.   One metric I ask my engineers to recognize in everything that they do:

“The root cause of every problem – no matter how complicated – must be identified in less than 60 minutes”

Imagine how a complex software product must be designed and engineered to meet this goal.

Adjust your rear view mirror and don’t stop in 2013 until every competitor is a distant fixture behind you and your team.

Happy holidays!

Categories: Software Engineering
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: