10. You picked an embedded processor that yielded a firmware footprint headroom of 127% for future expandability.
9. Your firmware person often writes innovative features beyond what’s in the spec to harness some of that excess power in your processor.
8. Your product has a custom adaptor for an interchangeable component for which there is no alternative option.
7. You designed your PCB to be modular so you can plug different boards into the main board with nice flex cables. But you only ever sell the main board with the same module plugged in.
6. Your typical end user regularly uses only 7 out of 32 available user interface elements.
5. You invested heavily in a highly original feature that an end user championed. Upon investigation, he was one of 17 who cared about this feature – out of 13,267 end users.
4. It’s hard to write a tutorial that exercises the full feature set, because 40% of your features don’t fit in the top 3-5 use cases.
3. You keep holding the release because someone keeps coming up with a last minute feature idea that really isn’t that hard to implement.
2. Your idea of product success is to solve some of the problems of all of the people out there, rather than solving all of the problems of some of the people out there.
1. It’s been 4 years since you proved the feasibility of your technology, yet your product is still in development. And your product has nothing to do with curing cancer or sending humans to Mars.
Is this you? If so, you may want to read this seminal article on Minimum Viable Product by Eric Ries, followed by this great article on the Minimum Viable Process by Cindy Alvarez. It may help make your product development cycle a little leaner the next time around.