Be a scope minimalist

Tips on how to apply this value:

"I prioritize effectiveness and impact over perfection and precision."

vs.

"I make sure I achieve perfection in my work."

"I prefer to make a quick, decent decision instead of pursuing perfection."

vs.

"I hold myself to making perfect or near-perfect decisions no matter the cost."

• It is okay to ask for help, it is okay to say a task/project is lagging behind and seek for assistance from peers.
• Be aware of your limitations (it is okay NOT being "everything and everywhere" at the same time), don't overpromise, thus underdeliver.
• Don't over-explain! Keep communication short, sweet, and to the point!

A journey of a thousand miles begins with a single step - by Prasad

Every feature that we are building in the Remo with the same concept, I realized how important to make REMO is more productive in the Market by just making it minimum viable product in the beginning.

Build for the Minimum is a basic, When Minimum Viable Product is created with intent to enable faster time to market, attract early adopters and achieve product-market fit from early on. Once the Minimum Viable Product is launched, initial feedback is awaited — based on which — we reiterate to fix the bugs and introduce new features that those early adopters suggest.

One of the examples is Floor plans; we start virtual meetings with just 4 basic floor plans, yes just 4 basic plans, now if you look at we have 50 basic floor plans and 1000s of custom floor plans. Now a days I the product team (Carpenco, Bryan all comes with new features that we are building minimum) thanks everyone who is part of bring these concepts more and more bright and more value to the REMO.

Maximum Errors Allowed: