Only SENSORICA logo is copyright. Content on this document is Creative Commons (BY NC SA)

Kickstart a project

This is a co-creation document

If you contribute to this doc make sure you respect the Content rules

Kickstarting a project is helping a project take off. Before that, a project needs to exist for everyone around. Open this document to learn how to create a project in the system.

Table of contents


Open project

Main characteristics of open projects

Methodology for starting open projects

Add other types of projects


SENSORICA is more like an open source community. It is a doacracy. Creating a project on SENSORICA’s platform doesn’t necessarily mean that it will magically take off. You need to nurture it.

The approach to kickstart a project depends on the type of project.

But first, here’s how to create a new project.

Open project

Advocated by: Tibi, add your name

Advantages: compatible with long-tail production, can be swarm-like projects

Main characteristics of open projects

Methodology for starting open projects

A methodology for open projects can be formalized using Workflow recipes in the NRP-VAS system. For R&D projects that have as a goal to bring a product-idea on the market, the methodology is composed of a couple of interrelated recipes, see more on the wiki. A concrete example would be the Conditions part of the methodology, which is a pattern of activities (a recipe, a script) designed to put in place the conditions for the project to develop. See an example of Conditions recipe. See the wiki to learn how to create or modify methodologies, or how to use one for your new project.

In this document we are only concerned with the initial part of a project.

0. Preliminary exploration

This is an informal process, not captured by the example of Conditions recipe.

Explore/test the project idea. Talk about it on social media (G+ or Facebook) or directly with SENSORICA affiliates.

Based on the feedback

1. Create the space

Put in place virtual and physical spaces, communication channels, coordination tools, etc. Create the project on SENSORICA’s platform

2. Mapping interest

From what you know, try to build a map of of individuals and organizations that would be interested in your project-idea. You’ll use it in conjunction with a communication strategy to get more structured feedback.

3. Outreach idea

If the project picks up you put in place more structure and processes.

4. Create structure

Making a general plan, thinking about incentives (value accounting and value equation), put in place governance.

5. Market study

Assess the need for the product and get design requirements.

This can be done through a crowdfunding campaign, or even using a pre-croudfunding service before the actual crowdfunding campaign.

6. Outreach for resources

Signal needs and tell people how they can help.

Create a communication strategy and all the materials necessary for an outreach campaign. This campaign is designed to attract resources to the project. A crowdfunding campaign is one form of outreach that could fit here, but we need to think larger than that, to attract people with skills, spaces, equipment and tools, $ and more.

7. Mapping existing technology

This is a very important step in Open source projects, one that will save you a lot of resources down the line, and a lot of time. The main goal is to integrate as much as possible open source innovation, in order avoid reinventing the wheel, to increase the speed of innovation.

Map open source communities and their offers.

Other processes will follow to insure the development of the project, see more on SENSORICA’s use of Workflow recipes.

See also 

How to realize the market value of your innovation By Steve Bosserman

Guide to Innovation Portfolios By Steve Bosserman

Created in the context of glocal food systems development.

Add other types of projects

Please log that on the wiki as well.

Project documentation

In order to insure speed of innovation in an open environment we need to work stigmergically. Concretely, and generally speaking you need to leave traces of your work and instructions for others to know how to build on it.

All projects have a main doc, which links to all the documentation created for it. Structure it well. The main function of this doc is orientation.

All projects have a main website page, which should be built as the main entry point for the project.

R&D projects have working docs, for all the major components of the project. Here’s a Working doc TEMPLATE that you can copy and use.