Organizational Structure

Organization

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

• Society is an organization.

• Community is an organization.

• Family is an organization.

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.

Organizations involve responsibilities that their members must assume.

• 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.

• Dismissing others from responsibility is a responsibility.

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.

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.

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.

• 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.

• 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.

• 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.

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.