Many thanks for continuing to follow me on the journey of putting this book together.
Over the last week or two, I've been thinking about what makes this book different from others out there. And I think it's this: a focus on teaching modelling as an integrated system. Model structure and workflows are both parts of that system. I don't see other writers on modelling talking about what they do as parts of a system. And I think that makes all the difference.
I've therefore rewritten the whole of the Introduction in Part 1 of the book with this in mind. I've lost all the stuff on "how to be a great modeller". In the end, I decided that was all a bit pompous.
I'd dearly love to hear your feedback on how this lands with you. Is this is a useful concept/approach?
Here are links to the new chapter structure in Part 1. Each section is very short.
- How I hacked my sock drawer
- This is not a book about Excel
- Why your financial modelling system matters
- What makes a good financial modelling system?
- Simple does not mean easy
- Systems don't impede creativity
- Financial modelling standards
- Changing working habits is difficult
- Self-discipline is just as important as intelligence
- Financial modelling is part of a bigger process
- All models are wrong. Some are useful.
I also wrote a couple of additional chapters on working capital after a useful teaching session on Full Stack Modeller.
- Accounts receivable - what happens if the invoice payment lag is longer than the modelling time period?
- Accounts receivable - what happens if different customers or different products have different payment lags?
I'd love to hear your views about whether this "modelling as a system" focus is helpful. Part of me wonders whether it's only interesting to me. But then that's true of the whole book!
Many thanks again, your comments and support are invaluable. Please keep them coming.
Sign in or become a Financial Modelling Handbook member to join the conversation.
Just enter your email below to get a log in link.