Collaborative Design

From Open Source Ecology
Jump to: navigation, search

Introduction

What is true collaborative Design?

True collaborative design produces professional grade results in that it carries out a formal development methodology of product (of any kind) based on industry standards, using a completely transparent and open process. I allows anyone to join regardless of skill, as there are many levels of involvement, it features Economic Time Binding, and it works toward Economic Freedom. The natural outcome is thus solving Pressing World Issues.

Value Proposition

This is related to the Extreme Enterprise Hackathon, which is OSE's large-scale manifestation of collaborative design. Thousands of people contribute meaningfully. But the value has to be significant and MTP, BHAG - at the same time very simple: collaborative creation of genius. It must inspire, it must produce tangible results. This can and indeed should be transfered as general practice to white collar workers, as earth transitions to Homo Sapiens Collaboratus. Some of the things of high value are:

  1. Mindset of scarcity vs abundance, in how this affects business and planning decisions.
  2. How to expand the time frame of one's enterprise thinking, without going out of business before that.
  3. Where collaboration already exists, and where is it sorely missing. Opportunities from this insight.
  4. Learn the basics of effective communication - via value addition through Distiller Video. Thing of crude oil gushing out of the ground on one side, and perfume + lady on the other.
  5. How to convert incentive challenges such as HeroX to collaborative
  6. Practical, open source tools for design, part libraries, and repositories that allow anybody to learn to design like a pro within hours.
  7. Widely accessible tools for organizing contributions of thousands of collaborators. Critical elements of the toolset, such as logs, development templates, taxonomies, design guides, part libraries.
  8. Collaborative video protocols that get professional results
  9. Mixing real and virtual with gaming, but not design of trinkets, but of real-world design that shall be built.
  10. Basics of collaborative literacy: the obvious principle of collaborative development. The critical question: how to address collaborative waste.
  11. The psychology of collaboration: privacy, vulnerability, self-esteem, growth mindset, and psychopathy.

Collaborative Design Guide

edit

OSE Case

OSE involves all collaborators in a formal process marked by:

  1. Documention for Time Binding and Economic Time Binding
  2. Development Templates - breaking down the entire product development process and enterprise development process into its parts.
  3. Large-scale collaborative design via appropriate Module Based Design, Collaboration Architecture, under principles of transparency embodied in Collaborative Literacy
  4. Essentially, using transparent tools (open source software/hardware), a transparent process (wiki + work logs + Development Templates, towards Distributive Enterprise and Distributed Market Substitution towards solving Pressing World Issues.

Principles

  1. There is a framework for development with various principles that can be operationalized.
  2. All tools, processes, and outcomes are open, open source, collaborative, libre.
  3. Design follows specifications, the OSE Specifications
  4. All product development is useful to Distributive Enterprise
  5. Natural outcome intent is Distributed Market Substitution
  6. Natural sociological outcome is Economic Freedom and the creation of democratic society
  7. Natural outcome is solving Pressing World Issues as a byproduct of natural resource stewardship. This is effectively Regenerative Development

Operation

  1. For a large collaborative process, complete CAD, BOM, Icon, Video, Instructional is required in digital form. Enterprise is a derived quantity.
  2. What does reconciliation mean below? It means that 'it agrees with' or 'is another way to represent' or 'can be derived from'.
  3. Dev Team, Collaborators support CAD-BOM-Icon-Instructionals-Vidoes-Enterprise reconciliation.
    1. CAD gets build procedures, and animations.Both FreeCAD and SweetHome3D output can be rendered as walk-through videos in SweetHome3D.
    2. Videos translate CAD into reality - we can composite reality and CAD at all phases
    3. CAD translates to build procedures, Videos reconcile with build procedures
    4. BOM reconciles CAD
    5. CAD/BOM/Icon are fully reconciled.
    6. Video derives build time, assuming video is comprehensive and frame rate is known.
    7. BOM and Video derive cost - because cost is materials cost + time it takes to build.
    8. Instructionals can be created from Videos - pending insight on BOM/CAD.
    9. Every single tool and part and supply should be included in CAD.
    10. Layers of CAD (fasteners, structure, utilities, etc) inform build diagrams and procedures.
  4. Free Agents
    1. Unskilled people can take raw footage and convert it to Video Gallery. Base level of edit is cutting out dead space in videos.
    2. Skilled free agents can take BOM/CAD, and create animations for procedures or promotional videos
    3. Skilled agents can take instructional text and turn it into animated text for compositing - aka Kinetic Typography.
    4. Sound people can create a gallery of sweetener (sounds to enhance videos) - OSE Sweetener Library
    5. Totally integrated development reconciles CAD-BOM-Icon-Instructional-Videos-Enterprise-Explanatory Diagrams.
    6. Free agents create Process Icons - for publishing sections, diagrams, wiki sections etc.
  5. Style guide - fonts, colors, icons for book. This would be a publishing template.
  6. Work Log, Product Links, Time Log, Wiki, Docs, FreeCAD, Kdenlive, Inkscape, Blender, KiCad, OBS Studio are main tools used.

Links