As I wrote before, I wanted to start sharing application details with you folks and others for usability purposes, and just maintaining momentum in general, but if you do that without protecting your IPR first, you basically have no IPR anymore. So I needed to file a patent so I can then speak freely about the application we’re doing which will utilize the patent.
So I learned how to file a Preliminary Patent Application by reading
Patent It Yourself. And that text says that even for a preliminary patent app, I must “describe your invention in complete enough detail that a "person having ordinary skill in the art" could build (practice) the invention (as defined by the claims in the utility patent which you will file later based on the provisional) from your application.” So for software, that means you either give them source code, which becomes a matter of public record if the patent is issued, or you give them a flowchart and other related docs. So as I brought my Inventor’s Notebook up to snuff (and fwiw other would be inventors, if you haven’t read how to do this, you are probably not creating a proper legal record of your invention) , I realized that because our app is very data driven, it’s most likely I will probably also need to provide our data model to allow a "person having ordinary skill in the art" to be able to build the app.
So I started doing Entity Relationship Diagrams of the data model in support of the patentable claims. But you can’t really just do the parts affecting the patent and do the model right, you have to consider all of the account holder databases and billing and other periphery crap, and also the future application data sharing,etc. And then I may as well normalize the tables while I’m there, right to make sure this is all implementable, right? -None of which I’ve done before.
So, 3 weeks later, as I recurse deeper and deeper, I realized that I could have paid a Data Architect to knock this out in about 2 days, and hired a patent attorney for 2-3 hrs to set me on the right path. –And if I had planned ahead, I would have realized I needed to have most of the design done even to file a PPA and never swallowed the fly in the first place.
I wouldn’t work this way if someone was paying me, why am I working this way on my own, when my time is even more valuable?
New Plan: Even Teams of 1 Need a Project Plan.
Make a realistic plan/schedule for this iteration, which involves farming out some critical path tasks to keep the schedule predictable (More on that in another post). Keep a scrum chart on the wall to stay on task and group logical tasks for a cycle, and put on the old Program Mgr hat (now called a “Scrum Master” for those at home who want to search/replace in their resume…) to realistically revise and reassign. And unfortunately, I also just need to take the Cupertino-approach and STFU until the PPA is filed as much as I want to loop you all in.
Now to arm that mouse with some Post-It Notes and posterboard...