New Here?
My name is Nir and I'm the founder of Nbd-Tech, this blog is about things that interest me, so you can find posts on productivity, running a software company and obscure technological topics.
If you like what you read you can
![[RSS]](../../../../Skins/NBD/Images/feed-icon-14x14.png)
subscribe to the blog feed or
![[Twitter]](../../../../Skins/NBD/Images/twitterrific.png)
follow me on twitter.
Yes, it’s ok to fail, it’s ok to make mistakes and it’s ok to throw away hard work because of your mistakes – it can even make you more productive.
We all learn from an early are that failure is bad and that avoiding failure is good – but that’s not always true, the hard truth is that avoiding failure isn’t productive work.
It’s easy to spend more time preventing failure than it would have taken to fail in the first place, when you are going to start a new project you can plan, analyze and research all aspects of the project, you can prepare detailed documents and make absolutely sure the project will succeed before starting – and then the project will either succeed because of your preparation or fail because of things behind your control (like a sudden world-wide recession).
On the other hand, you can cut the planning phase short and do only the most basic analysis in order to get the general idea about what the first phase of your project will look like and start working – this way you have a very good chance of failing because of mistakes you made – but you may just fail and move on the next project in less time than it would have taken you to complete the detailed plan.
In the end of the day you are much more likely to succeed by accomplishing more than by producing just one perfect project.
posted @ Monday, June 22, 2009 5:21 PM