Organizational Development

What is this new flurry of organizational diagrams, started in the last blog post? We are planning OSE Proposal 2011, with a goal to deploy the remaining 39 technologies of the Global Village Construction Set in a radically rapid, parallel development fashion involving $2M in funding and 1 year in time. You can download this graph source here (in Dia) to make improvements, as this is work in progress, and Proposal 2011 is meant to be a collaborative process. Yes, you can involve yourself directly in building a new world.

The graph summarizes the organizational tasks required for Factor e Farm to build its infrastructure to handle 12 on-site people and to handle widespread global collaboration – by the first half of 2011. Key tasks in this involve explaining our work to a broad audience, recruiting a wider development team, building an internet platform, building additional physical infrastructure at Factor e Farm, and funding the whole package. We have had a major upsurge of involvement and support, and our goals, while admittedly optimistic, are definitely not impossible.

This package involves further open-sourcing of critical infrastructure technologies up to Full Product Release; living and testing our developments; collaborating globally; and building an initial community of 5 onsite people. We are refactoring civilization at Factor e Farm.

Ragarding the recruiting of on-site people, the farmer, builder, and engineer are critical on-site people who are contributing directly to the demonstration that a minimum 5 person team can attain a high standard of living with a 100% autarkic production of food, fuel, energy, housing, and essential technologies for comfortable living. These 3 people are in addition to a custom fabricator and general resource developer, already part of the Factor e Farm community. See the Economy in a Box presentation, second half – for a further explanation of the roles of the 5 person team. This is intended to be a direct demonstration of a lifestyle where an awake set of individuals may thrive upon 2 hours of daily labor – at a cost of living of around $25 per month and initial capitalization of $30k-$100k (depending on access to land), while attaining unprecedented quality of life free of geopolitical compromise. This is intended to demonstrate a feasibility of replicable lifestyles based on not ‘making a living,’ but rather, ‘pursuing one’s true interests and passions’ on one’s path of evolving to freedom – where the tasks required for meeting the community’s ‘creature comforts’ are attained with minimum effort.

The broader package involves developing an advanced industrial economy in a box that may be replicated inexpensively anywhere around the world, according to Permakent. Subscribe.


  1. Joe

    Have you heard of the hackspace group The Cowtown Computer Congress in Kansas City? They might be a good source to tap for knowledge assets:

    Not as local, but this hackspace in NYC has interesting info on their site:

    1. Marcin

      Of course, and I’ve tried inviting myself a couple of times for a presentation, so far unsuccessfully. They first contacted us about a year ago. Please contact them on our behalf.

  2. Marcin

    From Miquel:

    One detail: those are not exactly burndown graphs, I think. As I understand it, in SCRUM, a burndown graph is not drawn in advance. It is a depiction of actual progress in the developing of backlog features. So you are actually showing how you would like your burndown chart to look reality.

    So maybe change the title and call it just “GVCS organizational development”.

    Also, burndown charts usually depict the development rate of a particular sprint, of which there are many in a release, while you show a lot of things which is not clear whether it is a release (milestone), or everything or what. I would be useful if you complement the “Roadmap graph” with a feature or goal list for each milestone, like I told you before.

    So my suggestion would be:
    – Perhaps this is a “GVCS Organization/infrastructure” first release.
    – You can divide it into milestones (better name than sprints, I think).
    – Each milestone should be, like each sprint in SCRUM’s language, somewhat in a “releaseable state”. That means that it should be coherent in itself, make sense. That if the release wouldn’t be developed any further than a given milestone, at least it would somewhat work in that state.
    – In the document or next article on the subject, first write the (bullet) list with the milestones and their explanation, and then as a closure the Roadmap graph.

    What do you think?

    PS: Also, for important general updates and roadmap posts like this, you could send a draft so that we can review it and improve, so that the general quality may improve. It’s just a suggestion, not to say that your articles are any bad 🙂

  3. […] with Proposal 2011 for the rapid deployment of the remaining 39 GVCS technologies in a rapid, parallel fashion by […]

  4. Steady Growth | Open Source Ecology

    […] The plan is to use True Fans donations to bootstrap the revolution – but that has its limits. Getting the word out is slow, and while there are hints of meteoric rise in our True Fans numbers, we are at 132 at present. Miracles do happen, though, and our crystal ball tells us to build real productive capacity in tandem – so the updated plan of action – to be started this building season – is a new 3000 square foot workshop to accomodate 4 full-time fabricators. It takes 2 weeks to produce a CEB or tractor – but we believe that if we complete our open source  CNC torch table and other tooling optimization – we can get down to one week in our new flexible fabrication facility. We can earn $5k per device produced – so with 4 people, that would be $80k/month bootstrap earnings to pump into the rapid deployment of the complete Global Village Construction Set. […]