150 karma · joined April 21, 2020
Are people finding that managers have become more efficient in remote settings?
VBA is terrible, but it is the only programming-like option for most office workers outside of IT/Engineering
I agree with you that it is unlikely accountants will learn SQL/Python/R. They are tied to their ERP and Excel. My hope is the FP&A analysts will develop the SQL/Python/R skills to enable the better/faster development of complex models to forecast.
>The product that would've solved the problem (and then some) was IBM's TM1
I have not used TM1, but have heard many good things about it. Today I hear more people discuss Workday's Adaptive Planning than any other product in that class. Unfortunately most are still creating their primary forecast in a spreadsheet, then loading it into the TM1 or Adaptive which then has additional rules to build out the forecast.
I agree that using these types of products increases transparency and speed.
Like MeinBlutIsBlau, I thought this was going to be Microsoft finally ditching VBA for Python as its macro language.
As a CFO, I want to earn a seat at the table where decisions are made. Finance frequently has access to a significant amount of data about the company and if the Finance team does it job well, they turn that into useful information. Bringing key information to the executive team (and entire company at times) to facilitate the decision-making process is one part of how to earn that seat.
Finance does not have all of the information. The Technology (IT/Engineering/Product Dev/etc) team will have a unique perspective. Marketing will have a unique perspective. The People team will have a unique perspective. I think a company with a strong culture figures out how to embrace all of these perspectives and collaborates to develop world class products and services.
Finance does get tasked with evaluating the ROI question - does the proposed investment opportunity create more financial benefit (can be expansively evaluated) than the investment. That should be to ensure a consistent process and is frequently because Finance is viewed as independent from the group requesting the investment.
A good CFO, heck an average CFO, wants to support good investments. It is always more exciting to say 'yes' than 'no' and importantly the company grows by making smart investments. I have never seen a compensation structure for a CFO that provides for increased compensation for always saying 'no.'
Over the years I have noticed a few conventions that make spreadsheets easier to read from a model perspective. - Inputs should have their own tab and ideally a name. Should also be a color-coded font (blue is popular). - A worksheet should work left to right, top to bottom. I am always frustrated when I try to work through someone else's spreadsheet and the formulas just drift across a tab rather than working in a pattern toward a conclusion/summary - Pretty print sections should be separate from the actual engine. Do the calculations in a manner that is easy to understand. Create an output tab to create the pretty report. - Flag with a bright background color when a formula changes (yellow is popular). This frequently happens when your boss asks you to create a scenario where you override a formula with a constant. I cannot tell you how many hours of my life have been lost tracking down an overridden formula.
These types of conventions make spreadsheets easier to inherit from someone else. They do not change the fact that there can be a lot of calculations happening through a multi-tab that you simply cannot see the bigger picture.
My personal hope is financial analysts get more tech savvy over time. SQL should be a year one skill with Python/R soon after. These should complement spreadsheets which would still have an important role in ad hoc analyses. Combine this increased tech savvy with an understanding of a visualization tool such as Tableau/Power BI and I think financial analysts could be significantly more productive than they are today.
There would also be far fewer spreadsheets lying around on the network drives. It is amazing how many of those spreadsheets are simply the same model with the next month's data. Better use of databases would allow one spreadsheet with a database to store the changing inputs.
With respect to FP&A, I have seen several firms that simply embed them within a product line or business unit. They need to submit forecasts to a central group, but their primary mission is to support the product or business line.
As I mention above, opex vs capex is usually a compensation issue.
The opex / capex argument is about compensation. Opex reduces income immediately while capex gets spread out over the projected life of the asset (software, power plant, computer, etc). By shifting items from opex to capex, a company temporarily increases its net income. Increasing net income often leads to higher bonuses.
This is what drives the silly behavior. To make matters worse, once a company goes down this path, it cannot get off as it is usually evaluated on a year-over-year basis.
As for accountability, CFOs of public companies can be found criminally guilty (i.e. go to jail) if they not only commit accounting fraud, but simply do not establish a robust enough control framework to ensure the financial statements are correct.
CFOs are always accountable ultimately to the CEO and sometimes to the Board of Directors. If you think the CEO was unaware the company was spending "two or three dollars in capex every year than a dollar of opex," your either mistaken or you had a clueless CEO.
Cash flow is the actual movement of money - paying payroll, paying vendors, receiving cash from clients (not just sending out the invoice). Lack of cash flow is what makes companies go bankrupt.
Allocations are methods to attribute income and/or expenses to groups. It may be something simply such as dividing up an enterprise software license for email by the number of employees and allocating that expense to their department. It can be more difficult / squishy such as how to attribute brand marketing spend to various product lines. Generally, companies use allocations because they are trying to understand the profitability of something (a product, geography, client, etc).
Your example of the million dollar spend is a good one. Very easy to see where the cash flow went (Developers, Sales people, rent, etc) but the important question to assist on future investment decisions is how much should be allocated to Project X vs Y vs Z. One would also need to understand how much cash was generated by Project X, Y, and Z so they can determine the ROI (Return On Investment) for each project. Knowing the ROI is important in making future investment decisions.
IMHO, the best thing you can do is work with someone in your FP&A (Financial Planning & Analysis) group discuss your investment idea and why you think it is a good idea. If they are a decent analyst, they will help build a model to describe financially your investment opportunity. This is what they live for.
This article is disappointing in that it gives the impression that one department makes or breaks a company. To be clear, there are poorly run Finance organizations in the world and they can make the culture at a company less than fun. There are also poorly run IT organizations (to include product development) that can ruin a company culture. Even ones run by a CTO that reports to the CEO.
I have also never seen a company where the CFO does not ultimately report to the CEO. I have seen companies where the CFO reports to a Chief Administrative Officer (CAO) who reports to the CEO. I completely agree that the CEO ultimately sets the vision of the company and hires the executive team to deliver on it. That being said, a CEO is not Superman/Superwoman. They need a team surrounding them to deliver what you expect.
What the article could have emphasized is how software engineers can work with the Finance team to better describe investment opportunities like hiring production engineers to increase the productivity of application engineers. Yes, investment opportunities ultimately need to generate more cash returns than the investment. This may require serious thought around the benefits from increased software quality, faster cycle times, increased cybersecurity etc. Importantly the analyses do not have to be decimal level precise. But, if you cannot describe how your investment opportunity ultimately creates more cash flow than the investment required, your opportunity will likely not be funded.
Nothing exciting. Send them feedback on how OCW made a difference in your life and spread the word.
Deloitte study: https://www2.deloitte.com/content/dam/Deloitte/tr/Documents/...
Having the government provide the service introduces politics to the operation of running a business. Where should post offices be located, how often should mail be delivered, what products should we offer, should prices vary according to cost to delivery, etc. These issues make the USPS what it is today - a bureaucratic behemoth that is still delivering Christmas cards from 2020.