Description
Create a clear solution sketch – what exactly do you do? How does it work?
Not: Why it works. But: What must a person skilled in the art do to carry out the invention?
Important rule for invention descriptions
- “Do not describe why something works, but what needs to be done for it to work.”
- Describe the steps – not the theory behind them
- Target audience: a person skilled in the art (“average person skilled in the art”)
- No pages of equations – only what is necessary
Example
Self-adhesive disposable plaster that continuously measures body temperature and automatically sends a notification to the smartphone when fever is detected.
Before (“why” – too scientific): It works because an integrated thermistor changes its electrical resistance depending on temperature, a microcontroller converts resistance values into temperature values, and a Bluetooth Low Energy module transmits the data wirelessly once a defined threshold is exceeded.
After (“what to do” – exactly right): For reliable operation it needs a skin-friendly adhesive carrier with close skin contact, a calibrated temperature sensor on the skin-facing side of the plaster, a defined threshold setting (e.g. 38.5 °C), an energy-saving radio module for data transmission, and a paired app that receives the notification and records the temperature curve.
Difference: The first explains the physical and electronic mechanism. The second describes what must be implemented constructively and functionally – without theory.
Components and process
- What components does your solution consist of?
- How do they interact? (process, data flow)
- What inputs are needed? What outputs do you get?
Note your solution sketch (input, steps, output).
Conclusion
When you describe your technical solution, focus on the “what”. The “why” – why your invention works exactly this way – is less relevant for this step. What matters is that you get to the point on what a person skilled in the art must do to reproduce your result.