Choosing the data model for a project requires an extended conversation about the project itself. Its plans, goals and dreams. What does the project hope to be? It should not be a “choose your database and then fit your model”. You don’t buy a Ferrari and then see how much lumber you can fit on top: you choose the car for the purpose that you need it for.
As a Founder/CEO of a small (albeit growing) tech company one of my biggest issues — to which I’ve not been able to find a solution still — is time management. I end up taking up a lot of work (some of which I probably shouldn’t) and between financials, client management, product development, roadmap structuring, hiring, and the dozen other tasks I assign myself to, I barely have time to do any of it timely and effectively — let alone spare some time to myself.