#CFOMustRead: Technical Debt, Status Quo Activists, and Megatrends

Five stories from this week that CFOs won't want to miss.

Print

It was difficult to pick one story this week, so we picked five. (See below.)

Just as a reminder, you can join our CFO readers who participate in #CFOMustRead by sending us your most interesting reads of the week from around the web. Send us the link as well as a brief take on why you think other CFOs will find the story valuable. We publish the best submissions weekly.

You can send us a #CFOMustRead in two ways:

  1. Send a nomination to us via Twitter, by inserting the hashtag #CFOMustRead into a tweet.
  2. Nominate a story in the comments section of this post.

CFO‘s editors will be watching for your recommendations daily. Each week we publish an article that highlights the best recommendations and the readers that submitted them.

If you’d like to follow along to see what stories are recommended, you can track the comments on this page or follow the #CFOMustRead Twitter stream using Twitter Search or TweetDeck.

This week’s must reads all came from Mark P. Borman, who is a CFO, an audit chair, and a NACD board leadership fellow, among other roles. Here’s his profile on LinkedIn.

One of four favorite nominations of Borman’s was a Deloitte piece on “How to Calculate Technical Debt.”

As the writer explains, “technical debt” refers to the accumulated costs and long-term consequences of using poor coding techniques, making quality/time trade-offs, delaying routine maintenance, and employing other suboptimal IT practices in the enterprise.

Given the procrastination of some firms in upgrading their finance department’s systems, we think it is a timely piece. And it actually dovetails nicely with John Parkinson’s piece this week on CFO, “Finance: Processing Like It’s 1995.”

Here are the four other stories that you may want to take a look at this weekend:

 

 

 

Keep the nominations coming.

Leave a Reply

Your email address will not be published. Required fields are marked *