I had been managing IT budgets for over a decade when I started my EMBA. I thought I was doing it well — negotiating contracts, controlling spending, justifying investments with uptime data and incident counts. The finance module in the first term made me rethink everything.
The problem I didn't know I had
There's a distinction in financial management that seems obvious when you read it, but that very few IT professionals apply systematically: the difference between outputs and outcomes. An output is what you produce. An outcome is the impact that generates. I was always measuring outputs — never systematically calculating outcomes like how much the company saves in productive time for each extra hour of uptime.
Three concrete changes the EMBA introduced into how I manage IT
1. Risk-based budgeting, not historical cost
The most common model is: "last year we spent X, this year we're asking for X plus 5%." The right question is: what are the risks that technology must mitigate, and how much is it worth to mitigate them? When you budget from risk, you stop defending "we need to upgrade the server" and start saying "if this server fails without planned replacement, the estimated recovery cost is X."
2. TCO instead of acquisition price
A SaaS tool that costs €50 per month might seem cheap. But if it adds to a stack of 40 tools, requires training every time someone new arrives, and doesn't integrate with the rest — its real TCO can be ten times the license price.
3. Talking about investment, not spending
IT perceived as a cost center is always on the defensive. IT perceived as a growth lever is in a completely different conversation: "this investment allows us to do X, which generates Y for us, with an expected return in Z months." The EMBA gave me the financial framework. The previous 15 years gave me the real impact data.
I regularly share about this process on LinkedIn.