tldr; yes, "starting with finance" is a good way to transform IT.
tldr; yes, "starting with finance" is a good way to transform IT.
My experience is that IT and finance people simply have a very difficult time communicating with each other properly. They are different type of people and speak different languages.
A CFO will be very open to invest if he’s convinced that there is a clear return on invest. Many IT folks don’t want to bothered thinking from that perspective.
If you want to have an easy life learn how to speak with your board, especially the CFO.
PS: that’s one of the core reasons some IT guys get management consultants to do the translation job.
Understanding the language and process of basic bookkeeping and simple accounting has given me me immense traction with finance people. When I demonstrate even a rudimentary understanding of the metrics and reports finance uses (understanding what financial statements communicate, tax ramifications of CapEx vs OpEx, cost of money, etc) the trust level and willingness to listen goes up tremendously. Stand-offish and distant relationships became more concrete and productive when finance people realize I'm not spouting techno-bullshit for bullshit's (or techno's) sake.
Anybody with serious IT management aspirations in the private sector really should have a reasonable amount of business knowledge. An IT operation, both the in-house and contracted services components, should be considered an internal business unit. It should be evaluated on the expenses it charges-back to the revenue-generating business units, and on the gains in revenue it creates by driving efficiency. Knowing the metrics that finance will use to evaluate an IT operation allows you to make a case for improving those metrics.
At a bank or in retail sure, it may make sense for IT to report to the CFO. At a healthcare proivder or insurance company, ok sure that makes sense. In that case, IT is really just another part of the plumbing because the core product isn't really technology anyway. The blog post is moot because the technology itself will have a minimal impact on the value added by the company, which is elsewhere, and nobody in IT is likely to have a seat at the product discussion table anyway.
But at a technology company? One where the core value add is software products or services or hardware? I don't believe it. I simply don't think that any company that places management of technology based core value added products under the CFO can succeed. If there happens to be some company out there that has this structure, I'd treat them as having a big target on their back - they're ripe for disruption by a company where technology leads.
Repeat after me: software development *is not* IT.
IT is the department that hands out laptops and buys office licenses from MS.
Software Engineering is a product development group.
They're two entirely different functions.
IT can make sense to have under the CFO, but product development almost never does.
Just get a CTO.
But seriously, it's always hilarious to listen to non-tech companies pitch how they can pivot to becoming a "tech company just like Google" while following none of the practices in SV. Developers still working for "IT", cost cutting and penny pinching. No free food of course...
The only distinction I see is that software developers want to believe they are somehow more special than everybody else.
The companies that recognize this are the successful ones, and the ones who don't fail eventually. Even John Deere sees the light here. Why do you think they have all of the DRM BS? The value comes from the software.
IT is also not nearly as expensive as other types of businesses that require huge capital investment, like farming equipment, factory assembly lines, biotech reactors, etc.
Otherwise you lose a lot of your economies of scale because each business unit is trying to figure out the best way to do things. Or you end up with shadow IT all over the place because the BUs come up with cheaper but unsanctioned/unsupported ways to do things.
You also need a way to objectively evaluate how IT is performing. If the business units are going to third parties because IT is unresponsive or overly "expensive" then the exec team needs a way to see that. When IT is responsible for the IT budget then they have incentive to minimize costs and it's easy to do budget reviews. When the business units have to pay that budget then IT acts as a monopoly with little incentive to improve service or reduce prices and it's much harder to find the shadow IT that's being implemented to get around bad internal IT.
There's no one perfect answer.
It’s still better than the typical approach, where everyone is just angry at IT all the time “because they are such a drag with so many expenses”. Outside of the extremely dysfunctional cases, charging everything back to business units is at least the more honest approach.
I had this fight with my last CEO. She put anything tech-related under my budget. Worked with accounting to show what the budget would look like if expenses were correctly attributed, and suddenly I wasn't spending so much money anymore.
Reason she didn't want to change it? So they didn't have to explain why expenses changed so much quarter-to-quarter during the next board meeting.
Seems like a win-win. Now she knows the reality of the enterprise and is okay with the expenses but she feels that investors would be bothered by it, so better not change anything in order to avoid having to answer their questions
10 years later, my ex-CFO still thanks me for what I did, and wish I was still with the company.
Wait there are companies that don't do that?
It seems to be mostly the really large companies who have enough of an internal economy where they actually get to the point of internal chargebacks.
In my experience as an IT person, IT people are almost always full of shit when they talk money or roi. Usually when you think the tech team has their money story together, it’s because they are growing and you can hide mistakes in growth.
Once growth slows, you realize there’s some dude making $250k and nobody knows what he does. Or that you’re paying $1M/month for AWS charges that you cannot track back to revenue. Or that you’re running a data center that full of end of life equipment that isn’t used or brand new equipment that was never commissioned. So the CEO brings in the bean counters to rein in the nonsense.
Great insight, and mirrors my own experience a lot.
> you realize there’s some dude making $250k and nobody knows what he does
I've been through this situation several times as a CTO. CEO's can come off as Jekyll and Hyde, one day shouting at you to hire, hire, hire and then giving you flak about those same hires when things don't go as planned.
ROI and it's cousin TCO should be useful terms, but it's been so twisted and bastardised that it's basically a useless metric. Everyone has some bullshit story that shows that if you give them millions now they'll deliver a lower ROI or TCO.
But if you’re not growing, the obvious way to make more money is to spend less. Many companies get away with this for decades.
I joined a firm recovering from this very problem. The previous IT director spent wildly and justified every purchase to finance who trusted their judgement. When the bills finally came due it almost put the firm under and the IT director left.
...but without IT, everything else stops, and usually people think about that only when IT departments get so "skinny", that things fail... and then they get blamed for that too.