Organizational Charts Should be Written in Pencil: TBM Part 10

Periodic reviews of the IT org structure can be an effective way to align IT staff with business initiatives. I find it is best to construct the desired org structure without slotting the existing staff. Then begin to fill in the chart with individual names based on their unique skills.

A photo of two pencils, one red, one blue juxtaposed against diagonally split red and blue background
Photo by Alice Yamamura on Unsplash

Executing a mission, such as transforming an IT organization, requires an alignment in talent, aspirations, and context. It's the people in the organization that will determine if this journey is successful or not. While leadership plays a critical role, and may even be the catalyst for change, it's the vast majority of the organization, the boots on the ground, that truly matter.

My friend Peter High, an author, columnist, and advisor to global CIOs, identifies five principals of successful, industry leading IT strategies in his book World Class IT: Why Businesses Succeed When IT Triumphs. Peter's five principals are:

  1. People
  2. Infrastructure
  3. Project and Portfolio Management
  4. IT & Business Partnerships
  5. External Partnerships

In Peter's model, each principal builds on the one before it, so it is no surprise to me that he begins with People. Having the right engaged, knowledgeable, and willing talent is the most important aspect of formulating an IT strategy.

"Without the right people doing the right jobs at the right time, it will be nearly impossible to achieve excellent performance." - Peter High

I think Peter's statement is powerful because he includes the element of time, suggesting that the org structure should be fluid based on the desired business outcomes. Periodic reviews of the IT org structure can be an effective way to ensure you are aligning IT staff and leadership with business initiatives. While difficult in practice, I find it is best to construct the desired org structure without slotting the existing staff.  And only then begin to fill in the chart with individual names based on their unique skills, talents, and experiences. This method helps to identify critical gaps where desired business outcomes may require a skill set you are not properly staffed to fulfill. You can then decide the best approach to closing these gaps by training, hiring, or reassigning personnel.

Managing through change is a skill and an experience that should be highly valued. Think about how often you hear the word "transformation" when talking with IT leaders. It seems every company is transforming in some way or another. Transformation requires doing things differently. Said another way, without change, you cannot successfully transform. Leaders who are willing to morph their roles and coach and guide their staff through these changes are critical.

Leaders should clearly communicate any organizational change and the context for the change to the entire staff. This is an important step in building a culture among all employees who may more readily accept change, applying their brain power and skills to moving forward. The absence of proper communication leaves a void that I have seen filled with distrust, conspiracy theories, and generally distracts the staff from the mission at hand.

Others are showing support for a recurring schedule of organizational changes. Lee Congdon, CIO of Red Hat, penned a great article just today entitled Why CIOs should change their minds (and their organizations) once a year. Lee makes the case that annual org changes provide dual motivations, aligning to current business goals and providing his staff with a sense of purpose.

"When you commit to adjusting your focus on a regular basis, not only can you better align with the right opportunities for business growth, you can also better develop skills and capabilities within your IT organization." - Lee Congdon

Paul Chapman, CIO of Box, wrote an article earlier this year on LinkedIn entitled CIOs: Lead People, Not Technology. He closes the article by noting the following:

"Ultimately, it’s not enough to think about where technology is going. You have to think about roles and the entire IT team structure—because you’re not leading technology, you’re leading people." - Paul Chapman

I think he's spot on.