User driven development

Been thinking about using this as a guiding principle in some of my personal projects.

Don’t develop a feature, however trivial or easy to build, till a user asks for it.

That way we know someone wants it enough to ask for it. And, when we deliver, the user will be satisfied/delighted enough to spread a good word about the product.

This may be more useful for small teams, early in the product lifecycle.

The alternative, anticipating user needs and developing ahead of time may sometimes lead to wasted effort on ghost town features.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.