2 points | by julienreszka 1769 days ago
3 comments
You would have to improve all defects.
The worse defects obscure the lesser ones.
Ask not how do you improve, ask how do you not improve.
Find out what "it" does, then change it so that it is:
1. Faster
2. Cheaper
3. Less likely to break
Identify existing solutions or methods, if any.
Determine deficiencies or frustrations.
Address significant ones of these you can tractably address.
Improvements may address inputs, outputs, results, experience (including UI/UX), robustness, scalability, speed, universality, extensibility, (revenue) conversion, risk, specificity, generality, and more.
TL;DR: Find an itch. Scratch it.
You would have to improve all defects.
The worse defects obscure the lesser ones.
Ask not how do you improve, ask how do you not improve.
Find out what "it" does, then change it so that it is:
1. Faster
2. Cheaper
3. Less likely to break
Identify existing solutions or methods, if any.
Determine deficiencies or frustrations.
Address significant ones of these you can tractably address.
Improvements may address inputs, outputs, results, experience (including UI/UX), robustness, scalability, speed, universality, extensibility, (revenue) conversion, risk, specificity, generality, and more.
TL;DR: Find an itch. Scratch it.