Build Competencies - Revision history

Marcin at 17:58, 7 August 2025

2025-08-07T17:58:50Z

← Older revision		Revision as of 17:58, 7 August 2025
Line 1:		Line 1:
	There are 6 levels of competency, where pay for work-study time depends on competency:		There are numerous levels of competency, where pay for work-study time depends on competency:

	#'''Technical Competency''' - Related to technical skill. Ability to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.		#'''Technical Competency''' - Related to technical skill. Ability to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.
Line 7:		Line 7:
	#'''Sourcing Competency''' - ability to follow BOMs, vBOMs, and other instructions for acquiring materials. Determining admissible parts.		#'''Sourcing Competency''' - ability to follow BOMs, vBOMs, and other instructions for acquiring materials. Determining admissible parts.
	#'''Ergonomic Design Competency''' - ability to design workflows for efficient builds		#'''Ergonomic Design Competency''' - ability to design workflows for efficient builds
			#'''Management Competency''' - ability to run crews efficiently.
	#'''Executive Competency''' - ability to make decisions on enterprise aspects, backing them up with back-of-the-envelope cash flow analysis		#'''Executive Competency''' - ability to make decisions on enterprise aspects, backing them up with back-of-the-envelope cash flow analysis

Marcin at 17:55, 7 August 2025

2025-08-07T17:55:32Z

← Older revision		Revision as of 17:55, 7 August 2025
Line 1:		Line 1:
	There are 4 levels of competency, where pay for ~~any non~~-~~volunteers~~ depends on competency:		There are 6 levels of competency, where pay for work-study time depends on competency:

	#'''Technical Competency''' - ~~ability~~ to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.		#'''Technical Competency''' - Related to technical skill. Ability to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.
	#'''Tactical Competency''' - ~~tested~~ when context switching is applied in the field when transitioning from one task to another, so that good self-management, organization, tool awareness, preparation, cheatsheets, etc come into play in a team scenario.		#'''Tactical Competency''' - Related to context switching. Tested when context switching is applied in the field or in the RLF when transitioning from one task to another, so that good self-management, organization, tool awareness, preparation, cheatsheets, etc come into play in a team scenario.
	#'''Peak vs stable''' - Peak competency is one-off best when everything is perfect. However, the situation is rarely perfect, thus it ~~matgters~~ how one ~~negotiated~~ imperfection. Stable competency is what one can do day in and day out.		#'''Peak vs stable''' - Peak competency is one-off best when everything is perfect. However, the situation is rarely perfect, thus it matters how one negotiates imperfection. Stable competency is what one can do day in and day out.
	#'''Sequencing competency''' - having a good awareness of build order, such that at any given build stage, one can determine the critical next step with precision		#'''Sequencing competency''' - having a good awareness of build order, such that at any given build stage, one can determine the critical next step with precision
			#'''Sourcing Competency''' - ability to follow BOMs, vBOMs, and other instructions for acquiring materials. Determining admissible parts.
			#'''Ergonomic Design Competency''' - ability to design workflows for efficient builds
			#'''Executive Competency''' - ability to make decisions on enterprise aspects, backing them up with back-of-the-envelope cash flow analysis

Marcin at 03:07, 7 August 2025

2025-08-07T03:07:58Z

← Older revision		Revision as of 03:07, 7 August 2025
Line 1:		Line 1:
	There are 3 levels of competency, where pay for any non-volunteers depends on competency:		There are 4 levels of competency, where pay for any non-volunteers depends on competency:

	#'''Technical Competency''' - ability to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.		#'''Technical Competency''' - ability to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.

Marcin at 20:05, 26 February 2024

2024-02-26T20:05:11Z

← Older revision		Revision as of 20:05, 26 February 2024
Line 4:		Line 4:
	#'''Tactical Competency''' - tested when context switching is applied in the field when transitioning from one task to another, so that good self-management, organization, tool awareness, preparation, cheatsheets, etc come into play in a team scenario.		#'''Tactical Competency''' - tested when context switching is applied in the field when transitioning from one task to another, so that good self-management, organization, tool awareness, preparation, cheatsheets, etc come into play in a team scenario.
	#'''Peak vs stable''' - Peak competency is one-off best when everything is perfect. However, the situation is rarely perfect, thus it matgters how one negotiated imperfection. Stable competency is what one can do day in and day out.		#'''Peak vs stable''' - Peak competency is one-off best when everything is perfect. However, the situation is rarely perfect, thus it matgters how one negotiated imperfection. Stable competency is what one can do day in and day out.
			#'''Sequencing competency''' - having a good awareness of build order, such that at any given build stage, one can determine the critical next step with precision

Marcin: Created page with "There are 3 levels of competency, where pay for any non-volunteers depends on competency: #'''Technical Competency''' - ability to execute in a controlled environment of the..."

2024-02-26T20:04:11Z

Created page with "There are 3 levels of competency, where pay for any non-volunteers depends on competency: #'''Technical Competency''' - ability to execute in a controlled environment of the..."

New page

There are 3 levels of competency, where pay for any non-volunteers depends on competency:

#'''Technical Competency''' - ability to execute in a controlled environment of the [[RLF]], doing a task solo or with other dedicated support team members. This emphasizes ''controlled environment'' as the data point in extreme cases.
#'''Tactical Competency''' - tested when context switching is applied in the field when transitioning from one task to another, so that good self-management, organization, tool awareness, preparation, cheatsheets, etc come into play in a team scenario.
#'''Peak vs stable''' - Peak competency is one-off best when everything is perfect. However, the situation is rarely perfect, thus it matgters how one negotiated imperfection. Stable competency is what one can do day in and day out.