Organizational Structure

An organization is a group of people coordinating towards a common purpose.

An organization depends on:

• Communication
• Coordination
• Operation

An organization optimizes for:

• High productive efficiency and versatility
• High educational efficiency and versatility
• Strong intrinsic motivation
• Strong organizational resilience

Operation involves:

• Research
• Development
• Production
• Documentation

Communication involves:

• Physical Gestures
• Talking
• Texting
• Emailing
• Blogging
• Wiki Content Uploading

Coordination involves:

• Single Person
• Group Consensus
• Group Majority
• Group Weighed Majority
• Group Minimum Vote Pass
• Other methods not even using votes

Individual versatility optimizes an organization; it means, in addition to having deep skills in particular areas, individuals should have at least basic proficiency for a broad set of tasks.

Individual versatility allows:

• Rapid substitution of functional positions
• Rapid changes of productive concentration

Recruiting people involves:

• meeting
• networking
• analysis of existing organizations
• database analysis

Financial distribution may involve financial trustees that receive revenues and donations on behalf of a team or organization. The trustees distribute the funds using a system decided upon by the organization's coordination.

Dismissal of persons should involve certain standards established by the organization's coordination. If the standards are not met, then the dismissal of the person is pending based on a system decided upon by the organization's coordination.

Communication is important for:

• Sharing Technical Information
• Scheduling Coordinated Tasks
• Recruiting/Dismissal/Financial Distribution

Consider a project for which an organization must manufacture hundreds of parts and assemble them into one final assembly. Let's tackle this organizational problem in 2 parts:

• Part creation
• Assembly

For part creation, the founder(s) of the organization needs to establish and document some basic parameters (around what size, how many people to operate, energy consumption, etc) and draw a systems engineering diagram (ex. For a spaceship, hull, navigation electronics, propulsion, communication electronics, etc). The initial work of the founding team (parameters and diagram) are sent to others for peer review. Finally, the founding team assumes responsibility for the hull, and recruits other teams for the other major systems who confirm and read the peer reviews for the initial parameters and diagram.

• Founding team- system 1
• A team- system 2
• B team- system 3
• C team- system 4

These system teams set further specific parameters based on the existing parameters (ex. If weight and energy consumption is X and Y, then propulsion should be archetype Z). And also new diagrams that get even more specific (ex. Oscillator circuit, bearings). The more specific parameters and diagrams are sent by each team for peer review again. And again, each team takes on a more specific system as necessary and recruits more teams to help out. The new teams read over the parameters, diagrams, and peer review.

• Founding team- system 1.1
• A team- system 2.1
• B team- system 3.1
• C team- system 4.1
• D team- system 2.2
• E team- system 2.3
• F team- system 3.1
• G team- system 4.1
• H team- system 4.2
• I team- system 4.3

This cycle of specific parameters, diagram, peer review, and recruiting keeps occurring until the all the teams are able to complete their system within the alloted timeframe.

Time passes, the progress for each team documented throughout the process, and now we are almost finished with the creation of all the parts. The organization must somehow prepare for all the sub-assemblies and eventually the final assembly of the project.

The teams begin their assembly by communicating with other teams involved in their next sub-assembly according to the sys diagram potentially, and schedule time and location assembly events. So the parts are assembled at the lowest level, then next, next, next, next, and finally the final assembly occurs, with all teams participating and communicating on active comm channels and such. This organizational method involves these key mechanisms:

• Expansionary Participation
• Per-level Parameter Set-up/Systems Breakdown
• Per-level Peer Review
• Progress Documentation