In the web development industry, most companies build applications for their clients but deep down inside want to build the “next big application” for themselves. The client work pays the bills now and the internal project will rake in millions — when or if the team can get around to building it.
I hear about these ideas all the time and doing so usually reminds me of an episode of Ze Frank’s “the show” entitled “Brain Crack“:
Some people get addicted to that brain crack. And the longer they wait, the more they convince themselves of how perfectly that idea should be executed. And they imagine it on a beautiful platter with glitter and rose petals. And everyone’s clapping for them. But the bummer is most ideas kind of suck when you do them. And no matter how much you plan you still have to do something for the first time. And you are almost guaranteed the first time you do something it will blow. But somebody who does something bad three times still has three times the experience of that other person who is still dreaming of all the applause. When I get an idea, even a bad one, I try to get it out into the world as fast as possible, because I certainly don’t want to be addicted to brain crack.”
It is very common for the exciting, innovative idea to be put on the back burner repeatedly. We all do it. Somehow, you have to be able to say no to the money you could be making with client work today and spend time on your internal project which will pay off in the future.
Nothing is free. Time is money.
Spending time on your internal project will cost real money. Therefore, this expenditure must be viewed as an investment. Any work you turn down to make room in your schedule for development of the project would be considered the cost of this investment.
Do not abandon the process.
Another common pitfall when trying to build an internal project is management. People often think that you can build it on the side — poke at it for a few minutes here and there between other things. If the project is relatively simple, this may be possible. Generally not.
Once people free themselves of clients and work on their internal projects, they generally neglect to use a standard development process. Without a client breathing down their necks, developers often want to forget about deadlines, schedules, meetings, reviews, and setting up milestones.
A development team is a machine that thrives on structure. Making schedules, determining features, and having meetings are pivotal for a smooth development cycle. The normal structure needs to be maintained for internal projects. In order to be productive, you must treat yourself like you would a client because you are your own client. Schedule reviews. Set deadlines and milestones. Allocate time in your schedule as if it was paid client work.
Do not procrastinate. There is no time like the present.
Many people do the client work now and plan for the internal project later.
When? Later.
The part of Ze Frank’s “Brain Crack” video that most people should be able to relate to is the part where he says “You can tell yourself that you don’t have the time or resources to do them right.” Generally, this is just an excuse to procrastinate. You can make the time. You probably have the resources to at least get started. If you do not have the resources, you should be working on that right now.
You can do it. You are just uncomfortable with the sacrifices you will have to make to get your idea off the ground. The only way you can get it off the ground is by making those sacrifices and investing the time.
One Reply to “That Internal Project..”