Showing posts with label Marketable Goods. Show all posts
Showing posts with label Marketable Goods. Show all posts

Wednesday, June 23, 2010

Road Map

A map is nothing more than detailed directions on how to get from point A to point B. If you have ever used MapQuest or a GPS you know that there is a multitude of ways to navigate from one place to another. You can change your preferences to go by certain landmarks or to avoid certain roads. With each new request you get a new map, a new set of directions.
Today I start with an idea and want to get it to market. There are no landmarks I want to see or heavily trafficked areas I want to avoid (not yet anyway). The good thing about directions is you can change them along the way to suit your needs. If you are driving down the road and you see a sign for the World’s Largest Ball of Twine, you can go. After you are done analyzing the string you can double back or just get new directions. This will be my approach.

Idea > Record Idea > Patent Idea > Manufacture Widget > Market Widget > Sell Widget

When I was a child my parents had bought some land in Kentucky. This land was well off the beaten path. We stopped at the local market to ask for directions where I could hear the locals saying things like “turn right at the big oak tree” or “it’s about 10 miles as the crow flies”. I am sure these were great directions if you grew up in this community (or if you were a crow), but they were not so good if you did not.
My point! I know nothing about patent law, patents, intellectual property, marketing an idea, manufacturing, getting something to market, etc. Not yet anyway. Your input will be welcomed.
Thanks!

Wednesday, June 16, 2010

Engineer Process

I am an engineer so I need to make the chaos work in my world. I know what I have (an idea) and I know where I want to go (to market). So I am going to use an engineer’s solution process to make this work
Given:
Find:
Assumptions:
References:
Solution:
The Given here is my idea, or any idea. The Find is Marketable Goods, with the Solution being the path or my Road Map.
Assumptions are used by the engineer to simplify a problem. If I was calculating the weight of a 2000 linear feet wall, I could look at a one foot slice of that wall and then multiply it out at the end. This would be an assumption that the wall is similar throughout the 2000 feet. A common assumption that I make every day is that is reinforced concrete weighs 155 pounds per cubic foot the actual weight could be a little less or a little more, but when doing calculations on a building or foundation this assumption suffices. If it was discovered later that the reinforcement steel was going to be much more, the calculation could easily be redone by changing the assumption.
The first assumption that I am going to make for this project is that my idea is a great one and it will sell. Will it? I do not know, only time will tell. I could spend years and lots of money trying to figure this out and never proceed any further. At some point I do have to fill in an answer for this assumption, I will need to know if my idea is marketable, but I can figure that out later.
References for an engineer may be a design standard, test method or building code; for this project it will most likely be patent law, the USPTO and others.
So I plan on breaking the solution (Road Map) into smaller problems each with their own assumptions, and references then reconstruct the whole package back together at the end.