Self assessment should give you enough to be convinced of your own idea. If not, its not worth pursuing it. Now, the next challenge is to write the idea in an explainatory way. Start with writing an abstract for it.
Abstract
One page is all you have, Write your idea in concidse way. Use short sentences. No Jargons. No unnecessary technical details. What is problem? What is the solution? Pros and Cons. Thats it.
The abstract is helpful in a way that you can keep it handy for later references. Send it to conferences. But, since it didn’t captured all your thoughts, we need to write a detailed document.
I know we all hate documenting stuff. You would be eager to jump straight into implementing it. The running proof of concept is worth more than the document about it. May be. May be not. We can argue either way. But I would recommend you write it first. And I will tell you why.
Detailing
The detailing part is very boring. You would want raher be implementing it than writing about it. But tell me would even feel like writing about it once you have implemented it. I know some pieces you might want to implement to verify if it works or not. This is subjective area. Do what common sense suggests.
So when you finally prepare yourself for detailing, read your abstract first. The detailing would be on same lines. Start with problem. The variants of the problem. Give examples if possible. Now what your solution is. Write details. Diagrams as much possible, A picture is blah blah thousand words. End with summary and references. Summarize what you achieved. Pros and Cons. References are very helpful. Think of it. Couple of months down you revisit the idea. Won’t all the links be very helpful.
Keep the abstracts and detailed version with you. Whenever you get a chance you can publish them as article or submit to conference. If its patentable, you will keep thanking youself that you wrote it.
