Organizational Structure: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
An organization is a group of people coordinating towards a common purpose.
=Organization Basics=


An organization depends on:
'''Definition'''


*Communication
An organization is a group of people working collectively towards a common goal.
*Coordination
*Operation


An organization optimizes for:
*Society is an organization.


*High productive efficiency and versatility
*Community is an organization.
*High educational efficiency and versatility
*Strong intrinsic motivation
*Strong organizational resilience


Operation involves:
*Family is an organization.


*Research
'''Optimization'''
*Development
*Production
*Documentation


Communication involves:
Great organizations bring out the best that their groups can achieve.


*Physical Gestures
*The best productive and educational efficiency and versatility.
*Talking
*Texting
*Emailing
*Blogging
*Wiki Content Uploading


Coordination involves:
*The best intrinsic motivation.


*Single Person
*The best organizational resilience.
*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.
'''Identification'''


Individual versatility allows:
Organizations differentiate themselves using unique names.


*Rapid substitution of functional positions
*A name could be “Open Source Ecology”
*Rapid changes of productive concentration


Recruiting people involves:
*A name could be “Fabrication Team”
*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.
'''Inclusivity'''


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.
Organizations are inclusive.


Communication is important for:
*People can be a part of many organizations at the same time.


*Sharing Technical Information
*Organizations can be a part of many organizations at the same time.
*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:
'''Tasks'''


*Part creation
Organizations need their members to figure out their tasks.
*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.
*What tasks are necessary.


*Founding team- system 1
*How tasks are distributed.
*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.
*How to revise the set of tasks.


*Founding team- system 1.1
*How to redistribute tasks.
*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.
'''Systems'''


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.
Organizations use systems to organize their tasks.


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.
*A system is a network of inter-connected things.
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:
*A system can break down something broad, such as firefighting, into more specific things, such as driving to the location and spraying water on the fire.
*Expansionary Participation
 
*Per-level Parameter Set-up/Systems Breakdown
*A system can group specific things, such as lifting a cup of water and pouring water into the mouth, into something more broad, such as water-drinking.
*Per-level Peer Review
 
*Progress Documentation
*A system needs to break down an organization's goals enough so that the members know exactly what tasks are required.
 
*A system needs to group an organization's tasks into unique categories so that the members can easily understand and talk about the system from different scales and perspectives.
 
'''Task Distribution and System Revision'''
 
Organizations need to assign different tasks to different people, and reassign tasks especially after a change in the system.
 
*Organizations include their methods for task distribution, redistribution, and system revision within their system.
 
*Organizations can use their system's method of system revision to revise their method of system revision, as well as everything else in the system.
 
=Organization Advanced=
 
'''System Creation and Task Distribution: Expansionary Autonomy'''
 
Organizations create systems and distribute tasks by sharing the system-creation and work tasks among teams.
 
*System-creation involves the incremental breakdown of broad goals into specific tasks.
 
*A team can only break down a goal so many times before the next incremental step becomes too much for them to handle alone for a given deadline.
 
*At that point, the team may share the work half-half with another team, or share in as many pieces to as many teams necessary to complete the system-creation within the deadline.
 
*Sharing the work with other teams involves active and/or passive communication about the system's needs.
 
*The new teams may do the same, splitting their work with other teams, and so on.
 
*The end result is a branching tree-like growth of the system, handled by many teams who are all working at the tip of a system branch.
 
'''System Revision and Task Redistribution: Categorical Assignment'''
 
During system creation, each system category is assigned an individual, team or group of teams to handle cases of system revision and task redistribution.
 
*System revision may cause system categories to change its parameters, which constrain other categories and require mass communication.
 
*System revision may cause reorganization of system categories which requires inter-team communication.
 
*System revision may cause system category removal, which requires mass communication.
 
*System revision may cause system category creation, which requires expansionary autonomy.
 
*System revision may involve additional processes than the work of the assigned team in order to improve organizational resilience.
 
'''Documentation: Passive Communication'''
 
Members of an organization need to publicly document their progress in detail so that people can inform themselves about the state of the system without active communication.
 
*People in the organization can more easily inform themselves about particular system parameters that constrain their work
 
