Pod Insights The Real Estate Espresso Podcast When Idealism Confronts Reality About this episode On today’s show we are talking about whether it’s better to be better, or better to be simple. Today’s episode is an embarrassing story that I’m going to share with you so that you can learn from our mistake. One of the consequences of working with really smart people is that you can often get caught up in the elegance of an ideal solution. There is something to be said for consistency. If you want to reduce the possibility of errors, then it makes sense to eliminate or at least reduce the number of choices. Each decision represents an opportunity for error, or for misunderstanding. Today's story was an attempt at driving consistency that had unintended consequences. -------------**Real Estate Espresso Podcast:** Spotify: [The Real Estate Espresso Podcast](https://open.spotify.com/show/3GvtwRmTq4r3es8cbw8jW0?si=c75ea506a6694ef1) iTunes: [The Real Estate Espresso Podcast](https://podcasts.apple.com/ca/podcast/the-real-estate-espresso-podcast/id1340482613) Website: [www.victorjm.com](http://www.victorjm.com) LinkedIn: [Victor Menasce](http://www.linkedin.com/in/vmenasce) YouTube: [The Real Estate Espresso Podcast](http://www.youtube.com/@victorjmenasce6734) Facebook: [www.facebook.com/realestateespresso](http://www.facebook.com/realestateespresso) Email: [podcast@victorjm.com](mailto:podcast@victorjm.com) **Y Street Capital:** Website: [www.ystreetcapital.com](http://www.ystreetcapital.com) Facebook: [www.facebook.com/YStreetCapital](https://www.facebook.com/YStreetCapital) Instagram: [@ystreetcapital](http://www.instagram.com/ystreetcapital)
Transcript 0:02 Speaker 00 Welcome to the Real Estate Espresso Podcast, your morning shot of what's new in the world of real estate investing. I'm your host, Victor Manash. On today's show, we're talking about whether it's better to be better or better to be simple. Today's episode is an embarrassing story that I'm going to share with you so that you can learn from our mistake. One of the consequences of working with really smart people is you can often get caught up in the elegance of an ideal solution. There's something to be said for consistency. If you want to reduce the possibility of errors, it makes sense to eliminate or at least reduce the number of choices. Each decision represents an opportunity for error or for misunderstanding. For example, if you're designing a building and all the windows are different, that's an opportunity for error. You want to keep them consistent
0:45 Speaker 00 so that the installation is going to be seamless. If you make certain decisions consistent between projects, then it stands to reason the process from one project to the next would automatically carry over, fewer chances for error. So I'm going to share with you is an embarrassing story from within our organization. This was an attempt at simplification that had unintended consequences. We thought it would be a genius idea to bring consistency to our construction accounting system by developing a chart of accounts that would be consistent between projects. Chart of accounts is a naming convention that breaks down the expenses in a project into a set of categories. For example, concrete will go into one category, landscaping into another, electrical, would have a series of accounts
1:27 Speaker 00 associated with it and so on. It was literally hundreds of these categories in a hierarchy. The goal was that anyone within the company who's trained in our accounting system could move seamlessly from one project to another with zero learning curve. Anyone looking at the project would be immediately able to understand the allocation of costs. It sounds so elegant, so consistent. When we came up with this genius idea, we were so excited. Well, it really didn't turn out quite as elegantly as we'd hoped. This fancy new accounting system turned out to be a major source of confusion and misunderstanding. You see, the general contractor who produces the invoice for each phase of the construction has their own categories of how the invoice is broken down. That list of categories does not match our super elegant list of categories.
2:10 Speaker 00 It's not just that the account numbers don't match, the differences run much deeper. In order to map the contractor's categories into our account numbers, we would have to create a detailed breakdown of the contractor's invoice in order to map the contents of the contractor's invoice into our super awesome categories. You might already be seeing the problem, but it gets worse. After that first level of translation, the invoice then needs to be translated again into the budget categories that the cost consultant uses. The cost consultant is the one who certifies the construction draw payments for the lender. If the cost consultant has questions about the draw request, the supporting documentation to justify each line item in the cost consultant's budget actually comes from the contractor and subcontractor invoices. But those documents don't line up perfectly with our budget,
2:54 Speaker 00 and they certainly don't line up perfectly with the cost consultant's budget. It's gone through two levels of translation, not one. If the question from the cost consultant goes back to the general contractor, it's almost impossible for the contractor to understand the question, let alone answer it, because it's not presented in a form that the contractor recognizes. It was a well-intentioned drive for consistency. Our team inadvertently created needless complexity. Now, I'm not sharing this story to publicly embarrass anyone on our team. We were all involved in the decision, myself included, to implement a system that seemed so elegant at the time. After spending countless hours debugging the budget spreadsheets, a third of the way into the project, we realized that our super awesome elegant accounting system
3:35 Speaker 00 was indeed at the root of much confusion and misinterpretation of the monthly budget reconciliation. Okay, so now we have a project that is struggling to balance its books every single month. The complexity of our system is multiplying the effort each and every month. It would be so much simpler if we eliminated our fancy accounting categories and simply reverted to the general contractor's categories with a single mapping to the cost consultant's budget. But if we made that change in the middle of the project, it would be impossible to reconcile the books because we would have to go back to the very beginning of the project and rewrite history for all of the money that had been spent on the project to this point. And that seems like an almost impossible task. Going through the monthly pain of mapping the invoices twice on a going-forward basis
4:16 Speaker 00 seems unattractive as well. Each mistake costs 10x the effort to correct compared with a simple success case. Well, it turns out we may have a solution. That's not the point. We won't know if it works until we try it and gain some experience with it. And we've all heard the mantra that complexity is the enemy when it comes to the management of projects. And we are living the consequences of a decision that inadvertently injected huge complexity in an effort to bring elegance and consistency to the wrong thing. So the question for you is to examine your own business. What are the things that you're doing in your daily life that result in complexity, where you get little, if any, benefit from that ultra sophisticated, super awesome elegance? As you think about that, have an awesome rest of your day. Go make some great things happen. And we'll talk to you again tomorrow.
Previous AMA - When Building Costs Are High Next Wisdom From The 80's with Tim Edwards Page updated November 15, 2026 · transcript and summary are machine-generated