Posts Tagged ‘software development’

Saying “No” To Customers Can Save Your Company

Tuesday, February 15th, 2011

Many entrepreneurs and small business owners argue that you should always listen to your customers. In fact, the popular lean startup principles advocate listening to your customers and iterating early and often.

But listening to customers – and responding to your customers’ suggestions by implementing all or many of them – are not the same thing. As Steve Jobs wisely said:

Innovation is not about saying yes to everything. It’s about saying NO to all but the most crucial features.

Unfortunately, many businesses fail because their leaders lose focus while trying to incorporate all (or many) of their customers’ suggestions. It’s easy to fall prey to the “yes’ mentality. Saying yes makes us happy. We believe that saying yes is more likely to cause the customer to buy our product or service. Saying yes makes our customers happy.

Ultimately, don’t we want happy customers?

Of course we do. But making customers temporarily happy while destroying your company is, in my opinion, an unacceptable cost. No company has unlimited resources and when you say yes to customers  – you’re committing – and often, over-committing – those resources.

If you’re creating software, you end up with bloated software and a terrible user experience. If you’re creating products, you end up with a complex and expensive product.

Henry Ford famously said:

If I had asked people what they wanted, they would have said a faster horse.

Many people reading Henry Ford’s quote conclude that innovation is driven by your own ideas – and not by ideas suggested by your customers. After all, how could people who use horses and buggies come up with the idea for a horseless “car”?

The reality is that listening and innovation go hand in hand. Steve Jobs was only partially right. You shouldn’t say yes to everything. But you also shouldn’t ignore what your customers say. The key is in how you listen – and what you do after you understand what your customers are saying.

Part of the answer lies in asking good questions. The quality of answers to your questions depend on the quality of your questions. Ask stupid questions and you’ll get stupid answers. Ask broad questions and you’ll get broad answers.

Moreover, how well you listen is measured not merely by your ability to hear WHAT the customer is suggesting – but also by your ability to understand your customer’s point of view. If enough customers tell you that there’s something wrong with your product, then there probably is something wrong. That doesn’t mean you should change the product at the whim of your customers – but it does mean that you should understand WHY your customers are having trouble with your product and deal with the underlying issues causing problems for customers.

More often than not, you’ll end up saying no to dozens, hundreds, and often thousands of suggestions from your customers. If you don’t – you’ll go out of business.

But how can you say “no” to a customer without discouraging them?

(more…)

Small business and startup issues: choosing the wrong software

Tuesday, November 30th, 2010

More than ever, small businesses and startups must execute and bring their software-based products or services to market quickly. As Groupon has demonstrated, there is often (but not always) a huge first-to-market advantage.

One risk of moving fast involves selecting software technologies that allow you to bring your products/services to market quickly, but that ultimately may not easily scale to accomodate increasing traffic.

Of course, you always should strive to pick the best technologies. But what if you make a mistake? What should you do if the software technology you pick doesn’t work for you later on?

We struggled with this issue at crowdSPRING in 2009 and completely refactored 100% of our code by the end of 2009, moving from PHP to Python. It was not a fun process.

I hope you never have to go through anything remotely similar. But if you find yourself in a situation similar to ours – here are five suggestions for what you should do when you find that your existing technology just isn’t good enough.

Do you have other suggestions, based on your experience?

Building Great Software: Less is More

Tuesday, November 23rd, 2010

My experience with crowdSPRING over the past several years has proven to me that with few exceptions, startups and established companies should strive to keep their software features simple. Simple features allow you to release software more often and to iterate and leverage feedback from users.

Time and time again, we’ve made the mistake of over-thinking a feature only to learn that we didn’t do a good job planning and took far too long to release that feature. This is a common problem for young startups. In fact, many startups fail to launch a product because they get bogged down with software development and either run out of money, or are left behind by their competitors.

Over the past year, we’ve done a better job – simplifying our scope and iterating more often. It’s clear to me that what we’re doing now – simple, focused features followed by iteration – is the best way for startups to operate.

In the video, I discuss five reasons why I believe companies should strive to simplify software features. Briefly, those reasons are:

1. it is much easier to focus on simple releases
2. it is much easier to launch a simple product
3. real feedback from users is critical to software development
4. shorter software development cycles are more fun and create more energy
5. better overall product

Please watch the video for a more detailed discussion of the five reasons – and let me know what you think.

Do you agree that startups should simplify features and iterate more often?

Product or Service Features Are Rarely A Competitive Advantage

Wednesday, October 20th, 2010

Many entrepreneurs and small business owners believe that their new product or service will beat the competition with great new features.

Product and service features are rarely a competitive advantage. There are many benefits to “less software”. I discuss why in the following short 3 minute video.

What do you think?