A growing section of tips and tricks
30/70 Rule
There’s a rule called 30/70. It takes 30% of effort to deliver 70% finished product, and it takes remaining 70% of effort to deliver remaining 30% that will make it perfect.
When you’re investing in your own company on the other hand, developing a system that you know will be in use, or you’re certain you will get the people to use your product otherwise, it’s probably better to start with something solid, that won’t have to be rewritten. You can be strategic about it too, instead of contracting a ready solution, have something simple to start with and plan to develop and improve it over months or years.
Hey I had this great idea yesterday!
Is the kind of words developers don’t like to hear as a welcome..! Changes during the development process introduce mistakes. If the product is not even out there on the market, and already there’s changes, it speaks poorly of your planning skills. It also leaves you and the developer with a problem
Do we renegotiate the entire project to account for the changes? I just spent a week abusing my brain to write the code, just to erase it? Of course changes happen. But the less of them, the more productive and reliable the results.
Do you like this article? Leave me some “claps” or let me know what you think in comments! Thanks!
Table of contents:
- #1 Idea to Product: Introduction
- #2 Idea to Product: Development : Marketing strategy
- #3 Idea to Product: Resource Management
- #4 Idea to Product: Man for the job
- #5 Idea to Product: Tech Stack
- #6 Idea to Product: Tips and other worth mentioning