BUSINESS: The balance between brainstorming and feasibility

One thing I've encountered recently with my ideas regarding technology is a simple question.

"Is there a need for this?"

Satisfying my own needs is one thing. Satisfying the needs of more people than me is something else. It's easy enough to develop things to satisfy my own needs and desires, but I'm a person that tends to feel "rewarded" when I create something that other people can use as well.

I imagine this is an important business precept as well; a concept that may have brought down more than one company. Smart businesspeople know that if there is no need, or "demand", then the product, or "supply" will never be sold at the desired rate.

Hence, market research is born.

I also think that it's important to have "focused freedom" in coming up with product ideas. A good brainstorming session is one that is as free of bounds and preconceptions as possible. However, simply going off on tangents will get you nowhere. Some focus on the subject at hand is needed to keep things working on the right track. It may even save some time, where a completely free session would wander down roads that simply waste time.

BUSINESS: About business, sales, and production

Just an observation after working at two different companies. It's important for everyone to know what the potential and limitations are for products.

One example of a good business practice is for sales to interact with the developers before a sales presentation. The idea is to gauge how much work it each for each component they want to sell. At this meeting, the developers can say how long it will take to complete something, and/or if it is feasible for the time period and price point proposed. This will avoid problems like over-selling and under-delivering, project timelines being delayed, and general frustration headaches.

It's fine to segregate responsibility to specific people so that they can focus on that area, but if one group needs to speak for another, e.g. sales speaking for developers, the two groups must discuss and agree on what is presented.

Also, make sure to TEST new ideas and processes before implementation. Often when implementing something for the first time in a new environment, adjustments are required. Throwing a new idea or process into an environment without prior testing slows down everything, often causing damage.

BUSINESS: Obligatory first blog

The main idea of this blog is to post ideas that I come up with that I want everyone to read about and possibly implement. In this case, royalties are not important to me; getting these ideas into physical reality is the priority.

The only thing I ask is that people not demand that I remove stuff from my blog once they put its ideas into practice. If you had prior design on an idea and can prove it, then I will happily remove it upon request.

Let's be civil folks, I just want life to be better. Screw intellectual property.