Organizational Structure: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
=Organization=
=Organization Basics=
 
'''Definition'''


An organization is a group of people coordinating towards a common purpose.
An organization is a group of people coordinating towards a common purpose.
Line 8: Line 10:


*Family is an organization.
*Family is an organization.
'''Inclusivity'''


Organizations are inclusive.
Organizations are inclusive.
Line 15: Line 19:
*Organizations can be a part of many organizations at the same time.
*Organizations can be a part of many organizations at the same time.


Organizations involve responsibilities that their members must assume.
'''Optimization'''
 
*Recruiting more members is a responsibility.
 
*Making things and providing services is a responsibility.
 
*Communicating with others in and out of the organization is a responsibility.
 
*Safeguarding physical and digital assets is a responsibility.
 
*Assuming and dismissing others to and from responsibility is a responsibility.


Great organizations bring out the best that their groups can achieve.
Great organizations bring out the best that their groups can achieve.
Line 34: Line 28:


*The best organizational resilience.
*The best organizational resilience.
Organizational responsibilities are identified through systems engineering.
*Systems that start broad and few and end deep and numerous.
*Systems that require members to assume system-expanding responsibilities.
Organizational responsibilities can be assumed in various ways.
*Assumed by an individual
*Assumed by a group
*Assumed by many Groups
=Expansionary Participation=
“Expansionary participation” is a system-creation process that provides significant efficiency, autonomy, and scalability.
*The founding team of the organization produces a basic systems engineering diagram going up a level in depth from the mission to the first set of specific systems.
*The founding team assumes responsibility for one or more of those specific systems and recruits more teams to assume the remainder (of the specific systems).
*The founding team and the newly recruited teams all produce another systems engineering diagram that goes up a level from each team's specific system to a second set of more specific systems.
*More teams are recruited and more systems engineering diagrams are produced until each team's system becomes specific enough to work on within the schedule without further task relegation to new teams.
Expansionary participation causes the organization to structure itself according to the systems engineering diagrams.
*Every step of recruiting and systems engineering involves passing on recruiting responsibilities to all teams within the organization.
*Every step of recruiting and systems engineering may involve peer review for the new teams to understand and criticize the current-level systems diagram.
*Every step of recruiting and systems engineering may involve more and more specific parameter-setting for the new teams to understand the design constraints and goals they are developing with.
Expansionary participation may face system revision during or after peer review and further system creation.
*Whoever notes the need for system revision must first communicate the issue to all teams working on systems directly connected to the problematic system.
*If the directly connected teams agree upon system revision through a majority vote process or otherwise, then the teams must communicate to all members of the organization plus all members on the organization's mailing list and optionally beyond for further insight.
*If the system revision still appears justified to the connected teams after an established waiting period, then the system is revised to a new version as proposed and agreed upon by the connected teams, then sent for peer review as normally.
Expansionary participation may face responsibility substitution at any time.
*The members of the organization (at a large-scale or small team-scale) decide on dismissing the particular person(s) from their responsibilities associated with the organization.
*The affected person(s) may communicate to an organization on a larger scale, in which the first organization exists, in order to press the issue.
*The origin-scale organization assumes the responsibility of recruiting person(s) to substitute and assume the responsibilities, though the recruiting responsibility may be passed on if that is deemed better.
Expansionary participation emphasizes that the most qualified people to solve a problem are the ones that know about and have worked on it the most, without harbouring conflicts of interest. That said, the introduction of the problem and supposed solution to active peer review serves as a safeguard that is especially useful for critical issues. Similarly, all responsibilities can be supported and dismissed by the collective decision of the group at any scale; majority vote is not always the best, but the last method to be used. Teams must upload progress documentation for their systems in order to facilitate passive peer review and passive inter-team communication.

Revision as of 20:50, 21 April 2012

Organization Basics

Definition

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

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

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.

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.
Retrieved from "https://wiki.opensourceecology.org/index.php?title=Organizational_Structure&oldid=60049"