Organizational Structure - Revision history

YK: /* Organization Advanced */

2012-04-23T01:31:10Z

Organization Advanced

← Older revision		Revision as of 01:31, 23 April 2012
Line 89:		Line 89:
	*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 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'''		'''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 ~~using expansionary autonomy~~.		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 ~~may~~ require mass communication.		*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 reorganization of system categories which requires inter-team communication.

	*System revision may cause system category removal ~~and creation~~, which ~~may require~~ mass ~~inter-team~~ communication ~~regarding the task redistribution~~.		*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.		*System revision may involve additional processes than the work of the assigned team in order to improve organizational resilience.

YK: /* Organization Advanced */

2012-04-23T01:22:27Z

Organization Advanced

← Older revision		Revision as of 01:22, 23 April 2012
Line 91:		Line 91:
	'''System Revision and Task Redistribution'''		'''System Revision and Task Redistribution'''

	~~Each~~ system category is assigned an individual, team or group of teams to handle cases of system revision and ~~the following~~ task redistribution using expansionary autonomy.		During system creation, each system category is assigned an individual, team or group of teams to handle cases of system revision and task redistribution using expansionary autonomy.

	*System revision may cause system categories to change its parameters, which constrain other categories.		*System revision may cause system categories to change its parameters, which constrain other categories and may require mass communication.

	*System revision may cause reorganization of system categories which requires inter-team ~~active and/or passive~~ communication		*System revision may cause reorganization of system categories which requires inter-team communication.

	*System revision may cause system category removal and creation, which may require mass inter-team communication regarding the task redistribution.		*System revision may cause system category removal and creation, which may require mass inter-team communication regarding the task redistribution.

			*System revision may involve additional processes than the work of the assigned team in order to improve organizational resilience.

	'''Documentation: Passive Communication'''		'''Documentation: Passive Communication'''

YK: /* Organization Advanced */

2012-04-23T01:18:42Z

Organization Advanced

← Older revision		Revision as of 01:18, 23 April 2012
Line 91:		Line 91:
	'''System Revision and Task Redistribution'''		'''System Revision and Task Redistribution'''

	Each system category is assigned an individual, team or group of teams to handle cases of system revision and ~~its~~ following task redistribution.		Each system category is assigned an individual, team or group of teams to handle cases of system revision and the following task redistribution using expansionary autonomy.

	*System revision may cause system categories to change its parameters, which constrain other categories.		*System revision may cause system categories to change its parameters, which constrain other categories.

YK: /* Organization Advanced */

2012-04-23T01:17:37Z

Organization Advanced

← Older revision		Revision as of 01:17, 23 April 2012
Line 75:		Line 75:
	'''System Creation and Task Distribution: Expansionary Autonomy'''		'''System Creation and Task Distribution: Expansionary Autonomy'''

	Organizations create systems by sharing the system-creation work among teams.		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.		*System-creation involves the incremental breakdown of broad goals into specific tasks.
Line 88:		Line 88:

	*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 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'''

			Each system category is assigned an individual, team or group of teams to handle cases of system revision and its following task redistribution.

			*System revision may cause system categories to change its parameters, which constrain other categories.

			*System revision may cause reorganization of system categories which requires inter-team active and/or passive communication

			*System revision may cause system category removal and creation, which may require mass inter-team communication regarding the task redistribution.

	'''Documentation: Passive Communication'''		'''Documentation: Passive Communication'''

YK: /* Organization Advanced */

2012-04-23T00:50:20Z

Organization Advanced

← Older revision		Revision as of 00:50, 23 April 2012
Line 82:		Line 82:

	*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.		*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 new teams may do the same, splitting their work with other teams, and so on.

YK at 19:43, 22 April 2012

2012-04-22T19:43:35Z

← Older revision		Revision as of 19:43, 22 April 2012
Line 73:		Line 73:
	=Organization Advanced=		=Organization Advanced=

	'''System Creation: ~~Splitting the Breakdown~~'''		'''System Creation and Task Distribution: Expansionary Autonomy'''

	~~New organizations need an efficient way to~~ create ~~their~~ system ~~within a set time period~~.		Organizations create systems by sharing the system-creation work among teams.

	*System-creation involves the incremental breakdown of broad goals into specific tasks.		*System-creation involves the incremental breakdown of broad goals into specific tasks.
Line 81:		Line 81:
	*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.		*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 ~~split~~ the work in half with another team, or ~~split~~ in as many pieces to as many teams necessary to complete the system-creation within the 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.

	*The new teams may do the same, splitting their work with other teams, and so on.		*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.

	'''Documentation: Passive Communication'''		'''Documentation: Passive Communication'''
Line 89:		Line 91:
	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.		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 ~~provide much-needed constraints for~~ their work		*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 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.		*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.

YK at 18:48, 22 April 2012

2012-04-22T18:48:05Z

← Older revision		Revision as of 18:48, 22 April 2012
Line 25:		Line 25:
	Organizations differentiate themselves using unique names.		Organizations differentiate themselves using unique names.

	*A name could be ~~“Remarian Center for Organizational Research”~~		*A name could be “Open Source Ecology”

	*A name could be ~~“Navigation~~ Team”		*A name could be “Fabrication Team”

	'''Inclusivity'''		'''Inclusivity'''
Line 39:		Line 39:
	'''Tasks'''		'''Tasks'''

	Organizations need their members to ~~work on~~ tasks.		Organizations need their members to figure out their tasks.

	*~~The members must figure out what~~ tasks are necessary.		*What tasks are necessary.

	*~~The members must figure out how~~ tasks are distributed.		*How tasks are distributed.

	*~~The members must figure out how~~ to revise the set of tasks.		*How to revise the set of tasks.

	*~~The members must figure out how~~ to redistribute tasks.		*How to redistribute tasks.

	'''Systems'''		'''Systems'''

YK at 23:27, 21 April 2012

2012-04-21T23:27:15Z

← Older revision		Revision as of 23:27, 21 April 2012
Line 70:		Line 70:

	*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.		*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: Splitting the Breakdown'''

			New organizations need an efficient way to create their system within a set time period.

			*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 split the work in half with another team, or split in as many pieces to as many teams necessary to complete the system-creation within the deadline.

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

			'''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 provide much-needed constraints for 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.

YK: /* Organization Basics */

2012-04-21T22:39:42Z

Organization Basics

← Older revision		Revision as of 22:39, 21 April 2012
Line 63:		Line 63:
	*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.		*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		'''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 need to assign different tasks to different people, and reassign tasks especially after a change in the system.

YK: /* Organization Basics */

2012-04-21T22:38:36Z

Organization Basics

← Older revision		Revision as of 22:38, 21 April 2012
Line 63:		Line 63:
	*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.		*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”~~		'''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 need to assign different tasks to different people, and reassign tasks especially after a change in the system.