Getting a project off the ground

You have an idea? You think it's a good idea? That's great! How do you go about putting it into practice? This is a really crucial step, and in this  post we'll be discussing how to do that in an open way. What I mean is that you establish a project that others can be join, advise on, or be informed about as it progresses.

I've previously blogged about an open science workflow, and this is the first stage. As I mentioned before, when there is the potential for collaborating with others it's key to be absolutely clear which stage you are at. So

Step 1: Identify that you have a new problem to solve

This means taking some time to check that it really is novel, that no-one's solved it before and that no-one is close to solving it (the latter is not so easy, unless they are also being open about their work).

Step 2: Write down what the problem is

This serves two purposes. Firstly, it makes it clear in your mind exactly what it is you want to tackle. I would recommend using a SMART approach, i.e. make the statement of the problem: specific, measurable, achievable, realistic and time-scaled. This will lead to measures of success for later, allowing you to better monitor progress. Secondly, the statement can be shared with others and will make it much clearer to them what the goal is. This means that all those involved in the project are pulling in the same direction.

Step 3: Consult stakeholders

Are there people who will be affected by the progress or outcome of the project? Get their input at this early stage. That will make it much more fit for purpose. In my experience, others can frequently make key contributions that turn a mediocre idea into a great one. This stage can also involve contacting funding bodies, which might mean you have to define a few of your methods as well (there's an upcoming post about that stage).

My experience is that most of these stages happen, but not necessarily in the correct order and with the optimum effect on the project. Planning is usually rushed and the proposed outcome defined somewhere near the end. Interested parties want to change the direction of the project when it is half-way through, which can lead to tension and be costly.

This advice has a lot to do with communication. Ask yourself, can you successfully communicate your project? Have you done so?

This advice isn't rocket science, and my hope in spelling it out is that it can be used to improve project visibility and get lots of people excited about you and your great new idea.