Meet Your New Boss
- 06 August, 2004 10:55
- Comments
Reporting to the CFO rather than the CEO is different. And once you swallow your pride, it can be better - for you, for your enterprise.
You've been demoted. The CEO called you into his office, sat you down and told you that after a great deal of careful thought and consideration, he's decided that you will now report to the CFO. Everyone agrees this makes the most sense. IT doesn't need to report to the CEO, so IT shouldn't.
Don't worry, he says, IT is still perceived as a strategic asset. But, your CEO insists, IT is best overseen now by the executive directly accountable for assuring that the firm gets maximum feasible returns for its capital and operational investments. That's the CFO.
Yes, the CEO fully understands your disappointment. But he also wants you to know he completely supports your work and wants you to succeed. He thinks IT will have a greater impact on the firm by reporting to finance. What's more, he adds, the CFO is world-class. He stands a better-than-even chance of ultimately succeeding the CEO or being headhunted to CEO at another firm. This new move could be great for you. Really.
So step up and be a team player, damn it. Your CEO is counting on you to sell this reorg to your people. This move is great for them too. Honest.
Who knows? Maybe the CEO is right. However, it sure doesn't feel that way. Let's be honest: There's no way this doesn't send a signal to the world that IT now matters less. Your vendors, for example, will know instantly. Perhaps your most important customers and clients will too. Certainly your colleagues - the C-level folks who used to be your peers - will know it. How can this not dramatically reduce your professional effectiveness?
The answer to that is simple: It depends on what you mean by "professional effectiveness". When the CEO says he no longer wants or needs you as a direct report, that means one of two things: that things are going so well that he really doesn't need to have direct interaction with you about current and future initiatives; or that, frankly, your interactions really aren't worth his time and attention relative to the other issues on his plate. Therefore, you should be interacting with someone else.
Care to guess which of the two is likelier?
While being demoted is undeniably a blow to one's pride, I strongly believe it can — if managed with shrewdness and guts — reinvigorate IT and reposition the CIO as a paragon of effectiveness within the enterprise. Post-demotion success, however, is predicated on a single mission-critical imperative: Are you willing to go the extra mile to help your new boss succeed?
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.
- Bookmark this page
- Share this article
- Got more on this story? Email CIO
- Follow CIO on twitter
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Top seven firewall capabilities for effective application control
-
Pfizer's Future Depends on IT Transformation
-
Face Time - Interview with John Brennan and Robert DiStefano
-
SOA Best Practices and Design Patterns
By learning from the experiences of those organisations that have been through the process and looking at the standard best practices of large‐scale technology implementations, success can come earlier and more dramatically. Read more now. -
Protecting Against the Leading Causes of Data Breach
This whitepaper was written for the organisation that wants to focus on prevention of data loss and doesn’t have millions to spend, but needs affordable solutions that can be implemented today to protect millions of sensitive records and dollars worth of intellectual property. This whitepaper addresses: - What organisations can do to prevent the four leading causes of data breaches - Why dedicated (pure-play) DLP solutions may not protect you from all four leading causes of data breaches - How to get prevent sensitive data leaving your organisation -
Three simple steps to better patch security
It’s estimated that 90% of successful attacks against software vulnerabilities could be prevented with an existing patch or configuration setting. Yet patching is a persistent challenge for IT managers. With the glut of patches released each year, how do you know which ones are truly critical security patches and which ones aren’t? And how can you identify which computers are actually missing the patches they need? This paper details a simple approach to patching that gives you better visibility into and control over patch assessment and compliance.
-
Adobe Creative Suite 4 Design Premium Digital Classroom
-
Introducing AutoCAD 2009 and AutoCAD LT 2009
-
Mastering Microsoft Project 2002
-
HTML
-
Beginning Sharepoint 2007 Administration
-
PC Magazine Printing Great Digital Photos
-
Data Mining Cookbook CD
-
Introduction to Electronic Business Technologies
-
Professional Wcf Programming








Comments
Post new comment