YouBundle

Keeping to the Core

As we push forth towards our September public release date of YouBundle; we become even more aware of the differences between “core feature” and “accessory”

Without getting into too much detail, a core feature could be defined as a balancing point on which success or failure of an application will be based.   Core features generally revolve around questions such as.

• What need is it purported to fill?
• Does it fulfill this need?
• Is the design pleasing and functional?
• Is the user interface smooth and acceptable - does the user always know where to click?

Just with these 4 questions we can define which Core Features need to be developed so that success may occur.   So many startups fail every day because in their development, they lose track of  what exactly is their core functionality and allocate limited time and resources to ‘auxiliary features’  that while very ‘neat’ do not do much to tip the balance between success and failure.

To sum up consciously - in this critical incubator stage in which the race is just to get the product developed and out - before even considering work on a new feature or dire decision - ask yourself.

Does this contribute towards the balance between success and failure?

If the answer is no, then put that feature at the bottom of the pile…