Organizational Structure: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Organization=
=Organization Basics=


An organization is a group of people coordinating towards a common purpose.
'''Definition'''
 
An organization is a group of people working collectively towards a common goal.


*Society is an organization.
*Society is an organization.
Line 8: Line 10:


*Family 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.
Organizations are inclusive.
Line 15: Line 37:
*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.
'''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.


*Recruiting more members is a responsibility.
*A system is a network of inter-connected things.


*Making things and providing services is a responsibility.
*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.


*Communicating with others in and out of the organization is a responsibility.
*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.


*Safeguarding physical and digital assets is a responsibility.
*A system needs to break down an organization's goals enough so that the members know exactly what tasks are required.


*Dismissing others from responsibility is a responsibility.
*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.


Great organizations bring out the best that their groups can achieve.
'''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=


*The best productive and educational efficiency and versatility.
'''System Creation and Task Distribution: Expansionary Autonomy'''


*The best intrinsic motivation.
Organizations create systems and distribute tasks by sharing the system-creation and work tasks among teams.


*The best organizational resilience.
*System-creation involves the incremental breakdown of broad goals into specific tasks.


Organizational responsibilities are identified through systems engineering.
*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.


*Systems that start broad and few and end deep and numerous.
*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.


*Systems that require members to assume system-expanding responsibilities.
*Sharing the work with other teams involves active and/or passive communication about the system's needs.


=Expansionary Participation=
*The new teams may do the same, splitting their work with other teams, and so on.


“Expansionary participation” is a system-creation process that provides significant efficiency, autonomy, and scalability, at the cost of almost completely losing management time.
*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.


*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.
'''System Revision and Task Redistribution: Categorical Assignment'''


*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).
During system creation, each system category is assigned an individual, team or group of teams to handle cases of system revision and task redistribution.


*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.
*System revision may cause system categories to change its parameters, which constrain other categories and require mass communication.


*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.
*System revision may cause reorganization of system categories which requires inter-team communication.


Expansionary participation causes the organization to structure itself according to the systems engineering diagrams.  
*System revision may cause system category removal, which requires mass communication.


*Every step of recruiting and systems engineering involves passing on recruiting responsibilities to all teams within the organization.  
*System revision may cause system category creation, which requires expansionary autonomy.


*Every step of recruiting and systems engineering may involve peer review for the new teams to understand and criticize the current-level systems diagram.
*System revision may involve additional processes than the work of the assigned team in order to improve organizational resilience.


*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.
'''Documentation: Passive Communication'''


Expansionary participation may face system revision during or after peer review and further system creation.
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.


*Whoever notes the need for system revision must first communicate the issue to all teams working on systems directly connected to the problematic system.
*People in the organization can more easily inform themselves about particular system parameters that constrain their work


*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.
*People out of the organization can more easily provide peer review


*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.
*People in and out of the organization can more easily learn about particular processes of the system for educational benefit.


Expansionary participation may face responsibility substitution at any time.
'''Documentation: Active Communication'''


*Whoever notes the need for responsibility substitution must first communicate the issue to the team of the problematic person(s), and more broadly to other teams if deemed necessary.
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.


*If the involved teams agree upon responsibility substitution through a majority vote process or otherwise, the affected person(s) may appeal through an established process that may involve up to all members of the organization and its mailing list and beyond.
*People in the organization can more easily coordinate system parameters that constrain multiple teams.


*If the responsibility substitution still appears justified to the involved teams at this point after an established waiting period, then new person(s) are recruited by the involved teams to assume the responsibilities in place.
*People out of the organization can more easily bring their insights to the organization’s teams.


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. Teams must upload progress documentation for their systems in order to facilitate passive peer review and passive inter-team communication.
*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"