Posts Tagged ‘Soft skills’

13th

From a distance, one might expect the relationship between CFO and CIO to always be strong.  After all, aren’t there a number of similarities?  Numbers are at the core of both career fields, and both are driven by logic, rules, and standards.  Analysis and problem-solving skills are highly valued, and the quality of results is important.  Coming up through the ranks of Finance and IT typically required significant time spent alone at one’s desk, which may contribute to the attraction of these professions to many tending toward introversion. 

There is no doubt of the importance of the CFO-CIO relationship.  A Deloitte CFO Signals survey states that “45 percent of CFOs surveyed had IT as a direct report, and about 25 percent more as a dotted line report.”  A Gartner study conducted for the Financial Executives Research Foundation found that CFOs have increased their role in technology decision making and that the CIO most often reports to the CFO.

Yet despite the similarities and the importance, there are major issues in the CFO-CIO relationship.  CFOs have long been frustrated by an inability to get a “single version of the truth” from the data in many companies (The Customer-Activated Enterprise).  This frustration is exacerbated with the mandate to accelerate the company’s performance while increasing transparency.  In fact, Deloitte reports that only a little over half the CFOs in one survey felt that they have the information they need to effectively manage the business. Another study by Gartner and Financial Executives International cites that only 25% of CFOs surveyed were confident that their CIO and IT department had “the organizational and technical flexibility to respond to changing business priorities” or are “able to deliver against the enterprise/business unit strategy.”  The study also noted that only 18 % of the CFOs surveyed believe that their “IT service levels meet or exceed business expectations.” In addition, only 1 out of 4 CFOs saw their CIO as a key player in developing and implementing business strategy.

So what actions can the CIO take to improve his relationship with the CFO?  Here are some practical suggestions:

Read the rest of this entry »

5th

Perhaps no C-suite relationship today is more broken than the relationship between the CMO and CIO.  In the past, there has been little need to collaborate.  Far too often the CIO functioned as a technologist who was not recognized for having a complete view of the overall business.  He concentrated more on cost cutting and efficiency.  On the other hand, the CMO was about direct mail, magazine advertisements, and television spots.  He was aimed primarily toward branding, lead generation, and communication.cmo-cio-best-friends1  They were almost like two ships passing in the night.  Neither had a tremendous need to interact with the other.  Each was relegated to (or chose to remain in) his own realm.  In some ways, there have been a number of similarities between the two positions.  It was quite normal for neither of them to actually sit on the executive team.  Corporate strategies were often determined without their input.  Just as the CIO struggled to explain the return on infrastructure investments, the CMO had difficulty proving the value of investment in various marketing programs.  It should not be surprising to learn that both the CIO and CMO have struggled in developing relationships with the rest of the C-suite (Outside Looking In:  The CMO Struggles to get in sync with the C-suite and The DNA of the CIO).

But as a result of societal, business, and competitive changes driven primarily by big data, analytics, cloud, social, and mobile technologies, the pressure is on both the CMO and CIO to transform themselves, their departments, and their relationships with other executives in order to ensure the success of their companies.  They need to markedly increase the collaboration between them.  Both need to move from their functional silos into becoming recognized leaders within the broader business context.  This will take a concerted effort – and for the benefit of the company, it needs to be done quickly.

Here are some suggestions for the CIO to improve his relationship with the CMO:

Read the rest of this entry »

14th

Isn’t it ironic?

Companies look to IT to develop systems to improve the relationships with their customers.  Yet when it comes to building relationships with the rest of the business, IT often seems to be out in the cold.Buidling relationships 2

Developers build and enhance CRM systems so that companies can track every customer interaction.  The CRM system can know what products a customer has purchased and what offers he has been given.  It can be aware of how the customer prefers to interact and a bit about his decision-making process.  The system may know the customer’s marital status, number of children, and the college he attended.  It can detail every interaction the customer has had with the company.  And by coupling corporate information with external data, systems can be more predictive of customer behavior and buying patterns.

With all this, IT should be extremely knowledgeable about building relationships…right?  And of course, the CIO should be a master at it.

Read the rest of this entry »

17th

Have you ever noticed that many IT professionals seem to leap to a conclusion?jumping-frog

I once attended a training course on how to elicit business requirements using a facilitated discovery session to gather requirements.  By bringing all the stakeholders together to define the project, the shared information and decision-making process was to improve buy-in, reduce risk of scope creep, and increase the speed of delivery.

As the instructor briefed us on the method, she recommended that IT people not be included in the discovery sessions.  Having come up through the ranks of IT, I questioned the reasoning behind such a statement and asked the instructor at the first break.  She cited an example of a recent discovery session her company had facilitated to gather requirements for a large project at a client company.  In attendance at the discovery session were a number of stakeholders from throughout the company – including two IT developers who had been with the company for quite a while.  After the facilitator had laid out the ground rules for the discovery session, she began eliciting business requirements from the attendees.  As requirements were suggested, they were to be discussed and refined as necessary.  However, it happened that as soon as the first business requirement was mentioned, one of the developers said, “We can’t do that.” When the next requirement came up, the other developer remarked, “We’ve tried that before, and it doesn’t work.”  Read the rest of this entry »

Subscribe

Name
Email Address*
 
Newsletter Powered By : XYZScripts.com