3 ms·
This is a bit silly, of course it's good to build things that people need. However, don't fall into the trap of building the solutions that people think suit t
by InclinedPlane 14y ago
This is a bit silly, of course it's good to build things that people need.
However, don't fall into the trap of building the solutions that people think suit their needs. In other words, don't let the public do your design work for you. People are very bad at falling victim to "satisficing", going with the easiest and simplest solution that seems to solve their problem. You should avoid that, and be smart enough to come up with solutions that may not have seemed obvious.
For example, falling victim to satisficing can result in trying to breed better horses when the smart move is the automobile. Or building a smarter email based form parser when the smart move is web based applications.
- orangethirty 14y agoThe horse vs the automobile is a great example of a want. People did not want to deal with horses. They smell, can only carry two or three people, are slow, and require a lot of upkeep. Worst is that they are dangerous. Horses can kill with a bite or kick. No matter how much you tried you could not really improve on a horse. The carriage proved that. How many hundred of years passed during which the carriage did not have any significant technical improvements? This due to the fact that you cannot simply improve a horse. On the other hand, the automobile has been evolving into something that people go broke to buy every day. They do smell, harm the environment, are sometimes slow (they started out to be very slow), require upkeep, and kill many people every year. Yet they still buy it. People want it. Sure, there are other factors at play such as automobile-biased planning to promote the sales of cars. But at the end of the day, the market conditions are the wants that define the want. The problem defines the want, which goes higher up the list than the need. Tell me, do you own a car? If so, which brand?