My Talent Strategy Principles


Back in graduate school, I took a couple of courses on Org Theory.  In these courses we studied many things (Org Theory is an absurdly broad topic with far more theories than practices), but one of the items that was particularly interesting to me was an examination of what makes a good executive and how high-performing executives are able to make good decisions quickly, with imperfect information. There are many theories on this topic, but one in particular had a strong ring of truth to it and has always struck me as being the most sensible.

The idea is that over the course of their career, the high-performing executive develops a set of principles that guides their strategy and enables them to make very fast decisions.

Notice I do not use the term “successful”… we all know successful executives that are dolts and gained their position via the Peter Principle… I am talking about you US airline industry

These principles are typically formed early in a career and come from lessons learned, formal education experiences, and influential people (parents, first great boss, mentors, etc.). Once this foundation exists, decisions can be quickly tested against this set of principles. The slightly-nerdy part of me would call this a set of business rules for decision-making. The very-nerdy part of me would call this a series of conditional test algorithms comprising a heuristics model for decision-making. Let’s take the “business rules” path and avoid making my brain hurt.

With ever-increasing frequency, I get “how did you do that?” questions from my industry peers (and every now and then a Superintendent or CEO). Whether the question relates to performance management systems, ERP, high-service levels, or simply cost picture, my answer is almost always “I built a good team”. That answer usually prompts a series of requests for org charts and job descriptions. While these artifacts are standard fare in our roles and as long as we have HR departments we will need them, I don’t feel that they are particularly important (though I do believe that the process of creating them has its value). The question I think should be asked is…

How do you build a good team and how do you keep it all together?

Whenever I try to answer this question I start to rattle off single-sentence advice tidbits and quickly sound like a business school version of Everybody’s Free to Wear Sunscreen.  I have come to realize that I have my own set of principles, developed over the course of my career, and that I do not typically think of them in concrete terms.  As an exercise to help me both identify these principles and articulate them more effectively, I decided to give them substance by writing them down.

  • Pay enough that salary is no longer part of the conversation
  • Avoid large pay disparities
  • Use bonuses to differentiate performance
  • Leverage the power of spot bonuses
  • Do not make the mistake of believing that you compete for technical talent with the K-12 sector.. you compete with EVERY sector.
  • A high-end team is the cheaper option
  • Foster a sense of elitism in your team
  • Firing is far more important than hiring
  • Bad attitudes are infectious, abate the wound
  • Balance your team with external hires and internally developed talent
  • Build a promotion path for the entry level positions
  • Titles matter
  • Training is sustenance, not luxury
  • Support regrettable attrition

Many of you will disagree with at least some of these principles and you might even think some of them are crazy (Support Regrettable Attrition usually elicts an “Oh.. he’s soft in the brain” response).  I encourage you to call me out on anything you believe is wrong.  I am a work in progress and as such, so are these principles.

In future posts I will take each individual principle and give a deeper explanation… stay tuned.

The story continues…

    1. My Talent Strategy Principles: The Original (You are already here)
    2. My Talent Strategy Principles: Compensation

About Richard Charlesworth

Mr. Charlesworth is the senior technologist at YES Prep Public Schools in Houston, TX, an open-enrollment public charter school system that is leading the pack in the national education reform movement by providing world-class education to Houston's most disadvantaged youth, and sending 100% of them to college for over a decade. As the technology leader for YES Prep Public Schools, Richard is responsible for all technology solutions and manages the IT Infrastructure and Support Teams as well as the Applications Development and ERP Systems teams. For an organization as agile and lean as YES Prep, these teams are key to realizing our vision of defining the next generation of education best practices. Since joining the YES Prep team and entering the world of education reform, Richard has led a variety of critical, transformational projects in areas that include business and IT strategy, business process improvement, strategic technology planning, ERP selection and implementation, Business Intelligence, and collaboration systems. He has also created and led best practice communities for IT Strategy, Business Intelligence, and Collaboration: bringing together industry leaders from Microsoft, Dell, Hitachi Consulting, and others with high-performing educational institutions.

Posted on May 31, 2011, in Org Theory, Talent Strategy and Management and tagged , , , . Bookmark the permalink. 3 Comments.

  1. Stephanie Hill Simione

    Photoshop is not even remotely intuitive and I think Adobe likes it that way. You have to have skillz and training to figure shit out. It’s for the serious-minded designer. (But I think it could be more intuitive and still retain its snob factor) For quick and easy, I tend to use Snagit which IS intuitive and cheap to boot. It can’t do layering or terribly fancy techniques but I use it pretty much every day to take screen shots and and then move bits and pieces around to show my developers what should move where. And I overlay fake customer information with it all the time.

  2. Stephanie Hill Simione

    How annoying. I intended my first comment to be back on your header topic. Hmmmm….. Anyway, just thought I’d say “Stan would be proud” in looking at your principles.

  3. Richard,

    I wanted to thank you for the great post. I have reported to you for over 2 years, and I can testify that these principles have made it very wonderful to work for you. You are by far the very best CIO that I know, and if I ever find myself in your shoes someday, I want to make it known that I have learned a lot from you, and I will continue to learn a lot from you.

    For me, keeping me engaged, and letting me know when I just did something amazing or not and keeping me encouraged is why I love working for you. Spot bonuses are also a great idea, and a great motivator… …especially when the person you are giving it to has been so “heads down” to the point they wouldn’t even expect to see it coming.

    You also are part of the team no matter how far out there your title is. You also support your team’s leadership’s decisions even if you do not agree with them. For me these traits are the most valuable traits, and it makes it a pleasure to work for you.

    Again, I will always value your advice, and I am looking very closely at your blog every new post.

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

Follow

Get every new post delivered to your Inbox.