Project
New Revenue or Cost Savings: Make Sure You Dig Deep to Find True Values for
Each
A few
years ago, I worked in the strategic planning department for a large publishing
organization. The group would assign a
project manager to a proposed initiative from senior management and then others
in department would be team members to contribute their expertise. I don’t think I ever worked with a group of
such talented individuals during my entire career.
One
individual originally worked for one of the big auditing organizations and she
was the ‘go to’ person for financial analysis.
Over her career, she developed her ability to focus intently on true
incremental new revenue and incremental cost savings. On the revenue side, many individuals would
optimistically state an initiative would bring in six figure incremental
revenue. She would begin to ask a series
of programmed questions which she had in her head. By the end of the session, much of the supposed
incremental new revenue was either built on a very flimsy set of assumptions or
was ‘switch revenue’ from another area to the new initiative.
On the
cost side, a significant amount of the cost structure was fixed. This was good for new initiatives which would
bring in true incremental revenue with no cost increases. But some initiatives proposed significant cost
savings. Again she would ask a different
series of programmed questions. And again
at the end of the session, many of the supposed costs savings were based on
flimsy assumptions or realistically not going to happen given the cost
structure.
Here are
two takeaways. First always involve
members of those in your financial organization on your projects. More than once, I’ve heard project leaders
say those from finance are too negative.
Get over that and bring them in from the beginning. Second make sure at least one of your
financial representatives knows the true revenue and cost drivers of your
business like the individual I mentioned above knew those in the publishing
business. This will save you and the
team from embarrassment during and after the project.
No comments:
Post a Comment