How to evaluate an invention idea

1. Identify what you are looking at

Different materials answer different questions. A polished image may communicate a design clearly while saying nothing about whether its mechanism works. Before evaluating a claim, identify the material supporting it.

• Concept: a proposed explanation of how something might work.
• Rendering: an illustration of a possible appearance or arrangement, rather than a photograph of demonstrated hardware.
• Prototype: a model built to investigate particular questions. It may leave major functions untested.
• Patent-related statement: information about an intellectual-property process. Patent-pending status alone does not demonstrate performance, safety or readiness.
• Test evidence: recorded observations under described conditions, with a method and limitations that another reader can examine.

2. Define the problem before judging the solution

Write down who experiences the problem, what they do today and what makes the current approach difficult. Separate an observed difficulty from an assumption about what people want. A useful problem statement describes a situation rather than praising the proposed product.

For a hypothetical Worm Cargo study, the question could concern extra package handling during transfers between vehicles. First map an ordinary transfer process and identify where handling occurs. Do not assume that a connected vehicle chain would improve it. Ask which part of the process the idea is supposed to change, and what new difficulties it might introduce.

3. Turn broad promises into explicit assumptions

List what must be true for the proposal to help. Include assumptions about people, physical constraints, information quality, maintenance and the surrounding environment. Mark each assumption as supported, uncertain or contradicted by the evidence currently available.

Transactional Traffic, considered as a hypothetical coordination concept, raises questions about whether participants understand an offer, whether information arrives in time and what happens when someone declines. A paper scenario or computer model could explore those questions without involving real traffic. A successful simulation would support conclusions about that model and its assumptions; it would not establish road safety or real-world effectiveness.

4. Plan one small, safe investigation

Choose a single uncertain assumption that matters to the larger idea. State the question before choosing a demonstration. A test that looks impressive can still answer the wrong question. Prefer an investigation that would change your understanding even if its result is disappointing.

For Living Nails, a hypothetical paper-layout exercise could compare where proposed components would sit and identify questions about bulk, movement and attachment. It would not demonstrate that powered nail displays are comfortable, durable or safe to wear.

• Question: what specifically are you trying to learn?
• Comparison: what alternative or starting condition will you examine?
• Observation: what will you record, using the same method each time?
• Decision: what result would support, weaken or leave the assumption unresolved?
• Limits: what will this investigation deliberately leave unanswered?

5. Use a baseline and keep an honest record

A baseline describes the starting situation or comparison approach. Without it, a claim such as faster, lighter or simpler has no clear reference. Compare like conditions, record the method and identify anything changed between attempts.

In a hypothetical Worm Cargo paper model, tokens could represent packages. Compare the same routing task under two stated rules and record transfers, unfinished routes and mistakes. Keep unsuccessful attempts as well as successful ones. Report what you counted, how you counted it and any ambiguity. Distinguish an observation from an explanation: a result may be real while your proposed reason for it remains uncertain.

6. Ask about reliability and safety separately

One successful attempt does not establish dependable operation. Ask whether the result repeats, what conditions were covered and what happens when an input is missing or a component behaves differently. Record variation instead of reporting only the best attempt.

Safety needs its own questions, including who could be affected and how a failure would be noticed. Keep early learning activities on paper or in appropriately limited models. Do not use public roads, people, powered wearables or medical use as informal testing environments. Work involving those settings needs relevant expertise and appropriate oversight. A demonstration of one function is not evidence that an entire system is safe.

7. Share the result and the next question

A useful learning note explains the question, assumptions, comparison, method, observations and limitations. Label concept illustrations clearly. Separate what was measured from what is estimated or proposed, and explain what evidence would be needed for a stronger conclusion.

The next step may be another modest investigation, a redesign or a decision to stop pursuing an assumption. Learning that an attractive idea has a difficult constraint is useful progress. Clear records let other learners question the reasoning and suggest better investigations without mistaking a proposal for a proven product.

Keep learning

Browse the free learning library or explore our public programs and research explanations.

Have a correction or an educational question? Contact the Foundation.