*People out of the organization can more easily provide peer review
 
*People in and out of the organization can more easily learn about particular processes of the system for educational benefit.
 
'''Documentation: Active Communication'''
 
Members of an organization need to document their communication pathways in detail so that people can contact others about the state of the system directly.
 
*People in the organization can more easily coordinate system parameters that constrain multiple teams.
 
*People out of the organization can more easily bring their insights to the organization’s teams.
 
*People in and out of the organization can more easily participate in the organization and other organizations.

Latest revision as of 01:31, 23 April 2012

Organization Basics

Definition

An organization is a group of people working collectively towards a common goal.

  • Society is an organization.
  • Community is an organization.
  • Family is an organization.

Optimization

Great organizations bring out the best that their groups can achieve.

  • The best productive and educational efficiency and versatility.
  • The best intrinsic motivation.
  • The best organizational resilience.

Identification

Organizations differentiate themselves using unique names.

  • A name could be “Open Source Ecology”
  • A name could be “Fabrication Team”

Inclusivity

Organizations are inclusive.

  • People can be a part of many organizations at the same time.
  • Organizations can be a part of many organizations at the same time.

Tasks

Organizations need their members to figure out their tasks.

  • What tasks are necessary.
  • How tasks are distributed.
  • How to revise the set of tasks.
  • How to redistribute tasks.

Systems

Organizations use systems to organize their tasks.

  • A system is a network of inter-connected things.
  • A system can break down something broad, such as firefighting, into more specific things, such as driving to the location and spraying water on the fire.
  • A system can group specific things, such as lifting a cup of water and pouring water into the mouth, into something more broad, such as water-drinking.
  • A system needs to break down an organization's goals enough so that the members know exactly what tasks are required.
  • A system needs to group an organization's tasks into unique categories so that the members can easily understand and talk about the system from different scales and perspectives.

Task Distribution and System Revision

Organizations need to assign different tasks to different people, and reassign tasks especially after a change in the system.

  • Organizations include their methods for task distribution, redistribution, and system revision within their system.
  • Organizations can use their system's method of system revision to revise their method of system revision, as well as everything else in the system.

Organization Advanced

System Creation and Task Distribution: Expansionary Autonomy

Organizations create systems and distribute tasks by sharing the system-creation and work tasks among teams.

  • System-creation involves the incremental breakdown of broad goals into specific tasks.
  • A team can only break down a goal so many times before the next incremental step becomes too much for them to handle alone for a given deadline.
  • At that point, the team may share the work half-half with another team, or share in as many pieces to as many teams necessary to complete the system-creation within the deadline.
  • Sharing the work with other teams involves active and/or passive communication about the system's needs.
  • The new teams may do the same, splitting their work with other teams, and so on.
  • The end result is a branching tree-like growth of the system, handled by many teams who are all working at the tip of a system branch.

System Revision and Task Redistribution: Categorical Assignment

During system creation, each system category is assigned an individual, team or group of teams to handle cases of system revision and task redistribution.

  • System revision may cause system categories to change its parameters, which constrain other categories and require mass communication.
  • System revision may cause reorganization of system categories which requires inter-team communication.
  • System revision may cause system category removal, which requires mass communication.
  • System revision may cause system category creation, which requires expansionary autonomy.
  • System revision may involve additional processes than the work of the assigned team in order to improve organizational resilience.

Documentation: Passive Communication

Members of an organization need to publicly document their progress in detail so that people can inform themselves about the state of the system without active communication.

  • People in the organization can more easily inform themselves about particular system parameters that constrain their work
  • People out of the organization can more easily provide peer review
  • People in and out of the organization can more easily learn about particular processes of the system for educational benefit.

Documentation: Active Communication

Members of an organization need to document their communication pathways in detail so that people can contact others about the state of the system directly.

  • People in the organization can more easily coordinate system parameters that constrain multiple teams.
  • People out of the organization can more easily bring their insights to the organization’s teams.
  • People in and out of the organization can more easily participate in the organization and other organizations.
Retrieved from "https://wiki.opensourceecology.org/index.php?title=Organizational_Structure&oldid=60217"