Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-settings.php on line 468

Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-settings.php on line 483

Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-settings.php on line 490

Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-settings.php on line 526

Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-includes/cache.php on line 103

Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/spinbits/public_html/wp-includes/theme.php on line 618

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/spinbits/public_html/wp-settings.php:468) in /home/spinbits/public_html/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 114

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/spinbits/public_html/wp-settings.php:468) in /home/spinbits/public_html/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 114
The Pleasure of Killing Features!
posts | comments
24Jul

The Pleasure of Killing Features!

1 comment so far

Nick Brandbury has touched on an issue, which is particulary relevant to the whole idea behind Zero2Beta, which is killing features.
Picture 3.png

Considering that we’re facing the challenge of designing, developing and deploying a product in 2 days, we decided to take killing features as a sport, and went on with removing stuff and deleting features from an already simple idea, even to the extent where we had to remove the core idea that started the whole project, because we couldn’t find a suitable way to convey it to the user within the time limit.

It’s so easy to add “one more thing” and that “nice little touch” but it doesn’t matter at the end of the day,and it ends up cluttering the product and pushing back the launch for a few days/weeks/months.

What’s the downside to killing features? Adding them later! And correctly so.

It won’t be the end of the world, if we discover later that users are asking for a certain feature and just go ahead and add it. On the contrary you will be adding features according to real-world scenarios, actual feedback and within the right usage context.

It’s definitely better than imagining what people may want/not-want and just keep going at it without any reality check.

Killing features is such a pleasure, it’s definitely going to remain our favorite sport even after the end of Zero2Beta App1 and going back to working on our own projects.

You might wanna give it a try.

Categories: App1

Thursday, July 24th, 2008 at 8:37 am and is filed under App1. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

One Response to “The Pleasure of Killing Features!”

  1. Posted by kill 3rd September, 2009 at 2:32 pm

    Trying to clear, Online home based?(?start/run? and type, could be We.Exhaustion and loss, affected by rough.Home In fact kill, short game also and magazines .Those who already, to taxation and.,

Leave a reply